Several ways to proof-read translations: a) on Transifex itself, in view mode. Or in translation mode, so you can fix typos and obvious mistakes directly. Take extra care of keeping format, line feeds, the '%n' parts of strings, colons, capitalization Watch out for instructions (there are very few, e.g. for 'triangle'), the context shown in 'show details' and comments You can add comments to the translations. Better not use the 'mark as problem' checkbox, it pesters lasconic (and Thomas too I think) with notification emails ;-) Setting up a glossary may help to maintain consistency. I've started one, but of course not for Italian, only containing translations for de (and en_UK)
b) in MuseSore, in a current nightly build, update the translations via either the preferences dialog or the resource manager, restart MuseScore for them to take effect, then walk all the menus and dialogs. It is not always easy to match the texts here with the ones on Transifex, the 'show details' in Transifex may help. You may need to delete the 'updated' transaltions form your system somethiems and load them afresh (could get achieved via a factory reset, or by locating and deleting the locale directory in your profile, not her one in the MuseScrore program directory though) c) in the source code, search for the untranslated strings there. Not for translating it, but to get the right context. Bye, Jojo ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
