I18n labels not picked up?

[rickard]

Hi,
I'm doing a Swedish I18n of version 3.01_GA_160.FC4 and have noticed that translations are not picked up in at least two places;

1) When you add a new contact, the headings 'Email', 'Work', 'Home', 'Other' and 'Notes' are not translated.

2) When you create a recurring meeting that for instance happens every day for three days, the text on both the web and in the invitation e-mail sent to the participants says 'Every xxx for nn xxx effective', where the 'xxx' is translated but not the words 'Every' and 'effective'.

I can't find references to this in your bugzilla, but maybe I just don't know my way around yet..?

Thanks
Rickard

[KevinH]

Did you translate both the AjxMsg and ZmMsg files?

[rickard]

Yes, and I also tried the Finnish translation posted here before with the same result.

Rickard

[StefanD]

I think it's hard-coded, not 100% sure but I think in the file:
/opt/zimbra/tomcat/webapps/zimbra/js/zimbraMail/abook/view/ZmContactView.js
at line 546, 547,548,549

[StefanD]

Originally Posted by StefanD

I think it's hard-coded, not 100% sure but I think in the file:
/opt/zimbra/tomcat/webapps/zimbra/js/zimbraMail/abook/view/ZmContactView.js
at line 546, 547,548,549

There is also line #356. All these text is hard coded between html code.
Also there is a lot of hard coded text in
/opt/zimbra/tomcat/webapps/zimbra/js/zimbraMail/abook/view/ZmContactSplitView.js

[KevinH]

Yep sure looks like it. Would you mind filing a bug in bugzilla with that info?

[StefanD]

ok, bugzilla# 6471
http://bugzilla.zimbra.com/show_bug.cgi?id=6471

[rickard]

Thanks guys.

Can you also confirm the second item above? ;
2) When you create a recurring meeting that for instance happens every day for three days, the text on both the web and in the invitation e-mail sent to the participants says 'Every xxx for nn xxx effective', where the 'xxx' is translated but not the words 'Every' and 'effective'.

You can also add that the words that do get translated are copied directly as-is to the smtp-invitation without first converting the utf8-strings back to us-ascii, which makes strings containing national characters incorrectly appear as raw utf8-encoded data in the invitations.

[StefanD]

Originally Posted by rickard

Thanks guys.

Can you also confirm the second item above? ;
2) When you create a recurring meeting that for instance happens every day for three days, the text on both the web and in the invitation e-mail sent to the participants says 'Every xxx for nn xxx effective', where the 'xxx' is translated but not the words 'Every' and 'effective'.

You can also add that the words that do get translated are copied directly as-is to the smtp-invitation without first converting the utf8-strings back to us-ascii, which makes strings containing national characters incorrectly appear as raw utf8-encoded data in the invitations.

Yes, same here.
bugzilla# 6472
http://bugzilla.zimbra.com/show_bug.cgi?id=6472

[andyc]

The recurrence dialog for appointments is hard-coded in the current public release (CRAY branch) of Zimbra. Also, the code for generating the human-readable description sent in the notification email message is hard-coded.

However, in the main branch of the source, I have rewritten this dialog and the recurrence description generator so that it can be fully localized. The dialog and description text is now generated using a number of messages in the ZmMsg.properties file. If you look in ZmMsg, you'll see the following properties:

recurDailyEveryDay = Every day.
recurDailyEveryWeekday = Every weekday.
recurDailyEveryNumDays = Every {0,number,integer} days.
recurWeeklyEveryWeekday = Every {0,date,EEEE}.
# {2} is marker to indicate new line for input, replaced with "" on output
recurWeeklyEveryNumWeeksDate = Every {0,number,integer} weeks on {2}{1,list,date,EEEE}.
recurMonthlyEveryNumMonthsDate = Day {0,number,integer} of every {1,number,integer} month(s).
recurMonthlyEveryNumMonthsNumDay = The {0,choice,-1#last|1#first|2#second|3#third|4#fourth} {1,date,EEEE} of every {2,number,integer} month(s).
recurYearlyEveryDate = Every year on {0,date,MMMM} {1,number,integer}.
recurYearlyEveryMonthNumDay = The {0,choice,-1#last|1#first|2#second|3#third|4#fourth} {1,date,EEEE} of every {2,date,MMMM}.
recurStart = Effective {0,date,medium}.
recurEndNone = No end date.
recurEndNumber = End after {0,number,integer} occurrence(s).
recurEndByDate = End by {0,date,medium}.
# {0} is recurrence text; {1} is start; {2} is end
recurBlurb = {0} {2} {1}

In order to see this work, you need to translate these patterns for your language and use them with a Zimbra deployment built from the main branch.