- xiaohanyu parentOne of the main reasons why books cannot update as software is because there is no GitHub or even Git thing for books crafting.
- I just watched a video https://www.youtube.com/watch?v=eIoohUmYpGI which I think summarize your points here, recommend it to you as well.
- The best demo for music programming language demo I can found is: https://www.youtube.com/watch?v=yY1FSsUV-8c&t=374s, The concert programmer.
- https://yamlresume.dev
A open source Node.js lib that allows people to create and version control resumes using YAML.
Support LaTeX/PDF/Markdown outputs in one shot with professional typesetting. Support English/Chinese/Norwegian/French languages out of the box. With clang style, real time error reporting.
To release soon: HTML output.
- 3 points
- 1 point
- One thing that LaTeX still win is CJK support, typst is still very young and lacks professional support for non-latin languages: https://blog.ppresume.com/posts/on-typesetting-engines#concl...
I admit that typst is quite promising and given enough time, its adoption will increase quite a lot.
- Actually I am planning to integrate AI to generate this kind of YAML first and then convert it to PDF.
The idea:
1. apply strict schema validation to YAML so AI won't generate wrong/invalid data 2. write prompt to AI help people generate a sample YAMLResume 3. adopt AI to parse existing PDF or images and convert it to YAMLResume format
- Typst is a pretty good alternative to LaTeX and I agree all pros in your comment, with only one major deal breaker now: its CJK support is not mature enough and not producation-ready yet.
I wrote a post half year ago explained the details for my decision between LaTeX and Typst: https://blog.ppresume.com/posts/on-typesetting-engines#typst
- If you do not insist on org-mode, then maybe you can try to organize your CV in YAML format with a tool called YAMLResume: https://yamlresume.dev, which transforms a resume in YAML to LaTeX and generate PDF.
- 3 points
- I know groff, at least the bible K&R C programming book is published by groff, if I am not wrong.
For me, I think groff/LaTeX/SILE/typst all belongs to same category, i.e, the author write some markup language, then processed by some processors, then get an output. I chose LaTeX and Typst as the classic ones in my post:
- LaTeX is the classic, old school typesetting engine - Typst, clearly more modern, with many advanced design like incremental compilation, wasm and web app, instant preview, better error message.
For others, groff/SILE, to be honest I don't have time to dive into each of these.
----
Do you see any advantages of groff over LaTeX?
- Just for keenwrite, from the screenshot: https://keenwrite.com/images/screenshots/05.png, seems that keenwrite doesn't implement Knuth Plass line breaking algorithm?
- Thanks for pointing this out.
Yes you are right, I am not a linguist so I have little knowledge for "Indo" languages.
Originally I adopted the word of "Germanic languages" then I found Spanish is not a Germanic language hence I then adopted "Indo European" language.
This needs a fix for sure.
- Author here.
I mentioned https://polytype.dev/ in the end of the post, which has pages.js included.
Is not that hard to simulate pagination with JavaScript, the deal breaker for me is still line breaking and also mixed languages typesetting nuances.