From: Alexander Law <exclusion@gmail.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: juergen@purtz.de
Cc: pgsql-docs@postgresql.org
Cc: vitus@wagner.pp.ru
Subject: Re: UTF-8 docs
Date: Wed, 24 Aug 2016 10:13:38 +0300
Message-ID: <7d22ce9f-051e-7e7a-2ac8-e6ca96c2e4f6@gmail.com> (raw)
In-Reply-To: <20160824.155847.1250205802793953352.t-ishii@sraoss.co.jp>
References: <d7eb5907-b025-3f10-2181-111c3e192753@gmail.com>
<20160824.081919.1280691778046843345.t-ishii@sraoss.co.jp>
<8befeaca-abab-27b7-4e1c-9a964d0c704c@gmail.com>
<20160824.155847.1250205802793953352.t-ishii@sraoss.co.jp>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
24.08.2016 09:58, Tatsuo Ishii пишет:
> Please look at the attached .pot for one of the doc files. You can use
>> any translation software (which supports .po (e.g. poedit, Lokalize,
>> ...)) to translate it to any language.
>> And you can look at all the docs converted to .po for translation:
>> http://oc.postgrespro.ru/index.php/s/puEJKoUwbZ3dia5/download
> Ok, the idea is, each sentence in the doc are regarded as "very long
> message". Interesting. Looks better than "replacing SGML contents with
> translated contents" (which Japanese doc project is doing for now).
Yes, the DocBook format has the natural blocks such as <para>, <title>,
<indexterm>, ... which could be translated as the separate text
fragments. So it's the question of the most accurate mapping of those
blocks to .po fragments and back. (We use for it customized xml2po from
gnome-doc-utils but there are another programs too.) All the other text
processing could be done with the rich gettext toolset.
> Unfortunately I can't read Japanese and don't understand how Japanese
> FreeBSD team works (and why cant it use the gettext technologies) ,
> but the main FreeBSD Documentation team is moving to PO (see
> https://www.bsdcan.org/2016/schedule/track/Hacking/680.en.html).
Please look at the presentation, and the
http://wonkity.com/~wblock/translation/translation.pdf -- these
documents greatly explain all the challenges of the pre-existing
approach and the solutions.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: exclusion@gmail.com, ishii@sraoss.co.jp, juergen@purtz.de, vitus@wagner.pp.ru
Subject: Re: UTF-8 docs
In-Reply-To: <7d22ce9f-051e-7e7a-2ac8-e6ca96c2e4f6@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox