ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: Problem with encoding, XML and writetolist...
Date: Wed, 05 Apr 2006 14:18:55 +0200	[thread overview]
Message-ID: <4433B5AF.8090903@seznam.cz> (raw)
In-Reply-To: <4433A3FC.1030808@wxs.nl>

Hans Hagen wrote:
> Vit Zyka wrote:
> 
>>Martin Kolařík wrote:
>>  
>>
>>>Hi Hans,
>>>
>>>I've analyzed the situation using different combinations of regimes and encodings, including switching off handling (\donothandleactivecharacter) and it seems to me, that every text with chars > 127, which is fully expanded (as in 8bit.tex), must cause difficulties, because TOC entry read back from TUO is scanned independently and thus spaces are gobbled.
>>>    
>>
>>Hi Martin,
>>
>>we have discussed this problem a year ago. In that time I solve it just 
>>writing '{}' in each title where was needed, like
>>
>>   \chapter{Dobré{} ráno}
>>
>>Now I have cooked an automatic solution. It is not optimal (effective) 
>>but working. The only needs is to redefine
>>
>>   \def\numcharacter#1{\char#1{}}
>>   \let\dochar\numcharacter
>>
>>and to load appropriate encoding file once more. Since it is banned a 
>>new macro \reuseencoding was introduce:
>>
>>For Hans:
>>It would be nice if this feature was enabled in a standard distro. 
>>Perhaps you will find some more optimal solution...
>>
>>-------------------------------------------------------
>>\unprotected
>>\def\doreuseencoding#1%
>>   {\letvalue{\c!file\f!encodingprefix#1}\empty
>>    \makeshortfilename[\f!encodingprefix#1]%
>>    \startreadingfile
>>    \readsysfile\shortfilename
>>      {\showmessage\m!encodings2{#1}}
>>      {\showmessage\m!encodings3{#1}}%
>>    \stopreadingfile}
>>\def\reuseencoding[#1]%
>>   {\processcommalist[#1]\doreuseencoding}
>>
>>
>>\def\numcharacter#1{\char#1{}}
>>\let\dochar\numcharacter
>>
>>\reuseencoding[ec]
>>
>>\enableregime[latin2]
>>
>>\starttext
>>\writetolist[chapter]{1}{Dobré ráno}
>>\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
>>
>>\placecontent
>>\stoptext
>>  
> 
> the {} may break liguature building (and maybe kerning) ... taco knows ...

Hmmm, that's right.

> I got a brainwave ... 
> 
> \enableregime[latin2]
> 
> \starttext
> 
> \def\numcharacter#1{\rawcharacter{#1}}%
> \let\dochar\numcharacter

So there is no need to have only 7-bit chars in tui/tuo etc.? All right, 
I think this will be better also for sorting. Sounds promissing.

> \writetolist[chapter]{1}{Dobré ráno}
> 
> \expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
> 
> \placelist[chapter][criterium=text]
> 
> test
> 
> \typefile{test.tuo}
> 
> \stoptext
> 
> this can be sped up (a bit) with 
> 
> % \dostepwiserecurse{0}{255}{1}
> %   {\setevalue{rchr:\recurselevel}{\rawcharacter\recurselevel}}
> 
> % \def\rawcharacter#1{\getvalue{rchr:#1}}
> 
> this means that all chars are round tripped to themselves in output files! 
> 
> raw characters are not active and they are therefore equivalent to \char  
> 
> it's enough then to put 
> 
> \def\numcharacter#1{\rawcharacter{#1}}%
> \let\dochar\numcharacter
> 
> into cont-new.tex 
> 
> (i will discuss this in more detail with taco later) 

All right, thanks Hans,
Vit

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-04-05 12:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  7:24 Martin Kolařík
2006-02-28  9:15 ` Hans Hagen
2006-02-28  9:33   ` Martin Kolařík
2006-03-31  8:42     ` Martin Kolařík
2006-03-31 17:01       ` Hans Hagen
2006-04-02 21:17         ` Martin Kolařík
2006-04-03  8:36           ` Hans Hagen
2006-04-03  8:57             ` Martin Kolařík
2006-04-03  9:56               ` Hans Hagen
2006-04-03 10:36                 ` Martin Kolařík
2006-04-03 12:33                   ` Mojca Miklavec
2006-04-03 12:39                     ` Martin Kolařík
2006-04-03 11:18                 ` Vit Zyka
2006-04-03 11:45                   ` Martin Kolařík
2006-04-04 20:18                 ` Martin Kolařík
2006-04-04 20:25                 ` Martin Kolařík
2006-04-05  8:17                   ` Hans Hagen
2006-04-05  9:54                   ` Vit Zyka
2006-04-05 11:03                     ` Hans Hagen
2006-04-05 12:18                       ` Vit Zyka [this message]
2006-04-05 14:09                         ` Hans Hagen
2006-04-03 14:25 ` Mojca Miklavec
2006-04-03 14:41   ` Martin Kolařík
  -- strict thread matches above, loose matches on Subject: below --
2006-04-05 11:59 Martin Kolařík
2006-04-06  9:07 ` Hans Hagen
2006-04-02 21:20 Martin Kolařík
2006-02-27 11:58 Martin Kolařík

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=4433B5AF.8090903@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --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).