Encodings, encodings. What would we do without those headaches I wonder. This concerns only Windows AFAIK.
I found that in multiline tables (using styles "grid" or "multiline"), strings are not encoded consistently; if there is a line feed (\n), things are fine. But when there is none, things go wrong:
The string in the upper right cell is encoded in latin1, in accordance with my locale setting, but the one on the bottom right is is actually encoded in UTF-8 (but interpreted as latin1).
Now by simply adding a \n at the end of the bottom string, we get consistent results:
Encodings, encodings. What would we do without those headaches I wonder. This concerns only Windows AFAIK.
I found that in multiline tables (using styles "grid" or "multiline"), strings are not encoded consistently; if there is a line feed (
\n
), things are fine. But when there is none, things go wrong:The string in the upper right cell is encoded in latin1, in accordance with my locale setting, but the one on the bottom right is is actually encoded in UTF-8 (but interpreted as latin1).
Now by simply adding a
\n
at the end of the bottom string, we get consistent results:Both strings are properly encoded in latin1. Unfortunately, since I can't build pander (neither on Windows nor on Linux), I can't debug it. :\