The sad part is that word/LO both have version control, but noone uses it. Instead, it's name.docx; name2.docx; name11_14.docx; name_SM11_15.docx; name_JT_11_18.docx, etc. But it DOES have [shoddy] version control that noone ever uses for some reason.
-
-
-
Don't forget "doc_final.docx", "doc_real_final.docx", doc_real_final_final2.docx", "doc_final_revised_final.docx" ... ;)
-
The only problem is that version control on binary files is a big bag of "no"! So I guess plain text is the way forward if you want to use version control on your documents — another reason latex is a neat choice (or markdown, etc).
-
Agreed. Also, I love being rather independent of the "toolchain" I use (also taking into account the machine and OS I do my stuff on). Text files are just so sexy! Maybe we should start using ASCII art for graphics version control...
-
Although more generally and seriously, it's already possible with things like git annex and git lfs to version control binary files that get edited a lot.
-
Thanks for the hint, it actually happens in my current project that I have huge files that aren't really meant for git (high-resolution voxel data). Integrating them into the git workflow would be really nice, though!
- 1 more reply
New conversation -
-
-
In case you didn't know, it's even possible to check out the underlying Git repository! https://www.overleaf.com/blog/195-new-collaborate-online-and-offline-with-overleaf-and-git-beta …
-
That's how I use it.
End of conversation
New conversation -
-
-
Cloud editing has a lot going for it! I hadn’t connected the dots there, but you’re exactly right. When version control is baked in it becomes NOT another tool that has to be learnt; it’s just there.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.