Ciao Mark I'm commenting here as a high-end user of PDF for print, not specifically about TW.
PDF is a de-facto standard in the print industry still. On Web it looks like "a" format. That is not quite right. PDF has vast possibilities on settings (resolution is critical in printing as is the color scheme, to suit the press, which can be tweaked endlessly). Its font handling is rich and allows embedding on the fly. Windows print drivers that do pdf mainly just do a common subset of features. A few can be manually set in the driver. I am TOTALLY UNCLEAR how you'd interact / set those refined functions PDF has without specialist software. There is likely a way on invocation but I'm unclear how. I think Mohammad's wow on Zettlr output via pandoc is its leveraging some of the PDF machine better than TW. But, in theory, you should be able to pass all quality and precision to PDF directly. Pagination in TW is an issue. I don't think its a PDF issue per se. Thoughts TT On Saturday, 4 April 2020 16:45:47 UTC+2, Mark S. wrote: > > > > On Saturday, April 4, 2020 at 2:16:23 AM UTC-7, TiddlyTweeter wrote: >> >> Mohammad >> >> -- *Output/Export* to PDF, Word etc ... Point is academics need to >> publish research & articles. >> They need flexible export because different journals have >> different requirements. >> >> So you need flexible export, or good PDF "virtual printing". >> >> I think that is achievable in TW. >> >> It just needs* better attention to CSS print styling* (though >> pagination remains a more complex problem). >> >> >> >> > If PDF is a requirement for output, then it seems like that is the place > to start, especially since it would be useful for many projects. > But is there any example of citation-quality PDF being built in TW? > > In terms of JS capability, there's a couple projects for producing PDF > using JS. It's unclear whether they can be used stand-alone, or whether > they would depend on someone else's hosted library, or a running node. > > What would need to happen is to parse the text (possibly from markdown, > not wikitext), and then turn it into js commands that get executed on a TW > internal object. That object then gets downloaded or displayed as PDF. > Then there's figuring out where to insert footnotes, etc. > > Doesn't seem trivial, especially considering the small user base. But > maybe there's a simpler way? > > You could use CSS and then print using a PDF extension, assuming that the > extensions will honor page breaks. I suspect this approach would be > fragile. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6ec824c0-8340-4294-a3f1-de983c1b56c3%40googlegroups.com.
