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: setuptex changes in minimals
Date: Sat, 09 May 2009 10:02:23 +0200	[thread overview]
Message-ID: <4A05388F.2010605@wxs.nl> (raw)
In-Reply-To: <68bfdc900905081857o4a54af57u65a2f1d14dd244e0@mail.gmail.com>

Yue Wang wrote:
> On Sat, May 9, 2009 at 2:20 AM, Yanrui Li <liyanrui.m2@gmail.com> wrote:
>> Sorry!
>>
>> s/MkIV have not support Chinese typesetting now / MkIV have not
>> support Chinese typesetting well now/g
> 
> 
> We can start a fork of scrp-* on code.google.com/p/ctex-kit,
> making a usable version, and later ask Hans to merge back into ConTeXt.

it all depends how scrp evolves as it has to deal with more issues too; 
i will not merge code that i don't fully understand but experimenting 
does not hurt; one problem with script stuff is that (in the future) it 
might be closely cooperate with other mechanisms of context (it used to 
be part of the font analyser, now it's plugged in elsewhere but even 
that might change, for instance when in upcoming versions of luatex we 
have a bit more control)

also, some issues will be dealt with in other code in the future (i 
simply cannot touch all code at the same time) so don't expect mkiv to 
be finished before 2012 (when luatex 1 is ready); it's a stepwise 
process and it's only driven by context (i.e. generic code only shows up 
when context code works okay);

anyhow, as long as nobody tells me what the expected behaviour is, with 
test code etc i can;t fix anything; one complication (e.g. with chinese) 
is that over the last few year is got conflicting requests; now, if 
there are multiple ways to deal with it, then i can implement variants 
but only if i know the exact conventions (with proper names for them)

for instance when i found out that cjk-korean is not the same as 
cjk-chinese (one of them) i split the machinery so we're not talking cjk 
here, but very specific needs; after the split i never tested chinese 
(no samples) and no one else propbably did that either

keep in mind that context is not meant for one language but for many and 
that when possible mechanisms need to be able to used mixed; there will 
never be exclusive solutions for one languages unless it's a very 
specialized module

anyhow, we can best follow the same route as with other language / 
script support

- we need consistent specs, or maybe multiple specs as variants
- as well as test files for each such case
- and then we can look into what can be improved or added

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-05-09  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 11:19 setuptex changes in minimals (was: bugs in beta) Mojca Miklavec
2009-05-08 12:16 ` Yanrui Li
2009-05-08 17:43   ` Mojca Miklavec
2009-05-08 18:17     ` Yanrui Li
2009-05-08 18:20       ` Yanrui Li
2009-05-09  1:57         ` Yue Wang
2009-05-09  8:02           ` Hans Hagen [this message]
2009-05-09 11:44             ` setuptex changes in minimals Yanrui Li
2009-05-09 15:57               ` Yue Wang
2009-05-10 15:35                 ` 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=4A05388F.2010605@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).