If they don't use git and you save the manuscript as a binary file, that's very tricky indeed. If you save as plain text things become easier even if they don't you can still version it on git.
-
-
So as with any technology it's a mix of what the user wants and what can be done with the technology. Plain text is undoubtedly the way forward if you want clear and clean git history. A GUI on top of that is what many users want, which is very possible in the case of
@overleaf. -
The reason I don't mention offline GUIs, of which there are a great many and of which some are excellent is because, even though that is how I work, most people (newbies) can't (yet) deal with the overhead of local compilation.
-
Anyway, you are free to DM me (they are open) if anybody wants more coherent and specific advice than can be offered over a bunch of separate tweets.
End of conversation
New conversation -
-
-
I dislike either of those.
-
Yeah, I have deep issues with concurrent edits in real time, but I can tolerate them if I know nobody is working on the same section or even the same table (yes, I put a table in a diff .tex file so I can edit it in peace).
-
Also ofc LaTeX tables make me cry (who's immune?), but at least you can save the contents as a .csv and compile to table.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
