t...@sss.pgh.pa.us (Tom Lane) writes:
> Peter Eisentraut writes:
>> On lör, 2010-06-12 at 11:18 +0200, John Gage wrote:
>>> A one file html version would be a godsend.
>
>> I've committed a build target for that now. Use 'make postgres.html' in
>> doc/src/sgml/.
>
> Huh, is that actually worth a
Tim Landscheidt wrote:
> Bruce Momjian wrote:
>
> > [...]
> > + # single-page text
> > + postgres.txt: postgres.html
> > + $(LYNX) -force_html -dump -nolist -stdin $< > $@
> ^^
> > +
> > [...]
>
> Isn't that unnecessary/wrong as the filename is sup
Bruce Momjian wrote:
> [...]
> + # single-page text
> + postgres.txt: postgres.html
> + $(LYNX) -force_html -dump -nolist -stdin $< > $@
^^
> +
> [...]
Isn't that unnecessary/wrong as the filename is supplied on
the command line?
Tim
--
Sent
John Gage wrote:
> UFB! This was definitely worth the visit from the Nebula.
>
> Thanks very, very much.
>
> Sensational.
>
> Thanks again,
>
> John Gage
We still have to decide how to make these accessible from our web site.
--
Bruce Momjian http://momjian.us
EnterpriseDB
UFB! This was definitely worth the visit from the Nebula.
Thanks very, very much.
Sensational.
Thanks again,
John Gage
On Jun 12, 2010, at 6:01 PM, Bruce Momjian wrote:
http://momjian.us/expire/
The new rule name is postgres.txt. The file size are:
7,789,730 postgres.h
Peter Eisentraut wrote:
> On l?r, 2010-06-12 at 09:10 -0400, Tom Lane wrote:
> > Peter Eisentraut writes:
> > > On l?r, 2010-06-12 at 11:18 +0200, John Gage wrote:
> > >> A one file html version would be a godsend.
> >
> > > I've committed a build target for that now. Use 'make postgres.html' in
On lör, 2010-06-12 at 09:10 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > On lör, 2010-06-12 at 11:18 +0200, John Gage wrote:
> >> A one file html version would be a godsend.
>
> > I've committed a build target for that now. Use 'make postgres.html' in
> > doc/src/sgml/.
>
> Huh, is tha
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Peter Eisentraut writes:
> > I've committed a build target for that now. Use 'make postgres.html' in
> > doc/src/sgml/.
>
> Huh, is that actually worth anything? How many browsers will open it
> without crashing, or will navigate the page with decent per
It was. But if the compromise is single file html, that is a vast
improvement over the current system imho.
What I want is the thing that is maximally amenable to being searched
conveniently using all the tools at our disposal especially regular
expressons. The point has been made that Go
Peter Eisentraut writes:
> On lör, 2010-06-12 at 11:18 +0200, John Gage wrote:
>> A one file html version would be a godsend.
> I've committed a build target for that now. Use 'make postgres.html' in
> doc/src/sgml/.
Huh, is that actually worth anything? How many browsers will open it
without
On lör, 2010-06-12 at 11:18 +0200, John Gage wrote:
> A one file html version would be a godsend.
I've committed a build target for that now. Use 'make postgres.html' in
doc/src/sgml/.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
A one file html version would be a godsend.
On Jun 12, 2010, at 3:20 AM, Bruce Momjian wrote:
Robert Gravsjö wrote:
I am for #1, not so much for #2, mainly on the grounds of size.
But
given #1 it would be possible for packagers to make their own
choices
about whether to include plain-te
Robert Gravsj?? wrote:
> >> I am for #1, not so much for #2, mainly on the grounds of size. But
> >> given #1 it would be possible for packagers to make their own choices
> >> about whether to include plain-text docs.
> >
> > Wouldn't it suffice to make it downloadable, like the pdf doc?
>
> And/
Leif Biberg Kristensen skrev 2010-06-10 17.33:
On Thursday 10. June 2010 17.24.00 Tom Lane wrote:
Alvaro Herrera writes:
Excerpts from Peter Eisentraut's message of jue jun 10 02:50:14 -0400
2010:
As I said back then, doing this is straightforward, but we kind of need
more than one user wh
Like all visitors from the Crab Nebula (except our leaders who are
genetically separate) I qualify as a novice when it comes to
Postgres. What is more, the people (humans, that is) who need the
documentation the most are those who, well, need the documentation the
most.
Hence, if this we
On Thursday 10. June 2010 17.24.00 Tom Lane wrote:
> Alvaro Herrera writes:
> > Excerpts from Peter Eisentraut's message of jue jun 10 02:50:14 -0400
2010:
> >> As I said back then, doing this is straightforward, but we kind of need
> >> more than one user who asks for it before we make it part o
Alvaro Herrera writes:
> Excerpts from Peter Eisentraut's message of jue jun 10 02:50:14 -0400 2010:
>> As I said back then, doing this is straightforward, but we kind of need
>> more than one user who asks for it before we make it part of a regular
>> service, which comes with maintenance costs.
Excerpts from Peter Eisentraut's message of jue jun 10 02:50:14 -0400 2010:
> On tis, 2010-06-08 at 11:04 +0200, John Gage wrote:
> >
> > Yet, the only one file edition of the Postgres documentation is
> > in...pdf format. Huh?
> >
> > I know. I know. I have already brought this up. And var
On tis, 2010-06-08 at 11:04 +0200, John Gage wrote:
>
> Yet, the only one file edition of the Postgres documentation is
> in...pdf format. Huh?
>
> I know. I know. I have already brought this up. And various ways
> of
> creating a one file text edition of the documentation have been
> p
Brian Modra wrote:
Personally I like to use html docs, and it would be good if the
documentation were downloadable from the postgresql website in other
formats, for convenience...
Good thing it is, then, albeit not in the most convenient format, i.e.,
DocBook. But then, from there you can gen
Excerpts from John Gage's message of mié jun 09 01:28:54 -0400 2010:
> I recently was re-looking at my files and saw
> "tsvector::text". I had forgotten that the double colon is one way to
> cast a type. Double colon is not in the html index of the
> documentation.
I just added an index e
Dave Coventry writes:
> Formatted text, whether PDF, HTML or (heaven forbid!) Word Documents,
> is easier to read than unformatted plain text, and those of us without
> the OP's very admirable proficiency in vi remain at the mercy of the
> various readers and their associated search functions.
>
>
My tupp'th:
Formatted text, whether PDF, HTML or (heaven forbid!) Word Documents,
is easier to read than unformatted plain text, and those of us without
the OP's very admirable proficiency in vi remain at the mercy of the
various readers and their associated search functions.
However, I sure that
Brian Modra schrieb:
Personally I like to use html docs, and it would be good if the
documentation were downloadable from the postgresql website in other
formats, for convenience...
But, what I use is this, which works pretty well:
(e.g. to get the 8.1 dosc)
mkdir postgresql
cd postgresql
wge
On 09/06/2010, John Gage wrote:
> 1) On a list that howls with complaints when posts are in html, it is
> surprising that there is resistance to the idea of documentation in
> plain text.
>
> 2) Posters are correctly referred to the documentation as frequently
> as possible. In fact, very frequen
John Gage wrote:
Posters are correctly referred to the documentation as frequently as
possible. In fact, very frequently. The frequency might decrease if
the documentation were in plain text. It is easier to search a single
plain text file than any other source, except perhaps the database
1) On a list that howls with complaints when posts are in html, it is
surprising that there is resistance to the idea of documentation in
plain text.
2) Posters are correctly referred to the documentation as frequently
as possible. In fact, very frequently. The frequency might decrease
On Tue, Jun 8, 2010 at 5:04 AM, John Gage wrote:
> I do suggest that a plain text file of the entire documentation be made part
> of the documentation armamentarium.
Not that I see a whole lot of utility in this endeavor, but it's
possible to do a decent PDF to plain text conversion. I tried some
Justin Graf wrote:
There are linux chm readers
...
Note that even Microsoft deprecated CHM back in 2003 after it was
realized it was full of potential security exploits that couldn't
readily be abated.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
***SNIP***
> 2) Its also available in chm windows help file format. Which i find
> allot
> more useful
> http://www.postgresql.org/docs/manuals/
> you could print chm to a text file.
>
> --I'll have to boot over to XP, ugh. Will do.
There are linux chm readers
http://www.linux.com/news/sof
jus...@magwerks.com (Justin Graf) writes:
> Its also available in chm windows help file format. Which i find allot
> more useful
> http://www.postgresql.org/docs/manuals/
> you could print chm to a text file.
>
> also it not hard to dump a PDF document into a text file.
I wish I could find a co
Thank you all for your suggestions. Thank you very much.
John
1) I suppose the next thing you'll be suggesting is that, because
Postgres is a database, the documentation should be stored as some
form of searchable table within the database itself?
--Well, that is exactly what I have
* John Gage (jsmg...@numericable.fr) wrote:
> But either I am a visitor from the Crab Nebula, or there is someone else
> out there who would like to have a text file of the entire
> documentation.
Soo.. there are quite a few man pages, and in-psql's help is also
pretty nice (\h and \?). That
On 6/8/2010 9:23 AM, Peter Hunsberger wrote:
> On Tue, Jun 8, 2010 at 4:04 AM, John Gage wrote:
>
>> Unix is a text-based operating system with unbelievably helpful text
>> manipulation tools.
>>
>> Postgres is a creature of Unix which happens to have unbelievable text
>> searching and manipul
On Tue, Jun 8, 2010 at 4:04 AM, John Gage wrote:
> Unix is a text-based operating system with unbelievably helpful text
> manipulation tools.
>
> Postgres is a creature of Unix which happens to have unbelievable text
> searching and manipulation tools.
>
> Yet, the only one file edition of the Pos
John Gage wrote:
I also use the National Library of Medicine's MeSH subject headings.
25,000 descriptors with definitions, synonyms and a lot of other things.
They give it to you in single files either as text, xml, or other ways.
Big files. Hundreds of megabytes. That makes it so that you can do
Unix is a text-based operating system with unbelievably helpful text
manipulation tools.
Postgres is a creature of Unix which happens to have unbelievable text
searching and manipulation tools.
Yet, the only one file edition of the Postgres documentation is
in...pdf format. Huh?
I know
37 matches
Mail list logo
