Re: Doc: typo in config.sgml
От | Yugo Nagata |
---|---|
Тема | Re: Doc: typo in config.sgml |
Дата | |
Msg-id | 20241008211854.9f1b17b843395c096be5b5af@sraoss.co.jp обсуждение исходный текст |
Ответ на | Re: Doc: typo in config.sgml (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Doc: typo in config.sgml
|
Список | pgsql-hackers |
On Mon, 7 Oct 2024 15:45:54 -0400 Bruce Momjian <bruce@momjian.us> wrote: > On Mon, Sep 30, 2024 at 11:59:48AM +0200, Daniel Gustafsson wrote: > > > On 30 Sep 2024, at 11:03, Tatsuo Ishii <ishii@postgresql.org> wrote: > > > > > >>>> I think there's an unnecessary underscore in config.sgml. > > > > > > I was wrong. The particular byte sequences just looked an underscore > > > on my editor but the byte sequence is actually 0xc2a0, which must be a > > > "non breaking space" encoded in UTF-8. I guess someone mistakenly > > > insert a non breaking space while editing config.sgml. > > > > I wonder if it would be worth to add a check for this like we have to tabs? > > The attached adds a rule to "make -C doc/src/sgml check" for trapping nbsp > > (doing so made me realize we don't have an equivalent meson target). > > Can we check for any character outside the support range of SGML? What we can define the range of allowed characters range in SGML? We can detect non-ASCII characters by using regexp /\P{ascii}/ or /[^\x00-\x7f]/, but they are used in some places in charset.sgml and some names in release-*.sgml. Regards, Yugo Nagata > > -- > Bruce Momjian <bruce@momjian.us> https://momjian.us > EDB https://enterprisedb.com > > When a patient asks the doctor, "Am I going to die?", he means > "Am I going to die soon?" > > -- Yugo Nagata <nagata@sraoss.co.jp>
В списке pgsql-hackers по дате отправления: