4 ms·

For pdf deliverables regarding things like a resume, I am wondering if it is just better to create an html document using FE web dev skills, and render it to pd

by platz 10y ago

For pdf deliverables regarding things like a resume, I am wondering if it is just better to create an html document using FE web dev skills, and render it to pdf (having done the latex resume thing recently). i.e. for PDF's (like a resume), What are the advantages of latex over html+css->pdf? (This is assuming I don't care about things like table-of-contents generation or precise chapter-aware commands)

hashhar 10y ago
If you are generating the HTML using data from a JSON schema (like JSON Resume) then HTML is a good enough way since the data is easy to handle. Raw HTML would be a very big pain once you want to generate tailored resumes based on some input criteria. LaTeX and JSON schema based resumes both offer modularization and help with generation of tailored resumes. I don't find any other advantages IMO.
- platz 10y ago
  i am not interested in json or resumes so much . its more html vs latex
mynewtb 10y ago
Nothing I can think of except for some typographic sugar that almost no one (except for other latex users or typography people) would notice. It really is not worth the frustration today.
- taeric 10y ago
  I take issue with calling it a frustration. Especially since trying to get good page layouts with html is frustrating to me. That said, if you need any document, be it a résumé or anything else, and you need it tomorrow, use the tools you know. And don't feel bad about not knowing other tools. Trying to get up to speed on anything that is worthwhile quickly on a new too will almost certainly be frustrating. Even word processors.
seanwilson 10y ago
> For pdf deliverables regarding things like a resume, I am wondering if it is just better to create an html document using FE web dev skills, and render it to pdf (having done the latex resume thing recently). For a resume, I think something like Google Docs is better. You want to have a lot of control over the layout so it fits on a page or two. Latex is good for automated document generation but with resumes it's not common you'll be generating them more than every year or so and you should be tailoring them to each job.

by platz 10y ago

hashhar 10y ago

If you are generating the HTML using data from a JSON schema (like JSON Resume) then HTML is a good enough way since the data is easy to handle. Raw HTML would be a very big pain once you want to generate tailored resumes based on some input criteria. LaTeX and JSON schema based resumes both offer modularization and help with generation of tailored resumes. I don't find any other advantages IMO.

platz 10y ago
i am not interested in json or resumes so much . its more html vs latex

mynewtb 10y ago

Nothing I can think of except for some typographic sugar that almost no one (except for other latex users or typography people) would notice. It really is not worth the frustration today.

taeric 10y ago
I take issue with calling it a frustration. Especially since trying to get good page layouts with html is frustrating to me. That said, if you need any document, be it a résumé or anything else, and you need it tomorrow, use the tools you know. And don't feel bad about not knowing other tools. Trying to get up to speed on anything that is worthwhile quickly on a new too will almost certainly be frustrating. Even word processors.

seanwilson 10y ago

> For pdf deliverables regarding things like a resume, I am wondering if it is just better to create an html document using FE web dev skills, and render it to pdf (having done the latex resume thing recently). For a resume, I think something like Google Docs is better. You want to have a lot of control over the layout so it fits on a page or two. Latex is good for automated document generation but with resumes it's not common you'll be generating them more than every year or so and you should be tailoring them to each job.