> I think the best thing to do is to have a langhook then. It seems a bit weird to have a langhook for a one-character difference, but if there's a consensus on it, I'll go along.
> Endianness issues may also appear. Maybe you should call iconv in the > langhook to get back to UTF-8, and print that representation instead. Endianness is already take care of, in the sense that the string is encoded in the target's endianness already. However, that makes calling iconv more difficult, because that has us going from target's endianness to UTF-8, which will be a pain. As only developers do read tree dumps, I think having a lot of \0 in them is fine. FX -- FX Coudert http://www.homepages.ucl.ac.uk/~uccafco/
