On 11/04/2015 09:30 AM, Kay Schenk wrote:
> 
> 
> On 11/04/2015 03:59 AM, Andrea Pescetti wrote:
>> Kay Schenk wrote:
>>> ​Ok, these are comments that already existed but I will change the
>>> spelling...
>>
>> Yes, all fixes are not due to some mistakes in your work, but to
>> previous stuff.
>>
>>>> but the corresponding fixes still need to be done on the 4.1.0 ->
>>>> 4.1.2
>>>> feed (and probably to the other two too) as currently attached to
>>>> the issue.
>>> ​I'm not quite understanding this last comment. Please see the
>>> update feed
>>> already committed you refer to.​
>>
>> The committed one is 4.1.1 -> 4.1.2 and it is correct. The broken
>> one is 4.1.0 -> 4.1.2 and you fixed it with the spelling correction
>> but not with the localized sites update. The latest one
>> https://bz.apache.org/ooo/attachment.cgi?id=85105 still misses the
>> Lithuanian site (it doesn't contain "/lt").
> 
> oops! Apparently my eyes are failing! :(
> 
>>
>>> ​The native lang urls are not directly referenced in the update feed.
>>
>> Yes they are. If I am using version 4.1.1 in Italian, the pop-up
>> will send me to
>> http://www.openoffice.org/it/download/
>> and not to
>> http://www.openoffice.org/download/
>> since line 1342 (and similar) of
>> http://svn.apache.org/viewvc/openoffice/updates-site/trunk/aoo411/check.Update?view=markup
>> are configured that way. So the two "missing" languages were not
>> missing, but they were sending people to a wrong (well, a working
>> one but not the best one) URL.
>>
>>> ​ah! I actually found a generation script for this at:
>>> http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/
>>
>> Good find! You really saved us a lot of time by investigating,
>> thanks. This is perfect to the purpose, and even the list I had in
>> mind is already done there:
>>
>> http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/LanguageCodeMap.txt?revision=1619063&view=markup
>>
> 
> I had a vague recollection of Oliver doing this...so I looked around.
> 
>>
>> So a fix on lines 36 and 40 of that file will incorporate the 3
>> fixes (Lithuanian spelling, Lithuanian URL, Portuguese URL) and it
>> will be enough to:
>> 1) Regenerate all 4.x.y -> 4.1.2 feeds with it
>> 2) Compare the generated feed for 4.1.1 -> 4.1.2 to the one you
>> committed, so that we can check it is consistent.
> 
> Good idea! I can continue to help, but maybe not until tomorrow.

Ok, more update feeds to see attached to:
https://bz.apache.org/ooo/show_bug.cgi?id=126612

using the script which is AWESOME! Please not the script uses
today's date, Nov.5, and not our release date of Oct. 28. This is
just a comment, so if we want to change all these to Oct.28, we can
do this.

I fixed up the localized download areas which is an input file to
the script, so hopefully we're good on that now.

So, once we get a FINAL (hopefully!) review, I will copy these over
to where they need to go an commit. The 4.1.1 -> 4.1.2 we have
already committed is OK.


> 
>>
>>> How we lost the two languages initially I don't know.
>>
>> We never lost them. What happened is that in 2014 we didn't have a
>> well-maintained Lithuanian and Portuguese site. We now do, so the
>> best target URL for updates from Lithuanian and Portuguese has now
>> changed. And this is why we have a file (link above) for it.
> 
> OK. I thought it might be something like this. Maybe we need to
> revisit our "policy" on continuing releases for languages even if
> the 100% translation is not reached.
> 
>>
>> Regards,
>>   Andrea.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
> 

-- 
--------------------------------------------
MzK

“The journey of a thousand miles begins
 with a single step.”
                          --Lao Tzu



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to