Bob Harner wrote:
[...]
I concede that you guys are right. It took a while for me to fully
realize what you were saying -- that by contract the content xml files
must contain only one very specific URl format for the <a href="foo">
links -- namely, "/pubid/area/docid.html", with the servlet context
(if any) REMOVED. (Is this *documented* anywhere? This is a rather
weird an unexpected behavior to be left undocumented, although I now
understand the thinking.)
I guess it's not documented, at least not where I'd look or it :)
I'll try to take care of it.
I guess I need to adjust the FCKeditor implementation so that it
produces content xml files without the servlet context.
There is still a small issue with assets, though. As I understand it,
they must be document-relative URI's, right?
Yes, they're still relative. But this is hopefully going to change.
Kupu seems to make image
tags like this:
<object data="foo.jpg" title="foo.jpg" type=""/>
BXE makes image tags like this:
<object href="" title="foo.jpg" type="image/jpeg" data="foo.jpg"/>
BXE makes asset hyperlinks like this:
<a href="foo.pdf" title="bar">a pdf file</a>
And what if a document with a link like "../foo.pdf" moves? That
would make a broken link.
Yes, that's true. Relative links to assets of other documents are
not supported.
So I guess I still see a need for a
generalized link rewriter. Links have to be rewritten multiple places
(e.g. in StaticHTMLExporter, and when moving a file). One would think
somebody has already written something like that somewhere in the
world. Maybe Forest has such a capability?
I hope the repo/UUID stuff will be introduced soon enough so we
don't have to extend the current non-UUID link handling.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
