6.0.0-alpha12
6/12/25

[#11107] localized access key problem
Summary localized access key problem
Queue Horde Groupware
Queue Version 4.0
Type Bug
State No Feedback
Priority 2. Medium
Owners
Requester leena.heino (at) uta (dot) fi
Created 03/27/2012 (4825 days ago)
Due
Updated 04/27/2012 (4794 days ago)
Assigned 04/05/2012 (4816 days ago)
Resolved 04/27/2012 (4794 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/27/2012 09:15:13 AM Jan Schneider State ⇒ No Feedback
 
04/07/2012 10:56:03 AM leena (dot) heino (at) uta (dot) fi Comment #9 Reply to this comment
The 'emails' setting in nls.php. It's even documented.
Ok. Thanks. I'll test that setting.
04/07/2012 10:12:24 AM Jan Schneider Comment #8 Reply to this comment
The problem is that we have to force the locale to use UTF-8 by
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
Why?
Are the any other way to force that all messages are sent using 
UTF-8 charset?
The 'emails' setting in nls.php. It's even documented.
04/06/2012 09:38:25 PM leena (dot) heino (at) uta (dot) fi Comment #7 Reply to this comment
The problem is that we have to force the locale to use UTF-8 by
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
Why?
Are the any other way to force that all messages are sent using UTF-8 charset?

Our users sent messages that contain texts that would have to be coded 
in different charset. Only way to send these messages is to use UTF-8 
charset.
04/06/2012 09:20:58 PM Jan Schneider Comment #6 Reply to this comment
The problem is that we have to force the locale to use UTF-8 by 
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
Why?
04/06/2012 08:44:51 PM leena (dot) heino (at) uta (dot) fi Comment #5 Reply to this comment
The problem is that we have to force the locale to use UTF-8 by 
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';

This results that characters are stripped from labels in this piece of code:
return preg_replace('/_([A-Za-z])/', 
$GLOBALS['registry']->nlsconfig->curr_multibyte && 
preg_match('/[\x80-\xff]/', $label) ? '' : '\1', $label);

Which I believe does this: If the translated label contains 8bit 
character and the locale uses multibyte charset eg. UTF-8 then remove 
any character after the underscore.

Stripping blindly the next character after the underscore results 
labels where a character is missing and might even break the resulting 
label if the desired access key is not a ascii character.
04/06/2012 11:39:16 AM Jan Schneider Comment #4 Reply to this comment
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?
04/05/2012 06:56:54 PM leena (dot) heino (at) uta (dot) fi Comment #3 Reply to this comment
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
2.  Localized access key characters are stripped from the string.

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

Why we use UTF-8 used instead of the default iso-8859-1? 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.
04/05/2012 04:56:06 PM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
I don't see this. But version 4.0 is really outdated anyway.
03/27/2012 08:32:21 AM leena (dot) heino (at) uta (dot) fi Comment #1
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Horde Groupware
Summary ⇒ localized access key problem
Type ⇒ Bug
Priority ⇒ 2. Medium
Reply to this comment
I have translated string:
msgid "Alerts _Log"
msgstr "Hälytys_loki"

Then I have this shown in the program as:
"Hälytysoki(l)"

Note that the letter l is now missing from translated the string: 
"loki" vs "oki(l)"

Saved Queries