Hi, On Thu, Oct 30, 2008 at 05:08:02PM +0100, Gerfried Fuchs wrote:
> Please take a look at these two outputs: > > $> export LANG=C > $> echo 'here is a german umlaut o: ö' | netrik - > here is a german umlaut o: รถ > > versus > > $> export LANG=de_AT.UTF-8 > $> echo 'here is a german umlaut o: ö' | netrik - > here is a german umlaut o: M-v > > Please notice that you can use any utf8 locale, it's just that I have > de_AT.UTF-8 locally enabled. > > I did build me a local test build with the attached straight-forward > patch and it worked for me. Please notice that the very same problem has > affected pal already, see #499403 for a reference of the issue. After > patching it with the attached diff and recompiling I was able to saw the > ö correctly with both locales. Note that netrik doesn't really do the right thing with your test in either case: It won't produce the right character when actually run on an UTF-8 terminal... (The problem is that netrik is totally unaware of utf8, or any charsets in fact, and will always try to output the entities as iso-8859-1 -- which is obviously wrong when using a different locale.) What your test case does show though is that ncurses now escapes any non-ASCII codes when running in a UTF-8 locale, while using ncursesw restores the old behaviour of simply passing through the extended codes. This is an important fix indeed, as it is required to keep netrik at least somewhat working in the common situation of viewing a UTF-8 page on a UTF-8 terminal. (There are many other problems though: Aside from the broken entities, screen positions are miscalculated, resulting in misplaced link highlights and stray characters at line ends. Also, if the input charset differs from the terminal charset, things won't work at all. All this requires proper charset support to fix, which is on the top of my ToDo list. However, I'm still not sure how to implement this, so I doubt I could do it in time for lenny, even if the release managers would actually accept such a late change...) -antrik- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
