From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Ambiguous grammar: unicode vs. \[uX] escapes
Date: Wed, 01 Oct 2014 16:51:13 +0200 [thread overview]
Message-ID: <542C14E1.3040700@bsd.lv> (raw)
In adding diacriticals to the shiny new MathML output, I stumbled across
a curious ambiguity.
Basically, I wanted the following sequence:
{ a sub b } under
Which in eqn(7), means a_b with a line under it all.
In the new eqn.c, I have a special "bottom" string I set to a
corresponding under-diacritical. (The others have a "top" string.) I
was setting this to \[ul], underscore. However, the character refused
to appear.
Mystified, I explored further. Then I saw that in print_encode()
(html.c), the \[ul] was being detected as a Unicode codepoint. Why?
Because the sequence is \[uxxx] (mandoc.c:88).
Is there any consensus on how we should handle this? groff_char(7)
doesn't say anything, but I'm guessing the Unicode codepoints should be
4--6 hexdigits long. That's an easy fix, but I'm not sure if it's the
right approach.
Thoughts?
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-10-01 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 14:51 Kristaps Dzonsons [this message]
2014-10-03 16:18 ` Ingo Schwarze
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=542C14E1.3040700@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.bsd.lv \
/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).