ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Asian Language Support
Date: Tue, 08 May 2012 17:41:15 +0200	[thread overview]
Message-ID: <4FA93E9B.30502@wxs.nl> (raw)
In-Reply-To: <4FA935BE.803@users.sourceforge.jp>

Hi Yusuke

>  > A question for Yusuke: what script name should we use?
>
> It is a difficult question. In Chinese or Korean case,
> what they have chosen? In Japanese, we need to prepare a
> lot of characters for font set if they complete Adobe-Japan-1.5
> or something. So, some font vendors publish the font sets
> including only kana-region and latin/number-region (and
> elementary school level kanjis). In this case, script=kana
> might be ok, but if the font set has all the characters
> of Adobe-Japan-1.5 region, then script=kana is too impolite.
>
> Moreover, in pTeX world, we use 'kanji' for this kind, but
> we need to rethink 'kanji' is most appreciate or not.

we use hangul for korean and hanzi for chinese so kanji sounds ok to me 
but in fact there a bit more to it, currently we have

\definescript[hangul]  [method=hangul]
\definescript[hanzi]   [method=hanzi]
\definescript[nihongo] [method=nihongo]

and these use default presets but as there can be be variants in spacing 
one can also define for instance

\definescript [myhangul] [hangul] [preset=mypreferences]

(not that there are such preferences defined now) and more key/values 
will be supported some day

so, shall we go for 'kanji' for the default setup? but 'japanese' could 
do as well as well because we can define synonyms

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-05-08 15:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 10:43 hwitloc
2012-05-07 13:12 ` S Barmeier
2012-05-07 22:07   ` Hans Hagen
2012-05-07 22:33     ` KUROKI Yusuke
2012-05-08 15:03     ` KUROKI Yusuke
2012-05-08 15:41       ` Hans Hagen [this message]
2012-05-07 13:17 ` KUROKI Yusuke
2012-05-07 12:54   ` [***SPAM***] " d.henman
2012-05-07 14:17     ` KUROKI Yusuke
2012-05-08  8:41     ` ABE Noriyuki
2012-05-08 14:11       ` hwitloc
2012-05-08  9:09     ` [***SPAM***] " Hans Hagen
2012-05-07 13:56   ` S Barmeier
2012-05-07 15:54   ` Hans Hagen
2012-05-08 10:39     ` KUROKI Yusuke
2012-05-09 13:37       ` KUROKI Yusuke
     [not found] <mailman.3.1336471202.23349.ntg-context@ntg.nl>
2012-05-08 13:48 ` dalyoung

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=4FA93E9B.30502@wxs.nl \
    --to=pragma@wxs.nl \
    --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).