Hi Santiago,
Santiago Seminario wrote:
Hello Bert et all,
Please let me answer to your questions.
- Well, setting up a calendar with dates and time is pretty difficult I'm
afraid.....But I think we could put
some structure in this, as long as all the reviewers agree of course.
Santiago: the reason why I ask for a calendar or similar, is that because there
are always other translation projects going on, we need to have someone ready
for amending the OLH at a certain moment and for a certain amount of time. So
the more we know in advance the better the preparation.
I understand the reason why. But please note that the community solely
exists of volunteers who this in their spare time. I'm going to be the
last person who tells them what to do and when to it in their spare
time. So making a calendar will not work.
- Perhaps it's a good idea to collect those [issues that Alpha could not get
fixed] in an empty spreadsheet, so they can be found more easily.
Santiago: in principle no problem, although in my opinion using a new column to
signal those items that haven't been fixed could be also very clear.
Particularly for the community reviewers who would be able to see immediately
and in one go what has been amended and what hasn't. Also, many times one item
might be related to the one above or the one after, and if we isolate it, it
might lose some of its message. Anyway, this is not a big issue.
Good point. I agree.
- can you tell me what you think of the comments you've seen so far in the
review sheets? Do they make sense to you?
Well, unfortunately it does not make sense to me, but because I don't
understand a word.
I remember some problems when we checked the QA reports that were hanged for
Calc some time ago in a nother issue number, before Natalie came in. I hope
that most of the problems we saw there have gone away after being filtered by
Natalie. We will know when Nicole can have a look at the QA reports.
I take it that the reason you don't understand is because you can't
speak/read/write Dutch?
Could you please specify what the problems are/were that you are
referring to? If we know what they are, then perhaps we can do something
about it.
- I'm not sure I understand what you mean with this one. Are you talking
about full paragraphs or something?
More or less. Actually what I mean is that if there are many mismatching strings, or if
we detect a long chunk of a gsi file where source and target don't match, it is
preferable to select those strings and translate them anew using SunTrans (now OLT Open
Language Tools), or Trados. This makes things easier for us. But I think it won't be the
case now. If you want to know what I mean by mismatching, I think I detected a few
examples of "mismatching" that were reported by your reviewer:
º see for instance rows 103, 106, 114, 115 in
NL_Help_MacrosandProgramming_GeneralInfo-Digro-nat.ods. The difference in
length between the source text, the old translation and the proposed
translation is huge, and I presume that the old translation does not match the
source, right?
That's right indeed. Any idea on how these errors originate?
º or rows 104, 105 in the same QA report, where the source segment
contains tags, the old translation doesn't and the proposed translation puts
the tags in.
The big question is: Should those tags be there or not? My guess would
be not. But I'm not sure.
Regards,
Bert
--
__________________________________________________
Broxtor on irc.freenode.net (#nl.openoffice.org)
Meepraten op IRC?
Download een korte handleiding vanaf:
http://home.wanadoo.nl/rijmeer/handleiding_IRC.pdf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
