Hi,

After several hours of peering through a hex editor, here's what I've found
out so far. I'm a bit of a novice with JDom, anyone out there have more experience?


(1)
On my WinXP platform, when "ant docs" is run, anakia returns documents that
are a mix of formats. (Incidentally, this apparently prevents cygwin "unix2dos"
from working properly). Most line endings are \r\n, but within <p>
tags and content within <source> tags it's a Unix-style "\n".


(2) The text within a <p> tag is displayed with AnakiaElement.toString().
This delagates to JDom's XMLOutputter.  XMLOutputter has the option to
specify a line separator but I couldn't get this to work.  Upgrading JDom
b10-rc1 to jdom-1.0 solved this problem.  Text within <p> tags now uses the
"\r\n" by default.  Perhaps someone on a Unix platform could test that it
outputs "\n" inside of <p> tags.

Example (for testing): anakia.xml, line 16, following text "to transform" has a "\n"

(3) Text within <source> tags still uses "\n" type formats. even with jdom
1.0.   site.vsl retrieves this text with:  $escape.getText($value.getText())

$value is of class AnakiaElement (subclass of jdom's element).

Example:
anakia.xml, line 125, following <project> text has a "\n"

I need to quit for a while (have paying work to do), but just thought I'd
throw this out there in case anyone else has ideas.

In my mind, this is really an anakia/jdom issue, not a subversion issue.
The line endings should definitely be consistent, and preferably be set to
the platform default.

WILL




----- Original Message ----- From: "Shinobu Kawai Yoshida" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]>
Sent: Tuesday, January 25, 2005 6:54 AM
Subject: Re: anakia generating wrong line endings



Hi guys,

If the xdocs and site2 were all LF, I'll bet the html commits will go
fine.

Is there a reason why the [[auto-generated]] html are in the repository in the first place?

Best regards,
-- Shinobu

--
Shinobu "Kawai" Yoshida <[EMAIL PROTECTED]>

---------------------------------------------------------------------
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]



Reply via email to