From: Tatsuo Ishii <ishii@postgresql.org>
To: bruce@momjian.us
Cc: peter@eisentraut.org
Cc: tgl@sss.pgh.pa.us
Cc: nagata@sraoss.co.jp
Cc: daniel@yesql.se
Cc: pgsql-hackers@postgresql.org
Subject: Re: Doc: typo in config.sgml
Date: Sat, 02 Nov 2024 12:02:12 +0900 (JST)
Message-ID: <20241102.120212.1541205818288992834.ishii@postgresql.org> (raw)
In-Reply-To: <ZyWAJp3Ujb2LNFpk@momjian.us>
References: <ZyUGLQ1jZ5MtRFnl@momjian.us>
<20241102.072700.1635141881080027242.ishii@postgresql.org>
<ZyWAJp3Ujb2LNFpk@momjian.us>
> Yes, we _allow_ LATIN1 characters in the SGML docs, but I replaced the
> LATIN1 characters we had with HTML entities, so there are none
> currently.
>
> I think it is too easy for non-Latin1 UTF8 to creep into our SGML docs
> so I added a cron job on my server to alert me when non-ASCII characters
> appear.
So you convert LATIN1 characters to HTML entities so that it's easier
to detect non-LATIN1 characters is in the SGML docs? If my
understanding is correct, it can be also achieved by using some tools
like:
iconv -t ISO-8859-1 -f UTF-8 release-17.sgml
If there are some non-LATIN1 characters in release-17.sgml,
it will complain like:
iconv: illegal input sequence at position 175
An advantage of this is, we don't need to covert each LATIN1
characters to HTML entities and make the sgml file authors life a
little bit easier.
Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
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-hackers@postgresql.org
Cc: ishii@postgresql.org, bruce@momjian.us, peter@eisentraut.org, tgl@sss.pgh.pa.us, nagata@sraoss.co.jp, daniel@yesql.se
Subject: Re: Doc: typo in config.sgml
In-Reply-To: <20241102.120212.1541205818288992834.ishii@postgresql.org>
* 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