From: Richard Gabriel <rgabriel@kerio.com>
Subject: Re: Chinese in current ConTeXt
Date: Tue, 20 Dec 2005 16:55:42 +0100 [thread overview]
Message-ID: <20051220155542.baecc985@mx1.kerio.com> (raw)
In-Reply-To: <43A81EB0.6060900@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 2395 bytes --]
> b) Labels: lang-chi.tex contains:
> \setuplabeltext [\s!cn] [\v!figure={\cnencoding\cnencodedfigure}]
> \startencoding[uni-c]
> \definecommand cnencodedfigure {\uchar{86}{254}}
> but if I use (with UTF-8) \placefigure{}{} the figure character is not
> shown; however if I setup this directly, i.e.
> \setuplabeltext[cn][figure={\uchar{86}{254}}]
>, the character is shown just fine.
Hello Tobias!
There's a small mistake in lang-chi.tex.
On line 98, the should actually be:
\startencoding[c-uni]
(instead of "uni-c" - see enco-chi.tex)
Change it and re-generate the format - it works fine! ;-)
-Richard
P.S. The rest is for Hans, I can't say... :-(
_____
From: Tobias Burnus [mailto:burnus@gmx.de]
To: mailing list for ConTeXt users [mailto:ntg-context@ntg.nl]
Sent: Tue, 20 Dec 2005 16:09:36 +0100
Subject: [NTG-context] Chinese in current ConTeXt
Hello,
some remarks/errors of the current UTF-8 Chinese support in ConTeXt
2005.12.19:
(For (a) to (c) see also attached file.)
a) unic-chi.tex: This contains the unicode vectors for which a Chinese
font will be used; currently it only covers
\dostepwiserecurse{40}{159}{1}{\defineunicodecommand #1 {\uchar}}
but this it misses the U+FFxx characters (fullwidth latin characters,
e.g. '?' which is as wide as a Chinese character)
=> solution: Add
\defineunicodecommand 255 {\uchar}
b) Labels: lang-chi.tex contains:
\setuplabeltext [\s!cn] [\v!figure={\cnencoding\cnencodedfigure}]
\startencoding[uni-c]
\definecommand cnencodedfigure {\uchar{86}{254}}
but if I use (with UTF-8) \placefigure{}{} the figure character is not
shown; however if I setup this directly, i.e.
\setuplabeltext[cn][figure={\uchar{86}{254}}]
, the character is shown just fine.
c) Doing font switching using \SimKaiTi seems to convert back to GBK,
can we have Unicode by default (at least when UTF-8 encoding is used)?
Examples for (a) to (c) see attachment (UTF-8 encoded).
* * *
Wish for the native speakers: Please translate
- Graphics/Illustration and Intermezzo(s)
Question to native speakers:
- \c!date={\v!month,\ ,\v!day,{,\ },\v!year},
Is this really the default? Or should this be
year年month月day日?
* * *
Another questions:
a) How to typset from top-to-bottom right-to-left using column(sets)?
b) How to change the numberformat used?
Tobias
[-- Attachment #1.2: Type: text/html, Size: 2999 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-12-20 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 15:09 Tobias Burnus
2005-12-20 15:55 ` Richard Gabriel [this message]
2005-12-20 16:46 ` Hans Hagen
2005-12-20 18:25 ` Tobias Burnus
2005-12-20 21:00 ` Hans Hagen
2005-12-20 21:18 ` Tobias Burnus
2005-12-20 22:34 ` Hans Hagen
2005-12-21 1:16 ` Xiao Jianfeng
2005-12-21 1:45 ` Tobias Burnus
2005-12-22 11:27 ` Richard Gabriel
2005-12-22 11:54 ` Hans Hagen
2005-12-22 13:30 ` Richard Gabriel
2005-12-22 14:57 ` Hans Hagen
2005-12-23 8:31 ` Richard Gabriel
2005-12-21 1:21 ` Xiao Jianfeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051220155542.baecc985@mx1.kerio.com \
--to=rgabriel@kerio.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).