ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Dohyun Kim <nomosnomos@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: beta release
Date: Mon, 2 Mar 2009 18:11:21 +0900	[thread overview]
Message-ID: <bfeb3bf10903020111y796605c5x8386773ded3cc4a@mail.gmail.com> (raw)
In-Reply-To: <49AB9945.302@wxs.nl>

2009/3/2 Hans Hagen <pragma@wxs.nl>:
> Yanrui Li wrote:
>>
>> There are some Chinese punctuations,
>> such as “," (fullwidth comma), "!" (fullwidth exclamation mark) and so on,
>> which are considered to be "chinese" but not "full_width_close" by
>> scrp-cjk.lua.
>> Is this deliberately doing?
>
> we have different vectors for chinese and korean and each of them can be
> optimized, of there can be several for each script
>
> keep in mind that when korean uses chinese, it does not use the chinese
> rules
>

Those Chinese punctuations we Koreans seldom use.
Nor we normally use characters from U+FF00 .. U+FFFF area.
So it's OK to delete this line in scip-ini.lua :

    for i=0x0FF00,0x0FFEF do hash[i] = "chinese" end

as requested by Chinese people.

Or it would be better if the order is reversed, that is to say,
if the line mentioned above and other adjacent lines comes before
the hash table of individual characters.

Dohyun Kim
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-03-02  9:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 16:09 Hans Hagen
2009-02-24 17:11 ` mkiv ppchtex greek character bug Alan BRASLAU
2009-02-24 17:23   ` Hans Hagen
2009-02-24 17:49     ` Alan BRASLAU
2009-02-24 22:36   ` Hans Hagen
2009-02-24 22:46   ` Hans Hagen
2009-02-24 22:52     ` Hans Hagen
2009-02-25  7:52       ` Alan BRASLAU
2009-02-25  8:23         ` Hans Hagen
2009-02-25 14:45           ` Mojca Miklavec
2009-02-24 18:03 ` beta release Wolfgang Schuster
2009-02-28  3:55 ` Yue Wang
2009-02-28  4:05   ` Yue Wang
2009-03-01 18:53     ` Hans Hagen
2009-03-01 19:02       ` Otared Kavian
2009-03-01 19:53         ` Hans Hagen
2009-03-02  3:57         ` Yue Wang
2009-03-02  3:57           ` Yue Wang
2009-03-02  3:56       ` Yue Wang
2009-03-03  6:44       ` Yue Wang
2009-03-03  8:17         ` Hans Hagen
2009-03-01 17:19   ` Hans Hagen
2009-03-01 17:58     ` Wolfgang Schuster
2009-03-03  6:47       ` Yue Wang
2009-02-28  7:40 ` Yanrui Li
2009-03-01 18:57   ` Hans Hagen
2009-03-02  0:50     ` Yanrui Li
2009-03-02  8:31       ` Hans Hagen
2009-03-02  9:11         ` Dohyun Kim [this message]
2009-03-02 10:02           ` Hans Hagen
2009-03-02 10:17             ` Dohyun Kim
2009-03-02 10:41               ` Hans Hagen

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=bfeb3bf10903020111y796605c5x8386773ded3cc4a@mail.gmail.com \
    --to=nomosnomos@gmail.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).