On 05/11/2016 15:23, thr...@numericable.fr wrote: > I translated a few files into French and sent them to Mateusz (fdnpkg.fr, > fdpkg.fr, move.fr and xcopy.fr). After looking to these files, several > questions > and remarks spring to my mind:
Looks good, but I see that there are lines that wraps on the screen, which looks very bad (words are splitted in half), and it can make the help screens longer than the author expected, leading for eg. to being unable to fit on a single screen. More on that below. > - On some of these files, I couldn't respect the 80 characters per line > limit compared to the English version especially for the help message of > xcopy. Is this a problem? If it is, what can I do? (French is kind of more > verbose > and the same will also happen in compute.fr for instance) As said above, yes, it's quite bothering. Can you please review your translations to make sure the length of the translations is respected? It's not always easy, but that's part of the translation job :) Do not target an exact literal translation - a shorter, slightly uglier one is often better if it fits in the same space as the original and still conveys the same technical information in an understandable way. Example: Original (79 chars): Use common notation used on computers. Powers can be specified by "^" operator. Your version (119 chars): Utilisez la notation commune utilisée sur les ordinateurs. Les puissances peuvent être spécifiées par l'opérateur "^". My suggestion (79 chars): La notation est usuelle pour ordinateurs. Puissances possibles avec l'op. "^". > - On some files, the translation is incomplete. But when I open the file in > French, there are no "empty lines". How do I add new sentences to > translate to these? This happens when the translation file is older than the original. In such cases, you need to re-compare (manually) both files, and add the missing original strings into the translated version. Note, that sometimes strings can disappear from one version to another, so in case of outdated files you should also take care of removing the translated strings that do not appear anymore in the original. > - FDNPKG.FR is in UTF8 but I couldn't convert it locally to ISO-8859-1. > iconv complains about an illegal character at position 0. Hope Mateusz will > know what to do with it. I checked it, and it's simply because your UTF-8 translation contains a BOM. You can easily check that with a hex editor - the first 3 bytes of the file are set to 0xEF 0xBB 0xBF. These characters are not displayed by your text editor, which is why you might have been confused. It's usually possible to configure the text editor to stop adding this useless header. But you can also leave it as is, and use utf8tocp for conversions, as it will strip any BOMs automatically: http://utf8tocp.sourceforge.net In any case, the translations need to be stored within the freedoslocal project as UTF-8. The only reason you'd want to convert them yourself is if you wish to test them on an actual FreeDOS system (highly recommended). Finally, please note that FreeDOS uses CP850 (aka 'Latin 1') for French localizations, not ISO-8859-1. cheers, Mateusz > ---- Message d'origine ---- > De : "Mateusz Viste" <mate...@viste.fr> > À : freedos-devel@lists.sourceforge.net > Objet : Re: [Freedos-devel] How to rework some French translations and > contribute a Turkish translation? > Date : 04/11/2016 09:20:28 CET > > Hi, > > About translations of the installer - Jerome already provided an > extensive explanation. > > About the rest of the system - I'd suggest taking a look here: > http://freedoslocal.sourceforge.net/ > > We actually already have partial Turkish translations provided by Ercan > Ersoy, you might want to synch with him to avoid double work. > > Translations are simple text files. Encoding is UTF-8 when stored on the > freedoslocal project, there's an automated script that converts all > translations to proper 8bit codepages. > > If you'd like to contribute some translations, send some first work to > me, I'd provide you with a svn access to freedoslocal then. > > cheers, > Mateusz > > > > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > > > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
