Re: [DOCS] Windows CHM format for the documents
[EMAIL PROTECTED] writes: > I'm not sure if it would be a bad thing to give up DocBook, but I cannot see > anything but benefits from using this other type of document development... I don't see any advantages that this would have over the current setup. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [DOCS] Windows CHM format for the documents
-On [20030910 04:02], [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: >I'm not sure if it would be a bad thing to give up DocBook, but I cannot see >anything but benefits from using this other type of document development... It would be. Editing simple text files is less cumbersome for a technical writer than it is to do everything on the database/front-end. (And I work as a professional technical writer in case someone cared.) -- Jeroen Ruigrok van der Werven / asmodai PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ A woman either loves or hates; she knows no medium. - Publilius ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] Windows CHM format for the documents
-On [20030908 05:02], Bruce Momjian ([EMAIL PROTECTED]) wrote: >I have added that to the Win32 project page: > > http://momjian.postgresql.org/main/writings/pgsql/win32.html If you move to DocBook/XML and use XSL(T) you can use the htmlhelp.xsl stylesheet and go directly to CHM from XML files. -- Jeroen Ruigrok van der Werven / asmodai PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ To desire immortality is to desire the eternal perpetuation of a great mistake... ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] Windows CHM format for the documents
> >I'm not sure if it would be a bad thing to give up DocBook, but I cannot see > >anything but benefits from using this other type of document development... > > It would be. Editing simple text files is less cumbersome for a > technical writer than it is to do everything on the database/front-end. > > (And I work as a professional technical writer in case someone cared.) Yes that makes sense... I'll come up with something to make editing easier. Probably the whole stuff would be in the editor at the same time.. Thanks for the feedback. Ilkka ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] [PATCHES] minor documentation improvements
Peter Eisentraut wrote: > Neil Conway writes: > > > So, is upper-case or lower-case better? I'd personally prefer > > lower-case, I suppose, but I'm not too bothered either way. > > If you want to change them all to lowercase, that would be fine by me. At > least it would prevent more people being confused into inconsistencies in > the future. Have we come to a conclusion here --- that we should lowercase _all_ GUC variable references, both in runtime.sgml, SGML docs, and error messages? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
