[MonoDevelop] Welcome Page Localization Patch
lluis at ximian.com
Sat Nov 25 13:55:16 EST 2006
El dv 24 de 11 del 2006 a les 16:13 +0000, en/na Gideon de Swardt va
> > Does intltool-update really pick up those strings from the xsl page?
> > If it does, it's ok, although I would rather prefer not to change
> > GettextCatalog for this. Maybe you can just create a proxy class in
> > welcome page add-in and use it instead of GettextCatalog?
> > Lluis.
> Please excuse my ignorance, but I have very little experience and
> exposure to the intltool-update tool prior to today. Please correct me
> if I wrong, but the way I understand it, is that intltool-update is
> used to update and merge the translations files. It looks like it is
> extracting all the strings from the CS and Xml documents specified in
> the POTFILES.in file.
> I did a quick test by adding WelcomePage.xsl to POTFILES.in. The patch
> work if the strings are added to the po files (manually), but
> unfortunately intltool-update is not picking up the strings from the
> xsl and updating/merging them into an existing po file automatically.
> How does intltool know what strings to extract from cs and xml files?
> Is there a way that we can configure it to extract some strings from
> Xsl files?
> I can see this as being a very handy feature as it will enable us to
> translate all Xsl files in the future. I am also using Xsl in the Web
> Reference AddIn.
Support for different types of files is kind of harcoded in intltool, so
for .cs files it will look for GetString, but it won't do the same for
xsl files. I'm not an expert in intltool, but I don't think that can be
More information about the Monodevelop-list