Armin,
You have my sympathies! It sounds like trying to mix cake batter with
a screwdriver.
Maybe you can accomplish something more graceful by using Xalan's
extension functions and/or access to Java? I am not a Java programmer
-- which makes me suppose that a magician might be able to conjure up
something from Java libraries for handling HTML....
Cheers,
Wendell
At 03:46 AM 10/5/2010, you wrote:
> It's true this is very nasty stuff to have to deal with. For one
thing, you have no assurance going in that the "HTML" pseudo-markup
will actually parse -- like this example (there is an unclosed open
tag). Do you plan to intercept that or let it through?
Should is tell you the truth?
I parse every character of the content!
So i extract all things i need for the formatting. Why? Because i
can't transfer the content in a xml tree (XSLT 1.0).
I use a "character" recursion template and extract all information i need.
-> not what i want, but not other possibility in XSLT 1.0, because
all transformation have to be done in the ram - no save to the disk
and also a save to the disk and open again doesn't help, because the
database output is not a well formed XHTML as you see.
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--