openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (OOo)" <marcus.m...@wtnet.de>
Subject Re: template troubles in "xx" pseudo NL website
Date Fri, 30 Aug 2013 18:04:00 GMT
Am 08/30/2013 02:26 PM, schrieb Rob Weir:
> On Thu, Aug 29, 2013 at 1:08 PM, Ariel Constenla-Haile
> <arielch@apache.org>  wrote:
>> On Thu, Aug 29, 2013 at 09:49:33AM -0400, Rob Weir wrote:
>>> As I mentioned earlier I'm trying to make a self-contained English
>>> language website that can copied and translated to make new (or
>>> refreshed) NL websites.  This includes the 25 or so core pages that
>>> should be translated for every language.
>>>
>>> You can see the site here in:
>>>
>>> https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/
>>>
>>> or a live copy here:
>>>
>>> http://www.openoffice.org/xx/
>>>
>>> As you can see, it is not picking up the topnav at all.  Ditto for the
>>> side navigation on pages like:
>>>
>>> http://www.openoffice.org/xx/why/
>>>
>>> Any idea what I'm missing?  I've added a ssi.mdtext file into the
>>> templates directory, e.g.,:
>>>
>>> https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/ssi.mdtext
>>
>> I applied the general changes to make the /xx/ site work. It had some
>> issues, among those mixed line endings. There are still some things to fix
>> (specially with links). In general, you should look at the /es/ site to
>> see how it should be done; there I tried to avoid relative (of the kind
>> ../) and fixed (contenting http://www.openoffice.org/...) links, and use
>> the path to the site, for example:
>>
>> <script type="text/javascript" src="/download/download.js"></script>
>> <script type="text/javascript" src="/scripts/entourage.js"></script>
>>
>> @import url(/support/print.css);
>>
>> this is less error-prone.
>>
>
> Thanks.  I'll take a deeper look.
>
> But one question:  what is the strategy on locale detection on the
> download page for NL pages?  It looks like you are hardcoding it to
> "es", but preserving the OS detection code?
>
> I see:
>
> var NL_LANGUAGE = "es";
>
> Is that all that is needed?  We can otherwise just reuse the same scripts?

Please see also the comment one line above ;-) :

// Set a specific language ISO code to force to assemble a certain 
localized build as download URL

This was a request form the Spanish NL team some months ago. They wanted 
to have the same download webpage as we have for the main one. But only 
with offering "es" builds. So, I've implemented a way to override the 
language recognition:

- Put "xx" into the variable, then only "xx" builds will be offered.
- Leave the variable empty, then it will be offered what the DL 
scripting is recognizing as browser language,

HTH

Marcus


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


Mime
View raw message