Return-Path: <niedermann@isd.uni-stuttgart.de>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 90910 invoked from network); 17 May 2000 14:48:55 -0000
Received: from maulaf.isd.uni-stuttgart.de (129.69.110.30)
  by locus.apache.org with SMTP; 17 May 2000 14:48:55 -0000
Received: from autograf.isd.uni-stuttgart.de
 (IDENT:root@autograf.isd.uni-stuttgart.de [129.69.110.31])
	by maulaf.isd.uni-stuttgart.de (8.9.3/8.9.3) with ESMTP id QAA08260;
	Wed, 17 May 2000 16:48:49 +0200
Received: (from niedermann@localhost)
	by autograf.isd.uni-stuttgart.de (8.9.3/8.9.3) id QAA06382;
	Wed, 17 May 2000 16:48:49 +0200
X-Authentication-Warning: autograf.isd.uni-stuttgart.de: niedermann set sender
 to niedermann@isd.uni-stuttgart.de using -f
To: cocoon-users@xml.apache.org
Cc: joshmccormack@travelersdiary.com
Subject: Re: Multiple (human) language support
References: <200005171412.QAA63157@makeitso.isd.uni-stuttgart.de>
From: Hans Ulrich Niedermann <niedermann@isd.uni-stuttgart.de>
In-Reply-To: "Josh McCormack"'s message of "Wed, 17 May 2000 07:12:04 -0700"
Date: 17 May 2000 16:48:49 +0200
Message-ID: <nxcya59dyge.fsf@autograf.isd.uni-stuttgart.de>
Lines: 35
User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Arches)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

"Josh McCormack" <joshmccormack@travelersdiary.com> writes:

> I can picture making Cocoon work with multiple human languages being
> fairly easy if the content is stored in a database. You could even
> have screens set up for translators then, too. And by having the
> content in a databse you could mainatin the information architecture
> and design. I'll add a row to the category table of my database design
> (http://www.travelersdiary.com/Holometabolous/database_design.sql) for
> this and share if I get any information that's interesting. 

I was planning to stay within a simple XML-File -> XSLT-chaing -> HTML
scheme without involving database servers. I was rather thinking of
a solution using "xml:lang" attributes so you can write you text in
one XML file which is then served in the requested language.

Something like:

  <para xml:lang="en">Hello world!</para>
  <para xml:lang="de">Hallo Welt!</para>

Which results in either

  <para>Hello world!</para>

or

  <para>Hallo Welt!</para>

being delivered depending on the user's language preferences.

Still, the handling of nested elements with potentially different
"xml:lang" attribute values doesn't seem trivial and I haven't read
the specs about usage of xml:lang yet.

Uli