From: Klaus W. <Kla...@gm...> - 2006-07-23 16:06:07
|
Hello, I am not sure if I understood the problem right. Is it just problem you hav= e=20 on some systems or browsers how the pages are displayed? Have you thought=20 about that different browsers could have installed different default=20 encodings. As far as I could see on a quick view there gets not character=20 encoding transmitted from BackupPC, so that the browsers default will be us= ed=20 and that could be different from what BackupPC actually sends. Seems there = is=20 no line like "<meta http-equiv=3D"Content-Type" content=3D"text/html;=20 charset=3DUTF-8"/>" in the <head> tag of the html files. Or maybe you can a= lso=20 have a problem that the webserver sends a default encoding that overrides=20 others, like you can configure in Apache2? Just a few thoughts. Maybe it helps. I am looking forward to the next pre releases of BackupPC3.0.0! It looks go= od=20 so far. Regards, Klaus > > > I was planning to convert, but I believe it is correct the > > > way it is. Perl parses the language files as iso-latin, > > > and internally converts the strings automatically to utf8 > > > via the utf8 output filter. > > > > > > Do the french strings in 3.0.0beta0 render correctly for > > > you? They do for me. > > > > I'm confused... I have two BackupPC servers, one with my patch and one > > without and both render fine in Safari/OSX. I think that my problem was > > with Firefox on Windows. Give me some days and I'll try to figure it > > out. > > I'm using Firefox on Windows and it works for me. But it > certainly could be dependent upon perl versions, LANG settings > etc. =2D-=20 take care! xo,klaus |