On 06.09.24 10:50, Jürgen Purtz wrote:
For the PG community I would like to raise the question: Do we need
DocBook in the distro of any operating system? In the past we developed
some stylesheets to adopt DocBook to our needs. They are part of PG's
distro and refer to the standard with statemen
I took another look at this issue, and found that no Red Hat distro is
yet shipping DocBook 5.2; not even Fedora 40 which is bleeding edge.
So I would have to obtain and manually install the relevant DTDs
and style sheets, as would a lot of other contributors. I'm less
familiar with the D
=?UTF-8?Q?J=C3=BCrgen_Purtz?= writes:
> [ conversion to DocBook 5.2 ]
I took another look at this issue, and found that no Red Hat distro is
yet shipping DocBook 5.2; not even Fedora 40 which is bleeding edge.
So I would have to obtain and manually install the relevant DTDs
and style sheets,
#x27;m willing to work on this
if a) there is a consensus in the community that the work should go on
and b) someone helps me to resolve the reported unacceptable runtime
problem during PDF generation.
--
J. Purtz
DocBook 5.2 is published [1] [2].
This mail contains a new version of the Pos
Yeah, I think we'd have to convert all the supported versions to
make this palatable. If the conversion is sufficiently automated,
that might not be a big lift. (If it's*not* automated, I think
the change would never get off the ground even for HEAD, because
the docs are too much of a moving ta
are the benefits of making this
> >> change? They better be very very substantial.
>
> > Would we be converting docs for all supported versions of Postgres to
> > use DocBook 5.2, or just the most current version? If the later, we
> > would find backpatching a pain fo
stantial.
> Would we be converting docs for all supported versions of Postgres to
> use DocBook 5.2, or just the most current version? If the later, we
> would find backpatching a pain for five years.
Yeah, I think we'd have to convert all the supported versions to
make th
t are the benefits of making this
> change? They better be very very substantial.
Would we be converting docs for all supported versions of Postgres to
use DocBook 5.2, or just the most current version? If the later, we
would find backpatching a pain for five years.
--
Bruce Momji
On 05.09.22 11:50, Jürgen Purtz wrote:
Therefore, we should consider to introduce another validator. During the
migration phase,
we have used **jing**. It's Java, it's fast, the error messages are very
precise. But there
are many others:https://relaxng.org/#validators. Should we possibly provid
On 05.09.22 14:15, Guillaume Lelarge wrote:
Le lun. 5 sept. 2022 à 13:14, Alvaro Herrera
a écrit :
On 2022-Sep-05, Jürgen Purtz wrote:
> -
> +
> User-Defined Types
OK, these seem quite significant changes that are likely to cause
great
pain. So I repeat my q
Le lun. 5 sept. 2022 à 13:14, Alvaro Herrera a
écrit :
> On 2022-Sep-05, Jürgen Purtz wrote:
>
> > -
> > +
> >User-Defined Types
>
> OK, these seem quite significant changes that are likely to cause great
> pain. So I repeat my question, what are the benefits of making this
> change? They
On 2022-Sep-05, Jürgen Purtz wrote:
> -
> +
> User-Defined Types
OK, these seem quite significant changes that are likely to cause great
pain. So I repeat my question, what are the benefits of making this
change? They better be very very substantial.
--
Álvaro HerreraBreisgau, D
On 05.09.22 11:59, Daniel Gustafsson wrote:
Will the markup be similar enough to not carry a significant risk of
introducing pain for backpatching doc patches?
There are many changes. Most of them are systematically and others are
individual, which is more painful. To give you an impression wh
> On 5 Sep 2022, at 11:50, Jürgen Purtz wrote:
>
> On 04.09.22 17:39, Alvaro Herrera wrote:
>> What changes?
>> I doubt we'll want to adopt a new version immediately after release,
>> since we want to stay compatible with older systems.
>
> The migration isn't a matter of days. It's a huge step
we have to act carefully to deliver (nearly)
identical HTML, PDF, ... files as before. As a preview of the ongoing
the actual README.md file is attached.
Jürgen Purtz
Migration of PG's documentation from DocBook 4.5 to DocBook 5.2
===
On 2022-Sep-04, Jürgen Purtz wrote:
> DocBook 5.2 is around the corner [1], we use DocBook 4.5 which is 'feature
> frozen' since 2006, and there are even ideas for DocBook 6.x [2].
What changes?
I doubt we'll want to adopt a new version immediately after release,
DocBook 5.2 is around the corner [1], we use DocBook 4.5 which is
'feature frozen' since 2006, and there are even ideas for DocBook 6.x [2].
I want to inform you that I'm working on an upgrade of our documentation
to DocBook 5.2. Major steps have been done, but I need some more
17 matches
Mail list logo
