Hello i've an xsl stylesheet that must support xhtml entities,
my solution:
----
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE xsl:stylesheet [
<!ENTITY % xhtml PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
%xhtml;
]>
<xsl:stylesheet version="1.0"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:page="http://www.wolterinkwebdesign.com/xml/page"
xmlns:form="http://www.wolterinkwebdesign.com/xml/form">
<xsl:include href="xsl/xhtml/standard.xsl"/>
<xsl:output method="xml" indent="yes"/>
<xsl:param name="absolute_url"/>
<xsl:param name="upload_url"/>
<xsl:variable name="help_icon" select="concat($absolute_url, '/img/help_icon.gif')"/>
<xsl:variable name="error_icon" select="concat($absolute_url, '/img/error.gif')"/>
<xsl:variable name="max_file_size" select="2000000 "/>
<xsl:variable name="max_image_width" select="260"/>
<xsl:template match="/form:form">
<page:page type="module">
<form enctype="multipart/form-data" action="" method="post">
<input type="hidden" name="_xcm_module" value="{@module}" />
---- xsl file is longer
But when i edit this file in my xml-editor it complains that every <xsl: element must be declared.
For example:
Element type "xsl:include" must be declared.
I know what the problem is (i changed the doctype of xsl:stylesheet)
but i dont know the solution!
Please help. 13 3607 Hello i've an xsl stylesheet that must support xhtml entities, my solution:
why must it use these entities?
whether you use & # 1 6 0 ; or & n b s p ; within the stylesheet never
makes any difference to the result.
So you (and the processor) will have a simpler job if you used numeric
character references (or just use the characters directly) rather than
loading up the XHTML DTD.
If you really want to use the DTD then you will need a parser that reads
an external DTD entity but does not validate. Most parsers will do this
but they may need a special configurartion option. Some parsers default
to validating mode if the file starts with a DOCTYPE and you never want
that for XSLT (as you found:-)
If you say which system you are using someone may be able to tell you
what processor specific thing you need to do to turn off validation, but
as I say above you can avoid the entire problem by not using a DOCTYPE
in the stylesheet.
David
David Carlisle wrote: Hello i've an xsl stylesheet that must support xhtml entities, my solution:
why must it use these entities?
Because i want the xsl to output xhtml, if you know what i mean. whether you use & # 1 6 0 ; or & n b s p ; within the stylesheet never makes any difference to the result.
ok but i like to use So you (and the processor) will have a simpler job if you used numeric character references (or just use the characters directly) rather than loading up the XHTML DTD.
The WYSIWYG Xhtml editor that is embedded in my webpages output xhtml with
So spaces must be supported. If you really want to use the DTD then you will need a parser that reads an external DTD entity but does not validate. Most parsers will do this but they may need a special configurartion option. Some parsers default to validating mode if the file starts with a DOCTYPE and you never want that for XSLT (as you found:-)
Is there no other way?
I just want a valid xsl file that support If you say which system you are using someone may be able to tell you what processor specific thing you need to do to turn off validation, but as I say above you can avoid the entire problem by not using a DOCTYPE in the stylesheet.
But i want to use so the doctype must be included,
in the webapp i use sablatron, sablatron does not complain (IF i use the doctype xhtml entity defeinitions)
But in my editor (a java based editor) it does complain.
So is there a solution to my problem?
David
Tjerk
>> If you really want to use the DTD then you will need a parser that reads an external DTD entity but does not validate. Most parsers will do this but they may need a special configurartion option. Some parsers default to validating mode if the file starts with a DOCTYPE and you never want that for XSLT (as you found:-)
Is there no other way? I just want a valid xsl file that support
I've noticed that the transformer I use (that would be the one found
with the Sun's JRE 1.4.2 distribution) always outputs for
in the source, using HTML mode. Haven't tried it for XHTML,
though.
So you could check with the documentation of your transformation
library if there's some setting for it... as alternative to
including a DOCTYPE.
--
Stanimir
P.S.: And please, DON'T use all capital letters in the subject, next
time.
Tjerk Wolterink <tj***@wolterinkwebdesign.com> writes: David Carlisle wrote:Hello i've an xsl stylesheet that must support xhtml entities, my solution:
why must it use these entities?
Because i want the xsl to output xhtml, if you know what i mean.
No, I don't really know what you mean as using or not entity references
in the stylesheet has no bearing on whether or not they are used in the
result. whether you use & # 1 6 0 ; or & n b s p ; within the stylesheet never makes any difference to the result.
ok but i like to use
You are not the only one, but it's a distinctly odd thing to like.
nbsp is no shorter or easier to type than #160 and it's a lot harder to
set things up so that it works. as I say above you can avoid the entire problem by not using a DOCTYPE in the stylesheet.
But i want to use so the doctype must be included,
Yes, if you really must:-)
in the webapp i use sablatron, sablatron does not complain (IF i use the doctype xhtml entity defeinitions) But in my editor (a java based editor) it does complain.
So is there a solution to my problem?
Probably. But as I say it is entirely parser specific, so you'll need to
give a bit more information than "a java based editor" about what the
system is, or at least what XML parser it is using, and then hope that
someone reading this knows how to configure the system not to validate.
I'd be very surprised if it wasn't possible, but you have no guarantees,
an XML parser that always validated in the presence of a DOCTYPE is
fully conformant I believe, and if your parser is validating you are
going to get validity errors unless you declare all the elements
and attributes used in the XSL.
David
Stanimir Stamenkov wrote: If you really want to use the DTD then you will need a parser that reads an external DTD entity but does not validate. Most parsers will do this but they may need a special configurartion option. Some parsers default to validating mode if the file starts with a DOCTYPE and you never want that for XSLT (as you found:-)
Is there no other way? I just want a valid xsl file that support
I've noticed that the transformer I use (that would be the one found with the Sun's JRE 1.4.2 distribution) always outputs for in the source, using HTML mode. Haven't tried it for XHTML, though.
So you could check with the documentation of your transformation library if there's some setting for it... as alternative to including a DOCTYPE.
Ok but the problem is:
i have an xsl file lilke this
<xsl:stylesheet>
<xsl:template name="henk">
<page:section>
<page:header>LAst newsmessage</page:header>
<page:content type="xhtml">
--
some server side scripts gets the edited content from database,
because the content is genereated by a browser-based-text-editor
( http://www.blueshoes.org/en/javascript/editor/) and thus
contains characters like
could convert it with a strreplace($html, " ", " ") but
i must then do it for all entities.
So i leave it like IN the stylesheet:
--
</page:content>
</page:section>
</template>
</xsl:stylesheet>
sample result after a page request:
<xsl:stylesheet>
<xsl:template name="henk">
<page:section>
<page:header>LAst newsmessage</page:header>
<page:content type="xhtml">
<!-- editor generated xhtml --!>
<p>
Yes bla <b>yippa</b>
</p>
<!-- end editor generated xhtml --!>
</page:content>
</page:section>
</template>
</xsl:stylesheet>
So using numbers for nbsp is 'impossible'.
See below (sorry for the long quotation).
/Tjerk Wolterink/:
[...] some server side scripts gets the edited content from database, because the content is genereated by a browser-based-text-editor (http://www.blueshoes.org/en/javascript/editor/) and thus contains characters like could convert it with a strreplace($html, " ", " ") but i must then do it for all entities. So i leave it like IN the stylesheet:
[...] sample result after a page request:
<xsl:stylesheet> <xsl:template name="henk"> <page:section> <page:header>LAst newsmessage</page:header> <page:content type="xhtml"> <!-- editor generated xhtml --!> <p> Yes bla <b>yippa</b>
</p> <!-- end editor generated xhtml --!> </page:content> </page:section> </template> </xsl:stylesheet>
So using numbers for nbsp is 'impossible'.
Escape the markup as XML text (when read from the DB and supplied as
part of the stylesheet) and use the 'disable-output-escaping':
<xsl:text disable-output-escaping="yes">
<p>
Yes bla <b>yippa</b> &nbsp;
</p>
</xsl:text>
This way you can supply pure HTML source (i.e. not well-formed XML),
even.
--
Stanimir
Stanimir Stamenkov wrote: See below (sorry for the long quotation).
/Tjerk Wolterink/:
[...]
some server side scripts gets the edited content from database, because the content is genereated by a browser-based-text-editor (http://www.blueshoes.org/en/javascript/editor/) and thus contains characters like could convert it with a strreplace($html, " ", " ") but i must then do it for all entities. So i leave it like IN the stylesheet:
[...]
sample result after a page request:
<xsl:stylesheet> <xsl:template name="henk"> <page:section> <page:header>LAst newsmessage</page:header> <page:content type="xhtml"> <!-- editor generated xhtml --!> <p> Yes bla <b>yippa</b> </p> <!-- end editor generated xhtml --!> </page:content> </page:section> </template> </xsl:stylesheet>
So using numbers for nbsp is 'impossible'.
Escape the markup as XML text (when read from the DB and supplied as part of the stylesheet) and use the 'disable-output-escaping':
<xsl:text disable-output-escaping="yes"> <p> Yes bla <b>yippa</b> &nbsp; </p> </xsl:text>
This way you can supply pure HTML source (i.e. not well-formed XML), even.
this is a solution,
but id like to treat the genereated xhtml as xml.
But anyways thanks for your input;.
/Tjerk Wolterink/: this is a solution, but id like to treat the genereated xhtml as xml.
I didn't quite get - did you try configuring your parser as David
Carlisle already suggested in previous replies?
--
Stanimir
In article <37*************@individual.net>,
Stanimir Stamenkov <s7****@netscape.net> wrote: Escape the markup as XML text (when read from the DB and supplied as part of the stylesheet) and use the 'disable-output-escaping':
<xsl:text disable-output-escaping="yes"> <p> Yes bla <b>yippa</b> &nbsp; </p> </xsl:text>
That's not a good idea. It defeats one of the advantages of XSLT (the
guarantee of well-formed output) and does not work in tree-to-tree
transformations.
--
Henri Sivonen hs******@iki.fi http://iki.fi/hsivonen/
/Henri Sivonen/: In article <37*************@individual.net>, Stanimir Stamenkov <s7****@netscape.net> wrote:
Escape the markup as XML text (when read from the DB and supplied as
(self spell correction) ^^^^^^^^
XML character data
part of the stylesheet) and use the 'disable-output-escaping':
<xsl:text disable-output-escaping="yes"> <p> Yes bla <b>yippa</b> &nbsp; </p> </xsl:text>
That's not a good idea. It defeats one of the advantages of XSLT (the guarantee of well-formed output) and does not work in tree-to-tree transformations.
I admit - it is not a good idea. Probably the best solution for the
OP would be to do an identity transform (where all entities to be
expanded) on the submitted source prior storing it, which would
check the data for well-formedness at the same time, too. I think it
would be too late to report well-formedness errors when the data is
to be supplied to third-parties (in this case as part of another
document composed with an XSLT sheet).
Still, the copy transformation would require a parser configured to
read the external entities supplied by a DTD, through added DOCTYPE
to the source submitted data, and not to validate... but thinking
more, should the following work?
-----"generated source"
<?xml version="1.0" ?>
<!DOCTYPE xhtml-fragment [
<!ENTITY % xhtml PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
%xhtml;
<!ELEMENT xhtml-fragment ANY>
]>
<xhtml-fragment>
<!-- insert the submitted data here -->
</xhtml-fragment>
-----"generated source"--
--
Stanimir
Stanimir Stamenkov wrote: /Tjerk Wolterink/:
this is a solution, but id like to treat the genereated xhtml as xml.
I didn't quite get - did you try configuring your parser as David Carlisle already suggested in previous replies?
You suggested to use the html-data like this:
<xsl:text disable-output-escaping="yes">
<p>
Yes bla <b>yippa</b> &nbsp;
</p>
</xsl:text>
Well i dont want to have that, because now i dont know wether if the xhtml tags are valid (non overlapping <a><b></a></b> and stuff )
So i want to tread the editor-generated xhtml as xhtrml and not as xsl:text.
Stanimir Stamenkov wrote: /Henri Sivonen/:
In article <37*************@individual.net>, Stanimir Stamenkov <s7****@netscape.net> wrote:
Escape the markup as XML text (when read from the DB and supplied as cut
That's not a good idea. It defeats one of the advantages of XSLT (the guarantee of well-formed output) and does not work in tree-to-tree transformations.
I admit - it is not a good idea. Probably the best solution for the OP would be to do an identity transform (where all entities to be expanded) on the submitted source prior storing it, which would check the data for well-formedness at the same time, too. I think it would be too late to report well-formedness errors when the data is to be supplied to third-parties (in this case as part of another document composed with an XSLT sheet).
The editor says is generated well-formed xhtml. So i take that for granted.
The only problem are the entities like Still, the copy transformation would require a parser configured to read the external entities supplied by a DTD, through added DOCTYPE to the source submitted data, and not to validate... but thinking more, should the following work?
-----"generated source"
<?xml version="1.0" ?> <!DOCTYPE xhtml-fragment [
<!ENTITY % xhtml PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> %xhtml;
<!ELEMENT xhtml-fragment ANY>
]>
<xhtml-fragment> <!-- insert the submitted data here --> </xhtml-fragment>
Yes but how do i use it with xslt?
-
-
-
damn i made a mistake.
The IN the stylesheets are coded by hand, so i could
edit those to Ģ (it was 290 for nbsp right?).
-
So there is no problem after all. :-)
Sorry. but anyways thanks for all your help!
It would offcourse be more beatifull to use IN the xsl-styleheet,
but thats not a real problem. -----"generated source"--
damn i made a mistake.
The IN the stylesheets are coded by hand, so i could
edit those to Ģ (it was 290 for nbsp right?).
160
David This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Sergio del Amo |
last post by:
Hi,
I use the xslt functions provided by php. I am running in my computer
the package xampp(www.apachefriends.org) which includes php/apache/mysql
.. In this package the php includes the sablotron...
|
by: Bernd Fuhrmann |
last post by:
Hi!
I have some trouble with some simple stupid XSLT-stuff.
My stylesheet:
-------------
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet
version="1.0"...
|
by: Bernd Fuhrmann |
last post by:
Hi!
I have two (or more) templates for one certain tag:
The first one:
tobeimported.xsl:
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet
version="1.0"
|
by: full_philNO |
last post by:
Hi all,
I have a problem with the img tag. It simply doesn't want to translate
into a img XHTML tag.
When I write in XSLT :
<img src="..." alt="..." ..../> or <img src=".." alt="..."...
|
by: rush |
last post by:
I have a DTD that defines new elements "mytextfield" and "mysn", and
does it as an extension to XHTML. The idea is that my XML markup is
actually valid XHTML according to my DTD. This all works...
|
by: Grant Harmeyer |
last post by:
I have an XSL file that is being applied to an RSS feed, and it works great
except for 2 things:
1.) XSL doesn't close the <img> tag for xhtml even though I have it being
closed in the XSL file...
|
by: =?iso-8859-2?Q?K=F8i=B9tof_=AEelechovski?= |
last post by:
It is common knowledge that XHTML is better HTML and you can serve XHTML content as HTML.
However, the second statement is incorrect, for various reasons;
it is enough to say that the HTML...
|
by: C.W.Holeman II |
last post by:
For info on the context of my question see the end of this posting.
From http://www.w3.org/TR/XHTMLplusMathMLplusSVG/:
How can I validate the result of client-side XSLT transform which has...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
| |