Re: [DOCS] French PDF manual
On 26/05/06, Guillaume Lelarge <[EMAIL PROTECTED]> wrote: 2006/5/26, Peter Eisentraut <[EMAIL PROTECTED]>: > Am Freitag, 26. Mai 2006 14:19 schrieb Guillaume Lelarge: > > Yes, you're right. There's some changes to do on the documentation > > source files. I can provide a diff which will transform SGML files > > into valid XML files. > I've got the 8.1 postgres manuals in DocbookXML 4.2 format and I'm using POT files for translations. As soon as possible I'll have with the html, xml, pot and a little status page avaliable. However, the xml files are not 100% valid but it works for me. > Is that the only change? Then we don't need it. > I added some tags to specify columns' size (http://www.oasis-open.org/docbook/documentation/reference/html/colspec.html and http://www.sagehill.net/docbookxsl/ColumnWidths.html) and XSLT stylesheets to build HTML, PDF, htmlhelp and manpages. I also added some attributes to handle conditional texts (http://www.sagehill.net/docbookxsl/Profiling.html#MarkProfileText), needed to build the standalone install file. > > Do you want me to work on REL8_1_STABLE or HEAD > > branch ? > > HEAD branch always. > OK. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [DOCS] Switching to XML
On 08/12/06, Joshua D. Drake <[EMAIL PROTECTED]> wrote: There is a long standing support within the community to move to XML including: Josh Berkus Josh Drake Robert Treat Andrew Dunslane David Blewett David Fetter Devrim Gunduz Darcy Buskermolen And that is just from #postgresql And now in Chile, I wrote an app to translate postgres documentation (l10n.postgresql.cl). I took SGML sources, transform to XML and to POT files The results are good! but is it not the best. To move from SGML to XML is a hard work. -- http://www.advogato.org/person/mgonzalez/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[DOCS] Format Documents
Hello, This is my first post here, greetings! Well, I'm very interesting to help to translate PostgreSQL documents but I've seen all documents are in SGML. So I've got a question, will you change this format some time to DocBook XML? ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [DOCS] French PDF manual
On 08/05/06, Tom Lane <[EMAIL PROTECTED]> wrote: Alvaro Herrera <[EMAIL PROTECTED]> writes: > Peter Eisentraut wrote: >> Well, you can go into the documentation source directory and type 'make >> postgres.xml' to get an XML formatted DocBook file automatically. >> >> It has occasionally been suggested to convert the source of the >> documentation to XML, but while I'm not opposed to that, I don't see >> any specific advantages coming from such a move. > It would allow us to use xml2po to maintain translations, for one. Sounds like you can use that today, if you want to; it's just one extra step. But would it really be helpful on the documentation? I see where .po works for a lot of short, independent error messages, but I don't see it being real useful for big manuscripts. Hello! my name is Mario and I've been working in that. For learning purposes I'm writing the FAQ in a xml document. And, like Alvaro said, «it would allow us to use xml2po» So, what can we use for big documents instead? ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] DocBook/XML summary
On 15/07/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote: Joshua D. Drake wrote: > > - Translation tools may work better with XML sources. (Totally > > unconfirmed; would need to be in actual use by someone.) > > Do you mean language translation or transformation (as in pdf?). Language translation That's true. I've been working a bit in "Language translation", with Alvaro's help I'm writing a webapps for translate strings. In others words, to use the POT way in a webapps (l10n.postgresql.cl) And then, build the entire HTML manuals from .po -> DocbookXML -> HTML, I'm working as fast as I can. Sadly I haven't got a Postgres full time work :-) -- http://www.advogato.org/person/mgonzalez/ ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[DOCS] 'FOUND' keyword not found in index (pg8.2)
Hi. I was told earlier to 'report' those kind of things on this mailinglist, if I'm making a mistake here I appologize, and I'd appreciate guidelines for future 'reportings'. So, there goes: In PostgreSQL plpgsql language there is special variable calles FOUND, which is described here: http://www.postgresql.org/docs/8.2/interactive/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS Still, there is no mention of it in postgresql Index: http://www.postgresql.org/docs/8.2/interactive/bookindex.html Am I missing something here, or 'FOUND' keyword should be enlisted in Index? Mario ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [DOCS] Volunteer to build a configuration tool
On 18/06/07, Campbell, Lance <[EMAIL PROTECTED]> wrote: Next the person would press a button, "generate", found below the questions. The JavaScript HTML page would then generate content for two Iframes at the bottom on the page. One Iframe would contain the contents of the postgresql.conf file. The postgresql.conf settings would be tailored more to the individuals needs than the standard default file. The second Iframe would contain the default settings one should consider using with their operating system. I think it could be a great help to newbies. IMVHO a bash script in dialog could be better than a javascript file. There are many administrators with no graphics navigator or with no javascript. -- http://www.advogato.org/person/mgonzalez/ ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [DOCS] Volunteer to build a configuration tool
On 18/06/07, Campbell, Lance <[EMAIL PROTECTED]> wrote: Mario, The JavaScript configuration tool I proposed would not be in the install of PostgreSQL. It would be an HTML page. It would be part of the HTML documentation or it could be a separate HTML page that would be linked from the HTML documentation. Ok, then I'm not the correct person to make that decision, however just a tip: the postgresql documentation was wrote in DocBook SGML -- http://www.advogato.org/person/mgonzalez/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] Contrib modules documentation online
On 29/08/2007, Neil Conway <[EMAIL PROTECTED]> wrote: > > I wonder if it would be possible to keep the master version of the > contrib docs as SGML, and generate plaintext READMEs from it during the > documentation build. > Hello Neil, I think I'm doing something similar but not with README files. Currently I'm writing the FAQ into Docbook XML, that's why we can build the HTML and plain text at one. I'm going to finish this week then I'll show the results. > -- http://www.advogato.org/person/mgonzalez/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[DOCS] Array functions not mentioned in Index
None of the array functions (http://www.postgresql.org/docs/8.3/interactive/functions-array.html) are mentioned in the documentation index. Is that intentional? I thought it would be 'handy' to have those functions referenced in index. Mike -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Array functions not mentioned in Index
Alvaro Herrera wrote: Mario Splivalo wrote: None of the array functions (http://www.postgresql.org/docs/8.3/interactive/functions-array.html) are mentioned in the documentation index. Is that intentional? I thought it would be 'handy' to have those functions referenced in index. Agreed -- please submit a patch. Sure thing. It will take some time to get along with Docbook, indexing and everything. Mike -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Array functions not mentioned in Index
Alvaro Herrera wrote: > Mario Splivalo wrote: >> None of the array functions >> (http://www.postgresql.org/docs/8.3/interactive/functions-array.html) >> are mentioned in the documentation index. Is that intentional? >> I thought it would be 'handy' to have those functions referenced in index. > > Agreed -- please submit a patch. Hope this is ok. How can I submit patch for 8.3 documentation? Mario ? func.sgml.patch Index: doc/src/sgml/func.sgml === RCS file: /projects/cvsroot/pgsql/doc/src/sgml/func.sgml,v retrieving revision 1.473 diff -c -r1.473 func.sgml *** doc/src/sgml/func.sgml 23 Mar 2009 21:00:38 - 1.473 --- doc/src/sgml/func.sgml 1 Apr 2009 01:48:14 - *** *** 9338,9343 --- 9338,9380 for more discussion and examples of the use of these functions. + + array_append + + + array_cat + + + array_ndims + + + array_dims + + + array_fill + + + array_length + + + array_lower + + + array_prepend + + + array_to_string + + + array_upper + + + string_to_array + + + cardinality + + Array Functions -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Array functions not mentioned in Index
Tom Lane wrote: Mario Splivalo writes: Hope this is ok. How can I submit patch for 8.3 documentation? I think you just did. Applied, thanks. I pulled the source from CVS HEAD branch, I see that is 8.4 documentation (for instance, 'cardinality' function is nonexistant for 8.3). PS: why'd you omit unnest()? I overlooked it, I guess. Sorry. Mike -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] Underscorces in copy-documentation (9.0 and higher)
Hi,
- http://www.postgresql.org/docs/9.2/static/sql-copy.html,
- http://www.postgresql.org/docs/9.1/static/sql-copy.html and
- http://www.postgresql.org/docs/9.0/static/sql-copy.html
have underscores ("_") where there should be none,
e.g. in "FORCE_QUOTES".
Best regards,
Fwd: [DOCS] Underscorces in copy-documentation (9.0 and higher)
2013/3/20 Tom Lane : > Huh? The references to FORCE_QUOTE look correct to me. The syntax > doesn't support multi-word option names, so it has to be like that > (or else run the words together, which doesn't sound like an > improvement). Thanks, Tom, for your quick response. Maybe this is just a miscommunication, sorry for that then (i.e. I misunderstood the documentation here). (Stupid) example for the problem: "COPY (SELECT aggfnoid, aggtransfn from pg_aggregate) TO STDOUT WITH FORCE QUOTE * DELIMITER ',' CSV HEADER;" will run, a FORCE_QUOTE or FORCEQUOTE won't (e.g. on a "PostgreSQL 9.2.3 on i386-portbld-freebsd9.1, compiled by cc (GCC) 4.2.1 20070831 patched [FreeBSD]"). Best regards, Mario -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Underscorces in copy-documentation (9.0 and higher)
2013/3/20 Tom Lane > As Ian notes, that's the old syntax with a hard-wired option set. > The lack of parentheses after WITH is the difference. Aarfh, thanks, guys! -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
