|
<xsl:template match="//table2[table1/@id = @id]"><br />
...<br />
</xsl:template>
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
|
hello
i need help on how to convert xsl:fo or xml document to pdf using c sharp
i BADLY need that.
Asim
|
|
|
|
|
|
|
some good software is at http://www.antennahouse.com[^]
you will have to use interop, or shell the exe - but its a nice product and pretty conformant to the standard.
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
Hello,
this is a very basic problem, i think. How can I define an url in the XML file and format/output it with a XSL file?
This is my XML file:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE archive SYSTEM "archive.dtd">
<?xml-stylesheet href="archive.xsl" type="text/xsl"?>
<archive>
<entry>
<name>Download 1</name>
<webcode>DWL1</webcode>
<link>link</link>
</entry>
<entry>
<name>Download 2</name>
<webcode>DWL2</webcode>
<link>link2</link>
</entry>
</archive>
This is my XSL file:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
<xsl:template>
<link rel="stylesheet" type="text/css" href="default.css"/>
<h1>Archive</h1>
<table>
<tr><td>
<img src="images/menulinks.gif"/>
Downloads</td></tr></table><br/><br/>
<table>
<tr>
<td width="33%">Name</td>
<td width="33%">Webcode</td>
<td>Goto</td>
</tr>
<xsl:for-each select="archive/entry">
<tr>
<td><xsl:value-of select="name"/></td>
<td><xsl:value-of select="webcode"/></td>
<td><a href=" WHAT HERE??? "><xsl:value-of select='link'/></a></td>
</tr>
</xsl:for-each>
</table>
</xsl:template>
</xsl:stylesheet>
What do i have to put in the 8. line above? ("WHAT HERE???")
This mustn't be a fixed string, it must be loadable from the .xml file. How do i encode the link in the XML file?
-Dominik
|
|
|
|
|
you need to use xsl:attribute to create the href= part of the anchor tag. Something like:
<a>
<xsl:attribute name="href">
<xsl:value-of select="href"/>
</xsl:attribute>
</a>
That's off the top of my head, but it's basically correct.
Christian
<i>No offense, but I don't really want to encourage the creation of another VB developer.</i> - <b>Larry Antram 22 Oct 2002</b>
<i>Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that...</i> - <b>Shog9 04-09-2002</b>
<i>During last 10 years, with invention of VB and similar programming environments, every ill-educated moron became able to develop software. </i> - <B>Alex E. - 12-Sept-2002</B>
|
|
|
|
|
or the short version:
<a href="{link}"><xsl:value-of select='link'/></a>
notice the use of the curly brakets to shortcut any xpath expression....
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
That looks great - how does it work ? It's pulling a node called 'link' out of the current context node, and the curly brackets mean that it's put into there, or the curly brackets pull it out of the current context node seperately ?
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
During last 10 years, with invention of VB and similar programming environments, every ill-educated moron became able to develop software. - Alex E. - 12-Sept-2002
|
|
|
|
|
curly brackets are shorthand - they tell the xsl processor to replace the contents with the result of the xpath xpresions
xml:
<company logo="bob.gif"/>
xlst:
<xsl:apply-template match="company"><br />
<img src="{@logo}"/><br />
</xsl:apply-template>
hope this makes sense - saves alot of typing 
[edit]note that is always in the context of the current node - so equal to current()/@logo
[/edit]
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
Cool - yes, thanks. I did not know you could do that, and I will find it very useful.
Christian
No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
During last 10 years, with invention of VB and similar programming environments, every ill-educated moron became able to develop software. - Alex E. - 12-Sept-2002
|
|
|
|
|
Philip Fitzsimons wrote:
curly brackets are shorthand - they tell the xsl processor to replace the contents with the result of the xpath xpresions
Wow, thanks for the awesome tip. Never seen this mentioned in any XSL tutorial before, is it part of the standard?
Paul Watson
Bluegrass
Cape Town, South Africa
Ray Cassick wrote:
Well I am not female, not gay and I am not Paul Watson
|
|
|
|
|
|
how do i restrict the values of an attribute to be any integer value EXCEPT 0?
for example:
<xsd:attribute name="id" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:integer" >
<xsd:minExclusion value="0"/> <!-- i>0 -->
<xsd:maxExclusion value="0"/> <!-- i<0 -->
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
this code does not work... how can i allow all values for integer EXCEPT zero?
thanks..
meng
|
|
|
|
|
Your restriction will result in a void type, intersecting (0, +inf) with (-inf, 0).
Try using the following pattern: (\+|\-)?[1-9]+[0-9]*
rechi
|
|
|
|
|
thanks alot! the pattern works...
meng
|
|
|
|
|
hello
can someone guide me in opening a document i.e .doc or .pdf or .html or .txt in xml/xsl.
can someone help me out
Asim
|
|
|
|
|
this makes no sense, please give us more detail of what you are trying to do
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
I have a big XML file and I want to use some XSLT file to transform it, which is the best choice?
I used the DOM process the file, but I found It need a very huge memory. So I used the SAX, but it cann't transform the file with XSLT file.
|
|
|
|
|
Clark John wrote:
So I used the SAX, but it cann't transform the file with XSLT file.
Brief discussion on the topic[^]
Not having used SAX I am no authority but from what I know you use SAX when you want to do simple enough tasks on large XML documents. I think the main thing about SAX is that it is a stream or forward only type method, not like the DOM. Which is why XSL via SAX could be a b with an itch (e.g. XSL templates jump back and forth in an XML doc.)
Paul Watson
Bluegrass
Cape Town, South Africa
Ray Cassick wrote:
Well I am not female, not gay and I am not Paul Watson
|
|
|
|
|
Thanks. But the DOM process a 3.89M XML file need about 100M memory, how can I reduce the memory dosage on DOM.
|
|
|
|
|
Clark John wrote:
But the DOM process a 3.89M XML file need about 100M memory, how can I reduce the memory dosage on DOM.
Hmmm, I have not had any experience with working with such large XML files (I would consider 3.89M big for an XML file, must have a ton of entries.) Normally I use XML as an intermediary format (database -> xml -> XHTML/whatever) so the files never get big.
Just a thought and I may be totally off the mark but you might just open the XML file as a normal text file and then extract the block of nodes you want out of it and save those as a subset file of the original XML file. Then run that through DOM.
Also XSL on a 3.89M file could potentially be a killer.
This CP article may have some ideas for you and this seems like a starting point for some info.
Good luck
Paul Watson
Bluegrass
Cape Town, South Africa
Ray Cassick wrote:
Well I am not female, not gay and I am not Paul Watson
|
|
|
|
|
Think you!
|
|
|
|
|
Paul Watson wrote:
Hmmm, I have not had any experience with working with such large XML files (I would consider 3.89M big for an XML file, must have a ton of entries.)
Actualy you'd be suprised at how big some XML files can get.
Paul Watson wrote:
Just a thought and I may be totally off the mark but you might just open the XML file as a normal text file and then extract the block of nodes you want out of it and save those as a subset file of the original XML file. Then run that through DOM.
That's righ on.
At my last place we handeled transactions/data wharehousing for utility companys. Every company sent data in some bizzare flat-file format, EDI, or XML. Depending on the frequency of the transactions, we could see 10mb+ XML files.
We were just doing XML -> DB or DB ->XML -> format 'X'
Working on the XML files we would open up a stream, and use SAX to quickly parse the XML. At this point one could just use their XSL to verify content (we used a custom rules engine to apply business logic.)
Performance wasn't bad with this approach but, I have qualify this by saying that our implementation was done in <gasp> JAVA. With an optimized JVM.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
