Tickets :: [#2325] Translations are not efficiently used

6.0.0-beta1

7/17/25

Summary	Translations are not efficiently used
Queue	Horde Base
Queue Version	HEAD
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	thv (at) iki (dot) fi
Created	07/24/2005 (7298 days ago)
Due
Updated	07/25/2005 (7297 days ago)
Assigned
Resolved	07/24/2005 (7298 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/25/2005 07:50:08 AM	Jan Schneider	Comment #6	Reply to this comment
It is bogus because it can't be and won't be changed. What does make sense though is to seperate LC_MESSAGE locales from the other locale categories, if this is what you are looking for. Noone needed this before; if you do, create a new ehancement ticket for this. What's the difference between sv_FI and fi_FI locales anyway?

07/24/2005 08:24:39 PM	thv (at) iki (dot) fi	Comment #5	Reply to this comment
So what is actually the problem? Why does Horde make difference between for example Finnish as spoken in Finland and Finnish when spoken outside Finland. The language is same, Finnish. It doesn't matter where it is spoken, same language. Of course this is not the case in every language, e.g. en_US and en_GB are little different. As long as Finnish (still just one example) speaking people living outside Finland has to use wrong locale settings to get Horde work, it is a problem with Horde even though the original bug might be elsewhere. Clearly this is not bogus report.

07/24/2005 07:21:19 PM	Jan Schneider	Comment #4	Reply to this comment
The PHP gettext extension? The gettext library? Apache? OS? Anything but Horde.

07/24/2005 05:50:25 PM	thv (at) iki (dot) fi	Comment #3	Reply to this comment
This bug is not bogus, it should be moved to component where there is this technical bug that demands country code. What is the component which has those 'technical issues'?

07/24/2005 01:46:29 PM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
The reason that we use the full language/country locales is a technical one. Gettext (at least with PHP, I can't tell for other programming languages) works far more stable and on more systems if not using language-only locales.

07/24/2005 11:26:34 AM	thv (at) iki (dot) fi	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Translations are not efficiently used Queue ⇒ Horde Base New Attachment: po_README.patch	Reply to this comment
Currently Horde's translation has always country code. This means inefficient use of translations. For example in Finland there is approximately 500.000 people are using locale sv_FI but are speaking Swedish. Thus the sv_SE translation works okay for them. And similar is that Finnish translation should be named as fi.po instead of fi_FI.po because of approximately 100.000 finnish speaking people living in Sweden. This is also true for many other translations, but I'm not sure which ones. I've attached a fix for README residing in po directory which currently guides to wrong naming of translations. Also translators should be contacted to verify or fix that they are using correct filename for their translations.