You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2012/06/01 03:05:49 UTC
Audit of NL home pages
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.
Thanks!
-Rob
Arabic http://www.openoffice.org/ar/index.html
The Arabic page needs some urgent help. The downloads are pointing to
hard coded mirrors, to 3.3.0 RC1 downloads, and the links are dead.
------
Chinese (simplified) http://www.openoffice.org/zh-cn/
OK.
------
Chinese (traditional) http://www.openoffice.org/zh-tw/
OK
------
Czech http://www.openoffice.org/cs/
The Czech page needs some serious help. It immediately points the
user to some off-site webpage. It also claims the project is
sponsored by Novell and Sun, and that the latest version is OOo 2.2.
------
Dutch http://www.openoffice.org/nl/
Could use some improvements. It using the OpenOffice.org name and not
using the new logo. But it does link to AOO 3.4.
------
English (US) http://www.openoffice.org/download
OK
------
French http://www.openoffice.org/fr/
OK
------
Galician http://www.openoffice.org/gl/
Needs an update. Still points to OOo 3.3
------
German http://www.openoffice.org/de/
OK
------
Hungarian http://www.openoffice.org/hu/
Needs to special attention. Official downloads are in small print,
but then has more prominent links to off-site
OpenOffice.org_3.2.1_FSF.hu.exe
------
Italian http://www.openoffice.org/it/
OK
------
Japanese http://www.openoffice.org/ja/
Needs to be updated. Links are still to OOo 3.3.
------
Portuguese (Brazilian) http://www.openoffice.org/pt-br/
OK
------
Russian http://www.openoffice.org/ru/
OK
------
Spanish http://www.openoffice.org/es/
OK
------
Re: Audit of NL home pages
Posted by Rob Weir <ro...@apache.org>.
On Fri, Jun 1, 2012 at 4:15 PM, Marcus (OOo) <ma...@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?
>
>
Re: Audit of NL home pages
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
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. :-)
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?
Re: Audit of NL home pages
Posted by Ariel Constenla-Haile <ar...@apache.org>.
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.
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 ;) ).
@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?
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: Audit of NL home pages
Posted by Ariel Constenla-Haile <ar...@apache.org>.
On Fri, Jun 01, 2012 at 10:54:59AM +0200, Reizinger Zoltán wrote:
> I tried to solve th Hungarian landing page mess, but it is out my
> html knowledge.
> I decided to not touch it, I can only destroy it.
> The translation I will do if I get some direction.
That's why we need to switch to MarkDown, a plain text document format;
the MarkDown syntax is rather simple, and in case of translation, the
translation only has to translate, not create content/deal (== with
MarkDown syntax).
In a prefect situation, the mdtext files would be converted to PO files.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: Audit of NL home pages
Posted by Reizinger Zoltán <zr...@hdsnet.hu>.
2012.06.01. 3:05 keltezéssel, Rob Weir írta:
> 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.
I tried to solve th Hungarian landing page mess, but it is out my html
knowledge.
I decided to not touch it, I can only destroy it.
The translation I will do if I get some direction.
Zoltan
>
> Thanks!
>
> -Rob
>
>
>
> Arabic http://www.openoffice.org/ar/index.html
>
> The Arabic page needs some urgent help. The downloads are pointing to
> hard coded mirrors, to 3.3.0 RC1 downloads, and the links are dead.
>
> ------
>
> Chinese (simplified) http://www.openoffice.org/zh-cn/
>
> OK.
>
> ------
>
> Chinese (traditional) http://www.openoffice.org/zh-tw/
>
> OK
>
> ------
>
> Czech http://www.openoffice.org/cs/
>
> The Czech page needs some serious help. It immediately points the
> user to some off-site webpage. It also claims the project is
> sponsored by Novell and Sun, and that the latest version is OOo 2.2.
>
> ------
>
> Dutch http://www.openoffice.org/nl/
>
> Could use some improvements. It using the OpenOffice.org name and not
> using the new logo. But it does link to AOO 3.4.
>
> ------
>
> English (US) http://www.openoffice.org/download
>
> OK
>
> ------
>
> French http://www.openoffice.org/fr/
>
> OK
>
> ------
>
> Galician http://www.openoffice.org/gl/
>
> Needs an update. Still points to OOo 3.3
>
> ------
>
> German http://www.openoffice.org/de/
>
> OK
>
> ------
>
> Hungarian http://www.openoffice.org/hu/
>
> Needs to special attention. Official downloads are in small print,
> but then has more prominent links to off-site
> OpenOffice.org_3.2.1_FSF.hu.exe
>
> ------
>
> Italian http://www.openoffice.org/it/
>
> OK
>
> ------
>
> Japanese http://www.openoffice.org/ja/
>
> Needs to be updated. Links are still to OOo 3.3.
>
> ------
>
> Portuguese (Brazilian) http://www.openoffice.org/pt-br/
>
> OK
>
> ------
>
> Russian http://www.openoffice.org/ru/
>
> OK
>
> ------
>
> Spanish http://www.openoffice.org/es/
>
> OK
>
> ------
>