Apologies Clytie, I did not mean to sound harsh :)
I was on the IRC last night (brandelune) and seriously, I am very
impressed at all the work that is being done on the community side. I
currently am more involved at NetBeans, but we don't have to worry so
much since all the files are java l10n bundle.properties so it is
much easier to handle, plus the project is in itself smaller in scope.
I am slowly digesting the OOo-l10n related stuff and even though I am
only contributing a very small part of the French bundle I'd really
like to get more involved. Give me some time !
JC
ps: OmegaT has a PO filter given to us last year by a Debian-fr
activist... :)
ps2: I just registered to the wiki
On 19 janv. 07, at 16:44, Clytie Siddall wrote:
Hi J-C :)
Always happy to hear your ideas. :)
On 19/01/2007, at 5:15 PM, Jean-Christophe Helary wrote:
I have 2 questions: why is the translate toolkit necessary ? And
why aren't there any references to OLT ? The French community
receives .xlz files and would be unable to follow the howto since
it is exclusively based on po files (which is not a bad thing in
the absolute, but that is a different issue).
J-C, this was just a write-up of a draft howto Ain showed us during
the IRC meeting last night. It's by no means definitive, just
putting _something_ up there to cover at least one of the common
workflows. We do have a lot of people using PO and the Toolkit, so
this helps them.
It seems to me the document addresses team leader's needs and not
really translators who will certainly not have to deal with most
of what is described on the document.
True, but the aim of the doc was to cover the least-resourced
situation, which may happen more often than we think. It happened
to me: suddenly I was the de facto team leader and translator, with
no information.
Translators can focus on a subset, or we can do a separate howto
for translator-only workflow.
Again, this is only a start. (I did say that in the original
mail. :) ) Please feel free to amend it or add to it. But I wanted
to get something up there. Currently, there isn't anything for the
new translator and/or team-leader.
Also, I fear the described process is very likely to not attract
people who are translators and who could contribute quality work
because it is what they do for a living. It is way to geeky.
True. Time for someone to write a different howto. :)
I understand the fact that a lot of people involved in FOSS l10n
are familiar with most of the concepts and tools presented there.
But now that OOo has grown well beyond geek zone, it seems to me
most of the document's contents are not (or should not be)
relevant to what a potential translation contributor should really
be familiar with.
I suggest experienced team leaders edit the file to make a clear
distinction between the leader's job and the translator's job.
Please do. That was the idea in the first place, to get a draft up
for input. But it's important not to demand too much of a draft
doc. It took me most of the day, and it was never intended to be
comprehensive or to handle all possible audiences. So don't dump on
the volunteer, OK? :)
I'm hoping other people will expand it from what Ain started, and I
published. Grab your pencils and hit the wiki!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
