Re: Clarification on Translation policy
FR web forum wrote: Another issue: https://bz.apache.org/ooo/show_bug.cgi?id=126222 This is quite different, as I commented there yesterday. That request is not for a translation, but for a new language to support (in Format - Character for example). This does not require any interaction with Pootle and will not result in a new OpenOffice translation being available: it will result in a new document language being available. So this one has to be handled separately from translation issues, according to the feedback I've already solicited fro the original poster. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
>In my original estimate, I had included some languages that don't seem >to have current translation volunteers. Another issue: https://bz.apache.org/ooo/show_bug.cgi?id=126222 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
On 04/18/2015 03:24 PM, Andrea Pescetti wrote: > Kay Schenk wrote: >>> On 04/18/2015 09:01 AM, jan i wrote: >>> I thought 4.1.2 would be used to release non-released languages >> My assumption was this just meant "next release" and not necessarily >> 4.2. But, I am not a Pootle expert. > > Well, strings in Pootle correspond to some relatively random (but close > to the current situation) snapshot of trunk. 4.1.2 won't be based on > trunk, but on 4.1.1 (i.e., > http://svn.apache.org/viewvc/openoffice/branches/AOO410/ the AOO410 > branch). For sure they are not the same as 4.1.1 as there are about 500 > different words. If they can be reused, I'm definitely interested in > knowing more since all I have so far is some comments from Juergen > describing the process as very manual and tedious (and this is when > Pootle and code are aligned; with the two set to two different branches > I can only expect some extra complexity). > >>> let us at least release languages that are ready. >> we might actually have up to 8 new languages/dialects that would be >> ready for 4.1.2 > > There might be some ongoing misunderstanding here. Can you make some > explicit examples? I mean, languages that are complete or almost > complete in Pootle > https://translate.apache.org/projects/aoo40/ > but that we did not release in 4.1.1 > http://www.openoffice.org/download/other.html OK, yes. And, given what I see as current activity on https://translate.apache.org/projects/aoo40/ (is the right place?) 8 new was a bit off the mark. In my opinion, it seems Icelandic, Indonesian, Croatian, and Ukrainian are getting pretty close, at least for UI strings. By the time we release 4.1.2, these may be ready. In my original estimate, I had included some languages that don't seem to have current translation volunteers. > > If we do have some of them, then it is one more reason to investigate if > we can rebuild translations for 4.1.2 based on what we currently have in > Pootle. This is something that must be done for 4.2 anyway. > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- - MzK “What is the point of being alive if you don't at least try to do something remarkable?” -- John Green, "An Abundance of Katherines" - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
Kay Schenk wrote: On 04/18/2015 09:01 AM, jan i wrote: I thought 4.1.2 would be used to release non-released languages My assumption was this just meant "next release" and not necessarily 4.2. But, I am not a Pootle expert. Well, strings in Pootle correspond to some relatively random (but close to the current situation) snapshot of trunk. 4.1.2 won't be based on trunk, but on 4.1.1 (i.e., http://svn.apache.org/viewvc/openoffice/branches/AOO410/ the AOO410 branch). For sure they are not the same as 4.1.1 as there are about 500 different words. If they can be reused, I'm definitely interested in knowing more since all I have so far is some comments from Juergen describing the process as very manual and tedious (and this is when Pootle and code are aligned; with the two set to two different branches I can only expect some extra complexity). let us at least release languages that are ready. we might actually have up to 8 new languages/dialects that would be ready for 4.1.2 There might be some ongoing misunderstanding here. Can you make some explicit examples? I mean, languages that are complete or almost complete in Pootle https://translate.apache.org/projects/aoo40/ but that we did not release in 4.1.1 http://www.openoffice.org/download/other.html If we do have some of them, then it is one more reason to investigate if we can rebuild translations for 4.1.2 based on what we currently have in Pootle. This is something that must be done for 4.2 anyway. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
On 04/18/2015 09:01 AM, jan i wrote: > Hi > > > On 17 April 2015 at 08:38, FR web forum wrote: > >>> Here is the link to the issue in Bugzilla: >>> https://bz.apache.org/ooo/show_bug.cgi?id=126243 >> >> Other report for Thai translation: >> https://bz.apache.org/ooo/show_bug.cgi?id=125934 >> > > Looking at the comments in the above issues scares me a bit. > > Two things: > - I thought 4.1.2 would be used to release non-released languages that was > ready, why wait for 4.2 > - We aligned pootle with trunk preparing for 4.2, but honestly have anybody > looked at whether or not these > files are directly useable (or with minor corrections) for 4.1.2. My assumption was this just meant "next release" and not necessarily 4.2. But, I am not a Pootle expert. > > We do not have a lot of development patches for 4.1.2, so let us at least > release languages that are ready. > > Of course this is only my opinion. > rgds > jan i. I am in agreement with your opinion. I started looking at how far we were with potential translations a week or so ago, and my opinion is that we might actually have up to 8 new languages/dialects that would be ready for 4.1.2. This is a great way to provide new services to users, as well as recognize the work of our translator community. This being said, we probably should establish a threshold for the help files. Maybe at least 70% or something. -- - MzK “What is the point of being alive if you don't at least try to do something remarkable?” -- John Green, "An Abundance of Katherines" - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
jan i wrote:
On 17 April 2015 at 08:38, FR web forum wrote:
Here is the link to the issue in Bugzilla:
https://bz.apache.org/ooo/show_bug.cgi?id=126243
Other report for Thai translation:
https://bz.apache.org/ooo/show_bug.cgi?id=125934
Looking at the comments in the above issues scares me a bit.
I think you are scared because the issues are not very clear. You may
miss an important information: as of 4.1.1, both sr and th are released.
Two things:
- I thought 4.1.2 would be used to release non-released languages that was
ready, why wait for 4.2
Sure, that would be good (see below about feasibility). But at the
moment I don't think we have additional languages ready since 4.1.1. The
two issues merely report that the translators already translated the
~500 new words that came with the Pootle update AFTER 4.1.1.
- We aligned pootle with trunk preparing for 4.2, but honestly have anybody
looked at whether or not these
files are directly useable (or with minor corrections) for 4.1.2.
This would indeed be very interesting to know. I don't know where to
start from, and honestly it seems that updating Pootle with the trunk
("on the way to 4.2.0") strings introduced unnecessary complexity. But
if we have a safe way to take what is in Pootle and use it for 4.1.2 I'm
quite interested in pointers. So far we would have no new languages, but
we would be able to commit some translation fixes at least.
We do not have a lot of development patches for 4.1.2, so let us at least
release languages that are ready.
The two Bugzilla issues listed above won't change anything in terms of
released languages. They refer to languages that used to be at 100% for
4.1.1, were released for 4.1.1, got back to 98-99% after the string
update in Pootle and are now back to 100%.
Still, being able to release translation fixes for existing languages
would already help. This has been quite a black magic in itself so far,
and it is now made more complex because Pootle has the "wrong" (i.e.,
"4.2.0") strings at the moment.
Regards,
Andrea.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
Hi On 17 April 2015 at 08:38, FR web forum wrote: > > Here is the link to the issue in Bugzilla: > > https://bz.apache.org/ooo/show_bug.cgi?id=126243 > > Other report for Thai translation: > https://bz.apache.org/ooo/show_bug.cgi?id=125934 > Looking at the comments in the above issues scares me a bit. Two things: - I thought 4.1.2 would be used to release non-released languages that was ready, why wait for 4.2 - We aligned pootle with trunk preparing for 4.2, but honestly have anybody looked at whether or not these files are directly useable (or with minor corrections) for 4.1.2. We do not have a lot of development patches for 4.1.2, so let us at least release languages that are ready. Of course this is only my opinion. rgds jan i. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Clarification on Translation policy
> Here is the link to the issue in Bugzilla: > https://bz.apache.org/ooo/show_bug.cgi?id=126243 Other report for Thai translation: https://bz.apache.org/ooo/show_bug.cgi?id=125934 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
Andrea Pescetti wrote: > On 15/04/2015 jan i wrote: >> On Wednesday, April 15, 2015, Keith N. McKenna wrote: >>> A recent translation task in Bugzilla to ready a language for >>> translation was set as resolved not an issue because the help was not >>> 100% translated. As memory serves me correctly only the UI needed to be >>> 100% translated to qualify for a release. The help did not need to be. >>> Is this still correct? >> yes this is still the policy. > > I confirm this is the policy, but I don't think we have translations > that are 100% UI complete (for 4.1.x) and not released. > > Can you provide a pointer to the issue please? (Note that Pootle is now > configured for the 4.2.x releases, not 4.1.x). > > Regards, > Andrea. Andrea; Here is the link to the issue in Bugzilla: https://bz.apache.org/ooo/show_bug.cgi?id=126243 Regards Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
On 15/04/2015 jan i wrote: On Wednesday, April 15, 2015, Keith N. McKenna wrote: A recent translation task in Bugzilla to ready a language for translation was set as resolved not an issue because the help was not 100% translated. As memory serves me correctly only the UI needed to be 100% translated to qualify for a release. The help did not need to be. Is this still correct? yes this is still the policy. I confirm this is the policy, but I don't think we have translations that are 100% UI complete (for 4.1.x) and not released. Can you provide a pointer to the issue please? (Note that Pootle is now configured for the 4.2.x releases, not 4.1.x). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Clarification on Translation policy
On Wednesday, April 15, 2015, Keith N. McKenna wrote: > A recent translation task in Bugzilla to ready a language for > translation was set as resolved not an issue because the help was not > 100% translated. As memory serves me correctly only the UI needed to be > 100% translated to qualify for a release. The help did not need to be. > Is this still correct? yes this is still the policy. rgds jan i > > Regards > Keith > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > -- Sent from My iPad, sorry for any misspellings.
Clarification on Translation policy
A recent translation task in Bugzilla to ready a language for translation was set as resolved not an issue because the help was not 100% translated. As memory serves me correctly only the UI needed to be 100% translated to qualify for a release. The help did not need to be. Is this still correct? Regards Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
