Re: [Bashburn-info] Update on display problem.
Brought to you by:
bashburn
From: Nick W. <ni...@uk...> - 2008-10-11 18:32:53
|
On Sat, 11 Oct 2008 15:28:50 +0200 Anders Lindén <and...@gm...> wrote: > lör 2008-10-11 klockan 08:06 +0100 skrev Nick Warne: > > On Fri, 10 Oct 2008 21:19:16 -0400 (EDT) > > "Steven W. Orr" <st...@sy...> wrote: > > > > > There are two programs that I'm using to look at the problem. > > > > > > xlsfonts # Used to display the list of all fonts > > > xfd # to display the characters in a font. > > > > > > I took a look at a large font at random. > > > > > > xfd -fn > > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9' > > > > > > and it's clear that you can see all of the funny characters. > > > > > > Then I started an xterm using that font. > > > > > > xterm -font > > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9' > > > > > > Then from that xterm, I run bashburn. I switch from English to > > > Swedish and the problem still persists. > > > > > > So, my question is this: Why do we think that the encoding we're > > > using is even correct in the first place? > > > > > > If someone can show me a program that's written in anything that > > > displays these characters then I can get this solved. > > > > I still think the Sewdish lang files have extraenous control chars > > in it. > > > > Consider this: > > > > echo "Ångra Ändringar" > > > > (Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the file?) > > > > Works fine. So does changing these in Swedish lang file. > > > > Nick > > I noticed that the Swedish configure.lang is not in utf-8 but in > 'Non-ISO extended-ASCII'. Running the config menu now just gives me a > question mark in a circle where the Swedish characters should be (And > settings are still misaligned). > I created a new configure.lang where I just wrote down the menu text > and saved it in utf-8. Then all Swedish characters displayed > correctly (But again, things are still misaligned). > > I'm starting to think maybe it's not worth spending too much time with > this issue. It's not like it breaks anything and we're going to > replace the translation system anyway. Or will this issue still > appear when we gettextifies BashBurn? Thoughts? > > OK, what editor do you use - in fact, what distro do you use? Could it be some mangling on saving the file? I use Nano BTW -> http://www.nano-editor.org/ Nick -- Free Software Foundation Associate Member 5508 |