You are viewing a plain text version of this content. The canonical link for it is here.
Posted to l10n@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2013/02/22 01:57:24 UTC

Proposal: communications/workflow for new languages

What happens today:

1) Every few days someone posts to the list that they want to help
translate AOO.

2) Sometimes it is a new language, in other cases it is one where some
volunteers have previously expressed interest.

3) If it is a new language, Juergen creates a PO file, uploads it to
people.apache.org and notifies the volunteer.  If it is a language
where there are other volunteers, then Andrea tries to connect the
volunteers.

4) When a translation is done the new files are attached to a BZ issue.

An interesting idea is to use Bugzilla from the very start.  Then BZ
can help wit the routine communications, including keeping the
volunteers coordinated.

For example:

1) Point new volunteers to BZ from the start.  If you want to work on
a new language then create a new BZ issue.  We can then assign the
issue to Juergen.

2) When the PO files are available Juergen marks the BZ issue as
"Accepted".  The volunteer(s) is automatically notified by Bugzilla,
so no extra email is required.

3) When a new volunteer wants to join, we can point them to the BZ
issue.  The files are there, as well as the names of the other
volunteers.  Adding a comment to the BZ issue causes it to be sent to
all volunteers working on that language.

4) When translation is done, the issue is marked and Juergen can
integrate the new translation.

Would this help?

-Rob

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 23 February 2013 18:58, Michael Bauer <fi...@akerbeltz.org> wrote:

> A common translator's tuppence on the issue. Most translators are not
> programmers and the more technical and convoluted an approach you take, the
> more you narrow your potential translators down to that much smaller pool
> of people who can do both code and translation.
>
> The idea is to keep the "real" translation part as non-technical as
possible, but in order to do that some technical discussions are needed. I
have some ideas how we can make the strings to translate even simpler (e.g.
remove all the html tags, which is just noise to translation).


> They also, for the most part, don't give a fig about what license
> something is under. I realise that for the people running the project in
> question, issues of license exist but the translators on the whole just
> want to see X in their language released.
>
> Thirdly, duplication is hugely frustrating for translators, especially for
> people working in smaller languages. Having just "rescued" some Firefox
> translations from Launchpad, I can vouch for that.
>
> So what would be actually nice is if AOO and LO could agree on a neutral
> Pootle server which handles both AOO and LO strings and from which each
> project can extract whatever translations they require. Minimum duplication
> and standard signup and translation process (none of this Bugzilla stuff or
> the need for someone to extract po files, email them, translation offline
> and the the whole thing backwards to commit, if ever there was a #facepalm
> process, that's it...), if needed, slap a notice email in the process about
> how these will be used.
>
+1 That is high on my wishlist, and not that difficult to implement
technically, except it seems difficult to get a cooperation going and LO
just implemented a new .po file generation system, that are likely to end
up with different keys than AOO.

email is nice for larger translations, but a bit of overhead for the last
part where it often just a couple of messages that needs to be
corrected...that is the point where the pootle server is handy.


rgds
Jan I

>
> Michael
>

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 24 February 2013 17:25, Rob Weir <ro...@apache.org> wrote:

> On Sun, Feb 24, 2013 at 9:59 AM, janI <ja...@apache.org> wrote:
> > /
> > On Feb 24, 2013 3:42 PM, "Rob Weir" <ro...@apache.org> wrote:
> >>
> >> On Sun, Feb 24, 2013 at 4:04 AM, janI <ja...@apache.org> wrote:
> >> > On 23 February 2013 23:56, Rob Weir <ro...@apache.org> wrote:
> >> >
> >> >> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org>
> >> >> wrote:
> >> >> > A common translator's tuppence on the issue. Most translators are
> not
> >> >> > programmers and the more technical and convoluted an approach you
> > take,
> >> >> the
> >> >> > more you narrow your potential translators down to that much
> smaller
> >> >> pool of
> >> >> > people who can do both code and translation.
> >> >> >
> >> >> > They also, for the most part, don't give a fig about what license
> >> >> something
> >> >> > is under. I realise that for the people running the project in
> > question,
> >> >> > issues of license exist but the translators on the whole just want
> to
> >> >> see X
> >> >> > in their language released.
> >> >> >
> >> >> > Thirdly, duplication is hugely frustrating for translators,
> > especially
> >> >> for
> >> >> > people working in smaller languages. Having just "rescued" some
> > Firefox
> >> >> > translations from Launchpad, I can vouch for that.
> >> >> >
> >> >> > So what would be actually nice is if AOO and LO could agree on a
> > neutral
> >> >> > Pootle server which handles both AOO and LO strings and from which
> > each
> >> >> > project can extract whatever translations they require. Minimum
> >> >> duplication
> >> >> > and standard signup and translation process (none of this Bugzilla
> > stuff
> >> >> or
> >> >> > the need for someone to extract po files, email them, translation
> > offline
> >> >> > and the the whole thing backwards to commit, if ever there was a
> >> >> #facepalm
> >> >> > process, that's it...), if needed, slap a notice email in the
> process
> >> >> about
> >> >> > how these will be used.
> >> >> >
> >> >>
> >> >> These are all good points (and Claudio's points are good as well) but
> >> >> they are not related to my proposal.  I was just suggesting a way in
> >> >> which we can use Bugzilla improve communications and track progress
> on
> >> >> the offline translation of the PO files.
> >> >>
> >> >> For example, suppose right now a new volunteer posts a note saying
> >> >> they want to help with the Greek translation.  Where are the PO
> files?
> >> >>  What other volunteers have started on this effort?  Who else has
> >> >> expressed interest?  Today we need to search through list archives to
> >> >> find these facts.  But if we had one Bugzilla issue per locale, then
> >> >> we could track status there, including attaching files.  Volunteers
> >> >> can also add themselves to the cc-list for the Bug to stay "in the
> >> >> loop".  And they can even create sub-issues if they want to divide up
> >> >> the work formally.
> >> >>
> >> > I have nothing against using bugzilla, that would be fine for me. We
> are
> >> > soon at the point where po files are available in svn (they are on my
> > local
> >> > computer).
> >> >
> >> > An alternative to bugzilla, would be mwiki (not cwiki :-). We could
> move
> >> > the translation page you have made, and attach po files...then we
> would
> >> > only have the information in one place, and I am sure more people are
> > used
> >> > mwiki than bugzilla.
> >> >
> >>
> >> Is there a way wtih MWiki to get automatic notifications when there is
> >> a status change on your language?  I think that is the strength of the
> >> workflow tracking in BZ.  Someone can add themselves to the cc for the
> >> Greek tracking issue and get all messages related to that translation
> >> effort, without signing up for the L10n mailing list and without
> >> needing to remember to check a wiki.
> >
> > It should work, if not it is a setup change that I will make.When you
> watch
> > a page (default if you edit it) you get mail.
> >
>
> So one page per language?  25 languages == 25 wiki pages?
>
>
> > please also remember many translators are not technicians and do not
> have a
> > bugzilla account, where I think a mwiki account is more normal.
> >
>
> Most translators don't have a wiki account either, until they create
> one.  And note we have a backlog of user-submitted defect reports for
> translations as well.  So translators should get familiar with
> Bugzilla in order to respond to these.  We need communications to be
> good in that direction as well.
>

I think it is the wrong direction, asking translators to use more technical
pages, wiki is a lot more to what anybody using internet is used to. But I
have no way of making a proof, so lets just agree on disagreeing.


>
> > Would you consider moving your language page to mwiki, in order to be
> > available to a broader audience?
> >
>
> I don't own any page on any wiki.  But I am interested in seeing what
> makes the most sense.  IMHO a wiki is create for collaborating on page
> contents and instantly publishing it.  But we have other tools, like
> BZ, that may be more appropriate for coordinating complex workflows.
>

Sorry for my wording, it is correct you are the owner but my words ""your
page" referred to you as the "author and the one who advertised it" . And I
solely asked, because I would not consider it polite or correct if somebody
just moved the page without prior consensus with the author.

For sure we have other tools, but where do we have the biggest exposure
(where it is possible to edit), without having the latest figures I am sure
the mwiki has more hits than our part of cwiki and bz together. Please
remember the note earlier in the thread, some translators would like to see
their name online.

But this is just my 2cent, and I believe this is an issue where we need
opinions from translator, so I will refrain from further comments.

jan I

>
> -Rob
>
> > rgds
> > jan i
> >>
> >> -Rob
> >>
> >>
> >> > rgds
> >> > Jan I
> >> >
> >> >>
> >> >> Regards,
> >> >>
> >> >> -Rob
> >> >>
> >> >>
> >> >> > Michael
> >> >>
>

Re: Proposal: communications/workflow for new languages

Posted by Rob Weir <ro...@apache.org>.
On Sun, Feb 24, 2013 at 9:59 AM, janI <ja...@apache.org> wrote:
> /
> On Feb 24, 2013 3:42 PM, "Rob Weir" <ro...@apache.org> wrote:
>>
>> On Sun, Feb 24, 2013 at 4:04 AM, janI <ja...@apache.org> wrote:
>> > On 23 February 2013 23:56, Rob Weir <ro...@apache.org> wrote:
>> >
>> >> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org>
>> >> wrote:
>> >> > A common translator's tuppence on the issue. Most translators are not
>> >> > programmers and the more technical and convoluted an approach you
> take,
>> >> the
>> >> > more you narrow your potential translators down to that much smaller
>> >> pool of
>> >> > people who can do both code and translation.
>> >> >
>> >> > They also, for the most part, don't give a fig about what license
>> >> something
>> >> > is under. I realise that for the people running the project in
> question,
>> >> > issues of license exist but the translators on the whole just want to
>> >> see X
>> >> > in their language released.
>> >> >
>> >> > Thirdly, duplication is hugely frustrating for translators,
> especially
>> >> for
>> >> > people working in smaller languages. Having just "rescued" some
> Firefox
>> >> > translations from Launchpad, I can vouch for that.
>> >> >
>> >> > So what would be actually nice is if AOO and LO could agree on a
> neutral
>> >> > Pootle server which handles both AOO and LO strings and from which
> each
>> >> > project can extract whatever translations they require. Minimum
>> >> duplication
>> >> > and standard signup and translation process (none of this Bugzilla
> stuff
>> >> or
>> >> > the need for someone to extract po files, email them, translation
> offline
>> >> > and the the whole thing backwards to commit, if ever there was a
>> >> #facepalm
>> >> > process, that's it...), if needed, slap a notice email in the process
>> >> about
>> >> > how these will be used.
>> >> >
>> >>
>> >> These are all good points (and Claudio's points are good as well) but
>> >> they are not related to my proposal.  I was just suggesting a way in
>> >> which we can use Bugzilla improve communications and track progress on
>> >> the offline translation of the PO files.
>> >>
>> >> For example, suppose right now a new volunteer posts a note saying
>> >> they want to help with the Greek translation.  Where are the PO files?
>> >>  What other volunteers have started on this effort?  Who else has
>> >> expressed interest?  Today we need to search through list archives to
>> >> find these facts.  But if we had one Bugzilla issue per locale, then
>> >> we could track status there, including attaching files.  Volunteers
>> >> can also add themselves to the cc-list for the Bug to stay "in the
>> >> loop".  And they can even create sub-issues if they want to divide up
>> >> the work formally.
>> >>
>> > I have nothing against using bugzilla, that would be fine for me. We are
>> > soon at the point where po files are available in svn (they are on my
> local
>> > computer).
>> >
>> > An alternative to bugzilla, would be mwiki (not cwiki :-). We could move
>> > the translation page you have made, and attach po files...then we would
>> > only have the information in one place, and I am sure more people are
> used
>> > mwiki than bugzilla.
>> >
>>
>> Is there a way wtih MWiki to get automatic notifications when there is
>> a status change on your language?  I think that is the strength of the
>> workflow tracking in BZ.  Someone can add themselves to the cc for the
>> Greek tracking issue and get all messages related to that translation
>> effort, without signing up for the L10n mailing list and without
>> needing to remember to check a wiki.
>
> It should work, if not it is a setup change that I will make.When you watch
> a page (default if you edit it) you get mail.
>

So one page per language?  25 languages == 25 wiki pages?


> please also remember many translators are not technicians and do not have a
> bugzilla account, where I think a mwiki account is more normal.
>

Most translators don't have a wiki account either, until they create
one.  And note we have a backlog of user-submitted defect reports for
translations as well.  So translators should get familiar with
Bugzilla in order to respond to these.  We need communications to be
good in that direction as well.

> Would you consider moving your language page to mwiki, in order to be
> available to a broader audience?
>

I don't own any page on any wiki.  But I am interested in seeing what
makes the most sense.  IMHO a wiki is create for collaborating on page
contents and instantly publishing it.  But we have other tools, like
BZ, that may be more appropriate for coordinating complex workflows.

-Rob

> rgds
> jan i
>>
>> -Rob
>>
>>
>> > rgds
>> > Jan I
>> >
>> >>
>> >> Regards,
>> >>
>> >> -Rob
>> >>
>> >>
>> >> > Michael
>> >>

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
/
On Feb 24, 2013 3:42 PM, "Rob Weir" <ro...@apache.org> wrote:
>
> On Sun, Feb 24, 2013 at 4:04 AM, janI <ja...@apache.org> wrote:
> > On 23 February 2013 23:56, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org>
> >> wrote:
> >> > A common translator's tuppence on the issue. Most translators are not
> >> > programmers and the more technical and convoluted an approach you
take,
> >> the
> >> > more you narrow your potential translators down to that much smaller
> >> pool of
> >> > people who can do both code and translation.
> >> >
> >> > They also, for the most part, don't give a fig about what license
> >> something
> >> > is under. I realise that for the people running the project in
question,
> >> > issues of license exist but the translators on the whole just want to
> >> see X
> >> > in their language released.
> >> >
> >> > Thirdly, duplication is hugely frustrating for translators,
especially
> >> for
> >> > people working in smaller languages. Having just "rescued" some
Firefox
> >> > translations from Launchpad, I can vouch for that.
> >> >
> >> > So what would be actually nice is if AOO and LO could agree on a
neutral
> >> > Pootle server which handles both AOO and LO strings and from which
each
> >> > project can extract whatever translations they require. Minimum
> >> duplication
> >> > and standard signup and translation process (none of this Bugzilla
stuff
> >> or
> >> > the need for someone to extract po files, email them, translation
offline
> >> > and the the whole thing backwards to commit, if ever there was a
> >> #facepalm
> >> > process, that's it...), if needed, slap a notice email in the process
> >> about
> >> > how these will be used.
> >> >
> >>
> >> These are all good points (and Claudio's points are good as well) but
> >> they are not related to my proposal.  I was just suggesting a way in
> >> which we can use Bugzilla improve communications and track progress on
> >> the offline translation of the PO files.
> >>
> >> For example, suppose right now a new volunteer posts a note saying
> >> they want to help with the Greek translation.  Where are the PO files?
> >>  What other volunteers have started on this effort?  Who else has
> >> expressed interest?  Today we need to search through list archives to
> >> find these facts.  But if we had one Bugzilla issue per locale, then
> >> we could track status there, including attaching files.  Volunteers
> >> can also add themselves to the cc-list for the Bug to stay "in the
> >> loop".  And they can even create sub-issues if they want to divide up
> >> the work formally.
> >>
> > I have nothing against using bugzilla, that would be fine for me. We are
> > soon at the point where po files are available in svn (they are on my
local
> > computer).
> >
> > An alternative to bugzilla, would be mwiki (not cwiki :-). We could move
> > the translation page you have made, and attach po files...then we would
> > only have the information in one place, and I am sure more people are
used
> > mwiki than bugzilla.
> >
>
> Is there a way wtih MWiki to get automatic notifications when there is
> a status change on your language?  I think that is the strength of the
> workflow tracking in BZ.  Someone can add themselves to the cc for the
> Greek tracking issue and get all messages related to that translation
> effort, without signing up for the L10n mailing list and without
> needing to remember to check a wiki.

It should work, if not it is a setup change that I will make.When you watch
a page (default if you edit it) you get mail.

please also remember many translators are not technicians and do not have a
bugzilla account, where I think a mwiki account is more normal.

Would you consider moving your language page to mwiki, in order to be
available to a broader audience?

rgds
jan i
>
> -Rob
>
>
> > rgds
> > Jan I
> >
> >>
> >> Regards,
> >>
> >> -Rob
> >>
> >>
> >> > Michael
> >>

Re: Proposal: communications/workflow for new languages

Posted by Rob Weir <ro...@apache.org>.
On Sun, Feb 24, 2013 at 4:04 AM, janI <ja...@apache.org> wrote:
> On 23 February 2013 23:56, Rob Weir <ro...@apache.org> wrote:
>
>> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org>
>> wrote:
>> > A common translator's tuppence on the issue. Most translators are not
>> > programmers and the more technical and convoluted an approach you take,
>> the
>> > more you narrow your potential translators down to that much smaller
>> pool of
>> > people who can do both code and translation.
>> >
>> > They also, for the most part, don't give a fig about what license
>> something
>> > is under. I realise that for the people running the project in question,
>> > issues of license exist but the translators on the whole just want to
>> see X
>> > in their language released.
>> >
>> > Thirdly, duplication is hugely frustrating for translators, especially
>> for
>> > people working in smaller languages. Having just "rescued" some Firefox
>> > translations from Launchpad, I can vouch for that.
>> >
>> > So what would be actually nice is if AOO and LO could agree on a neutral
>> > Pootle server which handles both AOO and LO strings and from which each
>> > project can extract whatever translations they require. Minimum
>> duplication
>> > and standard signup and translation process (none of this Bugzilla stuff
>> or
>> > the need for someone to extract po files, email them, translation offline
>> > and the the whole thing backwards to commit, if ever there was a
>> #facepalm
>> > process, that's it...), if needed, slap a notice email in the process
>> about
>> > how these will be used.
>> >
>>
>> These are all good points (and Claudio's points are good as well) but
>> they are not related to my proposal.  I was just suggesting a way in
>> which we can use Bugzilla improve communications and track progress on
>> the offline translation of the PO files.
>>
>> For example, suppose right now a new volunteer posts a note saying
>> they want to help with the Greek translation.  Where are the PO files?
>>  What other volunteers have started on this effort?  Who else has
>> expressed interest?  Today we need to search through list archives to
>> find these facts.  But if we had one Bugzilla issue per locale, then
>> we could track status there, including attaching files.  Volunteers
>> can also add themselves to the cc-list for the Bug to stay "in the
>> loop".  And they can even create sub-issues if they want to divide up
>> the work formally.
>>
> I have nothing against using bugzilla, that would be fine for me. We are
> soon at the point where po files are available in svn (they are on my local
> computer).
>
> An alternative to bugzilla, would be mwiki (not cwiki :-). We could move
> the translation page you have made, and attach po files...then we would
> only have the information in one place, and I am sure more people are used
> mwiki than bugzilla.
>

Is there a way wtih MWiki to get automatic notifications when there is
a status change on your language?  I think that is the strength of the
workflow tracking in BZ.  Someone can add themselves to the cc for the
Greek tracking issue and get all messages related to that translation
effort, without signing up for the L10n mailing list and without
needing to remember to check a wiki.

-Rob


> rgds
> Jan I
>
>>
>> Regards,
>>
>> -Rob
>>
>>
>> > Michael
>>

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 23 February 2013 23:56, Rob Weir <ro...@apache.org> wrote:

> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org>
> wrote:
> > A common translator's tuppence on the issue. Most translators are not
> > programmers and the more technical and convoluted an approach you take,
> the
> > more you narrow your potential translators down to that much smaller
> pool of
> > people who can do both code and translation.
> >
> > They also, for the most part, don't give a fig about what license
> something
> > is under. I realise that for the people running the project in question,
> > issues of license exist but the translators on the whole just want to
> see X
> > in their language released.
> >
> > Thirdly, duplication is hugely frustrating for translators, especially
> for
> > people working in smaller languages. Having just "rescued" some Firefox
> > translations from Launchpad, I can vouch for that.
> >
> > So what would be actually nice is if AOO and LO could agree on a neutral
> > Pootle server which handles both AOO and LO strings and from which each
> > project can extract whatever translations they require. Minimum
> duplication
> > and standard signup and translation process (none of this Bugzilla stuff
> or
> > the need for someone to extract po files, email them, translation offline
> > and the the whole thing backwards to commit, if ever there was a
> #facepalm
> > process, that's it...), if needed, slap a notice email in the process
> about
> > how these will be used.
> >
>
> These are all good points (and Claudio's points are good as well) but
> they are not related to my proposal.  I was just suggesting a way in
> which we can use Bugzilla improve communications and track progress on
> the offline translation of the PO files.
>
> For example, suppose right now a new volunteer posts a note saying
> they want to help with the Greek translation.  Where are the PO files?
>  What other volunteers have started on this effort?  Who else has
> expressed interest?  Today we need to search through list archives to
> find these facts.  But if we had one Bugzilla issue per locale, then
> we could track status there, including attaching files.  Volunteers
> can also add themselves to the cc-list for the Bug to stay "in the
> loop".  And they can even create sub-issues if they want to divide up
> the work formally.
>
I have nothing against using bugzilla, that would be fine for me. We are
soon at the point where po files are available in svn (they are on my local
computer).

An alternative to bugzilla, would be mwiki (not cwiki :-). We could move
the translation page you have made, and attach po files...then we would
only have the information in one place, and I am sure more people are used
mwiki than bugzilla.

rgds
Jan I

>
> Regards,
>
> -Rob
>
>
> > Michael
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Thanks for the nice reply. I will start translating the rest. In the mean
while If you could set any automatic reminder every weak asking for the
status of translation , it will make this a little more faster.

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 16 March 2013 16:22, Andrea Pescetti <pe...@apache.org> wrote:

> On 11/03/2013 Kadal Amutham wrote:
>
>> The Panel Deck Bar - I did not translate since I could not. I did not know
>> what is that Panel Deck Bar.
>>
>
> OK, thanks for the explanation.
>
>
>  Is it not possible for you to get it checked by some one who knows Tamil?
>> Am I the only Tamil volunteer here?
>>
>
> Probably yes, but you are encouraged to recruit new ones! As for me, I can
> only confirm that the files I've looked at are formally correct, even
> though I'll have to trust you (and I do) on translation quality.
>
>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
On 11/03/2013 Kadal Amutham wrote:
> The Panel Deck Bar - I did not translate since I could not. I did not know
> what is that Panel Deck Bar.

OK, thanks for the explanation.

> Is it not possible for you to get it checked by some one who knows Tamil?
> Am I the only Tamil volunteer here?

Probably yes, but you are encouraged to recruit new ones! As for me, I 
can only confirm that the files I've looked at are formally correct, 
even though I'll have to trust you (and I do) on translation quality.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Andrea,

The Panel Deck Bar - I did not translate since I could not. I did not know
what is that Panel Deck Bar.
Do you want me to remove the file from Ubuntu One? . If so I will remove it.

Is it not possible for you to get it checked by some one who knows Tamil?
Am I the only Tamil volunteer here?

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 11 March 2013 12:58, Andrea Pescetti <pe...@apache.org> wrote:

> Il 10/03/2013 19:50, Kadal Amutham wrote:
>
>> [Andrea]
>>
>> - I opened the Ubuntu One space you shared
>> - I opened the first folder there: accessibility / source / helper.po
>> - It has one translated string (Browse =  தேடு ) and one untranslated
>> string (Panel Deck Tab Bar)
>> [Kadal] Now if some one could tell me is it as per your required
>> standard, then I
>> can proceed further
>>
>
> It isn't. Both strings should be translated. There are only two strings in
> the file:
> - "Browse" -> this is translated (as தேடு; I don't know Tamil but anyway
> this is formally correct)
> - "Panel Deck Tab Bar" -> this is untranslated
>
> So the file "accessibility / source / helper.po" as it is in the Ubntu One
> space is not OK. And it is not OK because it has an untranslated string.
> This is what I meant. Is this clear now?
>
>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Il 10/03/2013 19:50, Kadal Amutham wrote:
> [Andrea]
> - I opened the Ubuntu One space you shared
> - I opened the first folder there: accessibility / source / helper.po
> - It has one translated string (Browse =  தேடு ) and one untranslated
> string (Panel Deck Tab Bar)
> [Kadal] Now if some one could tell me is it as per your required standard, then I
> can proceed further

It isn't. Both strings should be translated. There are only two strings 
in the file:
- "Browse" -> this is translated (as தேடு; I don't know Tamil but anyway 
this is formally correct)
- "Panel Deck Tab Bar" -> this is untranslated

So the file "accessibility / source / helper.po" as it is in the Ubntu 
One space is not OK. And it is not OK because it has an untranslated 
string. This is what I meant. Is this clear now?

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Andrea Wrote:
Well, what I did is:
- I opened the Ubuntu One space you shared
- I opened the first folder there: accessibility / source / helper.po
- It has one translated string (Browse =  தேடு ) and one untranslated
string (Panel Deck Tab Bar)

Should I have looked somewhere else?

Now if some one could tell me is it as per your required standard, then I
can proceed further



With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 11 March 2013 00:03, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> I translated sentences from top 5-6 folders. Will this help you? Else I
>> can
>> do another translation of 10 lines and send it to you.
>>
>
> Well, what I did is:
> - I opened the Ubuntu One space you shared
> - I opened the first folder there: accessibility / source / helper.po
> - It has one translated string (Browse =  தேடு ) and one untranslated
> string (Panel Deck Tab Bar)
>
> Should I have looked somewhere else?
>
>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> I translated sentences from top 5-6 folders. Will this help you? Else I can
> do another translation of 10 lines and send it to you.

Well, what I did is:
- I opened the Ubuntu One space you shared
- I opened the first folder there: accessibility / source / helper.po
- It has one translated string (Browse =  தேடு ) and one untranslated 
string (Panel Deck Tab Bar)

Should I have looked somewhere else?

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Andrea,

I was using POedit (Available in ubuntu 11.10). POedit was displaying
the untranslated line  at the top and I just translated them. After
translation the lines get inserted (I think) as per the alphabetical order.
So I am finding it difficult to locate the exact lines which I have
translated.

I translated sentences from top 5-6 folders. Will this help you? Else I can
do another translation of 10 lines and send it to you.

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 10 March 2013 03:54, Andrea Pescetti <pe...@apache.org> wrote:

> On 09/03/2013 Kadal Amutham wrote:
>
>> I have done some translation for the first few folders. If some one can
>> check that it is as per your requirement and usable, I can continue with
>> the rest. I want to know whether I am in the right direction
>>
>
> Could you name one file (just one) to check and where to find it exactly?
> I had a look at your shared Ubuntu One folder (in the "accessibility" and
> "chart2" folders) and I didn't find completely translated files. Or should
> I look on Pootle?
>
>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
On 09/03/2013 Kadal Amutham wrote:
> I have done some translation for the first few folders. If some one can
> check that it is as per your requirement and usable, I can continue with
> the rest. I want to know whether I am in the right direction

Could you name one file (just one) to check and where to find it 
exactly? I had a look at your shared Ubuntu One folder (in the 
"accessibility" and "chart2" folders) and I didn't find completely 
translated files. Or should I look on Pootle?

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Andrea,

 I have done some translation for the first few folders. If some one can
check that it is as per your requirement and usable, I can continue with
the rest. I want to know whether I am in the right direction

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 5 March 2013 13:51, Kadal Amutham <vk...@gmail.com> wrote:

> Ok, fine, I have done some translation for the first few folders. If you
> some one can check that it is as per your requirement and usable, I can
> continue with the rest. I want to know whether I am in the right direction
>
> With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 5 March 2013 13:47, Andrea Pescetti <pe...@apache.org> wrote:
>
>> Kadal Amutham wrote:
>>
>>> I am editing / adding to the ta folder and the folder has been shared
>>> with
>>> the email ID pescetti@... Le me know if there is any problem is
>>> downloading the same
>>>
>>
>> Thank you, I tried access and it works. I won't follow it regularly, but
>> I'll be able to download files when you tell us that translations are ready
>> to be integrated.
>>
>> Regards,
>>   Andrea.
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
>> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>>
>>
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Ok, fine, I have done some translation for the first few folders. If you
some one can check that it is as per your requirement and usable, I can
continue with the rest. I want to know whether I am in the right direction

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 5 March 2013 13:47, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> I am editing / adding to the ta folder and the folder has been shared with
>> the email ID pescetti@... Le me know if there is any problem is
>> downloading the same
>>
>
> Thank you, I tried access and it works. I won't follow it regularly, but
> I'll be able to download files when you tell us that translations are ready
> to be integrated.
>
> Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.**apache.org<l1...@openoffice.apache.org>
> For additional commands, e-mail: l10n-help@openoffice.apache.**org<l1...@openoffice.apache.org>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> I am editing / adding to the ta folder and the folder has been shared with
> the email ID pescetti@... Le me know if there is any problem is
> downloading the same

Thank you, I tried access and it works. I won't follow it regularly, but 
I'll be able to download files when you tell us that translations are 
ready to be integrated.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org


Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
I am editing / adding to the ta folder and the folder has been shared with
the email ID pescetti@apache.org. Le me know if there is any problem is
downloading the same

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 4 March 2013 07:07, Kadal Amutham <vk...@gmail.com> wrote:

> I have installed poedit, from software center ubuntu 11.10 and downloaded
> the ta files. After translation, I will translate and save and let you know
>
>  With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 4 March 2013 01:44, Andrea Pescetti <pe...@apache.org> wrote:
>
>> Il 03/03/2013 19:43, janI wrote:
>>
>>> On 3 March 2013 19:01, Kadal Amutham<vk...@gmail.com>  wrote:
>>>
>>>  Is it possible to download  the text to be translated and send me as a
>>>> spreadsheet? A lot of time is wasted while my browser updates between
>>>> each
>>>> line of translation
>>>>
>>>>  If you do work offline, I would advice strongly against anything other
>>> than
>>> a speciliazed .po file editing tool like poedit.
>>>
>>
>> I totally agree with Jan. Working offline is the supported way; it is
>> more difficult, but we are here to help and all the recently released
>> translations have been done this way.
>>
>> So, if you prefer to download files, your steps are:
>> 1) Install POEdit (from http://www.poedit.net/ or otherwise, depending
>> on your operating system). If on Windows, install http://www.7-zip.org/too.
>> 2) Download the Tamil files from here: http://people.apache.org/~jsc/**
>> translation/aoo341_ta_po-**files.tar.bz2<http://people.apache.org/~jsc/translation/aoo341_ta_po-files.tar.bz2>and expand the archive.
>> 3) Open each file with POEdit, translate and save.
>> 4) When you are done, write again and we will take care of integrating
>> your translations.
>>
>> Regards,
>>   Andrea.
>>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
I have installed poedit, from software center ubuntu 11.10 and downloaded
the ta files. After translation, I will translate and save and let you know

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 4 March 2013 01:44, Andrea Pescetti <pe...@apache.org> wrote:

> Il 03/03/2013 19:43, janI wrote:
>
>> On 3 March 2013 19:01, Kadal Amutham<vk...@gmail.com>  wrote:
>>
>>  Is it possible to download  the text to be translated and send me as a
>>> spreadsheet? A lot of time is wasted while my browser updates between
>>> each
>>> line of translation
>>>
>>>  If you do work offline, I would advice strongly against anything other
>> than
>> a speciliazed .po file editing tool like poedit.
>>
>
> I totally agree with Jan. Working offline is the supported way; it is more
> difficult, but we are here to help and all the recently released
> translations have been done this way.
>
> So, if you prefer to download files, your steps are:
> 1) Install POEdit (from http://www.poedit.net/ or otherwise, depending on
> your operating system). If on Windows, install http://www.7-zip.org/ too.
> 2) Download the Tamil files from here: http://people.apache.org/~jsc/**
> translation/aoo341_ta_po-**files.tar.bz2<http://people.apache.org/~jsc/translation/aoo341_ta_po-files.tar.bz2>and expand the archive.
> 3) Open each file with POEdit, translate and save.
> 4) When you are done, write again and we will take care of integrating
> your translations.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Il 03/03/2013 19:43, janI wrote:
> On 3 March 2013 19:01, Kadal Amutham<vk...@gmail.com>  wrote:
>
>> Is it possible to download  the text to be translated and send me as a
>> spreadsheet? A lot of time is wasted while my browser updates between each
>> line of translation
>>
> If you do work offline, I would advice strongly against anything other than
> a speciliazed .po file editing tool like poedit.

I totally agree with Jan. Working offline is the supported way; it is 
more difficult, but we are here to help and all the recently released 
translations have been done this way.

So, if you prefer to download files, your steps are:
1) Install POEdit (from http://www.poedit.net/ or otherwise, depending 
on your operating system). If on Windows, install http://www.7-zip.org/ too.
2) Download the Tamil files from here: 
http://people.apache.org/~jsc/translation/aoo341_ta_po-files.tar.bz2 and 
expand the archive.
3) Open each file with POEdit, translate and save.
4) When you are done, write again and we will take care of integrating 
your translations.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 3 March 2013 19:01, Kadal Amutham <vk...@gmail.com> wrote:

> Is it possible to download  the text to be translated and send me as a
> spreadsheet? A lot of time is wasted while my browser updates between each
> line of translation
>
If you do work offline, I would advice strongly against anything other than
a speciliazed .po file editing tool like poedit.

Editing the texts in a spreadsheet carries a high possibility of loosing
the connection betwen key, english text, flags and translation.

rgds
Jan I.


>
> With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 3 March 2013 23:27, Kadal Amutham <vk...@gmail.com> wrote:
>
> > Thanks for the guidance Andrea. I have gone through the tips and I have
> no
> > reservation as working as "nobody"
> > (Transforming from somebody to nobody is a sign of progress)
> >
> > With Warm Regards
> >
> > V.Kadal Amutham
> > 919444360480
> > 914422396480
> >
> >
> > On 3 March 2013 23:14, Andrea Pescetti <pe...@apache.org> wrote:
> >
> >> On 02/03/2013 Kadal Amutham wrote:
> >>
> >>> Looks like most of the in the advanced stage of completion. If I put
> some
> >>> more effort, I can bring it a  little more closer to completion. What
> is
> >>> your advice to me?
> >>>
> >>
> >> We can perfectly do an experiment for Tamil, so you can go on (but
> please
> >> do read the "Tips for translators" I mentioned). The two problems we
> have
> >> now are:
> >> - We can't create accounts for new volunteers, so you will have to work
> >> anonymously
> >> - As Jan mentioned on the dev list, we can support a very limited amount
> >> of translators (2-3) due to performance limitations.
> >>
> >> These are the reasons that force us to wait before recommending Pootle
> >> for the translation workflow. But I don't see anything bad in making
> this
> >> test for Tamil. The strings you contribute will, obviously, be under the
> >> Apache License 2, like the OpenOffice source code.
> >>
> >> Regards,
> >>   Andrea.
> >>
> >
> >
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Is it possible to download  the text to be translated and send me as a
spreadsheet? A lot of time is wasted while my browser updates between each
line of translation

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 3 March 2013 23:27, Kadal Amutham <vk...@gmail.com> wrote:

> Thanks for the guidance Andrea. I have gone through the tips and I have no
> reservation as working as "nobody"
> (Transforming from somebody to nobody is a sign of progress)
>
> With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 3 March 2013 23:14, Andrea Pescetti <pe...@apache.org> wrote:
>
>> On 02/03/2013 Kadal Amutham wrote:
>>
>>> Looks like most of the in the advanced stage of completion. If I put some
>>> more effort, I can bring it a  little more closer to completion. What is
>>> your advice to me?
>>>
>>
>> We can perfectly do an experiment for Tamil, so you can go on (but please
>> do read the "Tips for translators" I mentioned). The two problems we have
>> now are:
>> - We can't create accounts for new volunteers, so you will have to work
>> anonymously
>> - As Jan mentioned on the dev list, we can support a very limited amount
>> of translators (2-3) due to performance limitations.
>>
>> These are the reasons that force us to wait before recommending Pootle
>> for the translation workflow. But I don't see anything bad in making this
>> test for Tamil. The strings you contribute will, obviously, be under the
>> Apache License 2, like the OpenOffice source code.
>>
>> Regards,
>>   Andrea.
>>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Thanks for the guidance Andrea. I have gone through the tips and I have no
reservation as working as "nobody"
(Transforming from somebody to nobody is a sign of progress)

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 3 March 2013 23:14, Andrea Pescetti <pe...@apache.org> wrote:

> On 02/03/2013 Kadal Amutham wrote:
>
>> Looks like most of the in the advanced stage of completion. If I put some
>> more effort, I can bring it a  little more closer to completion. What is
>> your advice to me?
>>
>
> We can perfectly do an experiment for Tamil, so you can go on (but please
> do read the "Tips for translators" I mentioned). The two problems we have
> now are:
> - We can't create accounts for new volunteers, so you will have to work
> anonymously
> - As Jan mentioned on the dev list, we can support a very limited amount
> of translators (2-3) due to performance limitations.
>
> These are the reasons that force us to wait before recommending Pootle for
> the translation workflow. But I don't see anything bad in making this test
> for Tamil. The strings you contribute will, obviously, be under the Apache
> License 2, like the OpenOffice source code.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
On 02/03/2013 Kadal Amutham wrote:
> Looks like most of the in the advanced stage of completion. If I put some
> more effort, I can bring it a  little more closer to completion. What is
> your advice to me?

We can perfectly do an experiment for Tamil, so you can go on (but 
please do read the "Tips for translators" I mentioned). The two problems 
we have now are:
- We can't create accounts for new volunteers, so you will have to work 
anonymously
- As Jan mentioned on the dev list, we can support a very limited amount 
of translators (2-3) due to performance limitations.

These are the reasons that force us to wait before recommending Pootle 
for the translation workflow. But I don't see anything bad in making 
this test for Tamil. The strings you contribute will, obviously, be 
under the Apache License 2, like the OpenOffice source code.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Looks like most of the in the advanced stage of completion. If I put some
more effort, I can bring it a  little more closer to completion. What is
your advice to me?

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 2 March 2013 20:30, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> I have edited some of the translation and added a new one. If some one
>> reviews my suggested translation, then 100% completion can be achieved for
>> Tamil
>>
>
> That file will be at 100%, but there are 240 such files. I sent you a link
> to one random file. The full list of files is at
> https://translate.apache.org/**ta/OOo_34/<https://translate.apache.org/ta/OOo_34/>
> and everything there, excluding the folder named "basic", must be
> translated.
>
> Read http://openoffice.apache.org/**translate.html<http://openoffice.apache.org/translate.html>(Tips for Translators) if you don't want to waste time. Instructions apply
> to both Pootle and POEdit.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> I have edited some of the translation and added a new one. If some one
> reviews my suggested translation, then 100% completion can be achieved for
> Tamil

That file will be at 100%, but there are 240 such files. I sent you a 
link to one random file. The full list of files is at
https://translate.apache.org/ta/OOo_34/
and everything there, excluding the folder named "basic", must be 
translated.

Read http://openoffice.apache.org/translate.html (Tips for Translators) 
if you don't want to waste time. Instructions apply to both Pootle and 
POEdit.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
I have edited some of the translation and added a new one. If some one
reviews my suggested translation, then 100% completion can be achieved for
Tamil

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 2 March 2013 06:39, Kadal Amutham <vk...@gmail.com> wrote:

> Dear Jan I, Thanks for the reply. Once I went to the  page
> https://translate.apache.org/ta/OOo_34/desktop/source/app.po/translate/ and
> checked . The page displayed my suggestions from Nobody. This happened
> since I did not login. How ever my suggestions are saved and safe. So
> anybody else can check and accept / reject the same.
>
> So when ever I find time, I keep continuing to  translate
>
> With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 1 March 2013 23:36, janI <ja...@apache.org> wrote:
>
>> On 1 March 2013 17:55, Kadal Amutham <vk...@gmail.com> wrote:
>>
>> > Ok, I have no other choice than wait , till Jan, a long way to go.....
>> >
>>
>> There is no problem in you (or others) translating, there is not a stop
>> sign active. Translators have been translating using either offline tools
>> (like poedit) or pootle for quite some time, and will continue to do so
>> for
>> some time.
>>
>> What is happening, is that I am changing the infrastructure of translation
>> in steps:
>> 1) change the tools to extract/merge the texts from the source and convert
>> to/from .po files for translation.
>>     This work is slowly comming to the stage where it can go into
>> production.
>> 2) change the pootle version to 2.5 when it is released.
>>     However how we exactly are going to use it, is something the community
>> in general has to discuss.
>>
>> Technically I have "frozen" the translations, in order to work on a non
>> changing set of files, but if you in the meantime translate strings, those
>> strings can later be integrated, so they are not lost.
>>
>> Regarding your suggestions (or offline translations), they can in theory
>> only be reviewed and committed by a committer is a native speaker, however
>> it is more important to have volunteers, so I have committed your change
>> (just as others did with my changes to Danish, before I became a
>> committer).
>>
>> Please keep up the good work it is really needed, and let me know if I can
>> assist you, with my limited knowledge.
>>
>> have a nice day.
>> rgds
>> jan I.
>>
>>
>>
>>
>>
>> >
>> > With Warm Regards
>> >
>> > V.Kadal Amutham
>> > 919444360480
>> > 914422396480
>> >
>> >
>> > On 1 March 2013 22:00, Andrea Pescetti <pe...@apache.org> wrote:
>> >
>> > > Kadal Amutham wrote:
>> > >
>> > >> I am able to modify few translation and press the suggest buttons.
>> Are
>> > >> these suggestions will be reviewed, and found better, accepted?
>> > >>
>> > >
>> > > No. They will very likely be ignored (in theory we might use them,
>> but we
>> > > -Jan, actually- are still working on an optimal workflow). This is the
>> > > reason why I was saying to wait for the new configuration to be
>> active.
>> > >
>> > > Regards,
>> > >   Andrea.
>> > >
>> >
>>
>
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Jan I, Thanks for the reply. Once I went to the  page
https://translate.apache.org/ta/OOo_34/desktop/source/app.po/translate/ and
checked . The page displayed my suggestions from Nobody. This happened
since I did not login. How ever my suggestions are saved and safe. So
anybody else can check and accept / reject the same.

So when ever I find time, I keep continuing to  translate

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 1 March 2013 23:36, janI <ja...@apache.org> wrote:

> On 1 March 2013 17:55, Kadal Amutham <vk...@gmail.com> wrote:
>
> > Ok, I have no other choice than wait , till Jan, a long way to go.....
> >
>
> There is no problem in you (or others) translating, there is not a stop
> sign active. Translators have been translating using either offline tools
> (like poedit) or pootle for quite some time, and will continue to do so for
> some time.
>
> What is happening, is that I am changing the infrastructure of translation
> in steps:
> 1) change the tools to extract/merge the texts from the source and convert
> to/from .po files for translation.
>     This work is slowly comming to the stage where it can go into
> production.
> 2) change the pootle version to 2.5 when it is released.
>     However how we exactly are going to use it, is something the community
> in general has to discuss.
>
> Technically I have "frozen" the translations, in order to work on a non
> changing set of files, but if you in the meantime translate strings, those
> strings can later be integrated, so they are not lost.
>
> Regarding your suggestions (or offline translations), they can in theory
> only be reviewed and committed by a committer is a native speaker, however
> it is more important to have volunteers, so I have committed your change
> (just as others did with my changes to Danish, before I became a
> committer).
>
> Please keep up the good work it is really needed, and let me know if I can
> assist you, with my limited knowledge.
>
> have a nice day.
> rgds
> jan I.
>
>
>
>
>
> >
> > With Warm Regards
> >
> > V.Kadal Amutham
> > 919444360480
> > 914422396480
> >
> >
> > On 1 March 2013 22:00, Andrea Pescetti <pe...@apache.org> wrote:
> >
> > > Kadal Amutham wrote:
> > >
> > >> I am able to modify few translation and press the suggest buttons. Are
> > >> these suggestions will be reviewed, and found better, accepted?
> > >>
> > >
> > > No. They will very likely be ignored (in theory we might use them, but
> we
> > > -Jan, actually- are still working on an optimal workflow). This is the
> > > reason why I was saying to wait for the new configuration to be active.
> > >
> > > Regards,
> > >   Andrea.
> > >
> >
>

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 1 March 2013 17:55, Kadal Amutham <vk...@gmail.com> wrote:

> Ok, I have no other choice than wait , till Jan, a long way to go.....
>

There is no problem in you (or others) translating, there is not a stop
sign active. Translators have been translating using either offline tools
(like poedit) or pootle for quite some time, and will continue to do so for
some time.

What is happening, is that I am changing the infrastructure of translation
in steps:
1) change the tools to extract/merge the texts from the source and convert
to/from .po files for translation.
    This work is slowly comming to the stage where it can go into
production.
2) change the pootle version to 2.5 when it is released.
    However how we exactly are going to use it, is something the community
in general has to discuss.

Technically I have "frozen" the translations, in order to work on a non
changing set of files, but if you in the meantime translate strings, those
strings can later be integrated, so they are not lost.

Regarding your suggestions (or offline translations), they can in theory
only be reviewed and committed by a committer is a native speaker, however
it is more important to have volunteers, so I have committed your change
(just as others did with my changes to Danish, before I became a committer).

Please keep up the good work it is really needed, and let me know if I can
assist you, with my limited knowledge.

have a nice day.
rgds
jan I.





>
> With Warm Regards
>
> V.Kadal Amutham
> 919444360480
> 914422396480
>
>
> On 1 March 2013 22:00, Andrea Pescetti <pe...@apache.org> wrote:
>
> > Kadal Amutham wrote:
> >
> >> I am able to modify few translation and press the suggest buttons. Are
> >> these suggestions will be reviewed, and found better, accepted?
> >>
> >
> > No. They will very likely be ignored (in theory we might use them, but we
> > -Jan, actually- are still working on an optimal workflow). This is the
> > reason why I was saying to wait for the new configuration to be active.
> >
> > Regards,
> >   Andrea.
> >
>

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Ok, I have no other choice than wait , till Jan, a long way to go.....

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 1 March 2013 22:00, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> I am able to modify few translation and press the suggest buttons. Are
>> these suggestions will be reviewed, and found better, accepted?
>>
>
> No. They will very likely be ignored (in theory we might use them, but we
> -Jan, actually- are still working on an optimal workflow). This is the
> reason why I was saying to wait for the new configuration to be active.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> I am able to modify few translation and press the suggest buttons. Are
> these suggestions will be reviewed, and found better, accepted?

No. They will very likely be ignored (in theory we might use them, but 
we -Jan, actually- are still working on an optimal workflow). This is 
the reason why I was saying to wait for the new configuration to be active.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
I am able to modify few translation and press the suggest buttons. Are
these suggestions will be reviewed, and found better, accepted?

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 1 March 2013 17:40, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> Here the the whole sentence is translated into Tamil and this look fine.
>> How to know a new sentence has been added and need translation? Can I
>> contact other Tamil volunteers so that a better translation can be
>> produced?
>>
>
> A working Pootle installation allows you to login and navigate through the
> untranslated strings. And it also allows to work in a team with no risk of
> overlapping. But the current installation is not yet ready to support this
> workflow for new volunteers, so you need to wait that it is reconfigured
> (no timeline yet, but I think Jan is working on it).
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> Here the the whole sentence is translated into Tamil and this look fine.
> How to know a new sentence has been added and need translation? Can I
> contact other Tamil volunteers so that a better translation can be produced?

A working Pootle installation allows you to login and navigate through 
the untranslated strings. And it also allows to work in a team with no 
risk of overlapping. But the current installation is not yet ready to 
support this workflow for new volunteers, so you need to wait that it is 
reconfigured (no timeline yet, but I think Jan is working on it).

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Andrea,

Here the the whole sentence is translated into Tamil and this look fine.
How to know a new sentence has been added and need translation? Can I
contact other Tamil volunteers so that a better translation can be produced?

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 1 March 2013 13:36, Andrea Pescetti <pe...@apache.org> wrote:

> Kadal Amutham wrote:
>
>> I want to try Pootle and see how it translates English to Tamil. Can you
>> guide me ?
>>
>
> The current setup is not yet good enough to allow volunteers to register
> and contribute, but if you want to see Pootle in action you can see
> https://translate.apache.org/**ta/OOo_34/desktop/source/app.**
> po/translate/<https://translate.apache.org/ta/OOo_34/desktop/source/app.po/translate/>
> (Pootle is a translation management tool; all the strings you see there
> have been contributed by Tamil volunteers over the past years).
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
Kadal Amutham wrote:
> I want to try Pootle and see how it translates English to Tamil. Can you
> guide me ?

The current setup is not yet good enough to allow volunteers to register 
and contribute, but if you want to see Pootle in action you can see
https://translate.apache.org/ta/OOo_34/desktop/source/app.po/translate/
(Pootle is a translation management tool; all the strings you see there 
have been contributed by Tamil volunteers over the past years).

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Kadal Amutham <vk...@gmail.com>.
Dear Andrea,

I want to try Pootle and see how it translates English to Tamil. Can you
guide me ?

With Warm Regards

V.Kadal Amutham
919444360480
914422396480


On 1 March 2013 04:54, Andrea Pescetti <pe...@apache.org> wrote:

> On 25/02/2013 Rob Weir wrote:
>
>> And maybe that starts getting too geeky when we post PO files in
>> tar.bz2 format, a format unheard of to Windows users who comprise 90%+
>> of our users?
>>
>
> This is surely a steep learning curve. And I believe we do lose volunteers
> at this step.
>
>  Look around.  How many
>> volunteers have come through asking to help about Hebrew, Greek and
>> Portuguese?   Isn't a non-optimal that they haven't managed to
>> coordinate on the translation?  Isn't it non-optimal that we have no
>> idea whether this is even being worked on?  That is the problem we're
>> facing.
>>
>
> And Pootle is the solution. A working Pootle installation, with a
> well-thought access policy, allows effortless collaboration and monitoring.
>
>  we need to help with
>> the coordination side as well.  And this might mean smart use of
>> technology rather than just complaining that technology is hard.
>>
>
> In March we can try the BugZilla way. We can probably even start the
> registration process at https://issues.apache.org/ooo/**createaccount.cgi<https://issues.apache.org/ooo/createaccount.cgi>leaving to volunteers the only task of confirming their e-mail address.
> This should be simple enough for everybody, if we explain it properly.
>
> But in the medium-long term I really believe that Pootle will make the
> difference.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
On 25/02/2013 Rob Weir wrote:
> And maybe that starts getting too geeky when we post PO files in
> tar.bz2 format, a format unheard of to Windows users who comprise 90%+
> of our users?

This is surely a steep learning curve. And I believe we do lose 
volunteers at this step.

> Look around.  How many
> volunteers have come through asking to help about Hebrew, Greek and
> Portuguese?   Isn't a non-optimal that they haven't managed to
> coordinate on the translation?  Isn't it non-optimal that we have no
> idea whether this is even being worked on?  That is the problem we're
> facing.

And Pootle is the solution. A working Pootle installation, with a 
well-thought access policy, allows effortless collaboration and monitoring.

> we need to help with
> the coordination side as well.  And this might mean smart use of
> technology rather than just complaining that technology is hard.

In March we can try the BugZilla way. We can probably even start the 
registration process at https://issues.apache.org/ooo/createaccount.cgi 
leaving to volunteers the only task of confirming their e-mail address. 
This should be simple enough for everybody, if we explain it properly.

But in the medium-long term I really believe that Pootle will make the 
difference.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by Rob Weir <ro...@apache.org>.
On Mon, Feb 25, 2013 at 3:13 AM, Jürgen Schmidt <jo...@gmail.com> wrote:
> On 2/23/13 11:56 PM, Rob Weir wrote:
>> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org> wrote:
>>> A common translator's tuppence on the issue. Most translators are not
>>> programmers and the more technical and convoluted an approach you take, the
>>> more you narrow your potential translators down to that much smaller pool of
>>> people who can do both code and translation.
>>>
>>> They also, for the most part, don't give a fig about what license something
>>> is under. I realise that for the people running the project in question,
>>> issues of license exist but the translators on the whole just want to see X
>>> in their language released.
>>>
>>> Thirdly, duplication is hugely frustrating for translators, especially for
>>> people working in smaller languages. Having just "rescued" some Firefox
>>> translations from Launchpad, I can vouch for that.
>>>
>>> So what would be actually nice is if AOO and LO could agree on a neutral
>>> Pootle server which handles both AOO and LO strings and from which each
>>> project can extract whatever translations they require. Minimum duplication
>>> and standard signup and translation process (none of this Bugzilla stuff or
>>> the need for someone to extract po files, email them, translation offline
>>> and the the whole thing backwards to commit, if ever there was a #facepalm
>>> process, that's it...), if needed, slap a notice email in the process about
>>> how these will be used.
>>>
>>
>> These are all good points (and Claudio's points are good as well) but
>> they are not related to my proposal.  I was just suggesting a way in
>> which we can use Bugzilla improve communications and track progress on
>> the offline translation of the PO files.
>>
>> For example, suppose right now a new volunteer posts a note saying
>> they want to help with the Greek translation.  Where are the PO files?
>>  What other volunteers have started on this effort?  Who else has
>> expressed interest?  Today we need to search through list archives to
>> find these facts.  But if we had one Bugzilla issue per locale, then
>> we could track status there, including attaching files.  Volunteers
>> can also add themselves to the cc-list for the Bug to stay "in the
>> loop".  And they can even create sub-issues if they want to divide up
>> the work formally.
>
> Michael said very clear that he believe Bugzilla is to technical and too
> heavy for many translators. Besides all the other good points he made we
> should think about a way to simplify the usage of Bugzilla in this use
> case. We don't want to lose any translators because of too technical
> process.
>

Actually, Michael didn't say anything specifically about Bugzilla.  Go
back and read his note.  He was complaining about the entire off-line
translation process and saying that it was too complicated.

And maybe that starts getting too geeky when we post PO files in
tar.bz2 format, a format unheard of to Windows users who comprise 90%+
of our users?

In any case, I even question whether that is our main problem.  If
volunteers were confused or could not figure out how to do something
then they would ask.  We see that on every other list where project
tools are involved.  Maybe not everyone would ask.  Some would just
leave.  But we would get questions.  Look at the dev list, the qa
list, even the marketing list.   But where have we received questions
from translators saying that they are confused about off-line
translation?  Zero, right?  Where we have seen questions is about the
anonymous Pootle usage.

IMHO, our problem today is about lack of coordination.  It is not
about the technology being too hard.   Look around.  How many
volunteers have come through asking to help about Hebrew, Greek and
Portuguese?   Isn't a non-optimal that they haven't managed to
coordinate on the translation?  Isn't it non-optimal that we have no
idea whether this is even being worked on?  That is the problem we're
facing.

We're wasting our time arguing whether typing into a box in Bugzilla
is harder or easier than typing into a box in MWiki.  Etiher would be
fine.  But our problem is that we're failing to provide the tools and
processes for small groups of new volunteers to coordinate on a
translation.  This is not about technology.  It is about our disregard
for the fact that technology is not enough, that we need to help with
the coordination side as well.  And this might mean smart use of
technology rather than just complaining that technology is hard.

-Rob


> Juergen
>
>
>
>>
>> Regards,
>>
>> -Rob
>>
>>
>>> Michael
>

Re: Proposal: communications/workflow for new languages

Posted by Jürgen Schmidt <jo...@gmail.com>.
On 2/23/13 11:56 PM, Rob Weir wrote:
> On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org> wrote:
>> A common translator's tuppence on the issue. Most translators are not
>> programmers and the more technical and convoluted an approach you take, the
>> more you narrow your potential translators down to that much smaller pool of
>> people who can do both code and translation.
>>
>> They also, for the most part, don't give a fig about what license something
>> is under. I realise that for the people running the project in question,
>> issues of license exist but the translators on the whole just want to see X
>> in their language released.
>>
>> Thirdly, duplication is hugely frustrating for translators, especially for
>> people working in smaller languages. Having just "rescued" some Firefox
>> translations from Launchpad, I can vouch for that.
>>
>> So what would be actually nice is if AOO and LO could agree on a neutral
>> Pootle server which handles both AOO and LO strings and from which each
>> project can extract whatever translations they require. Minimum duplication
>> and standard signup and translation process (none of this Bugzilla stuff or
>> the need for someone to extract po files, email them, translation offline
>> and the the whole thing backwards to commit, if ever there was a #facepalm
>> process, that's it...), if needed, slap a notice email in the process about
>> how these will be used.
>>
> 
> These are all good points (and Claudio's points are good as well) but
> they are not related to my proposal.  I was just suggesting a way in
> which we can use Bugzilla improve communications and track progress on
> the offline translation of the PO files.
> 
> For example, suppose right now a new volunteer posts a note saying
> they want to help with the Greek translation.  Where are the PO files?
>  What other volunteers have started on this effort?  Who else has
> expressed interest?  Today we need to search through list archives to
> find these facts.  But if we had one Bugzilla issue per locale, then
> we could track status there, including attaching files.  Volunteers
> can also add themselves to the cc-list for the Bug to stay "in the
> loop".  And they can even create sub-issues if they want to divide up
> the work formally.

Michael said very clear that he believe Bugzilla is to technical and too
heavy for many translators. Besides all the other good points he made we
should think about a way to simplify the usage of Bugzilla in this use
case. We don't want to lose any translators because of too technical
process.

Juergen



> 
> Regards,
> 
> -Rob
> 
> 
>> Michael


Re: Proposal: communications/workflow for new languages

Posted by Rob Weir <ro...@apache.org>.
On Sat, Feb 23, 2013 at 12:58 PM, Michael Bauer <fi...@akerbeltz.org> wrote:
> A common translator's tuppence on the issue. Most translators are not
> programmers and the more technical and convoluted an approach you take, the
> more you narrow your potential translators down to that much smaller pool of
> people who can do both code and translation.
>
> They also, for the most part, don't give a fig about what license something
> is under. I realise that for the people running the project in question,
> issues of license exist but the translators on the whole just want to see X
> in their language released.
>
> Thirdly, duplication is hugely frustrating for translators, especially for
> people working in smaller languages. Having just "rescued" some Firefox
> translations from Launchpad, I can vouch for that.
>
> So what would be actually nice is if AOO and LO could agree on a neutral
> Pootle server which handles both AOO and LO strings and from which each
> project can extract whatever translations they require. Minimum duplication
> and standard signup and translation process (none of this Bugzilla stuff or
> the need for someone to extract po files, email them, translation offline
> and the the whole thing backwards to commit, if ever there was a #facepalm
> process, that's it...), if needed, slap a notice email in the process about
> how these will be used.
>

These are all good points (and Claudio's points are good as well) but
they are not related to my proposal.  I was just suggesting a way in
which we can use Bugzilla improve communications and track progress on
the offline translation of the PO files.

For example, suppose right now a new volunteer posts a note saying
they want to help with the Greek translation.  Where are the PO files?
 What other volunteers have started on this effort?  Who else has
expressed interest?  Today we need to search through list archives to
find these facts.  But if we had one Bugzilla issue per locale, then
we could track status there, including attaching files.  Volunteers
can also add themselves to the cc-list for the Bug to stay "in the
loop".  And they can even create sub-issues if they want to divide up
the work formally.

Regards,

-Rob


> Michael

Re: Proposal: communications/workflow for new languages

Posted by Michael Bauer <fi...@akerbeltz.org>.
A common translator's tuppence on the issue. Most translators are not 
programmers and the more technical and convoluted an approach you take, 
the more you narrow your potential translators down to that much smaller 
pool of people who can do both code and translation.

They also, for the most part, don't give a fig about what license 
something is under. I realise that for the people running the project in 
question, issues of license exist but the translators on the whole just 
want to see X in their language released.

Thirdly, duplication is hugely frustrating for translators, especially 
for people working in smaller languages. Having just "rescued" some 
Firefox translations from Launchpad, I can vouch for that.

So what would be actually nice is if AOO and LO could agree on a neutral 
Pootle server which handles both AOO and LO strings and from which each 
project can extract whatever translations they require. Minimum 
duplication and standard signup and translation process (none of this 
Bugzilla stuff or the need for someone to extract po files, email them, 
translation offline and the the whole thing backwards to commit, if ever 
there was a #facepalm process, that's it...), if needed, slap a notice 
email in the process about how these will be used.

Michael

Re: Proposal: communications/workflow for new languages

Posted by Rob Weir <ro...@apache.org>.
On Fri, Feb 22, 2013 at 1:20 PM, Claudio Filho <fi...@gmail.com> wrote:
> Hi
>
> 2013/2/22 janI <ja...@apache.org>:
>> At current (based on work of the update of translate-vm) we are able to
>> share strings within the asf community and anybody else accepting our
>> license.
>
> This is a good new.
>
>> The bsd license is not valid for our installation (but  it is for the
>> general version), we accept only our ICLA license (committers only).
>
> This is the point: other contributions.
>
> Today we have two levels of contribution, but and if we have
> translators that wish to use Pootle without sign a ICLA? This is the
> good point (IMHO) at launchpad. When you register your self in there
> tool, you check/agree that all your work will be licensed under BSD.
>
> I understand that this process can be adopted by us, Ipsis litteris,
> changing the license by Apache.
>
> I took a look fast in Pootle docs and  saw that exist condition to
> enable other permissions for users and I think that is possible to
> create profiles. IMO, is possible to enable more one profile, of
> translator (without ICLA, but agreed in registration time with donate
> his work to ASF/project).
>
> The main point is collect more volunteers with translation skill (in
> some times is the *unique* thing that can help), and giving to him an
> idea about how works the project. In a second time (and with
> interaction with his l10n team or the project at all), he can sign the
> ICLA and will be promoted to commiter, with more "powers". ;-)
>
>> HOWEver, I hope with the new infra structure to provide a platform for
>> non-committers to use pootle in a motivating way, this depend however on a
>> vote in the community.
>
> I think that we have the same idea, Janl. And using your "way" (with
> images) in new propose for l10n, i did a flow explaining my idea[1].
> [1]http://people.apache.org/~filhocf/aoo/proposed_flow_pootle.png
>

This makes sense to me.  Apache does something similar in JIRA.  A
user can submit a patch on an issue in JIRA and say that it is under
the Apache License.  No ICLA is required.  Ditto for sending a patch
on the mailing list.  Pootle could be the same.

-Rob

> Regards,
> Claudio

Re: Proposal: communications/workflow for new languages

Posted by Claudio Filho <fi...@gmail.com>.
Hi

2013/2/23 janI <ja...@apache.org>:
> Translators can use pootle today without having signed a ICLA, however the
> submitted translations will be saved as suggestions until approved by a
> committer. This process is equivalent to volunteers submitting patches.

Yes. And this actor is represented in my image, but without any
recognition of his efforts. And if I have a good guy in my translation
team and I wish "to promote" him to translator, but without power of
commit?

A new level between "nobody" volunteer and a commiter. Many times,
volunteer translators wish just his name there, independent of
license. Is a intermediate step between "john doe" and "signed ICLA
commiter".

Do we can't accept this type of contribution?

One example was the pt-BR translation for OOo. I splitted the PO files
between a team, where only some guys has connection with international
project. We did in some months all translation and returned under my
name. How i hasn't way of recognize them efforts in international
pages, i did a page with their names, where have credits for all
people that help in translation (and any other part of brazilian
project).

And why i did this? Because the tools (in there time) isn't easy for
translators (many times, doctors, teachers, etc) without skills in IT.

Maybe the best way can be open the registration for new volunteers at
pootle, where this new users can suggest, so a commiter reviews their
contributions and help them to be commiters too.

I think that recognition is one of our "coin" here.

> I cannot find the BSD license remark on our version of the pootle server,
> we have our general ASF license. Please remember that since the server runs
> on a ASF VM work done on it automatically get the ASF license. The pootle
> server run by the pootle team uses the BSD license.

No. *IF* we to enable the "registration" (or "new account"), to give a
check box where you need to accept that all your contributions in this
pootle are licensed under Apache license, like when you subscribe in a
web service like Google or Yahoo!, where you agree with its terms.

>> I understand that this process can be adopted by us, Ipsis litteris,
>> changing the license by Apache.
>>
> Already done on our server (unless I have misunderstood something).

We haven't registration for new volunteers in our pootle, like in Lauchpad[1].
[1]https://login.launchpad.net/+new_account

>> I think that we have the same idea, Janl. And using your "way" (with
>> images) in new propose for l10n, i did a flow explaining my idea[1].
>> [1]http://people.apache.org/~filhocf/aoo/proposed_flow_pootle.png
>>
> This is pretty much how it works at the moment. I would like to go one
> step further and allow non-ICLA users to review and add translations, not
> only suggestions. With svn it is really no problem, if we want to do a
> rollback, and the user can see the effect imidiatly.
>
> Problem with suggestions are that they are not controlled in the review
> section of pootle, meaning the committer has more work.

Humm.. so need more study over this tool. Thanks by your comments.

Regards,
Claudio

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 22 February 2013 19:20, Claudio Filho <fi...@gmail.com> wrote:

> Hi
>
> 2013/2/22 janI <ja...@apache.org>:
> > At current (based on work of the update of translate-vm) we are able to
> > share strings within the asf community and anybody else accepting our
> > license.
>
> This is a good new.
>
> > The bsd license is not valid for our installation (but  it is for the
> > general version), we accept only our ICLA license (committers only).
>
> This is the point: other contributions.
>
> Today we have two levels of contribution, but and if we have
> translators that wish to use Pootle without sign a ICLA? This is the
> good point (IMHO) at launchpad. When you register your self in there
> tool, you check/agree that all your work will be licensed under BSD.
>
Translators can use pootle today without having signed a ICLA, however the
submitted translations will be saved as suggestions until approved by a
committer. This process is equivalent to volunteers submitting patches.

I cannot find the BSD license remark on our version of the pootle server,
we have our general ASF license. Please remember that since the server runs
on a ASF VM work done on it automatically get the ASF license. The pootle
server run by the pootle team uses the BSD license.

I would like to offer translators (in the future) that they can translate
directly on pootle (independent on their ICLA status), however this is a
somewhat hot community issue, since it would require a special pootle user
had access to svn.


>
> I understand that this process can be adopted by us, Ipsis litteris,
> changing the license by Apache.
>
Already done on our server (unless I have misunderstood something).


>
> I took a look fast in Pootle docs and  saw that exist condition to
> enable other permissions for users and I think that is possible to
> create profiles. IMO, is possible to enable more one profile, of
> translator (without ICLA, but agreed in registration time with donate
> his work to ASF/project).
>
yes, we use that today...committers can edit directly, and others make
suggestions.


>
> The main point is collect more volunteers with translation skill (in
> some times is the *unique* thing that can help), and giving to him an
> idea about how works the project. In a second time (and with
> interaction with his l10n team or the project at all), he can sign the
> ICLA and will be promoted to commiter, with more "powers". ;-)
>
> Agree

> > HOWEver, I hope with the new infra structure to provide a platform for
> > non-committers to use pootle in a motivating way, this depend however on
> a
> > vote in the community.
>
> I think that we have the same idea, Janl. And using your "way" (with
> images) in new propose for l10n, i did a flow explaining my idea[1].
> [1]http://people.apache.org/~filhocf/aoo/proposed_flow_pootle.png
>
> This is pretty much how it works at the moment. I would like to go one
step further and allow non-ICLA users to review and add translations, not
only suggestions. With svn it is really no problem, if we want to do a
rollback, and the user can see the effect imidiatly.

Problem with suggestions are that they are not controlled in the review
section of pootle, meaning the committer has more work.

rgds
Jan I.

> Regards,
> Claudio
>

Re: Proposal: communications/workflow for new languages

Posted by Claudio Filho <fi...@gmail.com>.
Hi

2013/2/22 janI <ja...@apache.org>:
> At current (based on work of the update of translate-vm) we are able to
> share strings within the asf community and anybody else accepting our
> license.

This is a good new.

> The bsd license is not valid for our installation (but  it is for the
> general version), we accept only our ICLA license (committers only).

This is the point: other contributions.

Today we have two levels of contribution, but and if we have
translators that wish to use Pootle without sign a ICLA? This is the
good point (IMHO) at launchpad. When you register your self in there
tool, you check/agree that all your work will be licensed under BSD.

I understand that this process can be adopted by us, Ipsis litteris,
changing the license by Apache.

I took a look fast in Pootle docs and  saw that exist condition to
enable other permissions for users and I think that is possible to
create profiles. IMO, is possible to enable more one profile, of
translator (without ICLA, but agreed in registration time with donate
his work to ASF/project).

The main point is collect more volunteers with translation skill (in
some times is the *unique* thing that can help), and giving to him an
idea about how works the project. In a second time (and with
interaction with his l10n team or the project at all), he can sign the
ICLA and will be promoted to commiter, with more "powers". ;-)

> HOWEver, I hope with the new infra structure to provide a platform for
> non-committers to use pootle in a motivating way, this depend however on a
> vote in the community.

I think that we have the same idea, Janl. And using your "way" (with
images) in new propose for l10n, i did a flow explaining my idea[1].
[1]http://people.apache.org/~filhocf/aoo/proposed_flow_pootle.png

Regards,
Claudio

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 22 February 2013 15:31, Jürgen Schmidt <jo...@gmail.com> wrote:

> On 2/22/13 3:06 PM, Claudio Filho wrote:
> > Hi
> >
> > 2013/2/22 Jürgen Schmidt <jo...@gmail.com>:
> >> On 2/22/13 1:57 AM, Rob Weir wrote:
> >> +1, a more streamlined approach is a good idea. And with the changes Jan
> >> is working on, we can improve or adapt this process to optimize it.
> >
> > Sorry my away, but i have doubts in the next step, to maintain a
> > localization, mainly in pootle.
> >
> > One point asked by me in other time was for translators without
> > "commiter flag" accessing Pottle.
> >
> > Other point was a political about contributions inside pootle, like
> > used in Launchpad translator part, where all contributions are made
> > under BSD license, giving chance of to rescue translations from other
> > projects hosted there, i.e., if I have a project there, is possible to
> > translate using strings from other projects, giving a big translation
> > database.
> >
> > Do we evolved some thing in this questions?
>
> I don't think so, at least not in detail. Please correct me if anybody
> knows more. But nothing is fixed and if it's possible to reuse existing
> strings or share strings with other projects, it make perfect sense from
> my pov. I believe we are very open here. In the end we need a working
> and intuitive process that is easy for the translators.
>
> Input, help and ideas are always welcome.
>
At current (based on work of the update of translate-vm) we are able to
share strings within the asf community and anybody else accepting our
license.

The bsd license is not valid for our installation (but  it is for the
general version), we accept only our ICLA license (committers only).

HOWEver, I hope with the new infra structure to provide a platform for
non-committers to use pootle in a motivating way, this depend however on a
vote in the community.

rgds
Jan I

>
>
> Juergen
>
d

Re: Proposal: communications/workflow for new languages

Posted by Jürgen Schmidt <jo...@gmail.com>.
On 2/22/13 3:06 PM, Claudio Filho wrote:
> Hi
> 
> 2013/2/22 Jürgen Schmidt <jo...@gmail.com>:
>> On 2/22/13 1:57 AM, Rob Weir wrote:
>> +1, a more streamlined approach is a good idea. And with the changes Jan
>> is working on, we can improve or adapt this process to optimize it.
> 
> Sorry my away, but i have doubts in the next step, to maintain a
> localization, mainly in pootle.
> 
> One point asked by me in other time was for translators without
> "commiter flag" accessing Pottle.
> 
> Other point was a political about contributions inside pootle, like
> used in Launchpad translator part, where all contributions are made
> under BSD license, giving chance of to rescue translations from other
> projects hosted there, i.e., if I have a project there, is possible to
> translate using strings from other projects, giving a big translation
> database.
> 
> Do we evolved some thing in this questions?

I don't think so, at least not in detail. Please correct me if anybody
knows more. But nothing is fixed and if it's possible to reuse existing
strings or share strings with other projects, it make perfect sense from
my pov. I believe we are very open here. In the end we need a working
and intuitive process that is easy for the translators.

Input, help and ideas are always welcome.


Juergen

Re: Proposal: communications/workflow for new languages

Posted by Claudio Filho <fi...@gmail.com>.
Hi

2013/2/22 Jürgen Schmidt <jo...@gmail.com>:
> On 2/22/13 1:57 AM, Rob Weir wrote:
> +1, a more streamlined approach is a good idea. And with the changes Jan
> is working on, we can improve or adapt this process to optimize it.

Sorry my away, but i have doubts in the next step, to maintain a
localization, mainly in pootle.

One point asked by me in other time was for translators without
"commiter flag" accessing Pottle.

Other point was a political about contributions inside pootle, like
used in Launchpad translator part, where all contributions are made
under BSD license, giving chance of to rescue translations from other
projects hosted there, i.e., if I have a project there, is possible to
translate using strings from other projects, giving a big translation
database.

Do we evolved some thing in this questions?

Regards,
Claudio

Re: Proposal: communications/workflow for new languages

Posted by Jürgen Schmidt <jo...@gmail.com>.
On 2/22/13 1:57 AM, Rob Weir wrote:
> What happens today:
> 
> 1) Every few days someone posts to the list that they want to help
> translate AOO.
> 
> 2) Sometimes it is a new language, in other cases it is one where some
> volunteers have previously expressed interest.
> 
> 3) If it is a new language, Juergen creates a PO file, uploads it to
> people.apache.org and notifies the volunteer.  If it is a language
> where there are other volunteers, then Andrea tries to connect the
> volunteers.
> 
> 4) When a translation is done the new files are attached to a BZ issue.
> 
> An interesting idea is to use Bugzilla from the very start.  Then BZ
> can help wit the routine communications, including keeping the
> volunteers coordinated.
> 
> For example:
> 
> 1) Point new volunteers to BZ from the start.  If you want to work on
> a new language then create a new BZ issue.  We can then assign the
> issue to Juergen.
> 
> 2) When the PO files are available Juergen marks the BZ issue as
> "Accepted".  The volunteer(s) is automatically notified by Bugzilla,
> so no extra email is required.
> 
> 3) When a new volunteer wants to join, we can point them to the BZ
> issue.  The files are there, as well as the names of the other
> volunteers.  Adding a comment to the BZ issue causes it to be sent to
> all volunteers working on that language.
> 
> 4) When translation is done, the issue is marked and Juergen can
> integrate the new translation.
> 
> Would this help?

+1, a more streamlined approach is a good idea. And with the changes Jan
is working on, we can improve or adapt this process to optimize it.

Juergen


> 
> -Rob
> 


Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
janI wrote:
> Yes, I can get this done (with the help of infra). I would however prefer
> we required a ICLA (not committer status) to allow editing on pootle, this
> is not a big administration, and we have a bit more hold on who edits.

I think it is still inconvenient (it requires disclosure of personal 
information and fax/scan), so I wouldn't push for it; or anyway I 
wouldn't see it as a requirement but rather as a recommendation. Let's 
really keep a low entry barrier unless we have reasons to be concerned.

> May I politely suggest that we put the alv2 licence in all PO files (this
> can be done today) then there are no doubt about licensing independent of
> toolset.

Sure. If we can add AL2 license information to the PO files we generate 
from sources, this will make it clear to everybody that they can be used 
under AL2 by both Apache OpenOffice and other products.

Regards,
   Andrea.

Re: Proposal: communications/workflow for new languages

Posted by janI <ja...@apache.org>.
On 24 February 2013 18:47, Andrea Pescetti <pe...@apache.org> wrote:

> On 22/02/2013 Rob Weir wrote:
>
>> For example:
>> 1) Point new volunteers to BZ from the start.  ...
>> 3) When a new volunteer wants to join, we can point them to the BZ
>> issue.  The files are there, as well as the names of the other
>> volunteers.  Adding a comment to the BZ issue causes it to be sent to
>> all volunteers working on that language.
>>
>
> This would be the main advantage. Be it Bugzilla or the wiki, we
> definitely need something better than the current system (which is, more or
> less: I keep a list of volunteers for each language and try to connect
> them, very often without any clue if there is progress or not; and this
> stops new volunteers from being immediately active).
>
> Problems we face, and possible solutions:
>
> A) Technical issues: not all volunteers are able to deal with a .tar.bz2
> archive of 240 PO files. Solution: send volunteers to Pootle (with PO files
> available for download for those who prefer it)
>
> B) Bootstrap issues: volunteers still need to wait that we make PO files
> available; in most cases this only takes a few days, but Catalan, for
> example, has been pending for weeks. Solution: have all PO files
> immediately ready (being done in Jan's new l10n process).
>
> C) Coordinating issues: volunteers need a collaboration space; currently
> they rely on private mail, but this makes it impossible to follow progress
> and to properly add new volunteers. Solutions: Bugzilla is an option,
> Mwiki's "watch this page" is another one, even a forum topic will do, and
> at the extreme a dedicated mailing list, but in all cases we need that
> volunteers register on a new system; if we can create an account for them,
> this would become even more user-friendly. Bugzilla has a file size
> limitation that currently prevents it from being really useful, since PO
> files are too big to be attached there. It is true that our internal
> workflow uses Bugzilla for PO files, but the reality is that in most cases,
> as you can see, PO files were sent by e-mail to either me or Juergen and we
> added them to Bugzilla (as links). Anyway, it is OK for me to start
> directing volunteers from March 1st to a new tool, the one we agree upon.
> No clear preference between Bugzilla and Mwiki for me.
>
> D) Licensing issues: if we rely more on Pootle, we must find a way to have
> all contributions clearly licensed (no ICLA). Solution: my preference would
> be: make Apache License 2 a mandatory registration requirement; anonymous
> users cannot do anything (not even suggestions); registered users can do
> both suggestions and approvals (let's try and be open); a committer takes
> care of review (when applicable) and committing to sources. If I understand
> correctly, Jan can make something like this possible, and Jan if you need
> any changes to the existing policy/configuration just ask.
>

Yes, I can get this done (with the help of infra). I would however prefer
we required a ICLA (not committer status) to allow editing on pootle, this
is not a big administration, and we have a bit more hold on who edits.

May I politely suggest that we put the alv2 licence in all PO files (this
can be done today) then there are no doubt about licensing independent of
toolset.

jan I.

>
> In the short term, it's enough to get C done.
>
> Regards,
>   Andrea.
>

Re: Proposal: communications/workflow for new languages

Posted by Andrea Pescetti <pe...@apache.org>.
On 22/02/2013 Rob Weir wrote:
> For example:
> 1) Point new volunteers to BZ from the start.  ...
> 3) When a new volunteer wants to join, we can point them to the BZ
> issue.  The files are there, as well as the names of the other
> volunteers.  Adding a comment to the BZ issue causes it to be sent to
> all volunteers working on that language.

This would be the main advantage. Be it Bugzilla or the wiki, we 
definitely need something better than the current system (which is, more 
or less: I keep a list of volunteers for each language and try to 
connect them, very often without any clue if there is progress or not; 
and this stops new volunteers from being immediately active).

Problems we face, and possible solutions:

A) Technical issues: not all volunteers are able to deal with a .tar.bz2 
archive of 240 PO files. Solution: send volunteers to Pootle (with PO 
files available for download for those who prefer it)

B) Bootstrap issues: volunteers still need to wait that we make PO files 
available; in most cases this only takes a few days, but Catalan, for 
example, has been pending for weeks. Solution: have all PO files 
immediately ready (being done in Jan's new l10n process).

C) Coordinating issues: volunteers need a collaboration space; currently 
they rely on private mail, but this makes it impossible to follow 
progress and to properly add new volunteers. Solutions: Bugzilla is an 
option, Mwiki's "watch this page" is another one, even a forum topic 
will do, and at the extreme a dedicated mailing list, but in all cases 
we need that volunteers register on a new system; if we can create an 
account for them, this would become even more user-friendly. Bugzilla 
has a file size limitation that currently prevents it from being really 
useful, since PO files are too big to be attached there. It is true that 
our internal workflow uses Bugzilla for PO files, but the reality is 
that in most cases, as you can see, PO files were sent by e-mail to 
either me or Juergen and we added them to Bugzilla (as links). Anyway, 
it is OK for me to start directing volunteers from March 1st to a new 
tool, the one we agree upon. No clear preference between Bugzilla and 
Mwiki for me.

D) Licensing issues: if we rely more on Pootle, we must find a way to 
have all contributions clearly licensed (no ICLA). Solution: my 
preference would be: make Apache License 2 a mandatory registration 
requirement; anonymous users cannot do anything (not even suggestions); 
registered users can do both suggestions and approvals (let's try and be 
open); a committer takes care of review (when applicable) and committing 
to sources. If I understand correctly, Jan can make something like this 
possible, and Jan if you need any changes to the existing 
policy/configuration just ask.

In the short term, it's enough to get C done.

Regards,
   Andrea.