On Fri, Jun 1, 2012 at 4:15 PM, Marcus (OOo) <marcus.m...@wtnet.de> wrote:
> Am 06/01/2012 05:45 AM, schrieb Ariel Constenla-Haile:
>
>> Hi Rob, *
>>
>> On Thu, May 31, 2012 at 09:05:49PM -0400, Rob Weir wrote:
>>>
>>> We're planning on enabling the OOo 3.3.0 update server soon. This
>>> will trigger the update prompts for OOo 3.3.0 users. We would only
>>> offer updates for users who have an appropriate translation/platform
>>> available for them in AOO 3.4.
>>>
>>>
>>> We could just have the update direct the users to
>>> http://www.openoffice.org/download/index.html. our English language
>>> download page.
>>>
>>> I proposed that we try to do a little better and direct users to the
>>> NL home page for each language. My assumption was that we had updated
>>> each NL page for which we had translations released with AOO 3.4. But
>>> just to be sure that this was true, I reviewed each NL home page.
>>>
>>> I found out that we're not ready yet. Five of the 15 NL home pages
>>> either point to older OOo versions or have other problems. Details of
>>> what I found follow.
>>>
>>> To some extent, I can fix some of these issues without even
>>> understanding the language. But the risk of error is increased. So
>>> it would be far preferable to have some volunteers step forward to
>>> help here.
>>
>>
>>
>> The thread http://markmail.org/message/e7evabaog3em4d5t ended with no
>> objections, so I'd propose to apply lazy consensus and follow in the
>> download page the principle of common layout and content for NL sites.
>
>
> That's also my impression.
>
>
>> With Marcus work, the en-US download page can be fully translated, with
>> support to offer localized builds:
>>
>> http://www.openoffice.org/download/index.html
>> http://www.openoffice.org/es/descargar/index.html
>>
>> Marcus did a great job, and the download page looks really nice, there
>> is no need to waste resource once again in each NL site when it can be
>> simply translated in a plain text Markdown file, no need for the
>> translator to deal with HTML, JavaScript, etc.
>>
>> So I'd suggest we take Dave's offer
>> http://markmail.org/message/kbazlvdg73sebyqp to turn the page into
>> a template (I just hole that offer is still valid ;) ).
>
>
> In general +1.
>
> However, with the tough timeframe from Oliver (2012-06-05 until 2012-06-08)
> to enable the "OOo 3.3 --> AOO 3.4 ping" I'm not sure if this is doable. We
> still need some people to do the translation work for the languages.
>
> Maybe it's better to start to update the remaining webpages with only the
> most needed improvements and then to start the migration into mdtext files
> within the next weeks?
>
> Please note:
> I don't want to be recognized to be too negative. I just want to point out
> the risk. :-)
>
I had similar thoughts. I can't read Hungarian, but I can still find
and replace "OOo 3.3." with "AOO 3.4" and update a hyperlink.
Then, as we get shiny new NL download pages, we can easily change the
XML to point to them.
-Rob
> Marcus
>
>
>
>
>> @Dave: If I understood correctly how templates work, for example
>> templates/brand.html
>>
>> <img id="ooo-logo" alt="{{ headers.name }}" src="/images/{{ headers.logo
>> }}"/>
>>
>> I could start with the Spanish translation I made, replacing the
>> localized text with variables of the type {{ header.something }} so that
>> you get an idea of what need to get localized. Then this variables go
>> to the mdtext file with the text to be translated. Am I right?
>
>
