On Tue, Apr 5, 2011 at 6:55 PM, Josh Kupershmidt wrote:
> On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas wrote:
>> In theory, we have
>> documentation that explains this:
>>
>> http://www.postgresql.org/docs/current/static/docguide-toolsets.html
>
> While we're on the subject..
>
> Attached is a pat
On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas wrote:
> In theory, we have
> documentation that explains this:
>
> http://www.postgresql.org/docs/current/static/docguide-toolsets.html
While we're on the subject..
Attached is a patch against that page suggesting using openjade 1.3,
not 1.4devel as p
On Tue, Apr 5, 2011 at 4:59 PM, Peter Eisentraut wrote:
> On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
>> and I've also had failures, I believe,
>> from not being connected to the Internet, which is surprising because
>> it's not at all obvious that building the docs should require an
>>
On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
> and I've also had failures, I believe,
> from not being connected to the Internet, which is surprising because
> it's not at all obvious that building the docs should require an
> Internet connection.
I understand this problem, but just to cl
On Tue, Apr 5, 2011 at 7:55 PM, Robert Haas wrote:
>
> I've also had failures, I believe,
> from not being connected to the Internet, which is surprising because
> it's not at all obvious that building the docs should require an
> Internet connection.
Oh, I've run into that and had it cause delay
On Tue, Apr 5, 2011 at 2:18 PM, Peter Eisentraut wrote:
> On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
>> AFAICT, the biggest problem with our existing toolchain is that it's
>> hard for some people to get it working. In theory, we have
>> documentation that explains this:
>>
>> http://w
On mån, 2011-04-04 at 19:26 +0200, Susanne Ebrecht wrote:
> Honestly, for German I don't mind yet if it is XML or SGML. XML might
> be better in future for maintenance tools.
>
> Anyway, I figured out there is another argument for XML:
>
> My information is that DocBook 5.0 won't support SGML any
Excerpts from Gabriele Bartolini's message of lun abr 04 16:47:26 -0400 2011:
> Il 04/04/11 22:26, Robert Haas ha scritto:
> > I think you still need to update Solution.pm to match.
> >
> Here it is, including change of 3 'Id' attributes (I made them lowercase).
Pushed this one also.
--
Álvaro
On mån, 2011-04-04 at 15:08 -0400, Tom Lane wrote:
> One thing I'd like to know is whether docbook v5 is any more
> portable/easier to install.
I don't see why. It's just a newer version of the same thing.
If you change the sources to XML and switch to the XSL toolchain, you
don't have to instal
On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
> AFAICT, the biggest problem with our existing toolchain is that it's
> hard for some people to get it working. In theory, we have
> documentation that explains this:
>
> http://www.postgresql.org/docs/current/static/docguide-toolsets.html
>
Il 04/04/11 22:26, Robert Haas ha scritto:
I think you still need to update Solution.pm to match.
Here it is, including change of 3 'Id' attributes (I made them lowercase).
Thanks,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartol
Excerpts from Robert Haas's message of lun abr 04 16:26:07 -0400 2011:
> On Mon, Apr 4, 2011 at 4:15 PM, Alvaro Herrera
> wrote:
> > Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400
> > 2011:
> >> Il 04/04/11 18:37, Tom Lane ha scritto:
> >> > AFAIK, the main stumbling bloc
On Mon, Apr 4, 2011 at 4:15 PM, Alvaro Herrera
wrote:
> Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400 2011:
>> Il 04/04/11 18:37, Tom Lane ha scritto:
>> > AFAIK, the main stumbling block for that is that XML doesn't allow
>> > abbreviated close tags (ie,whatever). Which
Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400 2011:
> Il 04/04/11 18:37, Tom Lane ha scritto:
> > AFAIK, the main stumbling block for that is that XML doesn't allow
> > abbreviated close tags (ie,whatever). Which is something that
> > we are not likely to give up. So I'm
On 04.04.2011 21:08, Tom Lane wrote:
Indeed. One thing I'd like to know is whether docbook v5 is any more
portable/easier to install
Unfortunately, as far as I know - there isn't a huge difference.
regards,
Susanne
--
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Train
On 4/4/11, Robert Haas wrote:
> On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne
> wrote:
>> On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht
>> wrote:
>>> Anyway, I figured out there is another argument for XML:
>>>
>>> My information is that DocBook 5.0 won't support SGML anymore.
>>>
>>> Whi
Robert Haas writes:
> On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne wrote:
>> There are arguments as to why to switch to version 5, which is,
>> indeed, XML-only.
>> http://www.docbook.org/tdg5/en/html/ch01.html#introduction-why-to-switch
> AFAICT, the biggest problem with our existing tool
On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne wrote:
> On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht
> wrote:
>> Anyway, I figured out there is another argument for XML:
>>
>> My information is that DocBook 5.0 won't support SGML anymore.
>>
>> Which means - sooner or later a reaction is
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht wrote:
> Anyway, I figured out there is another argument for XML:
>
> My information is that DocBook 5.0 won't support SGML anymore.
>
> Which means - sooner or later a reaction is needed.
Yes, indeed.
I don't think that during the 9.1 alpha phase
On Mon, Apr 4, 2011 at 2:42 PM, Tom Lane wrote:
> Robert Haas writes:
>> Even if that doesn't turn out to be the case, this is pretty harmless,
>> so maybe we should just apply it and move on.
>
> I have no great objection to the patch as such; just wondering what the
> roadmap is.
Me, too.
On
Robert Haas writes:
> Even if that doesn't turn out to be the case, this is pretty harmless,
> so maybe we should just apply it and move on.
I have no great objection to the patch as such; just wondering what the
roadmap is.
regards, tom lane
--
Sent via pgsql-hackers m
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht wrote:
> My information is that DocBook 5.0 won't support SGML anymore.
>
> Which means - sooner or later a reaction is needed.
Ouch.
Even if that doesn't turn out to be the case, this is pretty harmless,
so maybe we should just apply it and move o
On 04.04.2011 18:37, Tom Lane wrote:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,whatever). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're
Il 04/04/11 18:37, Tom Lane ha scritto:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,whatever). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You
Gabriele Bartolini writes:
> My intention was to start and change some simple documentation files in
> order to make our conversion process from SGML to XML smoother, while
> keeping the SGML compatibility of the original documentation intact.
AFAIK, the main stumbling block for that is that X
Hi Robert (and Tom),
Il 04/04/11 16:57, Robert Haas ha scritto:
Forgive me for asking what may seem like a stupid question, but what's
not XML compliant about them now, and why do we care? The text is
only ever going to parse as SGML (not XML) so I guess I don't see why
it matters. I don't rea
Gabriele Bartolini writes:
>I have made very small modifications to a few files in the
> documentation directory, which involve SGML entity declarations.
> Currently they are all written lowercase, the patch makes them
> uppercase. This won't affect SGML parsing, as SGML is case insensitive
On Mon, Apr 4, 2011 at 5:11 AM, Gabriele Bartolini
wrote:
> I have made very small modifications to a few files in the documentation
> directory, which involve SGML entity declarations. Currently they are all
> written lowercase, the patch makes them uppercase. This won't affect SGML
> parsing, a
Hi,
I have made very small modifications to a few files in the
documentation directory, which involve SGML entity declarations.
Currently they are all written lowercase, the patch makes them
uppercase. This won't affect SGML parsing, as SGML is case insensitive -
even though it is a good pr
29 matches
Mail list logo
