468,315 Members | 1,428 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,315 developers. It's quick & easy.

Multiple Elements

Hi,
I've got another question.
My Code works fine now and I've tried some other functions.
XSLT-Code is now:
<!DOCTYPE BUCH [
<!ELEMENT BUCH (KAPITEL)+>
<!ELEMENT KAPITEL (UEBERSCHRIFT*, ZWISCHENUEBERSCHRIFT*,
TEXT*)>
<!ELEMENT UEBERSCHRIFT (#PCDATA)>
<!ELEMENT ZWISCHENUEBERSCHRIFT (#PCDATA)>
<!ELEMENT TEXT (#PCDATA)>
] >

Like on the Book the MULTIPLE says "Allow Multiple Tags of this".
But IE6 &NE7 &MOZ doesn't show Multiple Lines. They only show ONE
Sub-Tag (the Content) per KAPITEL. They do show multiple KAPITEL.
Does anyone know why?
M.

Jun 1 '08 #1
5 1535


<Mi**************@t-online.dewrote in message
news:tt********************************@4ax.com...
Hi,
I've got another question.
My Code works fine now and I've tried some other functions.
XSLT-Code is now:
<!DOCTYPE BUCH [
<!ELEMENT BUCH (KAPITEL)+>
<!ELEMENT KAPITEL (UEBERSCHRIFT*, ZWISCHENUEBERSCHRIFT*,
TEXT*)>
<!ELEMENT UEBERSCHRIFT (#PCDATA)>
<!ELEMENT ZWISCHENUEBERSCHRIFT (#PCDATA)>
<!ELEMENT TEXT (#PCDATA)>
] >

Like on the Book the MULTIPLE says "Allow Multiple Tags of this".
But IE6 &NE7 &MOZ doesn't show Multiple Lines. They only show ONE
Sub-Tag (the Content) per KAPITEL. They do show multiple KAPITEL.
Does anyone know why?
M.
If the DOCTYPE is for BUCH you can only have one BUCH element otherwise the
XML would not be a well-formed document, it would be a fragment. The +
applies to the KAPITEL elements.

--

Joe Fawcett
http://joe.fawcett.name

Jun 1 '08 #2
Mi**************@t-online.de wrote:
Hi,
I've got another question.
My Code works fine now and I've tried some other functions.
XSLT-Code is now:
<!DOCTYPE BUCH [
That's the dtd not the XSLT, but I assume the xslt is similar to the
code posted in the earlier thread.

<H3>
<xsl:value-of select="ZWISCHENUEBERSCHRIFT"/>
</H3>
the select="ZWISCHENUEBERSCHRIFT" does select all those elements but
value-of (in xslt 1) just gives the string value of the first.

When rendering a document structure to html as here normally you dont
want to use for-each and value-of at all, but rather apply-templates, so
that the output structure mirrors the input structure.

so you don't need a template matching BUCH as you want the default
processing there
but you do want something like

<xsl:template match="UEBERSCHRIFT">
<h1>
<xsl:apply-templates/>
<h1>
</xsl:template>
<xsl:template match="ZWISCHENUEBERSCHRIFT">
<h3>
<xsl:apply-templates/>
<h3>
</xsl:template>
<xsl:template match="TEXT">
<p>
<xsl:apply-templates/>
<p>
</xsl:template>

David
--
http://dpcarlisle.blogspot.com
Jun 1 '08 #3
Hi,
I am sorry for not beeing totally precise.
The BUCH or KAPITEL function works fine. What
makes the problem ist the UEBERSCHRIFT-thing.

XSLT-Code says UEBERSCHRIFT can be more than one
(the reference part of my book says so). And I want
to have more than one UEBERSCHRIFT in one KAPITEL.
Even more than one ZWISCHENUEBERSCHRIFT and TEXT.
I don't want to have only one UEBERSCHRIFT and ZWISCHENUEBERSCHRIFT
and TEXT Part in my KAPITEL, because, it makes no sense
to have an extra KAPITEL for a short TEXT which belongs to a
UEBERSCHRIFT.

M.
On Sun, 01 Jun 2008 10:55:04 +0100, David Carlisle
<da********@dcarlisle.demon.co.ukwrote:
>Mi**************@t-online.de wrote:
>Hi,
I've got another question.
My Code works fine now and I've tried some other functions.
XSLT-Code is now:
<!DOCTYPE BUCH [

That's the dtd not the XSLT, but I assume the xslt is similar to the
code posted in the earlier thread.

<H3>
<xsl:value-of select="ZWISCHENUEBERSCHRIFT"/>
</H3>
the select="ZWISCHENUEBERSCHRIFT" does select all those elements but
value-of (in xslt 1) just gives the string value of the first.

When rendering a document structure to html as here normally you dont
want to use for-each and value-of at all, but rather apply-templates, so
that the output structure mirrors the input structure.

so you don't need a template matching BUCH as you want the default
processing there
but you do want something like

<xsl:template match="UEBERSCHRIFT">
<h1>
<xsl:apply-templates/>
<h1>
</xsl:template>
<xsl:template match="ZWISCHENUEBERSCHRIFT">
<h3>
<xsl:apply-templates/>
<h3>
</xsl:template>
<xsl:template match="TEXT">
<p>
<xsl:apply-templates/>
<p>
</xsl:template>

David
Jun 1 '08 #4
Mi**************@t-online.de wrote:
Hi,
I am sorry for not beeing totally precise.
The BUCH or KAPITEL function works fine. What
makes the problem ist the UEBERSCHRIFT-thing.

XSLT-Code says UEBERSCHRIFT can be more than one
(the reference part of my book says so). And I want
to have more than one UEBERSCHRIFT in one KAPITEL.
Even more than one ZWISCHENUEBERSCHRIFT and TEXT.
I don't want to have only one UEBERSCHRIFT and ZWISCHENUEBERSCHRIFT
and TEXT Part in my KAPITEL, because, it makes no sense
to have an extra KAPITEL for a short TEXT which belongs to a
UEBERSCHRIFT.
Yes, it is possible (but unusual) to have more than one ueberschrift
in a chapter.

I think you may be confusing the ueberschrift with the concept of a
container like <sectionor <subsection>. XML is normally built on a
hierarchical model or containers, unlike (eg) LaTeX, where headings
are simply interruptions to the flow of text (eg \section{}, not
\begin{section}...\end{section}).

<!DOCTYPE buch [
<!ELEMENT buch (kapitel)+>
<!ELEMENT kapitel (ueberschrift,text+,unterkapitel*)>
<!ELEMENT ueberschrift (#PCDATA)>
<!ELEMENT unterkapitel (ueberschrift,text+)>
<!ELEMENT text (#PCDATA)>
]>
<buch>
<kapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
</kapitel>
<kapitel>
<ueberschrift></ueberschrift>
<text></text>
</kapitel>
</buch>

///Peter
Jun 1 '08 #5
Hi,
this seems to be the right way, I suppose and therefore
I will try this as soons as possible. And furthermore if
this works for me, I will try to understand it.
thanx
M.

Peter Flynn schrieb:
Mi**************@t-online.de wrote:
>Hi,
I am sorry for not beeing totally precise.
The BUCH or KAPITEL function works fine. What
makes the problem ist the UEBERSCHRIFT-thing.

XSLT-Code says UEBERSCHRIFT can be more than one
(the reference part of my book says so). And I want
to have more than one UEBERSCHRIFT in one KAPITEL.
Even more than one ZWISCHENUEBERSCHRIFT and TEXT.
I don't want to have only one UEBERSCHRIFT and ZWISCHENUEBERSCHRIFT
and TEXT Part in my KAPITEL, because, it makes no sense
to have an extra KAPITEL for a short TEXT which belongs to a
UEBERSCHRIFT.

Yes, it is possible (but unusual) to have more than one ueberschrift
in a chapter.

I think you may be confusing the ueberschrift with the concept of a
container like <sectionor <subsection>. XML is normally built on a
hierarchical model or containers, unlike (eg) LaTeX, where headings
are simply interruptions to the flow of text (eg \section{}, not
\begin{section}...\end{section}).

<!DOCTYPE buch [
<!ELEMENT buch (kapitel)+>
<!ELEMENT kapitel (ueberschrift,text+,unterkapitel*)>
<!ELEMENT ueberschrift (#PCDATA)>
<!ELEMENT unterkapitel (ueberschrift,text+)>
<!ELEMENT text (#PCDATA)>
]>
<buch>
<kapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
<unterkapitel>
<ueberschrift></ueberschrift>
<text></text>
<text></text>
<text></text>
</unterkapitel>
</kapitel>
<kapitel>
<ueberschrift></ueberschrift>
<text></text>
</kapitel>
</buch>

///Peter
Jun 1 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by JeeWee | last post: by
2 posts views Thread by areef.islam | last post: by
2 posts views Thread by libsfan01 | last post: by
reply views Thread by Teichintx | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.