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: Tue, 23 Aug 2016 18:17:06 +0300
Message-ID: <d7eb5907-b025-3f10-2181-111c3e192753@gmail.com> (raw)
In-Reply-To: <20160823.234340.102844932353677705.t-ishii@sraoss.co.jp>
References: <7fbf2e80-9507-0521-d0e9-913ab81a58df@gmail.com>
<20160823.075131.847843562615671158.t-ishii@sraoss.co.jp>
<a65e7fdf-c7a9-6106-307d-2fab50981c74@purtz.de>
<20160823.234340.102844932353677705.t-ishii@sraoss.co.jp>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Hello,
If I understand you right, your goal to change the docs encoding is to
allow for the docs translation.
But I don't think that the translation should be done that way (with
replacing sgml/xml/whatever).
Just as we don't translate server messages by copying all the source
files and replacing strings in them, we shouldn't translate the docs by
replacing sgml contents.
We at Postgres Pro using the gettext technologies for this. And we have
complete working toolchain (including modified Makefile) for translation
the docs.
(If someone is interested in, we can share our results and provide
everything needed to get started).
Those who translated sgmls/xml before are moving to gettext/po (The
FreeBSD Documentation Project is most remarkable example) or similar
approaches.
So I think a broader view to the evolution of the PostgreSQL
documentation is needed.
Best regards,
Alexander
23.08.2016 17:43, Tatsuo Ishii пишет:
>>> Really, what change we need, it is conversion from SGML to XML format.
>>> It would solve some real problems, such as ability to include diagrams
>>> in the docs,
> This argument sounds weak to me. Last time when I proposed to include
> diagrams in the docs in the pgsql-hackers list, some developers were
> against the idea because if the diagram is binary, it's hard to
> maintain in git. However up to now, there's no consensus that which
> text base diagram source (which allows to generate real diagrams from
> it) is good for our purpose. I don't see why just migrating to XML
> solves the problem.
>
> (the discussion on diagrams stopped in 2011, as far as I know)
> https://www.postgresql.org/message-id/1307972167.2862.518.camel@core2
>
> Don't get me wrong. I am not against migrating to XML. I just want to
> say that let's not pretend that migrating to XML would solve all the
> problems we have.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
>
--
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: <d7eb5907-b025-3f10-2181-111c3e192753@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