ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How do I get an empty line in a \framed[align=flushleft]{} item?
Date: Fri, 1 May 2020 13:45:00 +0200	[thread overview]
Message-ID: <F52CE49F-FF8E-422B-B263-36DBCBD063B3@rna.nl> (raw)
In-Reply-To: <3796d44c-7926-4da1-6cbb-cbbfc80c8cbe@xs4all.nl>



> On 1 May 2020, at 13:28, Hans Hagen <j.hagen@xs4all.nl> wrote:
> 
> On 5/1/2020 10:21 AM, Gerben Wierda wrote:
>> code it back to a \ ? E.g. something like
>>    { ‘\U{XXX}', '\' },
> \utfchar{100}
> \Uchar 100

Yes, but the question was: how do I code this in the XML and get it through my XML-lua-METAPOST-textext() path so that e.g. &#xB; or &#14; in the XML end up as \ in my textext() string?

E.g. a &#xA; in XML becomes a \n when lmtx XML handling has read the XML (so gets transformed on read). I’ve been thinking about the route &#xD; -> \r -> \ (so, misusing \r to code a TeX-\ in the XML, but that would probably not robust.

The question is more: what is a good UTF8 character to use (the first 32 would be good candidates if they would work and end in the strings that xml.foo() of lmtx produces).

G

> 
> -----------------------------------------------------------------
>                                          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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-05-01 11:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 20:47 Gerben Wierda
2020-04-30 20:51 ` Henning Hraban Ramm
2020-04-30 23:07   ` Gerben Wierda
2020-04-30 20:54 ` Wolfgang Schuster
2020-04-30 21:26   ` Gerben Wierda
2020-04-30 23:44   ` Gerben Wierda
2020-05-01  7:38     ` Hans Hagen
2020-05-01  8:21       ` Gerben Wierda
2020-05-01 11:28         ` Hans Hagen
2020-05-01 11:45           ` Gerben Wierda [this message]
2020-05-01 11:58             ` Hans Hagen
2020-05-01 12:00             ` Hans Hagen

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=F52CE49F-FF8E-422B-B263-36DBCBD063B3@rna.nl \
    --to=gerben.wierda@rna.nl \
    --cc=j.hagen@xs4all.nl \
    --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).