Thread: [Winmerge-development] Simplifying finding translatable files and unifying file naming
Windows visual diff and merge for files and directories
Brought to you by:
christianlist,
grimmdp
From: Kimmo V. <ki...@wi...> - 2008-09-02 17:18:43
|
I added a comment to Jochen's patch item for binary editor about this: #2036603 Side by side hex diff/edit/merge view http://winmerge.org/patch/2036603 I objected two things: - yet another folder for translatable files - yet another naming scheme Of course I don't mean Jochen's patch added these problems. The problem has already existed for a long time. But I don't want to make it worse. What kind of translated files we have: #1 WinMergeU.exe - Src/Languages - filename is [languagename].po (German.po) #2 Installer - Installer/InnoSetup/Languages - filename is [languagename].isl (German.isl) #3 ShellExtension - ShellExtension/Languages - filename is ShellExtension[languagename].rc (ShellExtensionGerman.rc) #4 Readme - Docs/Users/Languages - filename is ReadMe-[languagename].txt (ReadMe-German.txt) #5 heksedit (as in current trunk) - Externals/heksedit/Languages - filename is [languagecode].po (ge.po) Now imagine being translator and: - trying to keep up with the changes and keep translations up to date - wanting to translate WinMerge and find all those files Many translators find/bother only with WinMergeU.exe part. First problem of files being scattered all over folder structure could be solved by creating new top-level folder for them. E.g. "Translations". Under that folder we could have own subfolder for each component having actual files. Like this: Translations |-Installer | |-German.isl | |-Spanish.isl [...] |-Readme | |-ReadMe-German.txt | |-ReadMe-Spanish.txt [...] The problem with different filenaming schemes is trickier. Jochen's idea to use languagecode is good. But only language code makes filenames short and "uncomfortable". Where is the German file? And we have two Chinese translations. Currently we also have a bit weird naming for executable lang files. E.g. we have Brazilian.po and Portuguese.po. Which isn't very logical. The gettext uses languagecode_countrycode.po scheme, as documented here: http://www.gnu.org/software/gettext/manual/gettext.html#Locale-Names Perhaps our solution could be a bit more user-friendly solution to use Languagename_countrycode.po? E.g. German_DE.po, Portuguese_BR.po? Note, I'm not really suggesting real solutions (yet). I'm just document the issues and present some possible solutions. Changing folder structure and/or filenames requires changes to many places: installer, documentation, scripts etc. So it takes time and effort to do. We can't do these kind of changes many times, so we'll need some real solutions first before starting doing these changes. Regards, Kimmo |
From: Tim G. <ti...@ge...> - 2008-09-02 20:35:01
|
Kimmo Varis wrote: > First problem of files being scattered all over folder structure could > be solved by creating new top-level folder for them. E.g. > "Translations". Under that folder we could have own subfolder for each > component having actual files. Like this: > > Translations > |-Installer > | |-German.isl > | |-Spanish.isl > [...] > |-Readme > | |-ReadMe-German.txt > | |-ReadMe-Spanish.txt > [...] Sounds good! But should we maybe name the folder for the installer "InnoSetup"? Hopefully we have one day a MSI setup too and need then a folder for his translations. > Perhaps our solution could be a bit more user-friendly solution to use > Languagename_countrycode.po? E.g. German_DE.po, Portuguese_BR.po? Is the country code not also the top level domain for the country? So I think the most German WinMerge users should know, that they must work with the file "de_DE.po". ;-) So I would vote for "languagecode_countrycode"! Should we add the project name to the files? Like "WinMerge-de_DE.po" and "frhed-de_DE.po"? In this case the translators don't would need subfolders for their work. Greetings, Tim |
From: Kimmo V. <ki...@wi...> - 2008-09-02 20:46:25
|
>> Perhaps our solution could be a bit more user-friendly solution to use >> Languagename_countrycode.po? E.g. German_DE.po, Portuguese_BR.po? > > Is the country code not also the top level domain for the country? So I > think the most German WinMerge users should know, that they must work > with the file "de_DE.po". ;-) Unfortunately domain names and ISO country codes aren't 1:1. There are exceptions, though not many: http://en.wikipedia.org/wiki/Country_code_top-level_domain And yes I know my country's country code. But I've no idea about (for example) Slovenian country code. So when someone sents me Slovenian.po I need to find correct country code first. Which most likely just delays me committing that update. -Kimmo |
From: Kimmo V. <ki...@wi...> - 2008-09-22 14:06:24
|
>> Translations >> |-Installer >> | |-German.isl >> | |-Spanish.isl >> [...] >> |-Readme >> | |-ReadMe-German.txt >> | |-ReadMe-Spanish.txt >> [...] > > Sounds good! But should we maybe name the folder for the installer > "InnoSetup"? Hopefully we have one day a MSI setup too and need then a > folder for his translations. Good point. Though until we'll get MSI setup we propably have changed the system again... :) >> Perhaps our solution could be a bit more user-friendly solution to use >> Languagename_countrycode.po? E.g. German_DE.po, Portuguese_BR.po? > > Is the country code not also the top level domain for the country? So I > think the most German WinMerge users should know, that they must work > with the file "de_DE.po". ;-) > > So I would vote for "languagecode_countrycode"! Although I had some reservations for this earlier, I think this is the best way after all. Gettext uses this style so it must be familiar for lots of translators. So let's use this naming scheme. > Should we add the project name to the files? Like "WinMerge-de_DE.po" > and "frhed-de_DE.po"? In this case the translators don't would need > subfolders for their work. Nice idea. Downside is the folder gets cluttered as there are several kinds of files in the same folder, different naming schemes, different extensions etc. And I think it is easier for tools to handle files when all the files in the same folder (e.g. copy all .po files to correct folder when building). So what we now need is somebody willing to do the work for moving files and fixing scripts etc. Regards, Kimmo |
From: Tim G. <ti...@ge...> - 2009-03-23 21:01:24
|
Kimmo Varis wrote: > What kind of translated files we have: > #1 WinMergeU.exe > - Src/Languages > - filename is [languagename].po (German.po) > #2 Installer > - Installer/InnoSetup/Languages > - filename is [languagename].isl (German.isl) > #3 ShellExtension > - ShellExtension/Languages > - filename is ShellExtension[languagename].rc (ShellExtensionGerman.rc) > #4 Readme > - Docs/Users/Languages > - filename is ReadMe-[languagename].txt (ReadMe-German.txt) > #5 heksedit (as in current trunk) > - Externals/heksedit/Languages > - filename is [languagecode].po (ge.po) > > Now imagine being translator and: > - trying to keep up with the changes and keep translations up to date > - wanting to translate WinMerge and find all those files > > Many translators find/bother only with WinMergeU.exe part. > > First problem of files being scattered all over folder structure could > be solved by creating new top-level folder for them. E.g. > "Translations". Under that folder we could have own subfolder for each > component having actual files. Like this: > > Translations > |-Installer > | |-German.isl > | |-Spanish.isl > [...] > |-Readme > | |-ReadMe-German.txt > | |-ReadMe-Spanish.txt > [...] > > The problem with different filenaming schemes is trickier. Jochen's idea > to use languagecode is good. But only language code makes filenames > short and "uncomfortable". Where is the German file? And we have two > Chinese translations. > > Currently we also have a bit weird naming for executable lang files. > E.g. we have Brazilian.po and Portuguese.po. Which isn't very logical. > > [...] I am working on a translation system for our website. It is now only alpha code, but sooner or later we will have new translations files. So I think we should discus this schema again. We both like "languagecode_countrycode.po" most, right? So I would get the following structure for the new translations: Translations |- Web |- de_DE.po |- fr_FR.po |- ... Greetings, Tim |