Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 78680 invoked by uid 500); 20 Aug 2002 15:17:43 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 78666 invoked from network); 20 Aug 2002 15:17:42 -0000 Date: Wed, 21 Aug 2002 00:17:43 +0900 From: Hiroaki KAWAI X-Mailer: EdMax Ver2.84.3F MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: Japanese internationalized error messages; charset intypemapfiles Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: References: Message-Id: <20020820151951.44C7368D4@mail.bcl.t.u-tokyo.ac.jp> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I see. The idea of CONTENT_ENCODING seems to be nice. If we introduce the var, nagotiation of the docs in include/* will become unnecessary. The include/* would be common for all encodings. But, we also have to change xml:lang="en" attribute to xml:lang="ja". Shall we introduce a new var CONTENT_LANG? By the way, is it OK, that xml:lang="en" are commonly used now whatever lang we choose (de,fr,etc)? Erik Abele wrote: > We could also introduce an new variable (e.g. CONTENT_ENCODING) before > including top.html and set the correct encoding via the include/*.var's --snip-- > and to get it in top.html: > > > > > "?> > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> > > >  > " /> > -->" /> > ... > Hiroaki Kawai Department of Complexity Science and Engineering, The University of Tokyo http://www.bcl.t.u-tokyo.ac.jp mailto:hawk@bcl.t.u-tokyo.ac.jp --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org