Tickets :: [#10861] Application preferences page not fully translated

6.0.0-beta1

7/4/25

Summary	Application preferences page not fully translated
Queue	Horde Base
Queue Version	4.0.12
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	maciej.uhlig (at) us (dot) edu (dot) pl
Created	12/14/2011 (4951 days ago)
Due
Updated	12/14/2011 (4951 days ago)
Assigned	12/14/2011 (4951 days ago)
Resolved	12/14/2011 (4951 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/14/2011 02:23:55 PM	Jan Schneider	Comment #6 State ⇒ Not A Bug	Reply to this comment
Through magic :) No, really, if you want to learn more about how translations work in Horde, ask on the mailing list.

12/14/2011 02:10:38 PM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #5	Reply to this comment
That's perfectly fine, all applications contain the translations from the horde domain. How is it possible? These texts aren't present in imp.po file... Is it a matter of configuration which I'm possibly missing?

12/14/2011 02:03:28 PM	Jan Schneider	Comment #4	Reply to this comment
Those translations are in the "horde" domain, and the "horde" domain is active when the template is loaded. No, it isn't. The application domain (e.g. imp) is obviously active. That's perfectly fine, all applications contain the translations from the horde domain.

12/14/2011 01:43:37 PM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #3	Reply to this comment
Those translations are in the "horde" domain, and the "horde" domain is active when the template is loaded. No, it isn't. The application domain (e.g. imp) is obviously active. What makes you think that this is not the case? The following code (in previously indicated place): $td = textdomain(''); echo $td; textdomain('horde'); produces the following result: imp and then the texts are correctly translated. Needless to say, those translations work perfectly fine for me. Sorry. Not here.

12/14/2011 01:22:11 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Those translations are in the "horde" domain, and the "horde" domain is active when the template is loaded. What makes you think that this is not the case? Needless to say, those translations work perfectly fine for me.

12/14/2011 01:09:54 PM	maciej (dot) uhlig (at) us (dot) edu (dot) pl	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Application preferences page not fully translated Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Problem: some texts on application preferences page aren't translated. These are: "Show Advanced Preferences", "Hide Advanced Preferences", "Edit Preferences for". Reason: /pear/php/Horde/Core/Prefs/Ui.php script works in 'Horde_Core' domain and uses Horde framework translation method. However, the above texts should be translated in 'horde' domain. These aren't present in Horde framework. Workaround: add textdomain('horde'); after $t->set('header',...... line. Fix: I'm not able to propose the proper one, leaving this to the author.