GNOME Bugzilla – Bug 591939
Error in internationalization of strings
Last modified: 2010-06-03 14:25:17 UTC
Hallo evolution devs #: ../e-util/e-datetime-format.c:207 #| msgid "1 day ago" #| msgid_plural "%d days ago" msgid "%d days ago" msgstr "%d dage siden" As far as i know this construction is wrong. You need to have a proper plural construction for strings like this one, much like what it changed from. The problem is that several languages have more than one plural form, so they cannot translate this string correctly for both %d=2 and %d=3
This one is likewise probably wrong. It looks like a combinatio nof two strings, the first refering to the recurrence count and the second to the recurrence interval. #: ../calendar/gui/apps_evolution_calendar.schemas.in.h:12 msgid "Count of default recurrence for a new event. -1 means forever."
This one is not strictly speaking wrong, but it still ends up in something that is not localizable. Remember that that day(s) construction is not possible in all languages. I would suggest that you make it so that the contents of the [timeinternal] combobox changes as a function of what is selected in the [x] combobox. This is probably not triviel to implement, but should not be impossible either. Then for the [timeinternal] combobox, you could then use standard nplural strings like day/days. #. TRANSLATORS: Entire string is for example: #. 'This appointment recurs/Every[x][day(s)][for][1]occurrences' (combobox options are in [square brackets]) #: ../calendar/gui/dialogs/recurrence-page.glade.h:11 msgid "" "day(s)\n" "week(s)\n" "month(s)\n" "year(s)"
Do not use means Do not use.
As far as I can tell, you have made the singular/plural strings change two different items at once, which is somewhat unorthodox. In any case that means, as far as i can see, that including all the strings, there is no instance for the case with several ... for one mail, e.g. several tasks for one mail, which I am assuming is possible. #: ../plugins/mail-to-task/mail-to-task.c:399 msgid "" "Selected calendar contains some events for the given mails already. Would " "you like to create new events anyway?" #: ../plugins/mail-to-task/mail-to-task.c:402 msgid "" "Selected task list contains some tasks for the given mails already. Would " "you like to create new tasks anyway?" #: ../plugins/mail-to-task/mail-to-task.c:405 msgid "" "Selected memo list contains some memos for the given mails already. Would " "you like to create new memos anyway?" #: ../plugins/mail-to-task/mail-to-task.c:423 msgid "" "Selected calendar contains an event for the given mail already. Would you " "like to create new event anyway?" msgid_plural "" "Selected calendar contains events for the given mails already. Would you " "like to create new events anyway?" #: ../plugins/mail-to-task/mail-to-task.c:429 msgid "" "Selected task list contains a task for the given mail already. Would you " "like to create new task anyway?" msgid_plural "" "Selected task list contains tasks for the given mails already. Would you " "like to create new tasks anyway?" #: ../plugins/mail-to-task/mail-to-task.c:435 msgid "" "Selected memo list contains a memo for the given mail already. Would you " "like to create new memo anyway?" msgid_plural "" "Selected memo list contains memos for the given mails already. Would you " "like to create new memos anyway?"
(In reply to comment #3) > Do not use means Do not use. Ahh I will change it for the other ones as well
Garrrr.
(In reply to comment #6) > Garrrr. Sorry. I remember you telling me that I used that component wrong, I thought I had fixed all of them. Regards Kenneth
(In reply to comment #1) > This one is likewise probably wrong. It looks like a combinatio nof two > strings, the first refering to the recurrence count and the second to the > recurrence interval. > > #: ../calendar/gui/apps_evolution_calendar.schemas.in.h:12 > msgid "Count of default recurrence for a new event. -1 means forever." No, it isn't. It explains a special value. That's why the dot is there. Maybe use "recurrences" here? (In reply to comment #2) > msgid "" > "day(s)\n" > "week(s)\n" > "month(s)\n" > "year(s)" I just closed this one in bug #591133 for a won't fix. (In reply to comment #4) > As far as I can tell, you have made the singular/plural strings change two > different items at once, which is somewhat unorthodox. In any case that means, > as far as i can see, that including all the strings, there is no instance for > the case with several ... for one mail, e.g. several tasks for one mail, which > I am assuming is possible. We want to distinguish between event/task/memo and one or more events, but do not mention their actual count. It makes these sentences strange, but makes the translation more free. Is this enough for the explanation? For comment #0 Created commit 915beda in evo master (2.31.1+)
*** Bug 602707 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > (In reply to comment #1) > > This one is likewise probably wrong. It looks like a combinatio nof two > > strings, the first refering to the recurrence count and the second to the > > recurrence interval. > > > > #: ../calendar/gui/apps_evolution_calendar.schemas.in.h:12 > > msgid "Count of default recurrence for a new event. -1 means forever." > > No, it isn't. It explains a special value. That's why the dot is there. Maybe > use "recurrences" here? ok > (In reply to comment #2) > > msgid "" > > "day(s)\n" > > "week(s)\n" > > "month(s)\n" > > "year(s)" > > I just closed this one in bug #591133 for a won't fix. hmm > (In reply to comment #4) > > As far as I can tell, you have made the singular/plural strings change two > > different items at once, which is somewhat unorthodox. In any case that means, > > as far as i can see, that including all the strings, there is no instance for > > the case with several ... for one mail, e.g. several tasks for one mail, which > > I am assuming is possible. > > We want to distinguish between event/task/memo and one or more events, but do > not mention their actual count. It makes these sentences strange, but makes the > translation more free. Is this enough for the explanation? Yes, please include as translator comment
(In reply to comment #10) > > (In reply to comment #4) > > ... > ... > > Yes, please include as translator comment I'm not sure what kind of comment it should be, and repeating same sentence for 6 times is kinda weird. If you really need it there, then please give me the sentence you think describes this best and I'll add it to sources. Thanks.
Here you go: "TRANSLATORS SINGULAR/PLURAL: We are aware that not all permutations of singular and plural is present, i.e. either both the first and the second item are both plural or both are singular. This is intentional, and while we are aware that it may cause problems in some languages, where plural forms change depending on number, it cannot be made in any other way. Fell free to translate it in the way that you feel is most appropriate." You can just add it at one of the strings and then refer to the comment for that string in the others if you think that it will look to bulky to add it for all off them, i.e. "To see common comment for this group of strings, search the po-file for 'SINGULAR/PLURAL'"
(In reply to comment #12) > "TRANSLATORS SINGULAR/PLURAL: We are aware that not all permutations of > singular and plural is present, i.e. either both the first and the second item > are both plural or both are singular. This is intentional, and while we are > aware that it may cause problems in some languages, where plural forms change > depending on number, it cannot be made in any other way. Fell free to translate > it in the way that you feel is most appropriate." Can this be shortened please? > You can just add it at one of the strings and then refer to the comment for > that string in the others if you think that it will look to bulky to add it for > all off them, i.e. I prefer to see a comment added to all places instead. Especially because you cannot know which of the places a translator spots first as po files don't offer any predictable sorting. Let's not start "Hi, I am X. Try to find out how to search in comments and in your translation tool and then find Y to find out more about X. Good luck and enjoy wasting your time."
I'll try: "TRANSLATORS SINGULAR/PLURAL: We are aware that not all permutations of singular and plural is present, i.e. the two items are either both plural or both singular. This is intentional, fell free to translate it in the way that you feel is most appropriate." > I prefer to see a comment added to all places instead. Especially because you > cannot know which of the places a translator spots first as po files don't > offer any predictable sorting. Let's not start "Hi, I am X. Try to find out how > to search in comments and in your translation tool and then find Y to find out > more about X. Good luck and enjoy wasting your time." Agreed, it is preferable if it is present at all strings, I was just trying to adress Milans concern, but yes, it should be at all the strings.
"TRANSLATORS: Codewise it is impossible to provide separate strings for singular and plural. Please translate it in the way that you feel is most appropriate for your language."
Thank you master jedi ;) But actually it should be: ".. provide separate strings for all combinations of singular.." since it is that which is impossible, not providing strings for singular and plural.
so, what string is final?
The one that you will commit. I don't care. Just take TLE's?
Ok, use this one. It doesn't really matter, just as long as we have one: "TRANSLATORS: Codewise it is impossible to provide separate strings for all combinations of singular and plural. Please translate it in the way that you feel is most appropriate for your language."
Created commit 63b2ef3 in evo master (2.31.3+) with mail-to-task comments.