Thread: [FYI] german postgresql docs
Hi all, Christian Stasius (stasius@t-online.de) and I are working on the translation of the postgresql documentation. Christian has just finished his work on the tutorial. We are going to translate the other documents now. The docs will be available online soon, the url will be posted here. Please mail me, if you are working on german translations, too. have fun! Karsten -- Linux Systemhaus Schulz Tel.: 0231 3944432 Karsten Schulz Fax.: 0231 3944435 Hauptfeld 18 schulz@linux-systemhaus.de 44369 Dortmund http://www.linux-systemhaus.de/
> Christian Stasius (stasius@t-online.de) and I are working on the
> translation of the postgresql documentation. Christian has just finished
> his work on the tutorial. We are going to translate the other
> documents now. The docs will be available online soon, the url will be
> posted here.
Great! Are you translating the sgml source docs? If so, should we
include those in the CVS tree, or can you suggest another way of keeping
track of the latest versions?
Also, there was a request from the Spanish translators to coordinate
changes in the source docs, so they can make updates to the
translations. I can generate context diffs from CVS, but if you have
other ideas please speak up.
We've recently seen complete translations in Spanish and Chinese, and
this will be a fantastic addition to the set.
- Thomas
Thomas Lockhart wrote: > > Christian Stasius (stasius@t-online.de) and I are working on the > > translation of the postgresql documentation. Christian has just finished > > his work on the tutorial. We are going to translate the other > > documents now. The docs will be available online soon, the url will be > > posted here. > > Great! Are you translating the sgml source docs? If so, should we > include those in the CVS tree, or can you suggest another way of keeping > track of the latest versions? > > Also, there was a request from the Spanish translators to coordinate > changes in the source docs, so they can make updates to the > translations. I can generate context diffs from CVS, but if you have > other ideas please speak up. > > We've recently seen complete translations in Spanish and Chinese, and > this will be a fantastic addition to the set. > > - ThomasI I'v done my SGML tranalation, so I'll very appreciate for the diffs you make -- for me to upgrade those docs. Also, you may include them in CVS tree, if you like. Laser
On Tue, 19 Sep 2000, Thomas Lockhart wrote: > Great! Are you translating the sgml source docs? no, not at this moment. Christian translated the HTML code. We are working to get this DocBook-Stuff running on our machines and we will switch to SGML-translation, when this is done. > If so, should we > include those in the CVS tree, or can you suggest another way of keeping > track of the latest versions? I suggest to include our SGML source, when we will have started our work on SGML. I'm afraid, it will last a couple of weeks before we do so. But I think it is a good idea to keep the docs in one place. > [...] > translations. I can generate context diffs from CVS, but if you have > other ideas please speak up. I will tell you, when we will have switched to SGML. diffs sounds great :-) > We've recently seen complete translations in Spanish and Chinese, and > this will be a fantastic addition to the set. Thank you! have fun, Karsten -- Linux Systemhaus Schulz Tel.: 0231 3944432 Karsten Schulz Fax.: 0231 3944435 Hauptfeld 18 schulz@linux-systemhaus.de 44369 Dortmund http://www.linux-systemhaus.de/
in file ref/insert.sgml line 171: ' <literal>date_prod</literal> ' should be ' <literal>len</literal> ' The omitted column is 'len', not 'date_prod'; Laser
> in file ref/insert.sgml line 171:
> ' <literal>date_prod</literal> '
> should be
> ' <literal>len</literal> '
> The omitted column is 'len', not 'date_prod';
Got it. Thanks.
- Thomas
Thomas Lockhart writes: > Great! Are you translating the sgml source docs? If so, should we > include those in the CVS tree, or can you suggest another way of keeping > track of the latest versions? Perhaps we (or someone) could set up a separate CVS module (other than "pgsql") for these things. We probably don't want to commit to having these things up to date at release date, and IMHO shipping inaccurate docs is often worse than shipping none. Then you could also give access to that CVS module to a wider/different group of people. That would allow things to move faster for those groups, since for documentation translations you wouldn't need to wait for code developers to approve patches that they can't read anyway. > Also, there was a request from the Spanish translators to coordinate > changes in the source docs, so they can make updates to the > translations. I can generate context diffs from CVS, but if you have > other ideas please speak up. True, diffs aren't hard to make. But ISTM that diffs are not the ideal format for humans to process. For example, in my experience, doc diffs often contain typo and minor word choice fixes, white space/formatting changes, or sections moved elsewhere, which would make things very hard for translators to process. Furthermore, since translators probably won't track documentation updates day-to-day, but rather by release, you will probably get huge diffs. A pragmatic approach might be that you simply keep track in your translated copy which revision (RCS) of the original it corresponds to. If you get down to updating that file you will probably have to reread the whole file anyway in order to get an overview of the subject matter. At that point you can still look at the diffs to get an idea about the extent of the changes. As for specific mechanisms, subscribing to the pgsql-committers list might be a first step. Filter everything that matches "Subject: [COMMITTERS] pgsql/doc/src/.*" or similar. Put these files into a list of "potentially outdated", then look at each of them individually as described above. Just some ideas... -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/