Translation of Trac to German/Deutsch [de_DE]

[asmodai@…]

This ticket should be used to coordinate the translation to German.

[asmodai@…]

See also TracTermsDe.

[jruigrok]

There's preliminary work done in source:sandbox/i18n/trac/locale/de_DE/LC_MESSAGES/messages.po

[Axel Gembe]

German localization update

[Axel Gembe]

This is an updated localization file against the latest version from sandbox.

[cboos]

Please follow trunk now that the branch has been merged. Asmodai, you should perhaps remove source:sandbox/i18n, in order to reduce the possible confusion.

[jruigrok]

It's removed now, still a bit behind on everything. Thanks for the heads up. Let me integrate Axel's stuff now.

[anonymous]

Ooops, didn't know it was merged already. Someone should also edit TracDev/SandBox and put it under completed branches.

[jruigrok]

Committed in r7005.

TracDev/SandBox has been adjusted.

[jruigrok]

By the way Axel, yes, your comments in some places in the file are correct. It's still something we are working on for fixing. See for more background #G129.

[Axel Gembe]

Some more german translations

[Axel Gembe]

I've added another patch with more translations and a few that were left out of the previous commit (intentional?) About the comments, I've just added them to know where changes to the source code are needed. There is one really bad hack in those translations I posted.

[Axel Gembe]

Hmm, I just tried trunk with the translations, and I seem to get this:

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/Trac-0.12dev-py2.5.egg/trac/web/api.py", line 346, in send_error
    translation.deactivate()
  File "/usr/lib/python2.5/site-packages/Trac-0.12dev-py2.5.egg/trac/util/translation.py", line 79, in deactivate
    del _current.translations
AttributeError: translations

Is this a known problem ?

[Axel Gembe]

Fix a typo in the last patch

[Axel Gembe]

Fix another typo in the last patch

[Axel Gembe]

Fix some typos in the last patch

[cboos]

Replying to Axel Gembe:

... del _current.translations ... AttributeError: translations }}} Is this a known problem ?

More or less: I saw it and tried to trigger it, but when failing to do so, I wrongly concluded this couldn't happen ;-) Could you look up the original error in your Trac log? (what you pasted above was a secondary error which happened after rendering of the original error)

[Axel Gembe]

Sure, I just have to figure out trac logging. Expect a log in a few minutes.

[Axel Gembe]

Sorry, I don't know why, but its working again now. I've replaced the default config with one that does logging and reset the permissions on the trac folder, now it works.

[cboos]

Replying to cboos:

Replying to Axel Gembe:

... del _current.translations ... AttributeError: translations }}} Is this a known problem ?

More or less: I saw it and tried to trigger it, but when failing to do so, I wrongly concluded this couldn't happen ;-)

Fixed in r7051.

[benjamin-ruehl@…]

Hello,

nice work. Is ist possible to include/install this languagepackage in trac 0.9 und how can i do this?

Thanks.

[jruigrok]

No, trunk only.

[jruigrok]

Applied in r7139. Vielen Dank.

[Axel Gembe]

Fix 3 mistranslated strings

[Axel Gembe]

I've added another patch which fixes some errors I made while translating.

[Axel Gembe]

Update translation again (delete last one plz)

[jruigrok]

Hi Axel,

committed in r7282.

I left suchen with a small letter since it is still a verb, right? So no need to make it Suchen for all I know and could verify with other native German speakers.

Vielen Dank.

[anonymous]

Ein paar andere Vorschläge:

• Timeline (Zeitleiste) -> Zeitachse
• Roadmap (Fahrplan) -> Projektplan
• enhancement (Verbesserungsvorschlag) -> Verbesserung // Ist doch sonst zu lange. Aber scheint sowieso nicht zu gehen.

[Simon <saimen54@…>]

Replying to anonymous:

Ein paar andere Vorschläge:

Timeline (Zeitleiste) -> Zeitachse

Roadmap (Fahrplan) -> Projektplan

enhancement (Verbesserungsvorschlag) -> Verbesserung // Ist doch sonst zu lange.

I agree. IMO "Fahrplan" is not really the correct term for this context.

Some different suggestions:

• wontfix (abgelehnt) -> keineLösung // The current proposal has a completely different meaning. At least I don't use "wontfix" for this meaning.
• reopened (wiedereröffnet) -> wiedergeöffnet // The current proposal applies more e.g. to a shop reopening for me, but that might be a dialect issue :)
• attached to ... by ... (angehangen an ... von ...) -> angehängt an ... von ...
• reopened by ... (wiedereröffnet von ...) -> wieder geöffnet von ... // see above
• milestone completed (Meilenstein erreicht) -> Meilenstein vollständig or Meilenstein abgeschlossen

[kontakt at meitzner dot net]

* Roadmap -> I'd favour "Projektplan" in most cases

• Timeline -> What about "Verlauf" here?
• enhancement -> It's long, but I've come to actually use "Verbesserungsvorschlag" in the end, since it fits best semantically. "Erweiterung" should be a candidate, too.
• wontfix -> "bleibtso" ;-)
• milestone completed -> "Meilenstein abgeschlossen" fits best I'd say.

[Simon <saimen54@…>]

Replying to kontakt at meitzner dot net:

Timeline -> What about "Verlauf" here?

That's a good idea

enhancement -> It's long, but I've come to actually use "Verbesserungsvorschlag" in the end, since it fits best semantically. "Erweiterung" should be a candidate, too.

From my point of view "Verbesserung" or "Erweiterung" would be okay. Following your argument on "Verbesserungsvorschlag" then it should be called "Erweiterungsvorschlag", too ;)

wontfix -> "bleibtso" ;-)

Colloquial, but closest translation to wontfix :)

milestone completed -> "Meilenstein abgeschlossen" fits best I'd say.

yep

[jruigrok]

I'll gladly apply any patches once you reach sort of a consensus. :)

[Simon <saimen54@…>]

Personally I agree on these proposals. Any other comments?

[Heiko Graeber <ip.3777@…>]

Yes! I've got something. Please stand by.

[Simon <saimen54@…>]

Replying to Heiko Graeber <ip.3777@…>:

Yes! I've got something. Please stand by.

Standing by... :)

[Simon <saimen54@…>]

Should the changes proposed in comment:26, comment:27, comment:28 and comment:29 be applied as no further remarks have been made here for quite some time?

[cboos]

Well, those suggestions were only discussed, no actual patch was proposed so there's nothing to apply...