Opened 10 years ago

Last modified 3 years ago

#9577 needs_work enhancement

chinese translation of the tutorial

Reported by: schilly Owned by: mvngu
Priority: major Milestone: sage-8.0
Component: translations Keywords: tutorial, chinese
Cc: mvgnu, amao@…, vbraun, dimpase Merged in:
Authors: Ziyang Mao Reviewers: Frédéric Chapoton, Karl-Dieter Crisman
Report Upstream: N/A Work issues:
Branch: u/chapoton/9577 (Commits) Commit: f03189b3ded3ac5728d8fb1462ee78bac9ddc971
Dependencies: Stopgaps:

Description

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.

Attachments (1)

9577-chinese-tutorial.patch (178.6 KB) - added by schilly 10 years ago.
chinese translation of the tutorial

Download all attachments as: .zip

Change History (35)

Changed 10 years ago by schilly

chinese translation of the tutorial

comment:1 Changed 10 years ago by schilly

  • Status changed from new to needs_work

comment:2 Changed 6 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:3 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:4 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:5 Changed 6 years ago by chapoton

  • Branch set to u/chapoton/9577
  • Commit set to 4287a8917e792b31c435b7006d98a55e38724fb7
  • Keywords tutorial chinese added
  • Status changed from needs_work to needs_review

New commits:

4287a89#9577 chinese tutorial

comment:6 Changed 6 years ago by git

  • Commit changed from 4287a8917e792b31c435b7006d98a55e38724fb7 to f541688cec0ce85ef96e505d16fdf41e028d4d64

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

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

comment:7 Changed 5 years ago by git

  • Commit changed from f541688cec0ce85ef96e505d16fdf41e028d4d64 to b6c20e7fcdd9da15392803fef0584627a968c37d

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

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

comment:8 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:9 Changed 5 years ago by git

  • Commit changed from b6c20e7fcdd9da15392803fef0584627a968c37d to fe6d14c4d6e5e9201732c30a56f44afc53668a5d

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

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

comment:10 Changed 5 years ago by git

  • Commit changed from fe6d14c4d6e5e9201732c30a56f44afc53668a5d to 723bfc0101d7fa48eb667c8981c67ef20d305579

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

723bfc0trac #9577 modern style doctest continuation using ....:

comment:11 Changed 5 years ago by git

  • Commit changed from 723bfc0101d7fa48eb667c8981c67ef20d305579 to ff31f4e5463720d21f4c539d422bd76aec75d1fb

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

ff31f4etrac #9577 yet another duplicate reference

comment:12 Changed 5 years ago by git

  • Commit changed from ff31f4e5463720d21f4c539d422bd76aec75d1fb to c8fb2d6d4632fb9bebf814ec2ca5ca88d73c5edf

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

c8fb2d6trac #9577 inclusion of tour_advanced-zh in index

comment:13 Changed 5 years ago by git

  • Commit changed from c8fb2d6d4632fb9bebf814ec2ca5ca88d73c5edf to 9757fbd01894e8766bb17e6b738d33b363ff99ee

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

9757fbdtrac #9577 yet another duplicate ref

comment:14 Changed 5 years ago by git

  • Commit changed from 9757fbd01894e8766bb17e6b738d33b363ff99ee to f1029ee4d164148fe02b61a3cb07067255af0479

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

f1029eetrac #9577 again a duplicate

comment:15 Changed 5 years ago by git

  • Commit changed from f1029ee4d164148fe02b61a3cb07067255af0479 to fb72c199f1f1ad1bef193b7bdd2fb5e84f248a2d

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

fb72c19trac #9577 trying to build, once again

comment:16 Changed 5 years ago by git

  • Commit changed from fb72c199f1f1ad1bef193b7bdd2fb5e84f248a2d to c6d280490a4a0097b8eeaba140dedfd8cc6140d5

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

ebb7a89Merge branch 'u/chapoton/9577' of ssh://trac.sagemath.org:22/sage into 9577
c6d2804trac #9577 correct one failing doctest

comment:17 Changed 5 years ago by vbraun

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.

comment:18 Changed 5 years ago by vbraun

  • Status changed from needs_review to needs_work

comment:19 Changed 5 years ago by kcrisman

  • Component changed from documentation to translations

comment:20 Changed 5 years ago by kcrisman

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).

comment:21 Changed 5 years ago by kcrisman

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.

comment:22 Changed 5 years ago by kcrisman

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.

comment:23 Changed 5 years ago by kcrisman

  • Cc amao@… added

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

comment:24 Changed 5 years ago by kcrisman

  • Authors set to Ziyang Mao
  • Reviewers set to Frédéric Chapoton, Karl-Dieter Crisman

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.

comment:25 Changed 5 years ago by kcrisman

  • Cc vbraun dimpase added

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.)

comment:26 follow-up: Changed 5 years ago by dimpase

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

comment:27 in reply to: ↑ 26 Changed 5 years ago by kcrisman

\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}

comment:28 Changed 5 years ago by chapoton

  • Milestone changed from sage-6.4 to sage-6.8

comment:29 Changed 4 years ago by chapoton

  • Milestone changed from sage-6.8 to sage-6.10

comment:30 Changed 4 years ago by chapoton

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

comment:31 Changed 4 years ago by chapoton

  • Milestone changed from sage-6.10 to sage-7.0

comment:32 Changed 4 years ago by git

  • Commit changed from c6d280490a4a0097b8eeaba140dedfd8cc6140d5 to f03189b3ded3ac5728d8fb1462ee78bac9ddc971

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

9e9a36cMerge branch 'u/chapoton/9577' into 7.0.b2
f03189btrac #9577 fixing doctests

comment:33 Changed 3 years ago by chapoton

  • Milestone changed from sage-7.0 to sage-8.0

comment:34 Changed 3 years ago by kcrisman

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?

Note: See TracTickets for help on using tickets.