----- Original Message ---- > From: Dave Fisher <[email protected]> > To: [email protected] > Sent: Mon, June 27, 2011 6:55:12 PM > Subject: Re: Top level question on website migration > > > On Jun 27, 2011, at 3:17 PM, Joe Schaefer wrote: > > > None of what's done at Kenai or Collabnet has any bearing > > on how the Apache CMS works. Did you know it's compatible > > with httpd's content negotiation features, so you can serve > > up custom pages for each language? > > What structure is needed in a CMS generated website to take advantage of >multiple languages? > > Thanks, > Dave
To take advantage of content negotiation on say the home page, here's what you'd do. 1) Ensure all links to the homepage reference the page as /openofficeorg/ or /openofficeorg/index (no .html extension). 2) create content/openofficeorg/index.$lang.mdtext , where $lang = en, es, etc. 3) optionally create custom per-lang templates and use path.pm to add a regexp entry that ties each template name to a particular $lang.mdtext extension. HTH
