I mean that I use JSL with success to generate docs in Russian. I have had a lot of troubles with DVSL.
For example, DVSL always uses ASCII for navigation.xml transformation This can't be changed with properties because it is hardcoded (sic!) - all data included from separate files is processed in ASCII encoding. Another example: if I have my xdoc files written in UTF-8 and want result in UTF-8 too I should set maven.docs.outputencoding=ISO-8859-1 for DVSL. Not very obvious. So I'm for JSL. Best regards, Alexei > -----Original Message----- > From: Rademacher Tobias [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 5:52 PM > To: 'Turbine Maven Users List' > Subject: RE: xdoc:generate-from-pom and xml encoding > > > > I use it to generate documentation in Russian. > > Works fine with maven.docs.outputencoding=UTF-8 > > My problem: > > - using project.xml (only now files exits in /xdocs) > - run maven site > > maven xdoc:jelly-transform complains about generated > index.xml which does not contain a proper encoding scheme. > UTF-8 which is xml default won't work. If I add the ISO > format into the velocity template everything works fine. Mhm. > > So it would be nice you could consider to pass encoding > from maven to velocity. This would safe me to chance the > templates handy everytime I update maven. Or is this a > client side problem? > > Thx > Toby > > > ------------------------------------------------------------ > --------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
