From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: XML, multiple spaces encoded as %20 get merged into one space
Date: Wed, 6 Sep 2023 18:14:20 +0200 [thread overview]
Message-ID: <d9c837dd-8b06-6357-eea3-28fb48168a61@freedom.nl> (raw)
In-Reply-To: <d6175c17-be17-84f8-1fc6-f972ca381771@gmx.es>
On 9/6/2023 4:59 PM, Pablo Rodriguez wrote:
> On 9/6/23 12:28, denis.maier@unibe.ch wrote:
>> Hi,
>>
>> I have the example below that uses the three images in the attachment.
>> For some reason multiple spaces encoded as %20 get merged into a single %20.
>
> Hi Denis,
>
> this is standard TeX behavior (not only related to XML):
>
> \starttext
> \externalfigure[test two spaces.pdf]
> \externalfigure[test not two spaces.pdf]
> \stoptext
>
> I don‘t know whether this is intended or not.
>
> That being said, more than one consecutive space in a file name (I would
> say it) is rather an exception than the rule.
>
> Fixing this may cause more trouble that it might seem at first.
The problem with escaping is that there can be several round trips and
it's kind of hard to predict usage and such. Also, take this:
<graphic xlink:href='test%20%20n$ot%20t\wo%20s{p}a#ces.p"df'/>
Then, as i don't have these graphics, the test failed after a catch on
the fact that tex didn't like the string for rendering in the 'unknown
figure' drop in and after another catch the { } were not shown ...
Anyway, with a little magic i can now at least make this work but it
needs testing with existing documents because it's not like we can
update the xml stuff every thiem we have yet another exception (ok,
those using sane image names are probably okay).
So, in a next update you can test some,
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-09-06 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 10:28 [NTG-context] " denis.maier
2023-09-06 14:59 ` [NTG-context] " Pablo Rodriguez
2023-09-06 16:14 ` Hans Hagen via ntg-context [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=d9c837dd-8b06-6357-eea3-28fb48168a61@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).