ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Problem with encoding, XML and writetolist...
Date: Mon, 3 Apr 2006 16:25:19 +0200	[thread overview]
Message-ID: <6faad9f00604030725i5b2d5689o5e9f5b06d53b2c3c@mail.gmail.com> (raw)
In-Reply-To: <NCBBIFBEODPJOENMOHHBOEALILAA.martin.kolarik@email.cz>

On 2/28/06, Martin Kolařík wrote:
> Hi all,
>
> I have problem with chars encoding now; I have updated ConTeXt sometimes in
> January; before the time I was using old (year) version. In this
> prehistorical version the problem was not present.
>
> What is the stuff? The following code generates content with titles without
> spaces -- accented characters are replaced with \char XXX variant, so during
> reading TUI line TeX gobbles a space after XXX as a part of <number> syntax
> rule.
>
> Can I do something? With encoding? With XML?

Encoding has "nothing" to do with it. I don't really understand the
\[un]expanded commands in TeX, but this part could theoretically be
problematic:
 {\expanded
    {\section{\XMLflush{title}}}}

Consider the following (encoding-independent) minimal example, just in
case that this can help any of the gurus to understand the problem:

\defineXMLenvironment
 [chapter]
 {\defineXMLsave[title]}
 {\expanded
    {\section{\XMLflush{title}}}}

\starttext
\startbuffer
<chapter>
 <title>$a+b$</title>
</chapter>
\stopbuffer

\processXMLbuffer
\placecontent[criterium=all]
\stoptext

The entry in TOC is different from the title (one is in math mode and
the other one writen with dollars - literally).

Mojca


> Thank you very much, have a nice day, Martin
>
> Code:
>
> \defineXMLenvironment
>   [chapter]
>   {\defineXMLsave[title]}
>   {\expanded
>      {\chapter\XMLflush{title}}}
>
> \starttext
>
> \startbuffer
>
> <chapter>
>   <title>Ahojá hojč kuna</title>
> </chapter>
>
> \stopbuffer
>
> \processXMLbuffer
>
> \completecontent[criterium=all]
>
> \stoptext

  parent reply	other threads:[~2006-04-03 14:25 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
2006-04-05 14:09                         ` Hans Hagen
2006-04-03 14:25 ` Mojca Miklavec [this message]
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=6faad9f00604030725i5b2d5689o5e9f5b06d53b2c3c@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).