Re: Allowing \N to accept hex numbers?

[Dorai Sitaram]

 I'm trying to access a code point in a non-Unicode font, namely the ITC Zapf 
Dingbats font that comes with groff. E.g., the code point 0x6E in Dingbats is a 
black square, and so far I see no way of using the hex number directly to 
typeset a black square. I have to convert it to 110 decimal, e.g., 
\f(ZD\N'110'\fP.

Following your message, I tried using \f(ZD\[u006E]\fP, but no dice. U+006E is 
of course n, and groff tries to find "special character \n", even though the 
prevailing font when \[u006E] is being invoked is a non-Unicode font.

--d

     On Sunday, January 17, 2021, 05:46:30 PM EST, Oliver Corff 
<oliver.corff@email.de> wrote:  
 
 Hi Dorai,

is there any constraint that forces you to use \N, or can you use other
expressions as well? In that case, \[uxxxx] might be the desired answer
for you, where xxxx is a hex representation of a Unicode code point.

Oliver.


On 17/01/2021 19:34, Dorai Sitaram wrote:
> \N'num' takes a number num and typesets the glyph corresponding to the code 
> point num in the prevailing font. Currently, num can only be in decimal 
> format. Is there a downside to allowing hex numbers, with the usual 
> distinguishing prefix 0x?
>
> --d
>