211–220 of 285 posts
Earlier quoted context omitted.
when this tool has "FakeBold"[0] like Latex has, I'll make the switch. [0]: https://x.com/OrganicGPT/status/1920202649481236745/photo/1
What does that actually mean? The tweet is not very clear. Is it the bold in the header? What's special about it?
Not sure if I would be taunting the trademark lawyers of Quark Software like this, but you do you I guess.
Cool project, but seems dangerous to use the word “Quark” in a publishing context RE: QuarkXPress:
- https://tsdr.uspto.gov/#caseNumber=90886976&caseSearchType=U...
- https://tsdr.uspto.gov/#caseNumber=97009034&caseSearchType=U...
(Why do they have two for the same word?)
https://gitlab.com/DaveJarvis/KeenWrite/-/blob/main/docs/ima...
I developed KeenWrite to help write a sci-fi novel where I can use variables for character names, places, etc. See the tutorials[2] for details.
For anyone still using pandoc and shell scripts, my Typesetting Markdown[3] series describes building a script-based infrastructure for converting Markdown into PDF.
[2]: https://www.youtube.com/watch?v=CFCqe3A5dFg&t=15s
[3]: https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdow...
Earlier quoted context omitted.
Your statement is not correct, LuaLaTeX can output any unicode character you need and also you can use Lua as well for scripting.
Other incorrect statement is that LaTeX cannot generate HTML. There is number of projects for LaTeX to HTML conversion (TeX4ht, Lwarp, LaTeXML), also Pandoc can convert subset of LaTeX to HTML.
Earlier quoted context omitted.
llms are great at handling syntax for you so you can focus on your work I never wrote latex before, but writing a simple PDF / scholarly article from code is pretty easy with current tools if you're a dev
> writing a simple PDF / scholarly article from code is pretty easy with current tools I tripped over a lot of abandonware while looking for a free OSS HTML->PDF solution, recently. What do you recommend?
# justfile ── put in repo root set shell := ["bash", "-cu"] # one shell → predictable env, pipe-fail, etc.
# Build a PDF once pdf: tectonic -X compile src-v0.1/main.tex --outdir target/pdf # or swap for typst
# Clean artefacts clean: rm -rf target
# Live-reload while writing watch: cargo watch -q -x 'just pdf'
then i just split the paper in sections like react components but using tex
main.tex
\documentclass{article}
\input{preamble}
\begin{document} \maketitle
\input{sections/abstract}
\input{sections/introduction}
\input{sections/syntax}
\input{sections/evaluation}
\input{sections/conclusion}
\end{document}
Earlier quoted context omitted.
This is for academic and publication journals. Which is why you see Typst it's strongest competitor in the Comparison Chart.
Every conference has their own required LaTeX style file that must be used. Unless there is an automated way to convert these exactly, I don't see how LaTeX alternatives can be used.
