Re: setuptex changes in minimals

[Yanrui Li <liyanrui.m2@gmail.com>]

On Sat, May 9, 2009 at 4:02 PM, Hans Hagen <pragma@wxs.nl> wrote:
> 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)
>

What I have done is only experiment. I will try my best to follow the
evolves of the
 scrp-* files until that day, when MkIV support Chinese typesetting well, comes.
I have to introduce MkIV to Chinese users and make them paying close attention
to it in this way.

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

Yes. It is a key reson that we are still not familiar with MkIV well
now. But with
in-depth understanding of MkIV, maybe many suggestions will be post to you.
Of course these suggestions should be collected according actual demands by
Chinese TeX users group.

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

I think that maybe this needs a very long time until CJK users know what each
other needs. But three years should be enough :)

-- 
Best wishes,
Li Yanrui
___________________________________________________________________________________
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
___________________________________________________________________________________