chinese translation of the tutorial

[haraldschilly]

i found this on the internetz over here:
http://ai7.org/wp/html/682.html

i am unable to build the pdf, but html works.

CC: @sagetrac-mvngu amao@ai7.org @vbraun @dimpase

Component: translations

Keywords: tutorial, chinese

Author: Ziyang Mao

Branch/Commit: u/chapoton/9577 @ f03189b

Reviewer: Frédéric Chapoton, Karl-Dieter Crisman

Issue created by migration from https://trac.sagemath.org/ticket/9577

[haraldschilly]

Attachment: 9577-chinese-tutorial.patch.gz

chinese translation of the tutorial

[fchapoton]

Commit: 4287a89

[fchapoton]

New commits:

4287a89

#9577 chinese tutorial

[fchapoton]

Changed keywords from none to tutorial, chinese

[fchapoton]

Branch: u/chapoton/9577

[sagetrac-git]

Changed commit from 4287a89 to f541688

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

60e21a5	Merge branch 'u/chapoton/9577' of ssh://trac.sagemath.org:22/sage into 9577
f541688	trac #9577 correct all failing doctests

[sagetrac-git]

Changed commit from f541688 to b6c20e7

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

72f10c8	Merge branch 'u/chapoton/9577' of ssh://trac.sagemath.org:22/sage into 9577
b6c20e7	trac #9577 remove duplicate references

[sagetrac-git]

Changed commit from b6c20e7 to fe6d14c

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

d68f1a2	Merge branch 'u/chapoton/9577' of ssh://trac.sagemath.org:22/sage into 9577
fe6d14c	trac #9577 remove another duplicate of [Py] reference

[sagetrac-git]

Changed commit from fe6d14c to 723bfc0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

723bfc0

trac #9577 modern style doctest continuation using ....:

[sagetrac-git]

Changed commit from 723bfc0 to ff31f4e

[sagetrac-git]

Changed commit from fb72c19 to c6d2804

[vbraun]

comment:17

Is this traditional or simplified? The buildbot also builds the pdf doc. Since chinese is not TeX'ed using babel we'd have to disable pdf output.

[kcrisman]

comment:20

Since chinese is not TeX'ed using babel we'd have to disable pdf output.

Is that fairly easy to do with something analogous to the solution in #12559? It looks like it might "just work" if this ticket depends on that one (I have not tried this yet, though).

[kcrisman]

comment:21

This actually looks quite good (html). I think that the tour_advanced-zh file should replace the other one, since it is clearly a partial translation - or did I miss something there?

I'm going to move this to the zh_CN directory created by #12559, assuming that this is also mainland Mandarin. I have a colleague who has agreed to proofread some stuff and she can comment on that too, of course.

For pdf we'll at least need a config file change, not sure if the solution at #12559 will fix it once that's done.

[kcrisman]

comment:22

Okay, once I do that I get the same error as there,

Writing index file SageTutorial.idx
kpathsea: Invalid fontname `AR PL UMing CN', contains ' '

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! fontspec error: "font-not-found"
! 
! The font "AR PL UMing CN" cannot be found.
! 
! See the fontspec documentation for further information.
! 
! For immediate help type H <return>.
!...............................................  

which is presumably my lack of fontitude. Good.

[kcrisman]

comment:23

In the hopes that the original author might see this and have any comments...

[kcrisman]

Author: Ziyang Mao

[kcrisman]

comment:24

The change in fonts in this comment seems to work as well, so whatever solution we get there should work here. Obviously we could just have two different conf things by messing with that file, but that is not particularly elegant. There are still a few bugs with the LaTeX macros but on the way to happiness.

Also, the author confirms this is simplified Chinese in private communication.

[kcrisman]

Reviewer: Frédéric Chapoton, Karl-Dieter Crisman

[kcrisman]

comment:25

Okay, the errors I am getting are the same ones as in this other comment, but for this document we really do need the macros that \DeclareUnicodeCharacter provides.

There is a hack, I think, to just provide the macros this document needs, but it will definitely be just a hack. If we really want to use more xelatex in the future for our documentation, we will have to find a way to work around this, such as this one. (Or Sphinx, or someone, will need to do this.)

[dimpase]

comment:26

\DeclareUnicodeCharacter for each Chinese character would be fun :-)

[kcrisman]

comment:27

\DeclareUnicodeCharacter for each Chinese character would be fun :-)

Yikes! Luckily, I didn't need any of them, just

\newcommand{\Bold}[1]{\mathbf{#1}}
\newcommand{\ZZ}{\Bold{Z}}
\newcommand{\QQ}{\Bold{Q}}
\newcommand{\GF}[1]{\Bold{F}_{#1}}

As it turns out, the problem is that xelatex doesn't recognize \DeclareUnicodeCharacter, and so one never gets to this stuff in the first place. Of course, I didn't check whether some fairly important math characters for Sage such as

\DeclareUnicodeCharacter{0428}{cyrillic Sha}

appeared correctly, but from a little browsing I think most of those declarations are just to make things look "nice", e.g.

\DeclareUnicodeCharacter{221A}{\sqrt}

[fchapoton]

comment:30

Maybe we can use use here what has worked for japanese in #19188 ?

[sagetrac-git]

Changed commit from c6d2804 to f03189b

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

9e9a36c	Merge branch 'u/chapoton/9577' into 7.0.b2
f03189b	trac #9577 fixing doctests

[kcrisman]

comment:34

Just as an fyi slight updates are pending in tutorial for sagenb becoming legacy - no need to fix this though. It would be nice to figure out how to get this to work, or maybe we just give up on pdf?