fine, but you'd have to use some kind of "for /s" loop with the
command.com/cmd.exe.
-3. (at least read) access to the cvs is not necessary strictly speaking, but
+3. (at least read) access to the subversion is not necessary strictly speaking, but
will make things a lot easier for you and others.
gettext documentation for more details). It happens in several steps:
1. the strings to translate are extracted from the C++ sources using xgettext
- program into a wxstd.po file which is a "text message catalog"
+ program into a wxstd.pot file which is a "text message catalog"
-2. this new wxstd.po file (recreated each time some new text messages are added
+2. this new wxstd.pot file (recreated each time some new text messages are added
to wxWidgets) is merged with existing translations in another .po file (for
example, de.po) and replaces this file (this is done using the program
msgmerge)
Under Windows (If you don't have Cygwin or MinGW), you should execute the
commands manually, please have a look at Makefile to see what must be done.
+For platform specific translations, .po files such as 'locale/msw/it.po' can be
+used to provide translations that override the usual ones in 'locale/it.po'.
+The generated .mo files are then installed under the names such as 'wxmsw.mo'
+alongside the generic 'wxstd.mo'.
+
+A new platform specific translation should be added to a section such as this
+in wx.bkl:
+
+ <gettext-catalogs id="locale_msw">
+ <srcdir>$(SRCDIR)/locale/msw</srcdir>
+ <catalog-name>wxmsw</catalog-name>
+ <linguas>it</linguas>
+ <install-to>$(LOCALEDIR)</install-to>
+ </gettext-catalogs>
+
=== EOF ===
Author: VZ
-Version: $Id$
$Log$
+Revision 1.7 2005/08/12 15:34:01 MW
+Typo
+
+Revision 1.6 2005/08/12 15:29:47 MW
+Translate '&Help' to '&' for italian Windows only
+
Revision 1.5 2004/10/22 19:12:59 KH
*** empty log message ***