german translation is not complete or breaks in some points

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install and start the german version of rubyripper (rrip_gui)

What is the expected output? What do you see instead?
The german translation is not complete. For example
"Einstellungen" (engl. Settings) - "Sicheres Auslesen" (engl. secure read)
- "Only keep logfile if correction is needed" was not translated.

What version of rubyripper are you using? On what operating system? Are you
using the gtk2 or the commandline interface?
v0.5.2 on a gentoo machine, gtk interface

Please provide any additional information below.
I can look for further places where the german translation breaks. I can
help translating this, too.

Original issue reported on code.google.com by jbuec...@gmail.com on 6 Aug 2008 at 1:45

[GoogleCodeExporter]

Have a look at the wiki page how you can contribute with the translation. It's 
in
fact really easy, just takes some time.

Original comment by rubyripp...@gmail.com on 6 Aug 2008 at 2:44

• Changed state: Accepted

[GoogleCodeExporter]

I've updated the wiki page to show how you can update an existing translation.

Original comment by rubyripp...@gmail.com on 7 Aug 2008 at 7:47

[GoogleCodeExporter]

My local/po/de/rubyripper.po file. In two cases I'm not sure if the translation 
is
correct. I work with poedit. This tool tells me two failures, too. I attach the 
log
in a second. I don't believe this errors are relevant...

Original comment by jbuec...@gmail.com on 8 Aug 2008 at 12:31

Attachments:

• rubyripper.po

[GoogleCodeExporter]

Output of poedit.

Original comment by jbuec...@gmail.com on 8 Aug 2008 at 12:32

Attachments:

• log.txt

[GoogleCodeExporter]

Additions:
In the two cases I'm unsure what encoding thread means in german correctly...
For the english word "you" or "your" exist a special german problem :-)
Under friends, you say "du" and "dein" (more unformal) and if you speak with 
your
boss you say "Sie" and "ihre" (means ths is formal...). 
Because I don't know which translation you prefer I tried to take a third 
possiblitiy:
I don't use personal adress
Example: Drive doesn't exist on your system -> Drive doesn't exist on the system
and so on.

Original comment by jbuec...@gmail.com on 8 Aug 2008 at 12:43

[GoogleCodeExporter]

Under settings - others you give a "Example filename: /home/... -Sinner.ext
There is no entry in the .po to translate example filename...

Original comment by jbuec...@gmail.com on 8 Aug 2008 at 12:45

[GoogleCodeExporter]

Good work there! The errors in the log.txt indicate that you didn't have the 
same
amount of '\n' in the translation as in the original. '\n' means a newline. It's
pretty important they're there or you suddenly have a widescreen application ;)

About the formality, in dutch you have the same problem. I decided to use the 
formal
form. But your solution should work as well I guess.

Meanwhile, your changes are merged in r306.

I'll keep this one open to fix your request in comment 6.

Original comment by rubyripp...@gmail.com on 18 Aug 2008 at 6:42

[GoogleCodeExporter]

some corrections, error clean up, with translation of encoding thread and the 
error
of poedit was solved: A translation of one sentence after a /n was missing.

Are encoding threads the parallel encoding processes? Does this help on 
multicore
systems (like the -j option with make)?

Original comment by jbuec...@gmail.com on 18 Aug 2008 at 9:09

Attachments:

• rubyripper.po

[GoogleCodeExporter]

Hi everyone ;) Long time since my last contribution but here it is, new version 
of
the french translation ;) Enjoy

Original comment by rodolphe.ridel on 20 Dec 2008 at 8:12

Attachments:

• rubyripper.po

[GoogleCodeExporter]

Not exactly the right issue for this, but I've merged your french po file 
anyway :)

Original comment by rubyripp...@gmail.com on 24 Dec 2008 at 6:20

[GoogleCodeExporter]

The Example thing is now possible to translate as well. That means I'm closing 
this
issue :D

For any other findings about incomplete translation, please fire up a new issue.

Original comment by rubyripp...@gmail.com on 13 Jan 2009 at 11:37

• Changed state: Fixed