Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bcN3r-0008Ru-VU for pgsql-docs@arkaria.postgresql.org; Wed, 24 Aug 2016 01:33:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bcN3r-0005cD-23 for pgsql-docs@arkaria.postgresql.org; Wed, 24 Aug 2016 01:32:59 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bcN3q-0005c7-L0 for pgsql-docs@postgresql.org; Wed, 24 Aug 2016 01:32:58 +0000 Received: from [220.116.169.89] (helo=cubox) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bcN3m-00034J-S4 for pgsql-docs@postgresql.org; Wed, 24 Aug 2016 01:32:56 +0000 Received: from [192.168.1.9] (unknown [211.55.60.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by cubox (Postfix) with ESMTPSA id 9533BC46B for ; Wed, 24 Aug 2016 10:32:46 +0900 (KST) Subject: Re: UTF-8 docs To: pgsql-docs@postgresql.org References: <7fbf2e80-9507-0521-d0e9-913ab81a58df@gmail.com> <20160823.075131.847843562615671158.t-ishii@sraoss.co.jp> From: Ioseph Kim Message-ID: <010302fe-2648-2947-6c02-616631122282@postgresql.kr> Date: Wed, 24 Aug 2016 10:32:45 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: <20160823.075131.847843562615671158.t-ishii@sraoss.co.jp> Content-Type: multipart/alternative; boundary="------------2BBAC113E3701B2C55940012" X-Host-Lookup-Failed: Reverse DNS lookup failed for 220.116.169.89 (failed) X-Pg-Spam-Score: -1.1 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------2BBAC113E3701B2C55940012 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi. I greet this discussion. Korean PgDoc encoding is UTF-8 too. korean SGML encoding is utf8 since 10 years. currently, PgDoc is very inefficient for L10N work. but, we have no clean idea for this workaround. I think, English main document's encoding be continued currently. Encoding of each other language documents, I wish to entrust translators. Regards, Ioseph. 2016년 08월 23일 07:51에 Tatsuo Ishii 이(가) 쓴 글: > From: Alexander Law > Subject: UTF-8 docs > Date: Mon, 22 Aug 2016 16:36:14 +0300 > Message-ID: <7fbf2e80-9507-0521-d0e9-913ab81a58df@gmail.com> > >> Hello, >> I've just seen a discussion about docs endoding in pgsql-hackers. >> >> https://www.postgresql.org/message-id/20160822.141645.655870136709055853.t-ishii%40sraoss.co.jp >> Can we continue the discussion in this mailing list? >> We (at Postgres Pro) have developed the whole build chain (with >> support for l10n) so we can just share it. > I have been just subscribed to the pgsql-docs list. > Here is the last conversation with Peter at pgsql-hackers. > >> On 8/22/16 9:32 AM, Tatsuo Ishii wrote: >>> I don't know what kind of problem you are seeing with encoding >>> handling, but at least UTF-8 is working for Japanese, French and >>> Russian. >> Those translations are using DocBook XML. > But in the mean time I can create UTF-8 HTML files like this: > > make html > [snip] > /bin/mkdir -p html > SP_CHARSET_FIXED=1 SP_ENCODING=UTF-8 openjade -wall -wno-unused-param -wno-empty -wfully-tagged -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t sgml -i output-html -i include-index postgres.sgml > > Best regards, > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese:http://www.sraoss.co.jp > > --------------2BBAC113E3701B2C55940012 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi.

I greet this discussion. Korean PgDoc encoding is UTF-8 too.

korean SGML encoding is utf8 since 10 years.


currently, PgDoc is very inefficient for L10N work.

but, we have no  clean idea  for this workaround.


I think, English main document's encoding be continued currently.

Encoding of each other language documents, I wish to entrust translators.


Regards, Ioseph.

2016년 08월 23일 07:51에 Tatsuo Ishii 이(가) 쓴 글:
From: Alexander Law <exclusion@gmail.com>
Subject: UTF-8 docs
Date: Mon, 22 Aug 2016 16:36:14 +0300
Message-ID: <7fbf2e80-9507-0521-d0e9-913ab81a58df@gmail.com>


Hello,
I've just seen a discussion about docs endoding in pgsql-hackers.

https://www.postgresql.org/message-id/20160822.141645.655870136709055853.t-ishii%40sraoss.co.jp
Can we continue the discussion in this mailing list?
We (at Postgres Pro) have developed the whole build chain (with
support for l10n) so we can just share it.

I have been just subscribed to the pgsql-docs list.
Here is the last conversation with Peter at pgsql-hackers.


On 8/22/16 9:32 AM, Tatsuo Ishii wrote:

I don't know what kind of problem you are seeing with encoding
handling, but at least UTF-8 is working for Japanese, French and
Russian.

Those translations are using DocBook XML.

But in the mean time I can create UTF-8 HTML files like this:

make html
[snip]
/bin/mkdir -p html
SP_CHARSET_FIXED=1 SP_ENCODING=UTF-8 openjade  -wall -wno-unused-param -wno-empty -wfully-tagged -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d stylesheet.dsl -t sgml -i output-html -i include-index postgres.sgml

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

--------------2BBAC113E3701B2C55940012--