incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <robw...@apache.org>
Subject Re: [WWW]: shared ideas and looking for feedback
Date Fri, 19 Oct 2012 11:51:35 GMT
On Fri, Oct 19, 2012 at 4:22 AM, J├╝rgen Schmidt <jogischmidt@gmail.com> wrote:
> Hi,
>
> yesterday I had problems to find a good place for the German translation
> of the graduation press release. And I thought that it is probably a
> good idea to cleanup the whole page with a clear and well defined
> structure. I know that there is work ongoing and that we move already in
> this direction. But nevertheless I would like to share the things I have
> in mind to check if it is aligned with the already ongoing work or if it
> makes sense at all.
>
> 1. a clear structure for the English content as well as the translated
> pages.
>
> .../index.hmtl
> .../de/index.html
> .../it/index.html
> ...
> .../press/msg_20121019.html
> .../de/press/msg_20121019.html
> .../it/press/msg_20121019.html
> ...
>
> Means we have for all pages a translated version in the related sub
> directory. Same path and same name only the content is translated. This
> makes it easy to find the related translation for any files.
>
> We can also use Pootle to do the translation of the web content in the
> future.
>
> 2. we have special news areas where local communities can spread further
> news relevant to their local activities, e.g. local conferences, events.
> But in general we have the same content on all pages. Other local
> community relevant content should be moved in the wiki. The main idea is
> to have a smaller but cleaner and well structured and organized user
> portal www.openoffice.org. Community internal things should be move on
> openoffice.apache.org or the wiki.
>
> I know it is not really new and it is probably more to remind myself but
> I am interested to hear others opinion.
>

This has certainly been discussed:  enforce the same template for NL
pages, same look and feel, same base content.  But then have a portion
of the page be reserved for locale-specific concerns.  For example,
the Arabic page has a link to Bidi specific issue.  Or you might have
a locale event or news story.

We almost do this today for some languages, but this was based on a
one-time copy of the English website.  Once the copy is made the sites
diverge over time.  Truly using a single template, with strings
resourced in Pootle, would be ideal.

But do you see us integrating with Pootle in a way that allows us to
update a webpage without requiring manual steps to extract Pootle
resources and bring them into SVN and converted to HTML?  This would
really need to be automated to work for us.

-Rob
> Regards
>
> Juergen
>
>

Mime
View raw message