I personally think that providing "build.sh"/"build.bat" properly would be sufficient.
Kindly regards, -- Tetsuya. ([EMAIL PROTECTED]) ---- On Sat, 18 Aug 2007 13:37:43 +0100 (Subject: Re: svn commit: r567258 - in /jakarta/site: docs/ docs/site/ docs/site/downloads/ docs/site/news/ docs/site/pmc/ xdocs/stylesheets/) sebb wrote: > On 18/08/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: tetsuya > > Date: Sat Aug 18 04:14:52 2007 > > New Revision: 567258 > > > > URL: http://svn.apache.org/viewvc?view=rev&rev=567258 > > Log: > > Apache DB (http://db.apache.org/), especially OJB and Torque had been in > > Jakarta - "Ex-Jakarta". - Now I am using "CHCP 1252" mode (for ISO-8859-1 > > characters) > > > > Is there a way to fix build.xml so that the user's default encoding > does not affect the output? Or perhaps we could add a check and warn > if the encoding is wrong? > > The xml source files are already flagged as ISO-8859-1, as is the > stylesheet, which uses output encoding ISO-8859-1 as well, which one > might have hoped would be enough... > > As an alternative, I tried to generate the output to use ö/ü > etc instead of the iso-8859-1 characters, but could not work out how > to code this in the source XML without generating errors. > > It might solve the problem if the XSLT output format were changed from > xml to html, but I assume there are good reasons for using xml as the > output format, and it would mean updating every page. > > S/// > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- Tetsuya Kitahata -- Terra-International, Inc. - President - E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache News Online http://www.apachenews.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
