271–280 of 285 posts
I'm very excited to boot up and try this. I may have finally found what I need to replace my rickety pipeline of templates and pandoc conversions.
Maybe look at Quarto? Almost every project I start now begins with `quarto project create`. From there I can pivot the material into HTML, .docx, PDF, .PPTX, Typst, LaTeX, and all of them simultaneously.
This, Typst, etc etc are primarily typesetting systems for papers . I would love alternatives to HTML or whatever, but I tried Typst too and it's very clear that the authors only really care about typesetting for papers and other long form prose. Stuff like forms, invoices, flyers, handouts, leaflets, business cards -- an afterthought, at best. Edit: Actually I was thinking of Sile not Typst, but I think the same app…
> Stuff like forms, invoices, flyers, handouts, leaflets, business cards -- an afterthought, at best. It is because you can typeset beautiful long text algorithmically and all these small forms like invoices and flyers are more graphical design than typesetting: you need to place many small elements precisely, not relative to each other but to the edges of the page / optical centers / etc. It is not very convenient w…
Why isn't it easy to place something relative to the edges of a page via text? In HTML I do `padding: 2cm` and I'm done. I'd say most of design involves placing elements relative to eachother; half the constraints in GUI design tools are matching spacing or aligning to nearby elements.
I'm not saying you can do the whole thing blind, but for the odd thing that does need visual feedback, not having a convenient UI isn't a critical failure. Some of those things are hard to do in a GUI too, and having a good text based layout tool could be easier.
Earlier quoted context omitted.
> Stuff like forms, invoices, flyers, handouts, leaflets, business cards -- an afterthought, at best. It is because you can typeset beautiful long text algorithmically and all these small forms like invoices and flyers are more graphical design than typesetting: you need to place many small elements precisely, not relative to each other but to the edges of the page / optical centers / etc. It is not very convenient w…
I don't agree. Plenty of people write HTML by hand, no WYSIWYG, often with no more than a live preview pane like Typst's. Why isn't it easy to place something relative to the edges of a page via text? In HTML I do `padding: 2cm` and I'm done. I'd say most of design involves placing elements relative to eachother; half the constraints in GUI design tools are matching spacing or aligning to nearby elements. I'm not say…
I don't say it is impossible. But looks like it is hard.
Earlier quoted context omitted.
I gave your splash page a look: no docs, no examples, no screenshots. Your "free trial" is behind a sign-up wall. and I left.
Thanks for the feedback. Yep - we've yet to update the website. It's a waitlist, we're not launched yet. Absolutely fair criticism. It'll be updated in the next few weeks!
My FOSS text editor, KeenWrite[1], takes a similar approach: Markdown -> XHTML -> TeX -> PDF. The software architecture shows how you can have processor chains: 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, m…
For me, the issue is not document conversion and is content de-duplication. Product A and Product B manual will share number of sections. Any spelling or grammar error must be updated in Product A and B manuals. They man share the same additions. So far LaTex has been the only solution to allow binding shared sections into multiple document builds. These are for internal and customer facing information. Only binding…
R, being a Turing-complete language, can do this. If R Markdown can do it then KeenWrite and pandoc+knitr support it. R can also do conditional includes. For Product A and B to share authentication steps, this could look like:
`r#inc( '../common/authentication.Rmd' );`
\input ../common/authentication.tex
Earlier quoted context omitted.
Same. Replacing elements in with DOM in webdev is surprisingly fun with websockets too. Having to know and learn 300 clunky frameworks, 97 different syntaxes it gets old. HTML. CSS. Javascript. Ask the AI to give me a markdown to html converter, good2go
> Ask the AI to give me a markdown to html converter, good2go Why would you do that? There are dozens of libraries which do exactly that. Instead of AI you can ask npm or pip, heck you can even ask CRAN[1]. 1: https://cran.r-project.org/web/packages/markdown/index.html
Earlier quoted context omitted.
> Ask the AI to give me a markdown to html converter, good2go Why would you do that? There are dozens of libraries which do exactly that. Instead of AI you can ask npm or pip, heck you can even ask CRAN[1]. 1: https://cran.r-project.org/web/packages/markdown/index.html
Exactly. It tells me the same things. It'll often give me the require() for javascript on packages I should use.
Also modern JavaScript uses import, require() is very 2015. If the AI is recommending you use require() I would suggest a better one.
Earlier quoted context omitted.
I’d argue that Typst probably beats it on all levels. Have you ever seen a LaTeX document? (The question is rhetorical, of course you have) Just because it was the best thing before doesn’t mean it still is now. I’d say the only thing it still has going for it is momentum.
I looked at the Typst documentation and from what I could tell, it has 3 hard-coded "Modes" for 3 hard-coded kinds of syntax (normal, math, code). I couldn't find any way to add any custom syntax - is there a way to do this? Tex/LaTeX are completely syntactically extensible. For example, a logician might want to use the software with any number of their notations, or a physicist drawing Feynmann diagrams, etc. I thin…
But code syntax can not be changed an no you can't redefine if @ is a letter or not and flip flop that in your code like latex does.
Earlier quoted context omitted.
That assumes that the only issue with LaTeX is its syntax. Other issues I can think of are that LaTeX doesn't generate HTML and that LaTeX is completely Unicode-disabled.
Your statement is not correct, LuaLaTeX can output any unicode character you need and also you can use Lua as well for scripting.
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.