Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi again,

On Sun, Oct 31, 2010 at 3:40 PM, Christian Lohmaier
<lohmaier+ooofuture@googlemail.com> wrote:
On Sun, Oct 31, 2010 at 3:25 PM, Florian Effenberger
<floeff@documentfoundation.org> wrote:

Can someone enlighten me
on how the multi-domain setup works? Can we have de.libo with German
content, www.libo with English content and fr.libo with French content?

Sure, that's no problem -

..and you can have www.libo with english content as main language, but
still have translated pages
http://pumbaa.ooodev.org:7780/ for example is main-language english,
but has translations for some pages - those are available via links in
the page, and as alternatives in the html-code for the browser to
pick:
<link rel="alternate" type="text/html" title="Home" hreflang="fr-FR"
href="/home-fr/" />
<link rel="alternate" type="text/html" title="Home" hreflang="de-DE"
href="/home-de-DE/" />

(that (or something similar) was what I meant with the requiremet that
it must offer translation support)

How do I need to configure Apache? At the moment, all these are virtual
sites. Any special configuration required?

(I sent a mini-howto via PM)

ciao
Christian

-- 
E-mail to website+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.