Date: Sat, 02 Nov 2024 12:02:12 +0900 (JST)
Message-Id: <20241102.120212.1541205818288992834.ishii@postgresql.org>
To: bruce@momjian.us
Cc: peter@eisentraut.org, tgl@sss.pgh.pa.us, nagata@sraoss.co.jp,
 daniel@yesql.se, pgsql-hackers@postgresql.org
Subject: Re: Doc: typo in config.sgml
From: Tatsuo Ishii <ishii@postgresql.org>
In-Reply-To: <ZyWAJp3Ujb2LNFpk@momjian.us>
References: <ZyUGLQ1jZ5MtRFnl@momjian.us>
	<20241102.072700.1635141881080027242.ishii@postgresql.org>
	<ZyWAJp3Ujb2LNFpk@momjian.us>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20241102.120212.1541205818288992834.ishii%40postgresql.org>
Precedence: bulk

> 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