Thus spake Ken Hornstein: > > Your problem is probably the same one I ran into; isspace() would interpret > 0xA0 as a non-breaking space and replace it with a "real" space, messing > up UTF-8 sequences. > > This isn't perfect; in a perfect world you'd pull in the bytes and call > wcwidth() on each Unicode character, but it works good enough for me in > practice.
Thanks for the explanation. I intend to have a look at par again soonish and try to get it right with multibyte characters once and for all. -- J. _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
