Hi, I’ll list the plans for this year.
The preceding situation was the existence of the brazilian website that contained posts regarding PDF resources, about 30 essays, all translated (by other people) to portuguese. You can find those resources in a facebook page:
Now there are the EN, JP and TH domains and the tool I was using to generate those PDF files will be build from scratch.
The workflow was pretty straight forward: take an essay from some webpage, turn it into markdown (which can be posted in here), and then turn it into PDF. Now I want to make the translators’ work more integrated into the PDF generation.
Before that, I’ll describe the features the PDFs had: two target sizes (paper size and mobile size), cover with title, author, translators and background image, table of contents, some URL linking back to the website (for further commentaries or discussions), 3 types of footnotes (normal ones, in arabic counting; translator’s commentaries, in greek symbols; and URL used in that page, using misc symbols, such as asterisc and so on) and finally, arbitrary information inserted at the end of the PDF file.
Technically, a python script would create the main LaTeX file according to some customized information, and then use pdfLaTeX to generate the PDF file. Everything was really messy, but at least it had a batch run: If I wanted to change the font size, I could re-generate all PDFs in all formats in a single command.
Now I want to make a new one. The features should extend the previous one: consider not only essays but also books, and have alternative targeting to those who intend to print the files. It would be nice, as I said, to have some info about all of the translators and reviewers without adding too much complexity to them. Also some URLs linking translations of the same document in other languages. All this should be possible and practical if the project were translated with Transifex.
Technically, Rust+Tera will deal with the information structuring and TeX making, yaml configuration files will be enought to costumize each document, and XeLaTeX should deal with the PDF generation.
For Japanese language, I found some points that have to be settled:
Having another alternative version, with vertical writing? Found some URL material
- This would mean the template would be different from others, since it’s not XeTeX.
- Better for contextual translations, such as translating ‘Chapter 1’ information.
- This could be an alternative, and an appealing one if other languages other than Japanese also depend on LuaLaTeX: https://ctan.org/pkg/luatexja
Regarding makeindex, for books: https://ctan.org/pkg/mendex-doc
Back to the contextual japanese, this might help: http://jupiter.math.kyushu-u.ac.jp/~norio/XeTeX/work/gloss-japanese.ldf
other links, to look at later:
For furigana (ruby) text, here are some links, including a discourse plugin:
- https://edit.denshochan.com/# - really cool editor features, plus the epub converter
- http://www.aozora.gr.jp/annotation/etc.html#ruby - never saw anything like this
- about having the ruby inserted automatically, since you type it anyway to reach for the Kanji:
- But idk if this would be a good practice, since there might be more information than necessary (in every Kanji).