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 <[EMAIL PROTECTED]> 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: > > <!--#if expr="! $CONTENT_ENCODING" --> > <!--#set var="CONTENT_ENCODING" value="ISO-8859-1" --> > <!--#endif --> > <?xml version="1.0" encoding="<!--#echo var="CONTENT_ENCODING" -->"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";> > <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"> > <head> > <title><!--#echo var="TITLE" --></title> > <meta http-equiv="Content-Type" content="text/html; <!--#echo > var="CONTENT_ENCODING" -->" /> > <link rev="made" href="mailto:<!--#echo encoding="none" var="SERVER_ADMIN" > -->" /> > ... > Hiroaki Kawai Department of Complexity Science and Engineering, The University of Tokyo http://www.bcl.t.u-tokyo.ac.jp mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
