[Tickets #11107] Re: localized access key problem

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11107
------------------------------------------------------------------------------
  Ticket             | 11107
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | localized access key problem
  Queue              | Horde Groupware
  Version            | 4.0
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2012-04-06 13:39) wrote:

>> I don't see this. But version 4.0 is really outdated anyway.
>
> The actual version is 4.0.15-git.
>
> In order for reproduce this:
> 1.  Enable UTF-8 to you locale

No idea what you mean with that. Installing UTF-8 locales? Without  
that, Horde translations won't work at all anyway.

> 2.  Localized access key characters are stripped from the string.

Sorry?

> The problem or feature lies within the file:  
> horde/framework/Core/lib/Horde.php
> in function: stripAccessKey

Which problem? This method removes the underscore from labels.

> Why we use UTF-8 used instead of the default iso-8859-1?

Because there is no reason *not* to use UTF-8. Horde 4 is completely  
using UTF-8 internally and externally and requires UTF-8 support both  
on the server side and client side, which is fortunately not a problem  
anymore in 2012.

> Our users use may choose to use english or finnish interface but  
> write letters that contain finnish characters (needs iso-8859-1)  
> with euro character (needs iso-8859-15) and eg. some cyrillic  
> letters (KOI8-R).
> Only way to include all of these different character sets  in a  
> single message is to use UTF-8 as charset.

What does this have to do access keys?