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.
>
> Now I have solved it using not-stable solution -- I am using triple sequence
> of \expandafter to expand \XMLflush after \chapter instead \expanded. The
> solution is not stable as it is ConTeXt implementation dependent.
>
> On the other side, now I do not know, how to partially expand code
> \chaper{\XMLflush{XMLTag}} to obtain sequence of simple unexpanded chars.
> Simple \expandafter is not sufficient, more \expandafters is dirty trick and
> full expansion (\expanded) leads to TOC entry problem. In TeX source this
> cannot occur (or can occur in strange situations :-), in XML source this is
> almost rule.
>
> Maybe it would be useful to have in XML engine macro, which expands XMLdata
> exactly to get read (original) content (like mine triple \expandafter). Maybe
> such macro already exists and I am a real fool :-)
>
> Thank you for help, have a nice day,
>
some commands indeed have keys like:
expansion=no|yes|utf|xml|command
and alike
the problem is that when one does something \expanded{...} in a style, it
bypasses this mechanism
can you make me a (as small as possible) example of a doc? i can then test it
here with my version
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
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
