197 replies to this topic

[urko]

I have gone through the full process: downloaded xpi, extracted Spanish locale, register again as Spanish translator, upload the Spanish locale, filled the missing strings, and tested the updated localed in the xpi, modifying install.rdf and install.js in order to include es-ES (I describe it just in case somebody needs guide). Everything was OK, so Spanish locale is released and available in WTS

Merry Christmas - Feliz Navidad
urko

[Goofy]

Sorry again, urko.

[tommut]

When testing, we have an issue with the fr-FR locale. When we want to create a new reminder and fill the date zone, then it is impossible to save it and the new entry does not show in the "already-saved" list.

Hi there -
It appears that the problem is happening because the month names are not identical in the dtd and properties file. For example:
rf.options.month.10.name=Novembre
<!ENTITY month.11 "novembre">

Notice how it is capitalized int he properties file, but not the DTD file. The extension uses a function to convert the month in the options dialog dropdown to a numeric date (novembre=11) and it tries to get the values from the properties file, and it is returning null currently because it can't find "novembre" (only "Novembre").
Was this purposeful? To have one capitalized and the other not? If you change the months in the DTD to capitalized, it will work again.
I will look to fix this in the code to allow for this, by doing a case-insensitive comparison.
Thanks for notifying me about this problem,
Tom

[Goofy]

Oh I see, thank you for fast solving.
If I can understand you, we should have only capitalized words or only non-capitalized ones ?
well, it all depends in french :
- if the name of the month is a first word of a sentence "November is a foggy month", it is capitalized of course. Also if it is a single title-word.
- but when in a sentence, it is un-capitalized : "Mardi 12 novembre" for "Tuesday, November 12th" (example here)

So it may be interesting to have the double system and have the case-unsensitive feature as you kindly suggest ?
(I don't suggest you spend Christmas night codehacking )

Perhaps is there the same possibility in other languages ?

[tommut]

So it may be interesting to have the double system and have the case-unsensitive feature as you kindly suggest ?
(I don't suggest you spend Christmas night codehacking )

Perhaps is there the same possibility in other languages ?

Okay, that makes sense. I will just add the case-insensitive check, so you can keep the externalizations you have now.
Thanks
Tom

[Goofy]

WE thank you for your concern about languages !

[Luana]

Really really sorry for the delay
Fortunately the 'Italian team' is complete now, and we will try to provide the italian localization asap

[l0stintranslation]

Hi! I'm the second official translator, and I'm glad to communicate that the Italian translation of ReminderFox is ready

[Luana]

Hi! I'm the second official translator, and I'm glad to communicate that the Italian translation of ReminderFox is ready
[right][snapback]7539[/snapback][/right]

I want to thank you for your nice and quick collaboration
Thanks again


@ the Author(s)
I noticed two "free tooltips"
addReminderDialog.js file, lines from 286 and 297

CODE

function toggleCalendar() {
var calendar = document.getElementById("oe-date-picker-overlay-box");
var calendarToggleButton= document.getElementById("calendarToggle");
if ( calendarToggleButton.checked ) {
 calendar.setAttribute("hidden", "true");
 calendarToggleButton.setAttribute("tooltiptext", "Show Calendar");
}
else {
 calendar.setAttribute("hidden", "false");
 calendarToggleButton.setAttribute("tooltiptext", "Hide Calendar");
}
}

I noticed that in the same file, lines from 72 to 83 there are the 'correct strings'

CODE

// show calendar based on button state
var calendar = document.getElementById("oe-date-picker-overlay-box");
var calendarToggleButton= document.getElementById("calendarToggle");
if ( calendarToggleButton.checked ) {
 calendarToggleButton.setAttribute("tooltiptext", g_reminderFoxBundle.getString("rf.add.time.button.calendar.tooltip.hide"));    
 calendar.setAttribute("hidden", "false");
}
else {
 calendarToggleButton.setAttribute("tooltiptext", g_reminderFoxBundle.getString("rf.add.time.button.calendar.tooltip.show"));    
 calendar.setAttribute("hidden", "true");
}
}

so I replaced just for myself (for test) the strings containing the tooltips

CODE

function toggleCalendar() {
       var calendar = document.getElementById("oe-date-picker-overlay-box");
var calendarToggleButton= document.getElementById("calendarToggle");
if ( calendarToggleButton.checked ) {
 calendarToggleButton.setAttribute("tooltiptext", g_reminderFoxBundle.getString("rf.add.time.button.calendar.tooltip.show"));    
 calendar.setAttribute("hidden", "false");
}
else {
 calendarToggleButton.setAttribute("tooltiptext", g_reminderFoxBundle.getString("rf.add.time.button.calendar.tooltip.hide"));    
 calendar.setAttribute("hidden", "true");
}
}

Repackaged, tested, it works fine !
Really many many thanks for this great extension



ADDED:
Mmm... could it be possible for you to add the localized description ?

[tommut]

@ the Author(s)
I noticed two "free tooltips" 

Thanks a lot! I must have missed those. I've fixed them as you described. I'll look into the localized description.
Tom

[tommut]

To the Italian translators:

I noticed that setting the time for a reminder was failing. This is because the time delimiter is different from the delimiter used for the times in the DTD. For example, in the DTD the time is listed using a ':' for a delimiter --
<!ENTITY time.17 "5:00 PM">

but in the properties file, the delimiter is a '.' --
rf.add.time.delimiter=.

The code uses the delimiter to determine the time in the options dialog.
Is there a reason that these are different?

Thanks
Tom

[l0stintranslation]

No
It has been certainly an oversight
Now it's fixed.

[Slovak_Team]

Slovak locale released.

Best regards

[Karelik]

Hi all, I'm new here.
I have question, Czech time looks 10:00 (10:00am) and 15:00 (3:00pm).
Is possible to leave empty strings "rf.add.time.AM" and "rf.add.time.PM"? And how manage to have 100% translation status? Can it cause problem (uncomplete translation meaning)?
Czech translation complete (0.9.2).

[tommut]

Hi all, I'm new here.
I have question, Czech time looks 10:00 (10:00am) and 15:00 (3:00pm).
Is possible to leave empty strings "rf.add.time.AM" and "rf.add.time.PM"?

Hi there,
Yes you can leave the AM and PM strings empty if they are not needed.
Thanks,
Tom

[winiah]

Hello, everybody.

Locale zh-TW has beed finished.
*ADDTION 2: Now it is certainly ok, I guess.

----
And, I found locale zh-CN has some problems ( which the value between DTD and PROPERTIES is different ),
but I am going out now, so, after I come home I'll check what's wrong and try to contact with zh-CN translator.
*ADDTION: God, sorry. That's my mistake, now it is ok. And I'll add something after I come home.

[Luana]

Italian localization is ready, available as usual here

[urko]

Spanish locale for the new extension release available in WTS

[Slovak_Team]

Slovak (sk-SK) locale updated.

[hakabon]

Turkish (tr-TR) translation is updated in WTS.