RE: [xep-support] can the < > symbols be replaced with &lt; and &gt;

Ken,

starts-row= and ends-row=" is exactly what I needed.

Thank You !!

Jerry J

-----Original Message-----
From: owner-xep-support@renderx.com [mailto:owner-xep-support@renderx.com]
On Behalf Of G. Ken Holman
Sent: Sunday, October 14, 2007 7:14 PM
To: xep-support@renderx.com
Subject: RE: [xep-support] can the < > symbols be replaced with &lt; and
&gt;

At 2007-10-14 18:26 -0400, Jerry Janofsky wrote:
>No, you are wrong, you said exactly what I wanted to hear, that is, after I
>got passed the momentary feeling of being insulted.

Then I sincerely apologize ... that was not my intention.

>I think you gave me the solution by saying, " did you consider
>the cell-based row-grouping strategy instead of the row-based
>row-grouping strategy and just use the starts-row= and ends-row=". I didn't
>know that existed and believe it might be the answer to my problem.

It is very useful for a class of problems where algorithmically
expressing row boundaries is easier than packaging row boundaries as
one is obliged to do in HTML.

>Also, I did think quite hard about fixing my problem and always try to have
>well constructed algorithms. My solution led me to an odd situation,
>however, where I was forced to use a CDATA on a <fo:table-row> and
></fo:table-row> because my XSLT document was not valid XML if I didn't use
>it.

I understand where you found yourself in order to create such a
construct, and as I said I've seen it before. Such an approach
really isn't necessary, though I grant that at times "row packaging"
solutions can be very, very challenging, sometimes involving
recursive calls while doing handstands in front of the
keyboard. It's the nature of the beast.

>It just seemed feasible to me that a processor, whether or not it is an
>HTML or XSL-FO processor, would understand that &lt; is '<'. From your
>reaction, I guess there is something I am terribly confused about.

And not uncommon either ... but "markup is different than text" is
the foundation of XML and SGML. "<" is markup, "&lt;" is text, both
are "less-than signs". Blurring the two would cause everything to
fall apart. Think of the need to present XSL-FO markup on the
printed page: those angle brackets must be escaped and treated as
text, not markup, or it would end up not showing. How would one know
which "&lt;fo:table-row>" was text and which was an escaped row ending?

>However, thank you for responding so quickly. I am going to try the cell
>based solution. I think it is going to solve my problem.

I'm glad to hear that ... good luck in your work!

. . . . . . . . . . Ken

--
Comprehensive in-depth XSLT2/XSL-FO1.1 classes: Austin TX,Jan-2008
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Jul'07  http://www.CraneSoftwrights.com/f/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/terms-of-service.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html