> 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 either (except for the manual
> page macroset implementations), but i had a quick look and instantly
> identified at least three places where wcwidth(3) handling is
> obviously broken, see the patch below. That patch is *NOT* intended
> for commit, but merely for giving others some hints in which areas
> to look.
Thanks. Unfortunately, I don't have time to delve into the code,
sorry.
Werner
