From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Subject: [NTG-context] Re: Replacing %20 with spaces in xml attributes
Date: Fri, 21 Jul 2023 16:25:30 +0200 [thread overview]
Message-ID: <04222291-1CA6-46C8-A9BA-4DE75C76F5C0@ziggo.nl> (raw)
In-Reply-To: <ZRAP278MB049586881365EE0D137638CC833FA@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 2103 bytes --]
Here in Terminal on my Mac:
21 ~: lua
Lua 5.4.6 Copyright (C) 1994-2023 Lua.org, PUC-Rio
> string.gsub('a%20b', '%%20', ' ')
a b 1
> (string.gsub('a%20b', '%%20', ' '))
a b
> ^D
21 ~:
The first call returns the 1 giving the match, the extra ()'s get rid of that second return value.
yours sincerely
dr. Hans van der Meer
> On 21 Jul 2023, at 12:37, denis.maier@unibe.ch wrote:
>
> Hi,
>
> I’m typesetting an XML document where the links to the images contain spaces which are encoded as %20
> <graphic xlink:href="a%20filename%20with%20spaces.jpg"/>
>
> Using this works in cases without spaces:
>
> \startxmlsetups xml:fig:graphic
> \externalfigure[\xmlatt{#1}{xlink:href}]
> \stopxmlsetups
>
> This also works for normal spaces, but is there a way to decode/expand the %20s to regular spaces?
>
> I’ve tried with some Lua, but I don’t really know how to pass data around.
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \startluacode
> function replaceSpaces(s)
> result = string.gsub(s, "%%20", " ")
> context(result)
> end
> \stopluacode
>
> \define[1]\replaceSpaces{\ctxlua{replaceSpaces("#1")}}
>
> \startxmlsetups xml:fig:graphic
> \externalfigure[\replaceSpaces{\xmlatt{#1}{xlink:href}}]
> \stopxmlsetups
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> Any hints, why this does not work?`
>
> Also, maybe there’s a simpler way for this kind of scenario?
>
> Best,
> Denis
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl <https://www.pragma-ade.nl/> / http://context.aanhet.net <http://context.aanhet.net/>
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net <https://contextgarden.net/>
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 19488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-07-21 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 10:37 [NTG-context] " denis.maier
2023-07-21 14:25 ` Hans van der Meer via ntg-context [this message]
2023-07-21 15:27 ` [NTG-context] " denis.maier
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=04222291-1CA6-46C8-A9BA-4DE75C76F5C0@ziggo.nl \
--to=ntg-context@ntg.nl \
--cc=havdmeer@ziggo.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).