Steven Trogdon
Steven Trogdon
Vanilla `9.6.beta6` is available. I have some odd verbose results. Now this is an incremental build from `beta5`. I no longer get verbose results like ``` [346/531] gcc -g -O2...
Do you know whether this started with `9.7.beta3`?
`ebuild sage-9999.ebuild prepare`, then from the portage work folder, edit `src/sage_setup/command/sage_build_ext.py` and apply your `sage_setup-9.6-verbosity.patch` and then `ebuild sage-9999.ebuild compile` gives verbose output. So, perhaps not looking for the system...
I had noticed that when "googling". Latest on Gentoo is `texlive-2021`. There is a 2022. Perhaps a correction is available with the newer texlive.
If I comment out `f ckx.map` in `dvipdfmx.cfg` there is ``` # dvipdfmx -o tutorial-jp.pdf tutorial-jp.dvi tutorial-jp.dvi -> tutorial-jp.pdf [1 dvipdfmx:warning: Failed to load ToUnicode mapping: UTF8-UCS2 dvipdfmx:warning: Interpreting special...
Since I don't do `Japanese` I have no idea if the rendered characters are correct.
See https://oku.edu.mie-u.ac.jp/~okumura/texfaq/qa/52108.html for possible differences.
The above is for `EUC-UCS2` and not for `UTF8-UCS2`.
I believe this is what is not being processed properly ``` sphinxoptionshyperref.sty: \AtBeginShipoutFirst{\special{pdf:tounicode UTF8-UCS2}} ```
From what I can find `UCS2` is obsolete, although it is mentioned in the current `dvipdfmx` CTAN documentation. It may just be that `sphinxoptionshyperref.sty` should be modified to use something...