Hallo zusammen,
Rafaella hat mich nochmal direkt angeschrieben, wie wir helfen können,
den "Druck" für eine korrekte übersetzung etwas zu erhöhen. Sie hat mir
auch die Dateien für den Review der Übersetzung geschickt. Diese können
dazu genutzt werden, die Qualität der Übersetzung zu bewerten. Wenn sich
dabei herausstellt, dass die Hilfe nach objektiven Kriterien schlecht
übersetzt ist, haben wir sehr gute Chancen, dass die korrekturen höher
priorisiert werden.
Mein Problem ist aber, dass ich mich in absehbarer Zeit nicht darum
kümmern kann, das zu koordinieren :-( Gleichzeitig haben wir schon Leute
im Team, die sich mit den "Wehwehchen" der Hilfe-Übersetzung wesentlich
besser auskennen als ich.
Wäre jemand bereit, diese Aufgabe zu übernehmen?
André
PS.: die Dateien gibt's im moment erstmal nur bei mir auf Anfrage. Ich
werde aber nochmal nachfragen, wie weit ich die veröffentlichen darf. In
Koper wurde zumindest angekündigt, dass sie unter eine freie Lizenz
gestellt werden sollen.
-------- Original-Nachricht --------
Betreff: Re: Files for L10N Help Testing
Datum: Thu, 20 Oct 2005 15:53:28 +0200
Von: Rafaella Braconi <[EMAIL PROTECTED]>
Antwort an: [EMAIL PROTECTED]
An: Andre Schnabel <[EMAIL PROTECTED]>
Referenzen: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Hallo Andre,
just for your information, my reply to your mail (to the list) can be
read when you search in the archive. I personally haven't received the
mail in my inbox...
Great to hear that the instructions work.
Since you seem not to be happy with the German quality of the help, we
are more than willing to implement - as far as possible - your feedback
in the files. Yes, file and paragraph IDs need to be reported otherwise
we don't know where exactly to fix what.
My idea would be:
- to have you sumbit one collective issue for the Help
- to perform review (since you don't have so much time. I would suggest
to perform a 10% review accross all help). Usually a 10% spot review
gives you a quite good idea of the modules which are good quality and
the ones that need to be re-edited. Also, such a *spot* check will
definitively give you an idea of major issues that need to be fixed
troughout the help.
- to use the QA form during review which can be easily attached to the
issue. I am attaching the QA form as well as the instructions fot it but
if you have attended Monica's presentation at the OO.o conference you
may also have an idea of what I am talking about.
From my point of view, for this review you will need to divide the Help
in modules among 3-4 reviewers....
One more thing. You can assign the bug to iano directly and add me to
the interest list.
Let me know what you think.
Ciao,
Rafaella
Andre Schnabel wrote On 10/19/05 19:26,:
Hi Rafaella,
Rafaella Braconi schrieb:
Hi Andre,
sorry if I mail you directly, but since a couple of days it seems
that my replies to the OO.o lists take hours before you are able to
read them and I am having issues with IssueZilla .....
you are not alone with this at the moment :-( So .. private mail is ok
;-)
here below some instructions which can *help* to review the *Help*.
Of course these instructions work with OO.o builds as well.
Just tried it an it works.
I will post them tomorrow in the list and I will aslo try to file an
issue with the attachments.
Let me know if this is something that would work for you to fix the
Help as much as we can or if you have other suggestions....
Well .. the problem for me is, that I never really worked on fixing
help issues. So I'm not shure, what woulld help to identify, where (in
what file) the problem exists. From what I see, at least help file and
maybe paragraph ID's should be reported, when filing issues?
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
