German translation fixes

Here is an updated de.po based on the latest version in CVS with some spelling
fixes.

On Wed, 7 May 2008, Peter Eisentraut wrote:

> Here is an updated de.po based on the latest version in CVS with some
> spelling fixes.
>

I've actually taken the 8.3 translation supplied by Andre Bialojahn[1] to
use for HEAD because it has more messages translated.

His:
173 translated messages, 4 fuzzy translations.

Yours:
164 translated messages, 5 fuzzy translations, 8 untranslated messages.

Perhaps you didn't merge the latest messages prior to editing de.po. You
should run update-translations.sh prior to editing a po file.

While discussing translations, perhaps now would be a good time to discuss
joining the pgtranslation project. I personally have no way of knowing
whether a translation is "good", all I can do is check the msgfmt stats.
The JDBC project's translations are suffering from a lack of exposure as
well. What would we have to do to get our po files managed by
pgtranslation?

Kris Jurka

Dear all,

Peter Eisentraut schrieb:
> Here is an updated de.po based on the latest version in CVS with some spelling
> fixes.
> [...]

And I've finally managed to incorporate those changes in the latest
revision available through the CVS repository.

I attached the manually updated file to this mail for you to integrate
it into the repository.

Thanks a lot to Peter Eisentraut for supplying the corrections and for
nudging me today to finally submit the updates to the list.

Kind regards,
André

While having a small look over the file, this type hit me:

msgstr "Beim Erstellen eines Stack-Traces für {0} trat eine Exceptin
auf: {1}"

Exception is missing the 'o'.

With best regards,
Daniel Migowski

Andre Bialojahn schrieb:
> Dear all,
>
> Peter Eisentraut schrieb:
>
>> Here is an updated de.po based on the latest version in CVS with some spelling
>> fixes.
>> [...]
>>
>
> And I've finally managed to incorporate those changes in the latest
> revision available through the CVS repository.
>
> I attached the manually updated file to this mail for you to integrate
> it into the repository.
>
> Thanks a lot to Peter Eisentraut for supplying the corrections and for
> nudging me today to finally submit the updates to the list.
>
> Kind regards,
> André

Oh, another one:

- msgstr "Die EInfügezeile kann nicht aufgefrischt werden."
Second I must be a small i.

Daniel Migowski schrieb:
> While having a small look over the file, this type hit me:
>
> msgstr "Beim Erstellen eines Stack-Traces für {0} trat eine Exceptin
> auf: {1}"
>
> Exception is missing the 'o'.
>
> With best regards,
> Daniel Migowski
>
> Andre Bialojahn schrieb:
>> Dear all,
>>
>> Peter Eisentraut schrieb:
>>
>>> Here is an updated de.po based on the latest version in CVS with
>>> some spelling fixes.
>>> [...]
>>>
>>
>> And I've finally managed to incorporate those changes in the latest
>> revision available through the CVS repository.
>>
>> I attached the manually updated file to this mail for you to integrate
>> it into the repository.
>>
>> Thanks a lot to Peter Eisentraut for supplying the corrections and for
>> nudging me today to finally submit the updates to the list.
>>
>> Kind regards,
>> André
>
>

--

|¯¯|¯¯| *IKOffice GmbH Daniel Migowski*
| | |/| Mail: dmigowski(at)ikoffice(dot)de <mailto:dmigowski(at)ikoffice(dot)de>
| | // | Nordstr. 10 Tel.: 0441 21 98 89 52
| | \\ | 26135 Oldenburg Fax.: 0441 21 98 89 55
|__|__|\| http://www.ikoffice.de Mob.: 0176 22 31 20 76

Daniel Migowski schrieb:
> Oh, another one:
>
> - msgstr "Die EInfügezeile kann nicht aufgefrischt werden."
> Second I must be a small i.
>
> Daniel Migowski schrieb:
>> While having a small look over the file, this type hit me:
>>
>> msgstr "Beim Erstellen eines Stack-Traces für {0} trat eine Exceptin
>> auf: {1}"
>>
>> Exception is missing the 'o'.
>>
>> With best regards,
>> Daniel Migowski
>>> [...]

There are two more I just found. Will supply a fixed version in a few
moments.

Thanks a lot, Daniel!

André

Hello Daniel,

Daniel Migowski schrieb:
> While having a small look over the file, this type hit me:
>
> msgstr "Beim Erstellen eines Stack-Traces für {0} trat eine Exceptin
> auf: {1}"
>
> Exception is missing the 'o'.

*ahrgh*

> [...]

I've pinned that one down, too (as well as the others still hidden in
the file) and attached a corrected version to this message.

André

(Reading the file through in whole reminds me that I originally wanted
to nag Kris about some PGSQL-terms that I do not know the meaning of to
be able to supply a 100% translation... There are still some
uncertainties. So much to do, so little time.)

> I've pinned that one down, too (as well as the others still hidden in
> the file) and attached a corrected version to this message.
>

Updated translation installed.

Kris Jurka

In May 2008, Kris Jurka wrote:
> While discussing translations, perhaps now would be a good time to
> discuss joining the pgtranslation project. I personally have no way of
> knowing whether a translation is "good", all I can do is check the
> msgfmt stats. The JDBC project's translations are suffering from a lack
> of exposure as well. What would we have to do to get our po files
> managed by pgtranslation?

There are several components to that:

1. You need a script that copies the po files from the pgtranslation
repository to the pgjdbc repository before a release. That is the easy
part.

2. You need scripts that merge existing po files with the current code,
for publishing on the web. Those scripts would also have to interact
reasonably with the existing scripts.

3. The interaction with branches would need to be worked out. We
currently also publish and manager translations for PostgreSQL back
branches, but that doesn't align well with the JDBC driver. I'm not
sure how to sort that out.