Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Most engineers prefer markdown or *TeX. Drafting documents is for office minions.
vigidis210819dNow... Imagine I once had the courage to write an entire 30 page uni project in LibreOffice...
Needless to say, since then, I've only been using Linux for coding and nothing else...
C0D46223719dMarkdown -> export as PDF.
If they can't open a PDF, they probably shouldn't be using a computer in the first place.
Fast-Nop3203219d@SortOfTested Astonishing. The last time I ever saw and used *TeX for real was in the 1990s during my studies.
I've never used it afterwards because the main drawback is that you forget most of it as soon as you don't use it daily, and then the productivity drops to zero.
Let's also be real, most documentation doesn't need the layout quality to be ready for book print, so even the main reason for *TeX isn't there.
Some time ago I used wine to install MS Office in Linux. It was working like a charm. I highly recommend it.
ilPinguino300018dI once wrote a book in LO - 100 pages, somewhat complex layout.
The 2003 style interface is part of the problem, but mostly, it was the sub par performance on anything larger than two pages, or anything with images.
Or anything with diagrams.
So the perfect tool to write Nonfiction with, especially computer books.
I'm writing my current project with LaTeX and organize it with MS One Note and ToDo (because the rest of my business is also MS stuff)
Perfect combination for me. I'm not sure I could do better with Word than with writer, but the other tools from MS sure are superior. I just started the project in LaTeX and I dislike switching tools in the middle of a job.
I'm actually a big supporter of free software, but that whole split up in OOs development team set them back a decade in a race that they were at some point almost up to speed.
Fast-Nop3203218d@raulqf Even with a template, *TeX still sucks because its discoverability is bad. That's one of the pillars of usability and a major advantage of GUIs.
Especially devs tend to dismiss that and attribute the resulting user resentment to stupidity, which is a big point why you don't let devs design UIs.
What also sucks is the edit-compile-view-debug cycle.
I think these are the main reasons why it hasn't really caught on.
Fast-Nop3203218d@raulqf Just took a look at that, and apart from offering new problems through merge conflicts if multiple users are editing the same document, and the complex installation (you wouldn't use their hosted version for anything serious), I don't really see how it would solve the problems with *TeX.
What I'd wish for would be the TeX engine incorporated in browsers because the layout quality in renderers is just ridiculous compared to what TeX could achieve already decades ago.
Chromium in particular still fails to even auto-hyphenate because it's too difficult or something. Too difficult to use what TeX had, and also too difficult to copy what FF is doing.
Tonnoman09095518dSeriously... Anyone with any progressional standards at all should ask for at least a pdf or SOMETHING
Hazarth194118dtry using a .doc instead of .docx, the support for .doc goes deeper and microsoft have their own docx standard.
also, are you writting a completely new document, or are you adding stuff to an existing .docx made with MS Office?
devnulli62018ddude, theres 2 things you need to survive
1) don't release on fridays, ever
and then there's
2) dont use libreoffice, ever
Linux4win2118dThe problem you're mentioning can't really be blamed on LibreOffice. Regular .docx documents use a proprietary, incredibly complex format AFAIK making them difficult to use. Microsoft is more to blame here for not using an open standard.