On Wed, Aug 22, 2007 at 01:38:59PM +0300, Juha Tuuna wrote: > On Wednesday, 22. August 2007 13:29, Haines Brown wrote: > > I'm not sure when this problem came up, but perhaps when I upgraded to > > etch. Put simply, my browsers no longer can display accented > > characters. > > > > For example, I create a little test file with a and u umlaut and e > > ecute: > > > > This is a test > > ?? ?? ?? > > > > Xterm can display them, but in galeon and iceweasal they are broken: > > > > This is a test > > ???? ???? ???? > > > > I try to use the browser defaults, and the default for both browsers > > is "serif". I'm not sure what my system interprets that as (Times New > > Roman?), but I'd assume it is with a font that supports normal > > accented characters.
And then you _may_ need to tell the browser to use UTF-8 Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
