Tickets :: [#10823] horde-translation locale and env inconsistency

6.0.0-alpha12

6/17/25

Summary	horde-translation locale and env inconsistency
Queue	Horde Base
Queue Version	4.0.12
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	maciej.uhlig (at) us (dot) edu (dot) pl
Created	12/01/2011 (4947 days ago)
Due
Updated	12/01/2011 (4947 days ago)
Assigned	12/01/2011 (4947 days ago)
Resolved	12/01/2011 (4947 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/01/2011 11:25:53 PM	Jan Schneider	Comment #6 State ⇒ Not A Bug	Reply to this comment
No, there is a reason that enforce English locales here. And I don't think it's expecting too much that a system has English locales installed. I didn't even know it's possible to not have one.

12/01/2011 09:58:13 PM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #5	Reply to this comment
I don't understand, what's wrong with that? Don't you have en locales installed? Right. en locales aren't installed. Still, LANG value shouldn't be hardcoded; it rather should be a parameter.

12/01/2011 12:47:58 PM	Jan Schneider	Comment #4 State ⇒ Feedback	Reply to this comment
That's not an answer to my questions.

12/01/2011 10:35:13 AM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #3	Reply to this comment
I feel the wrong thing is the need of manual edit of horde-translation script (which could be read-only) in order to get rid of the gettext error. You shouldn't edit source while you could use a script parameter.

12/01/2011 10:23:48 AM	Jan Schneider	Comment #2	Reply to this comment
I don't understand, what's wrong with that? Don't you have en locales installed?

12/01/2011 08:04:20 AM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ horde-translation locale and env inconsistency Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
There is putenv('LANG=en'); line in horde-translation script. LANG value is hardcoded. While running the script with locale=pl_PL option, every exec of gettext produces a message "couldn't set locale correctly". The error message disappears when the above script line is changed to putenv('LANG=pl_PL'); but this can't be an accepted solution. If environment variable has to be set it should be set using script locale option in order to gettext could get the consistent information.