I'm in favor of 5, build the Chinese docs separately from the rest of
the docs with whatever tool works and keep the rest of the docs which
use western characters in the same tool chain.
JT
On 9/21/2020 4:06 AM, andy pugh wrote:
On Sun, 20 Sep 2020 at 20:10, Dr. Nikolaus Klepp <off...@klepp.biz> wrote:
I've made a deb with the HTML documentation of linuxcnc 2.8.0
I know that you were not suggesting that we remove the PDF docs, but I
would like to expand the discussion in that direction.
The current tool chain can not build docs in non-latin alphabets. For
2.8 we had a fairly big submission of Chinese docs. These render OK in
HTML:
http://linuxcnc.org/docs/2.8/html/getting-started/updating-linuxcnc-cn.html
but attempting to build a PDF leads to a build failure.
A partial solution is to replace latex with xetex in the docs
toolchain. However xetex is not available in Stretch.
A neater solution might be to use asciidoctor-pdf which is a one-step
process from asciidoc to pdf. It seems to work well (and with Chinese)
but relies on Ruby >v2.3 which is only the default version on the
newer OS versions.
This is partly a buildbot issue. Do the docs that are distributed with
the LinuxCNC version for a particular necessarily have to have been
built with that OS?
Options:
1) Keep things as they are, don't attempt to distribute a Chinese docs package.
2) Abandon PDF, distribute docs as HTML in the docs package.
3) Use xetex to make PDFs, abandon PDF docs build on older OS versions.
4) Use asciidoctor-pdf to make PDFs, abandon building PDF docs on
older OS version
5) ...
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
