On Fri, 2003-09-12 at 15:09, Adam Williamson wrote: > On Fri, 2003-09-12 at 14:34, Frederic Crozat wrote: > > On Fri, 12 Sep 2003 14:22:17 +0100, Adam Williamson wrote: > > > > > On Fri, 2003-09-12 at 14:11, Frederic Crozat wrote: > > >> On Fri, 12 Sep 2003 14:07:03 +0100, Adam Williamson wrote: > > >> > > >> > Since Galeon went up to 1.3.8, it seems to have trouble rendering a lot > > >> > of characters it could deal with before...just one example, the UK pound > > >> > sterling currency sign - � - is rendered as one of those little boxes > > >> > with the character code numbers in it, as are a bunch of other signs > > >> > it's always been able to display before. I have my encoding set to > > >> > Unicode (UTF-8). Fred? > > >> > > >> Testcase ? > > > > > > Yeah, hang on, here's a couple... > > > > > > http://mikesbballrants.blogspot.com/ > > > > > > Look at the end of the first entry (the paragraph starting "The first > > > person these criteria...". I see non-rendered characters after these > > > bits of text: > > > > > > "2.53 ERA while pitching 24" > > > "count 'em 24!" > > > "voted for Norris in a heartbeat" > > > "To be continued" > > > > > > http://forums.sudhian.com/messageview.cfm?catid=43&threadid=42566 > > > > > > Look at the post from "ciqala", I see a non-rendered character before > > > this text: > > > > > > "700 for the case plus shipping" > > > > > > which I think is meant to be a pound sign. > > > > No problem here.. Make sure you don't have a strange encoding selected.. > > Well, see first post, it's set to Unicode (UTF-8). I haven't changed any > settings at all since upgrading. Let me go and play with it a bit...
Okay, further. Changing my encoding to Western European doesn't fix it. Moving ~/.galeon away doesn't fix it. Anything else to try? It's also not a font problem, as I tried a couple of alternatives with the same result. I use the Vera fonts. -- adamw
