Re: Proposal: new border setting in psql

Поиск
Список
Период
Сортировка
От Greg Smith
Тема Re: Proposal: new border setting in psql
Дата
Msg-id Pine.GSO.4.64.0901081344170.11423@westnet.com
обсуждение исходный текст
Ответ на Re: Proposal: new border setting in psql  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Ответы Re: Proposal: new border setting in psql  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Список pgsql-hackers
On Thu, 8 Jan 2009, D'Arcy J.M. Cain wrote:

> On Thu, 8 Jan 2009 12:08:06 -0500 (EST)
> Bruce Momjian <bruce@momjian.us> wrote:
>> Right, so Tom says it isn't 100% ReST:
>>
>>     http://archives.postgresql.org/pgsql-hackers/2008-08/msg01310.php
>
> Right but did you see the followup?
>
> http://archives.postgresql.org/pgsql-hackers/2008-08/msg01319.php

Unfortunately, finding cases where the special markup characters don't 
matter isn't the same as proving that they will never matter.  The best 
example of that I noticed in the spec relates to Enumerated Lists.  This:

A. Einstein was a really
smart dude.

Is parsed as two lines of text, while:

A. Einstein was a really smart dude.

Will be treated as a single-item list.  That sort of ambiguity is quite a 
hindrance to machine-generation of ReST code.  As the spec itself is very 
loose, barring a deep read of the docutils code to figure out the rules 
that exist only via the code implementation it seems to me the only robust 
way around it is to just escape every special character.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "David E. Wheeler"
Дата:
Сообщение: Mention CITEXT in the FAQ
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Proposal: new border setting in psql