ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Basic question on Unicode and ConTeXt
Date: Tue, 19 Jul 2005 10:06:53 +0200	[thread overview]
Message-ID: <42DCB49D.5020209@wxs.nl> (raw)
In-Reply-To: <6faad9f005071816115514e6ba@mail.gmail.com>

Mojca Miklavec wrote:

>Hans Hagen wrote:
>  
>
>>Mojca Miklavec wrote:
>>
>>    
>>
>>>>(concerning eregi-* files: you can define filesynonyms so we need a list of filesynonyms and regimesynonyms)
>>>>
>>>>        
>>>>
>>>What do you mean by writing file synonyms? Where would it be used?
>>>      
>>>
>>\definefilesynonym  [mojka]  [mojca]
>>\definefilesynonym  [moika]  [mojca]
>>\definefilesynonym  [moica]  [mojca]
>>    
>>
>
>Ok, if you are provocating, I'll strike back:
>None of the definitions above are allowed because they don't warn the
>user if he's using the wrong name. They should throw an error instead.
>The only proper way would be to define something like
>
>\setuplabeltext[\s!en][\v!pronouncemyname=moitsa]
>\setuplabeltext[\s!de][\v!pronouncemyname=mojza]
>\setuplabeltext[\s!ru][\v!pronouncemyname=мойца]
>...
>  
>
so how about using:

\translate[en=moitsa,de=mojza,ru=мойца]

then -)

>OK. I'll prepare \defineregimesynonym-s proposals, but I still don't
>know what the file synonyms should be used for in this context. The
>user probably doesn't need to care about file names?
>  
>
depends on if you want to preload all those vectors (take quite some 
memory although i may find a way around that [maybe delayed loading]

>So why not mapping the characters to unicode first and defining the
>mapping from unicode to \TeXcommand only once? regi-* files (at least
>in the meaning they have now) could be prepared automatically by a
>script, less error-prone and without the need to say "Some more
>definitions will be added later."
>  
>
you mean ...

\defineactivetoken 123 {\uchar{...}{...}}

it is an option but it's much slower and take much more memory

\uchar{2}{33} takes 1 hash pointer and 7 char slots (so probably 8 mem 
locations) while \eacute takes one mem location

>Is it possible to switch the regimes in the middle of the document
>(like it is possible to switch the languages)? An example usage would
>be if some input documents (plain text, some older TeX files or
>database entries) are written in some other encoding than the main
>stream.
>(Possibly switching in such a way that no leftovers remain after the
>old encoding is replaced by a new one.)
>  
>
switching is possible but in that case  you probably want to set toc/index/etc expansion to yes 

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

  reply	other threads:[~2005-07-19  8:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  9:30 Steffen Wolfrum
2005-07-14 10:29 ` Henning Hraban Ramm
2005-07-14 19:13   ` Steffen Wolfrum
2005-07-14 19:32     ` VnPenguin
2005-07-15  5:16     ` Radhelorn
2005-07-15  9:09     ` Henning Hraban Ramm
2005-07-15 18:43   ` Mojca Miklavec
2005-07-15 18:59     ` hungarumlaut (was: Basic question on Unicode) Henning Hraban Ramm
2005-07-15 21:13     ` ISO/windows encodings (was: Basic question on Unicode ...) Mojca Miklavec
2005-07-17 23:38       ` ISO/windows encodings Hans Hagen
2005-07-17 20:01     ` Basic question on Unicode and ConTeXt Hans Hagen
2005-07-18  5:50       ` VnPenguin
2005-07-18 20:26       ` Mojca Miklavec
2005-07-18 21:46         ` Hans Hagen
2005-07-18 21:54         ` Hans Hagen
2005-07-18 23:11           ` Mojca Miklavec
2005-07-19  8:06             ` Hans Hagen [this message]
2005-07-20 20:35               ` Christopher Creutzig
2005-07-21  0:52                 ` Mojca Miklavec
2005-07-22 11:30                   ` Christopher Creutzig
2005-07-22 12:05                     ` Hans Hagen
2005-07-22 22:20                     ` Mojca Miklavec
2005-07-25 15:58                       ` Henning Hraban Ramm
2005-07-25 23:49                       ` Hans Hagen
2005-07-17 20:37     ` Hans Hagen
2005-07-17 21:51       ` Henning Hraban Ramm
2005-07-17 22:36         ` Hans Hagen
2005-07-18 16:18           ` Visual Debugging (was: Basic question) Henning Hraban Ramm
2005-07-18 20:44             ` Brooks Moses
2005-07-18 21:41               ` Visual Debugging 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=42DCB49D.5020209@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).