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 |
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
UTF-8 charset?
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
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.
defining it in horde/config/nls.local.php:
$horde_nls_config['charsets'] ['fi_FI'] = 'UTF-8';
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.
In order for reproduce this:
1. Enable UTF-8 to you locale
that, Horde translations won't work at all anyway.
horde/framework/Core/lib/Horde.php
in function: stripAccessKey
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.
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.
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.
State ⇒ Feedback
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Horde Groupware
Summary ⇒ localized access key problem
Type ⇒ Bug
Priority ⇒ 2. Medium
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)"