ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Correct usage of hash symbol in url / new upload
Date: Sun, 27 Aug 2023 13:52:07 +0200	[thread overview]
Message-ID: <e5819f53-dfb2-6e7a-04b6-8f60b7d0b6b3@freedom.nl> (raw)
In-Reply-To: <ZRAP278MB0495250B92D776D9493C540C83E3A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM>

Hi Denis,

> I need to process URLs in XML documents differently depending on the target. Thanks to Hans and Thomas I can now deal with the attributes.
> Now I need to prefix certain kind of targets with a certain URL (a web viewer for IIIF images in this particular case). The prefix contains a #, which, as a special character seems to cause an error. Adding a double hash seems to work, but those ## will end up in the link URL. How can I properly escape a single #? I've already tried using \Ux{23}, but that won't work either.
The duplication of hashes is kind of special. Consider this:

\def\foo#1{#1 test ##}

\def\foo#1{#1 test\def\more##1{(##1)}}

the internal representation of #1 is a reference to parameter 1 while 
the ## becomes one # (cc parameter) in the second exmaple followed by a 
character 1 (cc other)

then, when tex serializes e.g. in tracing it duplicates the hash (with 
cc parameter) so that the user is not confused (an alternative could 
have been to indicate a parameter reference differently but changing 
that now is no real option - what symbol to use anyway?)

with lua(meta)tex opening up matters this duplication becomes a bit 
annoying so i decided to see if it could be avoided in some cases

first i decided to provide an escape, possible because we already have 
such mechanism using # (not advertised because it is still experimental)

then i decided to just not duplicate unless we trace

in the lowlevel macro manual there is a section added that goes in more 

to come back to the escaping: here is a list:

#I  loop iteraor
#P  parent loop iterator
#G  grandparent loop iterator

#H  hash
#S  space (ascii 32)
#T  tab \t
#L  newline \n
#R  return \r
#X  backslash


#N nbsp

and some more. Keep in mind that #1-#9 #A-#E are in use as parameter 

but in the case of your url's escaping should not be needed (hopefully)


ps. all kind of expereimental because it's a bit hairy and we don't want 
to loose compatibility (hashes get interpreted in the macro preamble, 
macro body, running text, serialization etc)

                                           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

      parent reply	other threads:[~2023-08-27 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  8:16 [NTG-context] XML: Correct usage of hash symbol in url denis.maier
2023-08-25  8:35 ` [NTG-context] " Hans Hagen via ntg-context
2023-08-27 11:52 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5819f53-dfb2-6e7a-04b6-8f60b7d0b6b3@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \


* 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