Hallo zusammen,

wie bereits erwähnt habe ich darum gebeten, dass die zu übersetzenden 
Zeichenketten besser erklärt werden, da ich mir ohne Blick in den Quelltext an 
vielen Stellen nicht sicher sein kann, ob die Übersetzungen so passen. Die 
Antworten des Hauptentwicklers auf meine Bitten (ich habe ihm auch meine 
Mithilfe angeboten) empfand ich bisher allerdings als ignorant bis 
unverschämt:

https://bugs.launchpad.net/bugs/521823

Inzwischen hat sich auch David Planella eingeschaltet und auch der wurde erst 
einmal angepflaumt, obwohl er unser Anliegen wirklich ausführlich und 
freundlich erklärt hat. Sollte Scott Remnant auch nach den letzten Kommentaren 
von David und mir (ich musste mich sehr bemühen, freundlich zu bleiben) nicht 
einsehen, dass Übersetzerkommentare sinnvoll wären und es nicht unser Job ist, 
den gesamten Quelltext zu lesen, würde ich vorschlagen, dass wir die 
Übersetzung komplett löschen und upstart erst einmal unübersetzt lassen.

In der Oberfläche sind die Zeichenketten meines Wissens alle nicht zu sehen, so 
dass diese Entscheidung die deutschen Nutzer kaum beeinträchtigen sollte. Aber 
so ein ignorantes Verhalten braucht man sich meiner Meinung nach wirklich 
nicht gefallen lassen …

Grüße,
Moritz
--- Begin Message ---
Hi everyone,

I just filed a bug report against upstart, asking for comments which would help 
me translate difficult strings. I was told that it'd be my responsibility to 
take a look at the source code if the context was unclear.

I always thought it'd be the developer's responsibility to ensure the 
application is translatable. Apart from the fact that most translators 
probably don't know much C, looking everything up in the source code is not 
part of our normal workflow.

Is there any guideline I can refer to or am I wrong?

Regards,
Moritz

----------  Weitergeleitete Nachricht  ----------

Betreff: Re: [Bug 521823] Re: Comments would make translations easier
Datum: Montag, 15. Februar 2010, 17:13:22
Von: Scott James Remnant <[email protected]>
An: [email protected]

On Mon, 2010-02-15 at 15:50 +0000, Moritz Baumann wrote:

> To name some examples:
> 
> "stop", "start", "respawn", "pre-start", etc.: Should they even be 
translatable? Context?
> 
So go look at the context then.

The source is full of documentation about what these mean.

> "Failed to spawn %s %s process: %s": What is missing here?
> 
Look at the code?

        /* Return non-temporary error condition */
        nih_warn (_("Failed to spawn %s %s process: %s"),
                  job_name (job), process_name (process),
                  err->message);

This makes it very clear that those are a job name, a process name and
the error message.

> Of course it's the translators job to look up the terminology and what
> the program does, but then the rest should be self-explanatory. So
> whenever the context is not clear if you only see the string, please
> give us a hint.
> 
I'm not interested in doing that; you're not expected to be able to
translate by only seeing the strings - you're expected to read the
context as well - that's why you have the filename and line number.

 status invalid

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?


** Changed in: upstart
       Status: Incomplete => Invalid

-- 
Comments would make translations easier
https://bugs.launchpad.net/bugs/521823
You received this bug notification because you are a direct subscriber
of the bug.

Status in Upstart: Invalid

Bug description:
I'm currently trying to translate upstart into German. Since it is impossible 
to find most strings "using" upstart (everything which hasn't got anything to 
do with command line utilities like shutdown), some strings cannot be properly 
translated without taking a look at the source code, esp. those containing 
placeholders. Comments would definitely help a lot here!

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/upstart/+bug/521823/+subscribe

-------------------------------------------------------------

-- 
ubuntu-translators mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

--- End Message ---
--- Begin Message ---
Hi Moritz,

Thanks for letting us know about this bug.

El dl 15 de 02 de 2010 a les 17:36 +0100, en/na Moritz Baumann va
escriure:
> Hi everyone,
> 
> I just filed a bug report against upstart, asking for comments which would 
> help 
> me translate difficult strings. I was told that it'd be my responsibility to 
> take a look at the source code if the context was unclear.
> 
> I always thought it'd be the developer's responsibility to ensure the 
> application is translatable. Apart from the fact that most translators 
> probably don't know much C, looking everything up in the source code is not 
> part of our normal workflow.
> 
> Is there any guideline I can refer to or am I wrong?

You've done the right thing and you are absolutely right in your
assumptions, so don't worry.

I've now commented on the bug. Let's try to move forward and get it from
there.

Thanks!

Regards,
David.

-- 
David Planella
Ubuntu Translations Coordinator
david(dot)planella(at)ubuntu(dot)com
www.ubuntu.com



Attachment: signature.asc
Description: Això és una part d'un missatge signada digitalment

-- 
ubuntu-translators mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

--- End Message ---
_______________________________________________
Translators-de mailing list
[email protected]
https://eshu.ubuntu-eu.org/cgi-bin/mailman/listinfo/translators-de

Antwort per Email an