From owner-freebsd-doc@FreeBSD.ORG Wed Feb 19 18:40:35 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EEEFDD8; Wed, 19 Feb 2014 18:40:35 +0000 (UTC) Received: from mxout2.bln1.prohost.de (mxout2.bln1.prohost.de [91.233.87.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 90C5B1606; Wed, 19 Feb 2014 18:40:34 +0000 (UTC) Received: from Voyager.local (p4FC73A16.dip0.t-ipconnect.de [79.199.58.22]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.4/8.14.4) with ESMTP id s1JIeGpj003209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 19 Feb 2014 19:40:17 +0100 Message-ID: <5304FA92.7070308@FreeBSD.org> Date: Wed, 19 Feb 2014 19:40:18 +0100 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Warren Block Subject: Re: Translations (was Re: svn commit: r43974 - head/en_US.ISO8859-1/books/handbook/advanced-networking) References: <201402180226.s1I2QS0x076422@svn.freebsd.org> <5302C7B9.7090208@delphij.net> <5302E05F.1050200@delphij.net> <5303241B.8080906@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 889961cb496f0430d24866fc65d32121 Cc: "freebsd-doc@freebsd.org" , d@delphij.net, Warren Block X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 18:40:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am 19.02.14 03:30, schrieb Warren Block: > On Tue, 18 Feb 2014, Benedict Reuschling wrote: > >> Another tool is textproc/po4a that Thomas Abthorpe showed me on >> one of the hacker lounges two years ago in Canada. He set up a >> test project for a translation into en_GB to see how these tools >> fit our toolchain. >> >> He send me the following mini-howto, which I extended a bit for >> a first commit to the german doc repo recently: >> >> install textproc/po4a install editors/poedit # >> optional install devel/gtranslator #optional install lokalize # >> somewhere in kde4, too lazy to look >> >> To prep a new translation, inline, same directory the following >> works. Substitute en_GB for the language of your choice. >> >> po4a-gettextize -f xml -m article.sgml -p article.pot # renders >> to pot file > > I can use poedit to do the translation, but I always get > article.pot:7: header field 'Project-Id-Version' still has the > initial default value > I have this in my pot file header: "Project-Id-Version: 1\n" "Language: de\n" I guess we need to fill these automatically when a new or an updated translation is created. Maybe we could fill in some values from SVN (revision comes to mind) or use some kind of auto-incrementing counter for each new translated document. These are the things we need to figure out. Another question is: do we keep those po files holding the translated strings in our doc repo alongside the translation? Or do only the translation projects keep them for themselves? > It does appear to save the translations to article.pot, this is > something to do with catalogs. Manually editing article.pot and > setting "Language: \n" to "Language: en_GB\n" then complains about > the "Project-Id-Version" line having a default value. > >> I put everything in the DevSummit wiki page and will start a >> separate one with the results from the summit to continue from >> there: >> >> https://wiki.freebsd.org/201405DevSummit/Translation > > The instructions don't seem to be there. On another page? Well, I thought about putting them there, but decided against it as I want the discussion to be open rather than present a solution beforehand. Maybe someone else knows a better tool. I will demonstrate it, but will also show the current drawbacks and what I see with my translator hat on. The process in the mini-howto will get you started for sure, but it is very open for improvement. Cheers Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTBPqSAAoJEAQa31nbPD2LjGQIALfGCjQy5elI6L7hFxlRVkop c3OfKQLh8RuemK52ShxrdAv5m4BQng1PPIh28IFWBnEWgTKxUmg0pcMXwtvfvnUG zbLLmz9CZ2IUmyGJ19CRkqN9ImJZgdbnrxfKuCtRP6Qn83xIPYBTIRqI7c8thDvq Z6hlYVOnJ4hop+4FSLh6AqMnMTC/P38W1ekZb63RD/qA9YyF9lmO3wP5CNmey0Gk OWTa7XfY4eFpnokq/KCi6ysH9vYwmrvHirF/9IW6XT9XYjWxTJVN9Gnn07rBJZx3 O2qv6yucUitXOqhaFsZIci6cDt4MNcZzpyMjzqJW0u+pHutbs20zQKvueciBGGk= =FKUq -----END PGP SIGNATURE-----