Frédéric Delanoy frederic.delanoy@gmail.com writes:
po/fr.po | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
There are many more issues to fix. One of the motivations for po files is to reduce the patch churn caused by translations, so please don't send a separate patch for each string, do a review pass over the whole file and fix everything you can. The po format makes it easy to find places that need work.
2011/1/11 Alexandre Julliard julliard@winehq.org:
Frédéric Delanoy frederic.delanoy@gmail.com writes:
po/fr.po | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
There are many more issues to fix. One of the motivations for po files is to reduce the patch churn caused by translations, so please don't send a separate patch for each string, do a review pass over the whole file and fix everything you can. The po format makes it easy to find places that need work.
-- Alexandre Julliard
Actually I based on the Wine translation statistics page, which most probably will need a overhaul since it didn't find other non translated/correctly converted strings.
BTW while reviewing the po file, I stumbled upon a potential problem: menu accelerators. These might be place differently in different menus, to prevent duplicates.
Other problem, when one msgid translation can/must be translated differently according to the context, e.g. #: hhctrl.rc:29 notepad.rc:52 #, fuzzy msgid "&Search" msgstr "" "#-#-#-#-# fr.po (Wine) #-#-#-#-#\n" "&Recherche\n" "#-#-#-#-# fr.po (Wine) #-#-#-#-#\n" "&Rechercher"
I'm not quite sure how this can be fixed (in the general case)? Would splitting do? Using message contexts? I'm quite not an expert in PO files, so any insight would be appreciated.
Frédéric Delanoy
Frédéric Delanoy frederic.delanoy@gmail.com writes:
Actually I based on the Wine translation statistics page, which most probably will need a overhaul since it didn't find other non translated/correctly converted strings.
BTW while reviewing the po file, I stumbled upon a potential problem: menu accelerators. These might be place differently in different menus, to prevent duplicates.
This can be addressed with message contexts, if really necessary. But in general it's preferable to use the same accelerator for the same word across application if at all possible.
Other problem, when one msgid translation can/must be translated differently according to the context, e.g. #: hhctrl.rc:29 notepad.rc:52 #, fuzzy msgid "&Search" msgstr "" "#-#-#-#-# fr.po (Wine) #-#-#-#-#\n" "&Recherche\n" "#-#-#-#-# fr.po (Wine) #-#-#-#-#\n" "&Rechercher"
I'm not quite sure how this can be fixed (in the general case)? Would splitting do? Using message contexts?
Yes, message contexts, again only if really necessary.
-
Alexandre Julliard -
Frédéric Delanoy