From 17a4e1f12fce9e3c7808157c4c8474b23d2a1c49 Mon Sep 17 00:00:00 2001 From: Dimitri Schoolwerth Date: Tue, 18 Nov 2003 16:37:11 +0000 Subject: [PATCH] Updated translation technote to mention Makefile usage under Windows. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@24582 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/tech/tn0002.txt | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/docs/tech/tn0002.txt b/docs/tech/tn0002.txt index 29ef40af71..8f5a688179 100644 --- a/docs/tech/tn0002.txt +++ b/docs/tech/tn0002.txt @@ -12,7 +12,8 @@ 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 - www.wxwindows.org + www.wxwindows.org or install PoEdit (poedit.sourceforge.org) and + add /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 line: @@ -22,12 +23,13 @@ First of all, here is what you will need: are unlucky enough to not have xargs, you can use the -exec option of find instead. - b) for Win32 systems this is less trivial: if you have 4DOS/4NT/bash, that's + b) for Win32 systems you can use either Cygwin or MinGW. If you don't have + those it is less trivial: if you have 4DOS/4NT/bash, that's 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 - will make the things a lot easier for you and others. + will make things a lot easier for you and others. Now a brief overview of the process of translations (please refer to GNU @@ -46,16 +48,16 @@ gettext documentation for more details). It happens in several steps: 4. finally, msgformat must be run to produce a .mo file: "binary message catalog" -How does it happen in practice? Under Unix there is a Makefile in the "locale" -directory which will do almost everything (except translations) for you, i.e. +How does it happen in practice? There is a Makefile in the "locale" +directory which will do almost everything (except translations) for you. i.e. just type "make lang.po" to create or update the message catalog for 'lang'. Then edit the resulting lang.po and make sure that there are no empty or fuzzy translations left (empty translations are the ones with msgstr "", fuzzy translations are those which have the word "fuzzy" in a comment just above them). Then type "make lang.mo" which will create the binary message catalog. -Under Windows, 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. === EOF === @@ -63,6 +65,9 @@ Author: VZ Version: $Id$ $Log$ +Revision 1.3 2003/11/18 16:37:11 DS +Updated translation technote to mention Makefile usage under Windows. + Revision 1.2 2002/07/03 15:01:26 VZ typos and other doc corrections from Olly Betts (patch 573738) -- 2.45.2