I just submitted the first half of the french translation of the rules. Some original rules files were horribly formatted, so i cleaned then too, to make them more uniform and cute, to ease the work of other translators. I hope it's ok. Now some questions, statements, about it all : - Must i translate "GNOME Documentation Project" ? - Must i translate the license ? It raises some legal problems, as i'm not a lawyer, i couldn't translate it accurately enough. Is there already an accurate french translation of this whole thing ? - <sect2>Options</sect2> is always : <para>None</para> I guess it can safely be removed from all rule files, may i do this ? - I found some mistakes in the english rules, should i fix them ? - In Zebra, do foundations start with an Ace (in the game) or a Two (in the rules) - Block ten doesn't exist. Is it an old game ? Should its translation file be removed ? - Chapters <sect2> should appear emphased, for example in bold, it would be easier and faster to read. - Often the rules repeat themselves between the first part : foundations, stock, tableau, ... and the second part : rules. It would be better if it was avoided, because it would be faster to read and to translate. But i'm not sure it's worth the reworking. - In the game, game list should be sorted alphabetically dynamically, instead of once in the code with the english names. Otherwise, it isn't sorted in other languages like french. - Why is freecell independent from aisleriot in the game menu ? - What does aisleriot mean ? Where does this name come from ? I did this help for translators, which you (Callum) said could be integrated on http://www.gnome.org/projects/gnome-games/contributing.html I fear this is a bit long, so, well, take what you think is useful How to translate game rules What you must do ---------------- - Get the sources as explained on this page - From gnome games source directory, go to "your_game/help". if "your_language_code" directory exists, go to it (you language code is generally a two letters code, like "fr" for french). Else copy the "C" directory to "your_language_code". Here are all the xml files you must translate. - Edit them with your favorite text editor. - Open them with the command "yelp aisleriot.xml" to check what you've done. - When everything is done, submit it as a patch on bugzilla as explained on this page. - Warning : Some terms in the english rules aren't accurate. Please fix them in the english rules when you find some. What you should do ------------------ It's best that you do these things, but in case you don't feel up to it, someone will do this for you - rename aisleriot-C.omf to aisleriot-your_language_code.omf - In "your_game/help/you_language_code", edit the file "Makefile.am", and change, "lang = C omffile = aisleriot-C.omf", replacing C on each of these lines with your language code - from gnome games source directory, edit the file "configure.in", find the AC_CONFIG_FILES variable (near the end of the file) and add the line "your_game/help/you_language_code/Makefile" among other lines. Suggestions ----------- - To edit the files, colored xml support is preferable to avoid screwing up the xml tags, and better see what's going on. I personnaly use bluefish (it's just a suggestion). - Keep in mind that uniformity helps users quickly learn new games. Keep the whole thing consistent. - Start with aisleriot.xml, then definitions.xml (glossary), to set up the appropriate main terms in your language, so you can use them everywhere after that. That will bring speed and uniformity to your translation. - Try to always translate the same concepts with the same sentences in your language. - Copy and paste as much as you can to avoid mispelling and enhance uniformity, but take care of slight differences. -- Heretik <heretik tuxfamily org>
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=