How do I use Scrivener 3 with two authors

[kewms]

Having already the capability to base its synchronization on text files only, as opposed to the project's RTF-base, Scrivener can avoid the RTF issues explained by Devinganger's 1st issue. And since Scrivener in this way is already capable of synchronizing only the contents of the project without taking the files for the application's internal operations and state into account, the sync-issues as explained in the 2nd issue can be circumvented as well.

This statement is not accurate.

Scrivener does not create or manipulate plain text files unless you explicitly tell it to as part of an export operation. The internal project files containing your work are always RTF.

Moreover, the Import and Merge feature emphatically *does* consider the metadata that defines, for example, the structure of the Binder. That information is part of the "contents" of the project. If you attempt to manipulate the RTF files independent of those structural files, you are almost guaranteed to render the project non-functional.

Katherine

[sorin]

I while I do still hava a license, I think I would no longer use Scrivener until it would use native markdown format. Using markdown would sort the GIT issue and also play well with other tools/platforms.
I may be biased because I need it only for technical writing in a collaborative manner, where multiple people could change it.
PS. I know enough about RTF format to want to run from it at any cost

[kewms]

I while I do still hava a license, I think I would no longer use Scrivener until it would use native markdown format. Using markdown would sort the GIT issue and also play well with other tools/platforms.
I may be biased because I need it only for technical writing in a collaborative manner, where multiple people could change it.
PS. I know enough about RTF format to want to run from it at any cost

We'll miss you, but this is unlikely to happen.

Katherine

[Lethiux]

Is there a modding community? Is this a possibility?

[devinganger]

Is there a modding community? Is this a possibility?

No, and no.

[seefilms]

I could have just said, "Do a Save As, don't edit the project (or at least don't edit anything the other author will touch), then use the import function when they return the copy. Trash the save-as copies, and create another as needed for your collaborator." Does that sound "insane"? If so, the compile process will break your mind and send your soul into the abyss!

Yep, rdale. It would've been easier had you said that. And yes, I still think it is insane.
In 2006, Apple had a slogan that said: "It just works." Now, anyone who used Apple products knew that wasn't totally true. But they certainly held up far better than the competition.

Sure, what you tell us to do so that co-authors can work on a document together isn't difficult to achieve. But the end result isn't very effective. It's also a pain in the a$$. Especially when there is another piece of software out there that can collaborate very effectively. Is it the same as Scrivener? Nope. Will it allow me to collaborate with my writing partner? Yep.
Hmm... which will I choose... Hmmm............

The fact is, the simple answer to "How do I use Scrivener 3 with two authors?" is: You don't. I'm pretty sure Keith would agree with that evaluation.

[devinganger]

The fact is, the simple answer to "How do I use Scrivener 3 with two authors?" is: You don't. I'm pretty sure Keith would agree with that evaluation.

Don't presume to speak for Keith, none of the rest of us do.

Your statement as such is incorrect. There are a a few people who are members of the forums who use Scrivener 3 to work on projects with other authors.

They just don't do so *simultaneously* without understanding the project structure, limitations, benefits, and remediation steps.

[Jack Daniel]

Dev is correct.

My co-writer and I have developed a method using DropBox that works pretty well.

But it's still tricky. We have a master Scriv file in a DB shared folder. To edit/write/revise we copy it inside that folder, and immediately drag the copy to a local folder.

Once revised locally, we text, alerting that the master file will be updated (this keeps the other person from opening it independently), then open the master file, drag the new docs into the master, and move the older docs to an 'Older' folder inside the master.

We also initial and date the new docs in the doc title (Scriv updates the mod date if you only look at the doc funny, which is not helpful at all).

Also, revisions by me are labeled with a red icon, by her with a yellow one.

Then the revising author closes the master file on the shared folder. That saves it, and the mod date changes. Then the other person knows the change is complete, by checking the mod date of the Scriv file.