openoffice-l10n mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: National web sites
Date Sat, 02 Feb 2013 01:43:43 GMT
On Fri, Feb 1, 2013 at 6:54 AM, Jan Høydahl <> wrote:
> Hi,
> I have not been able to follow-up on this.
> The Norwegian site is lacking sadly behind, not even promoting the newly released 3.4.1
> Any updates on best-practice for keeping translations in sync, other than what you described

There are a few approaches:

1) Some do a complete translation of the homepage,
as well as the core pages linked from that page.   For example, see
the Spanish homepage:

2) Some maintain a full website, but following a different design,
e.g., French: or German:

3) Some keep a very basic website, translating the home page only and
then linking to the English pages for the the deeper pages, e.g.
Brazilian Portuguese:

There may be other approaches, but those are the ones that I see in common use.

Personally, I think a nice approach is to start with approach 3), and
then to add to it over time to get something more like 1).

If you or anyone is interested in this, let me know and I can put the
right files in place to translate.



> Any of the other Norwegian translators want to give it a try?
> --
> Jan Høydahl, search solution architect
> Cominvent AS -
> Solr Training -
> 20. okt. 2012 kl. 15:36 skrev Rob Weir <>:
>> On Sat, Oct 20, 2012 at 7:09 AM, Jan Høydahl <> wrote:
>>> Hi,
>>> The Norwegian national website @ is in pretty bad
shape. Most links and content in the left menu is outdated and/or wrong. I'd like to start
by moving the old homepage to /no/old and start a pure translation of the official home-page
into Norwegian, much like they have done for /es/. Then we can start filling in relevant national
content step by step.
>>> I'm aware of the Apache CMS system, is there some kind of guide for how to manage
a translation, both initially and keeping it up to date? Or is it all manual?
>> I've made a copy of the English content and put it into a new
>> nl-template directory here:
>> We can use this as a basis for new translations.
>> If you are familiar with SVN you can check it out as:
>> Then for your working copy, I'd recommend doing an svn copy to a
>> different name, like "no-new".  When you are done with the translation
>> then you can send a patch file which we can apply.
>> Or, if you prefer I can send you a ZIP file of that directory (< 2MB)
>> and you can send me a ZIP of the translation and I can take care of
>> checking it in.
>> Of course, doing this kind of non-linked copies will require ongoing
>> effort to avoid divergence.  So we should also continue thinking of
>> how we can improve this process.
>> Regards,
>> -Rob
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS -
>>> Solr Training -

View raw message