From: Bruce Horrocks <ntg@scorecrow.com>
To: ntg-context mailing list <ntg-context@ntg.nl>
Subject: [NTG-context] Re: XML processing, unwanted indentation/alignment
Date: Thu, 15 Feb 2024 23:34:45 +0000 [thread overview]
Message-ID: <C6B8D171-A2F4-4060-B297-0986B0C6D4B5@scorecrow.com> (raw)
In-Reply-To: <CAL-A5LYre0jNp+=2e3FFST__2g1rU19YtTuGLAchiX0u=o7VHg@mail.gmail.com>
The extra space is because you have a space between {first_name} and {\xmlatt... on line 9 of xml.tex.
> On 15 Feb 2024, at 20:28, Michael Guravage <guravage@literatesolutions.com> wrote:
>
> Greetings,
>
> I'm typesetting an address book whose addresses are in XML. A typical entry has this structure:
>
> <family surname="">
> <address street="" housenumber="" postcode="1" city="" telephone="" />
> <members>
> <member first_name="" initials="" maiden_name="" birthday="" email="" mobile="" />
> <member first_name="" initials="" birthday="" email="" mobile="" />
> <member first_name="" initials="" birthday="" />
> </members>
> </family>
>
> initials and birthday are required, first_name can be left blank and email, mobile and maiden_name are optional.
>
> I've written a macro (name) to compose the name, i.e. initials, first_name (maiden_name), and another macro (nameemaillink) to make the name a link associated with an email address.
>
> % Derive an individual's name
> \def\name#1%
> {\ifxmlattempty{#1}{first_name} {\xmlatt{#1}{initials}} \else {\xmlatt{#1}{initials}, \xmlatt{#1}{first_name}} \fi
%%%% Remove the space after {first_name} here
> \ifxmlattempty{#1}{maiden_name} {} \else { \tfxx(\xmlatt{#1}{maiden_name})} \fi}
>
> % Create a mailto:link that associates a individual's name with their email address.
> \def\nameemaillink#1%
> {\ifxmlattempty{#1}{email} {\name{#1}} \else {\goto{\name{#1}} [url(mailto:\xmlatt{#1}{email})]} \fi}
>
> I thought I was done when I noticed that a composed name with an empty first name, with or without an email address, is slightly indented. In the mwe Moe and Curly, without first names, are indented; while Shemp and Michael aren't.
>
> That the undesired indentation/alignment is dependent on the presence of a first name is baffling. After this long description, if someone would look at the code and tell me where I've gone wrong I would be very grateful. The interesting bits begin on lines 8 and 12 in xml.tex.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-02-15 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 20:28 [NTG-context] " Michael Guravage
2024-02-15 21:03 ` [NTG-context] " Wolfgang Schuster
2024-02-15 23:34 ` Bruce Horrocks [this message]
2024-02-16 8:32 ` Taco Hoekwater
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=C6B8D171-A2F4-4060-B297-0986B0C6D4B5@scorecrow.com \
--to=ntg@scorecrow.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).