ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: utf-based lang-* files?
Date: Thu, 22 Sep 2005 23:23:12 +0200	[thread overview]
Message-ID: <433320C0.5040504@wxs.nl> (raw)
In-Reply-To: <4332DADD.5010705@creutzig.de>

Christopher Creutzig wrote:

>Adam Lindsay wrote:
>  
>
>>>Is it possible to simply enclose the file in a
>>>\startregime[utf]...\stopregime pair or do I risk havoc by doing this?
>>>      
>>>
>>Well, if you're using a regime, it still (usually) depends on symbolic
>>character names being defined under the hood. Also, such an approach
>>    
>>
>
> Sure.  But editing the file is oh so much easier when I can just type
>\def\japChapterNumber#1{第#1章}
>than if I have to look up the unicode numbers first and type
>\def\japChapterNumber{\uchar{123}{44}#1\uchar{122}{224}}
>
>  
>
>>(explicitly calling \startregime[utf]) doesn't make XeTeX as happy as it
>>could be (XeTeX is happiest if you just pass through Unicode characters.
>>
If xetex handles utf-8 by just looking at catcodes letter, you don't 
need a regime; you just have to make sure that when the file is loaded 
the chars 128->255 have the right catcode

\dostepwiserecurse{128}{255}{1}{\catcode\recurselevel=11\relax}

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

      parent reply	other threads:[~2005-09-22 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 12:17 Christopher Creutzig
2005-09-22 12:27 ` Adam Lindsay
2005-09-22 16:25   ` Christopher Creutzig
2005-09-22 16:40     ` Adam Lindsay
2005-09-22 21:23     ` Hans Hagen [this message]

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=433320C0.5040504@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).