[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30869 [Internal Services/Service - nextcloud]: [Nextcloud] Feedback re: collaborative document editing
#30869: [Nextcloud] Feedback re: collaborative document editing
-------------------------------------------------+-------------------------
Reporter: alsmith | Owner:
| nextcloud-admin@…
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Service - | Version:
nextcloud |
Severity: Normal | Resolution:
Keywords: nextcloud, migration | Actual Points:
Parent ID: #29415 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by micah):
Replying to [comment:9 alsmith]:
> Thanks for your reply!
>
> Replying to [comment:7 micah]:
>
> > Replying to [ticket:30869 alsmith]:
> >
> > > * No ability to tag other accounts in comments that I can see or
find. In my eyes, this is the biggest roadblock. Being able to work
asynchronously on a document, tagging others in spots where their input is
needed, knowing they will receive notifications, has been key to working
across time zones with lots of people against deadlines.
> > >
> > This would be a nice feature. The only way I know that you can
somewhat get this kind of functionality is to agree as a group that
comments are things that must be resolved and that people should be
looking through comments for their names to find ones that they need to
resolve. Once they've resolved them, then the comment can be closed by
clicking the "Resolve" button if it was solved.
>
> I understand that this isn't possible with OnlyOffice -- just
elaborating on this point for the record. Coming to a consensus about how
to resolve and labeled could be possible, although cumbersome. After
writing or documenting rules for resolving comments, I can see the need
for me (or other authors) to notify others every time there's a new
comment -- which is not simple to keep track of in large projects with
many comments and edits. This will be logistically quite difficult (and
time-consuming) for those who are authoring or managing a document.
I will look around for an issue related to this upstream, and if there is
not one, I'll create one so we can track the feature.
> > > * Speed. For me, !OnlyOffice docs take 2-3 minutes to load per file.
Working on one or two small documents, this is doable. For huge projects
with multiple long/large documents, this may become difficult/impossible
to manage.
>
> > That is interesting, I haven't experienced that. I just opened a
document, and it took 5 seconds between clicking on it in nextcloud, and
it being editable in OnlyOffice. I'm really interested in exploring this
delay more to figure out what is causing it to take so long for you. Are
you experiencing this for all document types, or just certain ones... do
you experience it only with larger documents?
>
> Speed is an issue with all documents, all types, all sizes. I'd say 1
out of 5 times it's so slow it times out. I use Tor Browser exclusively
when accessing NextCloud. Maybe that's the issue; I'll test and report
back.
Ok, yeah... when using tor you are going to have very different latencies
in play that will make it hard to evaluate if the issue is OnlyOffice
itself. The server runs out of Seattle, so it should be very fast for you
to connect to it over the "clearnet". I'd be interested to hear your
experiences after you've tried it without Tor Browser.
> > > * To finalize documents for printing or saving to PDF, I need to
download and then edit again in Word because certain features are not
available, the biggest being that the Tor Project’s fonts are not
supported/available.
> > >
> > >
> > Yes, the Onlyoffice functionality is primarily oriented around the
collaborative elements. Finishing/printing documents are maybe not as
refined. Perhaps we can investigate how to get the Tor Project fonts
available, so this could minimize the problems. Which is the font that is
used? I can look at what it would take to incorporate that.
>
> Fair. Finishing features are less important than the collaborative
functions. Font is Source Pro (Serif & Sans Serif versions), more here:
https://styleguide.torproject.org/visuals/#typography.
Ok, I'll see what is involved in adding fonts.
> > > * No ability to do a word/character count that I can find. Critical
for grants, most have word or character count requirements.
> > >
> > It is possible to do this, but I think it could be more 'easy'. The
way you can do this is by clicking the "File" button on the left (Alt+F),
its a little icon that looks like a document and is above the search
spyglass. Then click "Document Info..." and you will get the counts you
are looking for.
> >
> > This isn't ideal, and the OnlyOffice developers are aware of this
enhancement request. The idea would be to put it in the status bar at the
bottom, where it tells you the page number you are on.
>
> Yes -- sorry, I should have been more clear. You can get word and
character counts for the entire document, but I can't select a paragraph
and get the word count or character count of that section, which is what I
use frequently. I've been writing in !OnlyOffice then copy/pasting chunks
of text into Word, getting the word count, editing it, and shifting it
back to !OnlyOffice. There's a higher margin of error with this flow, and
eats into the benefit of collaborative document editing if I am switching
between online and offline versions of the doc. Again, I recognize this
might not be solvable, but then I wonder if OO is the right option.
Thanks for clarifying! There is an issue about this upstream, and they've
said that it is planned, so it should be coming soon. I'm not sure how
soon though. If you wish, you can follow that issue here:
https://github.com/ONLYOFFICE/DesktopEditors/issues/167
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30869#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs