[horde] Fwd: Re: German translation lost with Firefox 10

[Gunnar Wrobel]

--
Core Developer

The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de



Gunnar Wrobel <wrobel at pardus.de> schrieb:





Jan Schneider <jan at horde.org> schrieb:

>
>Zitat von lst_hoe02 at kwsoft.de:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>>
>>> Zitat von lst_hoe02 at kwsoft.de:
>>>
>>>> Quoting Jan Schneider <jan at horde.org>:
>>>>
>>>>>
>>>>> Zitat von Vilius ?umskas <vilius at lnk.lt>:
>>>>>
>>>>>>> Zitat von Vilius ?umskas <vilius at lnk.lt>:
>>>>>>>
>>>>>>>>> Am 01.02.2012 13:29, schrieb lst_hoe02 at kwsoft.de:
>>>>>>>>>> So what is the reason that Horde/IMP is english only when
>used with
>>>>>>>>>> Firefox 10/IE9, but german as it should when accessed with 
>>>>>>>>>> Firefox <10
>>>>>>>>>> or IE <9 from the same client machine??? Does Horde not
>recognize the
>>>>>>>>>> language setting in the latest Browsers and if yes how can 
>>>>>>>>>> it be fixed?
>>>>>>>>>
>>>>>>>>> Have had the same Problem as IE9 was released. Added the
>ISO-8859-1
>>>>>>>>> locales on my server and the problem was gone. Before, there
>were just
>>>>>>>>> the UTF locales on the Server.
>>>>>>>>
>>>>>>>> I think that the main confusion is related to Horde_Browser
>library
>>>>>>>> which doesn't know about FF10 and didn't know about IE9 before
>Horde
>>>>>>>> 4 was released. Or better to say, UTF is not enabled for these
>>>>>>>> browsers. I remember submiting a patch for IE9 personally in
>CVS
>>>>>>>> during H4 development. I'm not sure how this relates to
>translations
>>>>>>>> and Accept-Language directive though.
>>>>>>>
>>>>>>> IE is a different story because it never sent an Accept-Charset
>>>>>>> header. Firefox/Mozilla/Netscape always did this. If it stops
>doing
>>>>>>> this now, this is a major break.
>>>>>>
>>>>>> Seems like so:
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=572652
>>>>>
>>>>> Yes, just found that ticket too. Looks like they only notified 
>>>>> Yahoo about removing that header. Great work.
>>>>> I'm going to release Horde_Browser with a fix for that.
>>>>>
>>>>> Jan.
>>>>
>>>> So the fix will be to rely per default on browsers supporting UTF-8
>no?
>>>
>>> Well, now that I think of it, this shouldn't be a problem in Horde 
>>> 4 anyway, because we already *do* require UTF-8 browser and server 
>>> support there. So is there anybody seeing this issue in Horde 4 or 
>>> is this only Horde 3?
>>
>> Any chance to get this fixed in Horde 3??
>>
>> Thanks
>>
>> Andreas
>
>I linked to the commit, the patch is small enough to apply it 
>manually. Horde 3 isn't receiving any bug fixes anymore.

If somehow possible we should however have a point of reference concerning this problem. This should help downstream vendors that want to continue to offer solutions based on Horde 3 to include the fix.

Cheers,

Gunnar

>
>Jan.
>
>-- 
>Do you need professional PHP or Horde consulting?
>http://horde.org/consulting/
>
>-- 
>Horde mailing list
>Frequently Asked Questions: http://horde.org/faq/
>To unsubscribe, mail: horde-unsubscribe at lists.horde.org

--
Core Developer

The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de