Alvaro Herrera wrote:
> Actually, now that I try it, it seems that the MediaWiki markup is not
> completely helpful here -- right now, on some items we have a one-line
> "header" and then possibly a longer description, and it seems the only
> way to do that in MediaWiki is like this:
>
> * Set pro
Actually, now that I try it, it seems that the MediaWiki markup is not
completely helpful here -- right now, on some items we have a one-line
"header" and then possibly a longer description, and it seems the only
way to do that in MediaWiki is like this:
* Set proper permissions on non-system sche
Alvaro Herrera wrote:
> Magnus Hagander wrote:
>> Alvaro Herrera wrote:
>
>>> Discussion with you and Magnus indicated that you were both committed to
>>> having the TODO on the wiki, but each was waiting on the other for
>>> anything to happen. Now that the PGCon dust has been settled for quite
Magnus Hagander wrote:
> Alvaro Herrera wrote:
> > Discussion with you and Magnus indicated that you were both committed to
> > having the TODO on the wiki, but each was waiting on the other for
> > anything to happen. Now that the PGCon dust has been settled for quite
> > a while, should we proc
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
>> Magnus has started moving the Developer's FAQ to a wiki. I am thinking
>> we should move the main FAQ and the TODO list to a wiki as well if the
>> community is in agreement.
>
> Discussion with you and Magnus indicated that you were both committ
Bruce Momjian wrote:
> Magnus has started moving the Developer's FAQ to a wiki. I am thinking
> we should move the main FAQ and the TODO list to a wiki as well if the
> community is in agreement.
Discussion with you and Magnus indicated that you were both committed to
having the TODO on the wiki
Joshua D. Drake wrote:
On Mon, 21 Apr 2008 19:06:53 +0200
Tino Wildenhain <[EMAIL PROTECTED]> wrote:
Well... or reStructuredText which has the advantage of beeing human
editable? (without specialized editor that is)
Huh? How is XML not human editable... didn't you ever create webpages
in vi?
Greg Smith wrote:
On Mon, 21 Apr 2008, Tino Wildenhain wrote:
Alvaro Herrera wrote:
I suggest we start an experiment with the FAQ in XML Docbook, which is
amenable to automatic processing, and move from there.
Well... or reStructuredText which has the advantage of beeing human
editable? (wit
Am Montag, 21. April 2008 schrieb Tino Wildenhain:
> Well... or reStructuredText which has the advantage of beeing human
> editable? (without specialized editor that is)
Well, there is also asciidoc, markdown, and various other wiki-like minimal
markup formats. All fine ideas, if we want to intr
On Mon, 21 Apr 2008, Tino Wildenhain wrote:
Alvaro Herrera wrote:
I suggest we start an experiment with the FAQ in XML Docbook, which is
amenable to automatic processing, and move from there.
Well... or reStructuredText which has the advantage of beeing human
editable? (without specialized ed
Tino Wildenhain wrote:
> Well... or reStructuredText which has the advantage of beeing human
> editable? (without specialized editor that is)
Hmm, that sounds like an useful idea, I'll do some research.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Re
On Mon, 21 Apr 2008 19:06:53 +0200
Tino Wildenhain <[EMAIL PROTECTED]> wrote:
> Well... or reStructuredText which has the advantage of beeing human
> editable? (without specialized editor that is)
Huh? How is XML not human editable... didn't you ever create webpages
in vi? :)
Joshua D. Drake
Alvaro Herrera wrote:
Bruce Momjian wrote:
Alvaro Herrera wrote:
As far as I know, what the doc translators do is translate the SGML
files directly, which is as difficult and cumbersome as you can possibly
get. I am in no way suggesting we do that for the FAQ.
What can we do to help people
Am Montag, 21. April 2008 schrieb Alvaro Herrera:
> Yes, basically my answer is "we don't". Currently there's no such thing
> as easy editing, and while I agree it would be good to have it, I don't
> have a solution for it.
I think easy editing and easy translating are sort of mutually exclusive
[EMAIL PROTECTED] (Bruce Momjian) writes:
> I am impressed at the state of the May wiki patch queue:
>
> http://wiki.postgresql.org/wiki/CommitFest:May
>
> It is even tracking the psql wrap patch I am working on now.
Aside: I have made a few little changes that oughtn't be too
controversial:
On Mon, 21 Apr 2008 12:22:45 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > I suggest we start an experiment with the FAQ in XML Docbook,
> > > which is amenable to automatic processing, and move from there.
> >
> > That makes sense. We
Bruce Momjian a écrit :
Alvaro Herrera wrote:
Bruce Momjian wrote:
Alvaro Herrera wrote:
As far as I know, what the doc translators do is translate the SGML
files directly, which is as difficult and cumbersome as you can possibly
get. I am in no way suggesting we do that for the FAQ.
What ca
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > I suggest we start an experiment with the FAQ in XML Docbook, which is
> > amenable to automatic processing, and move from there.
>
> That makes sense. We have many translations of the main FAQ so it would
> be a good test for the main docs. But
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
>
> > > As far as I know, what the doc translators do is translate the SGML
> > > files directly, which is as difficult and cumbersome as you can possibly
> > > get. I am in no way suggesting we do that for the FAQ.
> >
> > W
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > As far as I know, what the doc translators do is translate the SGML
> > files directly, which is as difficult and cumbersome as you can possibly
> > get. I am in no way suggesting we do that for the FAQ.
>
> What can we do to help people translate
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
> > Magnus Hagander wrote:
> >
> >> I remain very unconvinced that making it that much more complex is
> >> worth it.. But if someone sets up a complete system to test it, sure -
> >> since I don't write *or* read any of the translated FAQs we should
>
Brendan Jurd wrote:
> On Mon, Apr 21, 2008 at 11:20 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > For reference, the developer FAQ (which really is a different thing,
> > given the audience) now lives on the wiki at
> > http://wiki.postgresql.org/wiki/Developer_FAQ. I'd like to hear what
>
Magnus Hagander wrote:
> I'm sure we can find a way to do that. We do a lot of fairly ugly work
> to mirror from the cvs tree to the website today...
>
> For reference, the developer FAQ (which really is a different thing,
> given the audience) now lives on the wiki at
> http://wiki.postgresql.or
Joshua D. Drake wrote:
> Magnus Hagander wrote:
>
>> I remain very unconvinced that making it that much more complex is
>> worth it.. But if someone sets up a complete system to test it, sure -
>> since I don't write *or* read any of the translated FAQs we should
>> obviously listen more to those w
Alvaro Herrera wrote:
> ... and no response from Bruce, either.
Oh, I am trying not to read community email during weekends, especially
Sundays, so that is why you didn't get a reply earlier. I find it quite
liberating.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Enterpri
Peter Eisentraut wrote:
> Am Montag, 21. April 2008 schrieb Magnus Hagander:
> > Agreed. I don't think we *ever* backpatch FAQ stuff, which is a clear
> > indicator it's the later.
>
> Another thought: Would be still ship the FAQ in the release tarball? That
> might be a bit weird if it is not m
Alvaro Herrera wrote:
> Magnus Hagander wrote:
> > Alvaro Herrera wrote:
> > > Magnus Hagander wrote:
> > >
> > > > Hold on a minute. You're saying only the english version would be in
> > > > Docbook, and then you'd use .po files? So how do I as an end user
> > > > actually *read* the FAQ then? I
Peter Eisentraut wrote:
> Am Montag, 21. April 2008 schrieb Magnus Hagander:
> > Agreed. I don't think we *ever* backpatch FAQ stuff, which is a
> > clear indicator it's the later.
>
> Another thought: Would be still ship the FAQ in the release tarball?
> That might be a bit weird if it is not mai
Am Montag, 21. April 2008 schrieb Magnus Hagander:
> Agreed. I don't think we *ever* backpatch FAQ stuff, which is a clear
> indicator it's the later.
Another thought: Would be still ship the FAQ in the release tarball? That
might be a bit weird if it is not maintained in the source code reposit
Brendan Jurd wrote:
> On Mon, Apr 21, 2008 at 11:20 PM, Magnus Hagander
> <[EMAIL PROTECTED]> wrote:
> > For reference, the developer FAQ (which really is a different
> > thing, given the audience) now lives on the wiki at
> > http://wiki.postgresql.org/wiki/Developer_FAQ. I'd like to hear
> > wh
Magnus Hagander wrote:
Joshua D. Drake wrote:
And we've certainly had our share of people not working on the docs
because it's too hard. (I know I used to have to submit all docs
patches untested because it took me a year or so to get the build
process working on win32. Now I've given that up
On Mon, Apr 21, 2008 at 11:20 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> For reference, the developer FAQ (which really is a different thing,
> given the audience) now lives on the wiki at
> http://wiki.postgresql.org/wiki/Developer_FAQ. I'd like to hear what
> people think about that one
Joshua D. Drake wrote:
> Magnus Hagander wrote:
> > Alvaro Herrera wrote:
> >> Magnus Hagander wrote:
>
> > I remain very unconvinced that making it that much more complex is
> > worth it.. But if someone sets up a complete system to test it,
> > sure - since I don't write *or* read any of the tra
Magnus Hagander wrote:
> For reference, the developer FAQ (which really is a different thing,
> given the audience) now lives on the wiki at
> http://wiki.postgresql.org/wiki/Developer_FAQ. I'd like to hear what
> people think about that one, and get a "signoff" on if this should be
> the main loc
Alvaro Herrera wrote:
Actually not only I have to convince the translator -- I have to
convince Bruce *as a first step*. I have tried in the past and failed.
Now he is open to discuss changing the format of the FAQs, so I suggest
this idea again, and here I get a ton of negative responses from
On Mon, Apr 21, 2008 at 11:54 PM, Brendan Jurd <[EMAIL PROTECTED]> wrote:
> I did notice that the section on vim settings doesn't mention anything
> about the expandtab setting. Ideally this should be set to
> noexpandtab (noet) to preserve tab spacing. I'll add it to the wiki
> page, but fee
Magnus Hagander wrote:
Alvaro Herrera wrote:
Magnus Hagander wrote:
I remain very unconvinced that making it that much more complex is
worth it.. But if someone sets up a complete system to test it, sure -
since I don't write *or* read any of the translated FAQs we should
obviously listen mor
Magnus Hagander wrote:
> Alvaro Herrera wrote:
> > Magnus Hagander wrote:
> >
> > > Hold on a minute. You're saying only the english version would be in
> > > Docbook, and then you'd use .po files? So how do I as an end user
> > > actually *read* the FAQ then? I need to both process .po and
> > >
Peter Eisentraut wrote:
> Am Samstag, 19. April 2008 schrieb Alvaro Herrera:
> > The FAQs are another matter however. I suggested some time back
> > moving those to DocBook XML.
>
> The question is whether we consider the FAQ to be a document tied to
> a PostgreSQL release (e.g., there is a separ
Alvaro Herrera wrote:
> Magnus Hagander wrote:
>
> > Hold on a minute. You're saying only the english version would be in
> > Docbook, and then you'd use .po files? So how do I as an end user
> > actually *read* the FAQ then? I need to both process .po and
> > Docbook?
>
> The xml2po tools allow
Magnus Hagander wrote:
> Hold on a minute. You're saying only the english version would be in
> Docbook, and then you'd use .po files? So how do I as an end user
> actually *read* the FAQ then? I need to both process .po and Docbook?
The xml2po tools allow the reconstruction of translated XML fil
Am Samstag, 19. April 2008 schrieb Alvaro Herrera:
> The FAQs are another matter however. I suggested some time back moving
> those to DocBook XML.
The question is whether we consider the FAQ to be a document tied to a
PostgreSQL release (e.g., there is a separate FAQ applying to each release)
Joshua D. Drake wrote:
> Magnus Hagander wrote:
> > Alvaro Herrera wrote:
> >> The FAQs are another matter however. I suggested some time back
> >> moving those to DocBook XML. A friend was working on a script to
> >> do the initial conversion automatically. The nice thing about it
> >> is that
Alvaro Herrera wrote:
> Magnus Hagander wrote:
>
> > Looking at the state of many of our non-english FAQs today, I don't
> > put too much faith into a system that'll just show people "this is
> > not translated". I think it's more likely to get better if the
> > people can just edit the translatio
Magnus Hagander wrote:
Alvaro Herrera wrote:
The FAQs are another matter however. I suggested some time back
moving those to DocBook XML. A friend was working on a script to do
the initial conversion automatically. The nice thing about it is
that we can then use the xml2po tools to create PO
Magnus Hagander wrote:
> Looking at the state of many of our non-english FAQs today, I don't put
> too much faith into a system that'll just show people "this is not
> translated". I think it's more likely to get better if the people can
> just edit the translations directly instead of having to p
Alvaro Herrera wrote:
> The FAQs are another matter however. I suggested some time back
> moving those to DocBook XML. A friend was working on a script to do
> the initial conversion automatically. The nice thing about it is
> that we can then use the xml2po tools to create PO files for
> transl
Hello
>
> Magnus has started moving the Developer's FAQ to a wiki. I am thinking
> we should move the main FAQ and the TODO list to a wiki as well if the
> community is in agreement.
>
Czech translation of FAQ is on wiki one year - and it's much more
maintainable than HTML.
http://www.pgsql.cz
Bruce Momjian wrote:
The FAQs are another matter however. I suggested some time back moving
those to DocBook XML. A friend was working on a script to do the
initial conversion automatically. The nice thing about it is that we
can then use the xml2po tools to create PO files for translation.
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I am impressed at the state of the May wiki patch queue:
> >
> > http://wiki.postgresql.org/wiki/CommitFest:May
> >
> > It is even tracking the psql wrap patch I am working on now.
>
> Thanks. We've put a certain amount of effort on it. Cred
Bruce Momjian wrote:
> I am impressed at the state of the May wiki patch queue:
>
> http://wiki.postgresql.org/wiki/CommitFest:May
>
> It is even tracking the psql wrap patch I am working on now.
Thanks. We've put a certain amount of effort on it. Credit for the
templating system goes to
I am impressed at the state of the May wiki patch queue:
http://wiki.postgresql.org/wiki/CommitFest:May
It is even tracking the psql wrap patch I am working on now.
Magnus has started moving the Developer's FAQ to a wiki. I am thinking
we should move the main FAQ and the TODO list to a
52 matches
Mail list logo
