Werner LEMBERG wrote in <20180802.162932.2121529583718521640...@gnu.org>:
|> There appears to be specific code in groff to explicitly *BREAK* the
|> return value of wcwidth(3). Actually, egregious mishandling of
|> wcwidth(3) is a quite common error in application programs, so groff
|> is cert
> There appears to be specific code in groff to explicitly *BREAK* the
> return value of wcwidth(3). Actually, egregious mishandling of
> wcwidth(3) is a quite common error in application programs, so groff
> is certainly not alone here.
Well... :-)
> I'm not familiar with groff internals eith
Hi Robin,
Robin Haberkorn wrote on Thu, Aug 02, 2018 at 07:47:35PM +0600:
> But for the rest of glyphs, it should IMHO a) make sure that
> accentuation glyphs have a zero-width
There appears to be specific code in groff to explicitly *BREAK*
the return value of wcwidth(3). Actually, egregious m
> I tried adding a line like
>
> u0301 0 0 0xCC81
>
> to the R font for devutf8. But it doesn't work.
Right idea, wrong code point :-) See my other e-mail.
Werner
Hi Robin,
> I tried adding a line like
> u0301 0 0 0xCC81
> to the R font for devutf8. But it doesn't work. How does grotty
> interpret the code? They are obviously not simply UTF-8 bytes.
groff_font(5) explains the format under `charset'.
You've put `0xCC81' because it's the UTF-8 for U+030
> It boils down to persuading `\w', used by tbl(1), that the U+0301 takes
> no space.
>
> $ groff -Tutf8 >/dev/null
> .nr w \w'A'
> .tm \nw
> 24
> .nr w \w'\[u0435]'
> .tm \nw
> 24
> .nr w \w'\[u0435]\[u0301]'
> .tm \nw
> 48
> $
I
Hello Ralph!
I see! Groff seems to combine composites to single code points if possible,
probably in order to better support terminals and/or software that cannot
themselves combine them. Makes sense.
But for the rest of glyphs, it should IMHO a) make sure that accentuation glyphs
have a zero-widt
Hello Robin!
> Currently, I'm just adding a standalone UTF composite accent character
> (U+0301) after every vowel I want to show stress on since Unicode does
> not seem to define separate codepoints for all of the Cyrillic
> accented vowels.
That's the recommendation in
https://en.wikipedia.org/
