On Tuesday 13 Feb 2007 23:05, Alexandre Prokoudine wrote: > While we are at this, here I am asking again, if there is some way [1] > to make data/presets/presets.xml translatable :-/
Yes, and it's documented in the README in that directory. OK, that's a bit glib. Rosegarden will look for presets_$LANG.xml before it reverts to loading plain presets.xml, so the way to "translate" it is to provide a whole new file for your language. It's not ideal, because (a) you don't get the strings integrated into your usual translation tool and (b) it means you need to duplicate all the value definitions as well as the strings themselves, making for trouble if something is changed in the original. But given that the original file has not yet changed since it was first introduced (even this clef change we've been discussing happened in the C++ code rather than the XML file), I think it ought to be OK for now, no? The one thing that README doesn't make clear is that the names of the clefs in the file should not be translated. The literal values "guitar", "contrabass" etc should be considered as code tokens rather than strings. The displayed texts for those tokens come from code in TrackParameterBox.cpp, and are already i18n-ized. I'll update the README to reflect that fact. Chris ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
