JP Vossen via plug on 21 Jan 2021 20:13:28 -0800


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Is there a better alternative LATEX?


On 1/17/21 5:21 PM, Charlie Li via plug wrote:
JP Vossen via plug wrote:
Food for thought: `.odt` files (or even `.docx` files) are really just
zip files containing XML and other stuff.  The XML part is *not* as
human readable as any of the wiki markups we've talked about, but you
can puzzle it out, it *is* revision controllable and it produces at
least somewhat useful diffs.  You'd have to build a quick wrapper to
pull the XML out then commit both XML and zip, but...you could.  It's
not ideal, but it's a lot better than "binary files differ."

Flat XMLs can be opened and saved directly from the word processor; no
(re-)packing formalities needed. For the OpenDocument format, the file
extension is .fodt.


On 1/21/21 7:38 PM, Eric Riese via plug wrote:
I was looking at a LATEX based workflow for maintaining my resume. I
ultimately decided against it because it wasn't worth learning LATEX
just for that and there wasn't a good answer to generating a .docx
when necessary.

What I ended up with is that I use LibreOffice. But I save to a .fodt
format. That stands for flat ODT, meaning it's a single XML file, not
zipped. It behaves passably in git. Every save contains many more
changes than just what I intended, but at least it's something.

I also have a Makefile that builds .docx and Hybrid PDFs (that's a PDF
with an embedded ODT copy so it's edittable in LibreOffice at least)
from the .fodt and uploads it to my web server. Feels much better than
clumsily sftp'ing it and then sshing in, moving the files and changing
the permissions every time.

Just like what JP was suggesting, I was actually planning on putting
the zipping and unzipping in the Makefile before I found the .fodt
format.

I never noticed that one before.  Cool.  It's a tad ugly, but then it's XML so that's redundant.  And it's certainly more "plain text."

I used to have my resume in Word, way back when.  At some point I re-did it in plan old hand-crafted HTML, and that's been good enough since [1].  I'm not sure what I'd do now, probably try Asciidoc or some related wiki markup...or fall back to HTML.

[1] https://www.jpsdomain.org/jp/Vossen_Resume.html

Later,
JP
--  -------------------------------------------------------------------
JP Vossen, CISSP | http://www.jpsdomain.org/ | http://bashcookbook.com/
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug