Re: pgAdmin Documentation
От | Guillaume Lelarge |
---|---|
Тема | Re: pgAdmin Documentation |
Дата | |
Msg-id | 464B7F7E.6030801@lelarge.info обсуждение исходный текст |
Ответ на | pgAdmin Documentation (Dave Page <dpage@postgresql.org>) |
Ответы |
Re: pgAdmin Documentation
|
Список | pgadmin-hackers |
Dave Page a écrit : > I've been thinking about trying to sort out the documentation included > in pgAdmin. As you know, we currently bundle both the PostgreSQL and > Slony docs with pgAdmin - what you may not know is that integrating > these together at build time is a real pain, not to mention that those > docs account for a major percentage of the number of files in our > subversion repository, tarballs and Unix builds, and are also a fair > percentage of the total size. > > There are at least a couple of options: > > 1) Leave things as they are, maybe attempt to script some of the build > tasks. > > 2) Un-bundle the PostgreSQL and Slony docs. Allow the user to select a > directory, CHM file, or website for each of these (we already allow a > website to be selected for the PostgreSQL docs). This has the additional > advantage that the user can use the docs for their server/slony version, > rather than the ones we bundle. > There's one more advantage to this method : we can use a translated manual. > If we were to do the latter, in the Windows Installer for PostgreSQL > (which we also need to consider, because it relies on our bundled docs), > we would just build the CHM files for each of the three packages, > without trying to merge them together. > > Thoughts? > I would definitly vote for option 2. -- Guillaume. <!-- http://abs.traduc.org/ http://lfs.traduc.org/ http://docs.postgresqlfr.org/ -->
В списке pgadmin-hackers по дате отправления: