wxPropertyGrid: added wxPG_NO_INTERNAL_BORDER, wxPG_EX_NO_TOOLBAR_DIVIDER

[wxWidgets.git] / docs / tech / tn0002.txt

diff --git a/docs/tech/tn0002.txt b/docs/tech/tn0002.txt
index 8f5a6881794d8dd4fc17bc3b64e3265e85f38e39..a0d2572126bfe09762321f1e15e9a86a9e187396 100644 (file)
--- a/docs/tech/tn0002.txt
+++ b/docs/tech/tn0002.txt
@@ -1,7 +1,7 @@
-                          wxWindows translator guide
+                          wxWidgets translator guide

                           ==========================
 
                           ==========================
 

-This note is addressed to wxWindows translators.
+This note is addressed to wxWidgets translators.

 
 First of all, here is what you will need:
 
 
 First of all, here is what you will need:
 


@@ -12,7 +12,7 @@ First of all, here is what you will need:
       mirror (RPMs and DEBs are also available from the usual places)
 
    b) for Windows you can download the precompiled binaries from
       mirror (RPMs and DEBs are also available from the usual places)
 
    b) for Windows you can download the precompiled binaries from

-      www.wxwindows.org or install PoEdit (poedit.sourceforge.org) and
+      www.wxwidgets.org or install PoEdit (poedit.sourceforge.net) and

       add <installdir>/poEdit/bin to your path (so it can find xgettext).
 
 2. A way to run a program recursively on an entire directory from the command
       add <installdir>/poEdit/bin to your path (so it can find xgettext).
 
 2. A way to run a program recursively on an entire directory from the command


@@ -28,7 +28,7 @@ First of all, here is what you will need:
       fine, but you'd have to use some kind of "for /s" loop with the
       command.com/cmd.exe.
 
       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.
 
 
    will make things a lot easier for you and others.
 
 


@@ -36,10 +36,10 @@ Now a brief overview of the process of translations (please refer to GNU
 gettext documentation for more details). It happens in several steps:
 
 1. the strings to translate are extracted from the C++ sources using xgettext
 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
-   to wxWindows) is merged with existing translations in another .po file (for
+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)
 
    example, de.po) and replaces this file (this is done using the program
    msgmerge)
 


@@ -59,12 +59,39 @@ them). Then type "make lang.mo" which will create the binary message catalog.
 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.
 
 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$
 === 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 ***
+
+Revision 1.4  2004/05/04 08:26:58  JS
+Name change replacements
+

 Revision 1.3  2003/11/18 16:37:11  DS
 Updated translation technote to mention Makefile usage under Windows.
 
 Revision 1.3  2003/11/18 16:37:11  DS
 Updated translation technote to mention Makefile usage under Windows.