On 30 August 2013 15:28, Ariel Constenla-Haile <arie...@apache.org> wrote: > On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote: >> 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? > > yes, var NL_LANGUAGE = ""; will default to en-US. > > The download page, with all that javascript in it, is rather hard to > translate. Isn't it possible to use a cgi script (server-side vs. > client-side js)?
If the ASF servers can support server-side processing then it should be possible to use that for the OS auto-detection as well. However, if client-side processing is required, maybe the NL text strings should be extracted into a JSON object, making the javascript generic. That would make it much easier to maintain - only a single copy. Failing that, it should be fairly simple (?) to extract the NL strings into JS variables and group them at the start of the page. > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
