RE: Antwort: fo wysiwig editor
Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. So it seems I have to either instigate another tool, or go the word style route. Thanks Paul. Victor Mote [EMAIL PROTECTED] on 27/09/2002 18:51:42 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: Antwort: fo wysiwig editor Paul Hussein wrote: Al I want is an editor that that works with FO only. I don't know of anything out there right now that does what you are looking for. FO is not intended to be an editable format, but rather an intermediate format. The advantage to using FO is that it can be created pretty easily (using XSLT) from semantic XML. If you don't need that advantage, but need a WYSIWIG editor and PDF output, and don't mind paying for it, I would recommend either Microsoft Word or Adobe FrameMaker. Word's limitations are well-known, and FrameMaker has two that were major for us -- lack of Unicode support, and some footnote problems. There are other page layout engines that can create PDF as well, some with XML integration -- Arbortext comes to mind, but I am much less familiar with their products. In the long run, I am hopeful that some method will be devised that will allow the FO document to be tied back to its original semantic XML document so that the semantic XML document could be reconstructed from the WYSIWIG-editable FO document (or area tree document). A user could open a document pointing to 1) the semantic XML document, and 2) the appropriate stylesheet, edit it in a WYSIWIG session, then save the underlying semantic XML and stylesheet documents. This would be the best of all worlds, but I do not even yet have a clear idea that it is feasible. I agree strongly with Rhett that there is quite a bit of work left to just get FOP's existing mission completed, but the great thing about open source is that no one can (or would want to) stop you from working on such a project if you wished. Victor Mote (mailto:[EMAIL PROTECTED]) Enterprise Outfitters (www.outfitr.com) 2025 Eddington Way Colorado Springs, Colorado 80916 Voice 719-622-0650, Fax 720-293-0044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: New Editor Project (Was: Re: fo wysiwig editor)
Hi Paul, Fabio, Victor, everybody, I thought of founding a wysiwig editor project as well. My idea was to base it on the eclipse platform (www.eclipse.org), because that would save a lot of UI work. I also fancy Victor's vision about separating the semantic XML and the sytlesheet. Comments please. Best regards, Marc Migge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Antwort: fo wysiwig editor
That was my hope too. Maybe for us to pickup the rendering part of AWT Renderer, create new project with it, Then export as jar that fop could use maybe. Oleg Tkachenko [EMAIL PROTECTED] on 30/09/2002 11:50:29 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Antwort: fo wysiwig editor [EMAIL PROTECTED] wrote: Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. btw, guys from jCatalog, which actually developed fop's awt viewer ended up with xslfast, see http://www.jcatalog.com/products/xslfast/index.htm. I cherish a hope *someday* our clumsy awt viewer will grow into a full-fledged xsl editor :) -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: character
Tony Graham [EMAIL PROTECTED] escreveu: [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300: Out of the XML recomendation,section 2.2: A character is an atomic unit of text as specified by ISO/IEC 10646 [ISO10646]. Legal characters are tab, carriage return, line feed, and the legal graphic characters of Unicode and ISO/IEC 10646. XML 1.0 Second Edition removed graphic (which I always found confusing but which is good ISO-speak). or, more clearly: Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10] /* any Unicode character, excluding the surrogate blocks, FFFE, and . */ That means -, #12235 , etc are characters, while '1' is not. #12235; is a character reference. '#12235' is how you talk about a character's code point, although the hexadecimal representation is usually preferable. In XSL terms, '1' is a one-character string literal, but while you could claim that it is one character, there's no XSL conversion from a string to a character, so fo:character character='1'/ should fail. You are correct. What I tried to poit out is that '1' IS a string string that HAS one character. He who claim[s] it is one character is IMHO seriouly misled. 1 , on the other hand, IS a character. The concept of a character, in the XML syntax definition, is that of the symbols allowed in the grammar, the most elementary piece of the lexical. The term string is not formally defined in the recommendation (sadly), but it is used throughout the text meaning sequence of characters. A string _type_ is defined for attributes, and consists of a quoted literal string (i.e. a sequence of characters delimited by quotes). In the XML point of view, '1' is nothing but a three-character string. And a three-character string is not a character. The XSL recommendation defines a string datatype that has a rather different scope of the 'literal string' and 'string attribute type' defined in the XML spec. But defines no 'character' datatype, so I think there is no other option but to assume it means the XML definition of a character. So, fo:character character=1/ is correct, while, as you said, fo:character character='1'/ should fail. This leaves us with a problem, however, because since the character datatype is not defined, there is also no conversion rule which results in a character. You cannot store a character in a xsl:variable because there is no way to specify or retrieve it -- variables know only about strings. I find that very disturbing, because it hampers stylesheet coding, in that we cannot specify characters indirectly or do any work with them. I think this should be reported to the editors of XSLT 2.0 so they can provide a clear way out. = Marcelo Jaccoud Amaral Petrobrás (http://www.petrobras.com.br) mailto:[EMAIL PROTECTED] voice: +55 21 2534-3485 fax: +55 21 2534-1809 =
Re: Antwort: fo wysiwig editor
[EMAIL PROTECTED] wrote: Maybe for us to pickup the rendering part of AWT Renderer, create new project with it, Then export as jar that fop could use maybe. Probably, but I believe the primary task now is to give some attention to avt viewer in redesign branch and only when it's ready, extend it by adding edit capabilities. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: character
Tony Graham wrote: [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300: Out of the XML recomendation,section 2.2: A character is an atomic unit of text as specified by ISO/IEC 10646 [ISO10646]. Legal characters are tab, carriage return, line feed, and the legal graphic characters of Unicode and ISO/IEC 10646. XML 1.0 Second Edition removed graphic (which I always found confusing but which is good ISO-speak). or, more clearly: Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10] /* any Unicode character, excluding the surrogate blocks, FFFE, and . */ That means -, #12235 , etc are characters, while '1' is not. #12235; is a character reference. '#12235' is how you talk about a character's code point, although the hexadecimal representation is usually preferable. In XSL terms, '1' is a one-character string literal, but while you could claim that it is one character, there's no XSL conversion from a string to a character, so fo:character character='1'/ should fail. Tony, I don't think this gets us out of difficulty. A casual inspection reveals no conversion, either, from an NCName to a character. So an attribute value assignment of a will, I think, parse (in the parser implied by the grammar of XSL expressions) as an NCName (whereas - will parse as an unadorned MINUS sign.) So how do I represent a character? Furthermore, Section 5.11 has q character A single Unicode character. string A sequence of characters. /q If an attribute value assignment of 'a sequence of characters' assigns a sequence of characters, then 'a' must assign a sequence of one character. What's the difference between a single Unicode character and a sequence of one character? Well, one is a sequence, and therefore a string, and there's no XSL conversion, etc. So how do I represent a character? To me, the cleanest, least ambiguous way is to represent a character attribute assignment value with 'character' - a string literal of length 1. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Antwort: fo wysiwig editor
Hi, I checked out XSLfast. It's a nice start. But not advanced enough for professional print in my opinion. Marc - Original Message - From: Oleg Tkachenko [EMAIL PROTECTED] Date: Monday, September 30, 2002 12:50 pm Subject: Re: Antwort: fo wysiwig editor [EMAIL PROTECTED] wrote: Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. btw, guys from jCatalog, which actually developed fop's awt viewer ended up with xslfast, see http://www.jcatalog.com/products/xslfast/index.htm. I cherish a hope *someday* our clumsy awt viewer will grow into a full-fledged xsl editor :) -- Oleg Tkachenko Multiconn International, Israel --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: character
Peter B. West wrote at 30 Sep 2002 13:28:18 +1000: Tony Graham wrote: [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300: ... That means -, #12235 , etc are characters, while '1' is not. #12235; is a character reference. '#12235' is how you talk about a character's code point, although the hexadecimal representation is usually preferable. In XSL terms, '1' is a one-character string literal, but while you could claim that it is one character, there's no XSL conversion from a string to a character, so fo:character character='1'/ should fail. Tony, I don't think this gets us out of difficulty. A casual inspection Forgive me, but I wasn't trying to get anybody out of any difficulty, I was just trying to keep the terminology accurate. ... So how do I represent a character? To me, the cleanest, least ambiguous way is to represent a character attribute assignment value with 'character' - a string literal of length 1. Except that you know that that's not specified among the allowed conversions. The interesting thing is that 'character' doesn't appear in the productions in Section 5.9, Expressions, of the XSL Recommendation. Now there's a question for [EMAIL PROTECTED]! I think that you represent a character as a single character, e.g., character=c, or as a numeric character reference, e.g., character=#xA;. Regards, Tony Graham XML Technology Center - Dublinmailto:[EMAIL PROTECTED] Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3x(70)19708 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
large tables loop problem
Title: Nachricht hello, i successfully embed tables in my created pdf File using fop version20.4 now i got the problem of an endless loop when a table is bigger than one page and it does no fit on one page any more any ideas how i can deal with this problem? automatically split a table correctto the next page it would be no problem for me if the table ends "abrupt" and just starts on the next page without a headline or so.. i read a lot of this in fop-dev and fop-user but i did not find any solution... Many regards, Tobias Kuhn
RE: large tables loop problem
Title: Nachricht I'm actually trying to shore up this from happening, but it won't address your situation, since my patch simply terminates the endless loop rather than necessarily finding and making splits more aggressively. Could you post a copy of the FO data that is triggering the endless loop? I'd like the opportunity to analyze it. Putting in a bug in Bugzilla and attaching some sample data there would be even better. -Original Message-From: Tobias Kuhn [mailto:[EMAIL PROTECTED]]Sent: Monday, September 30, 2002 10:25 AMTo: [EMAIL PROTECTED]Subject: large tables loop problem hello, i successfully embed tables in my created pdf File using fop version20.4 now i got the problem of an endless loop when a table is bigger than one page and it does no fit on one page any more any ideas how i can deal with this problem? automatically split a table correctto the next page it would be no problem for me if the table ends "abrupt" and just starts on the next page without a headline or so.. i read a lot of this in fop-dev and fop-user but i did not find any solution... Many regards, Tobias Kuhn
AW: large tables loop problem
Title: Nachricht hi, simply terminating the endless loop would be a good "first fix" of the problem for me too... This is the part of the code creating the tables which will not fit in one page in some cases... !-- ANFANG TABLE "AUFWANDS- ZEITPLANUNG" -- fo:block space-before.optimum="2cm" space-after="0.75cm" font-style="italic" font-size="20pt" keep-together="always" Aufwands- / Zeitplanung /fo:block fo:table table-omit-header-at-break="true" table-layout="fixed" fo:table-column column-width="2cm"/ fo:table-column column-width="1cm"/ fo:table-column column-width="4cm"/ fo:table-column column-width="3cm"/ fo:table-column column-width="3cm"/ fo:table-column column-width="2cm"/ fo:table-column column-width="2cm"/ fo:table-header fo:table-row fo:table-cell background-color="#F7F24D" fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" PSP-Nr fo:block background-color="#F7F24D" font-size="10pt"xsl:value-of select="leer" //fo:block /fo:block /fo:table-cell fo:table-cell background-color="#F7F24D" fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Typ fo:block background-color="#F7F24D" font-size="10pt"xsl:value-of select="leer" //fo:block /fo:block /fo:table-cell fo:table-cell background-color="#F7F24D" fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Bezeichnung fo:block background-color="#F7F24D" font-size="10pt"xsl:value-of select="leer" //fo:block /fo:block /fo:table-cell fo:table-cell fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Anfang fo:block background-color="#F7F24D" font-size="10pt"(Plan)/fo:block /fo:block /fo:table-cell fo:table-cell fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Ende fo:block background-color="#F7F24D" font-size="10pt"(Plan)/fo:block /fo:block /fo:table-cell fo:table-cell fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Aufwand fo:block background-color="#F7F24D" font-size="10pt"(Plan)/fo:block /fo:block /fo:table-cell fo:table-cell fo:block font-weight="bold" text-align="center" vertical-align="middle" border-width="1pt" border-color="black" background-color="#F7F24D" font-size="10pt" Kosten fo:block background-color="#F7F24D" font-size="10pt"(Plan)/fo:block /fo:block /fo:table-cell /fo:table-row /fo:table-header fo:table-body xsl:for-each select="/projekt/projektstruktur/planzeile" xsl:sort select="id" order="ascending" data-type="number"/ fo:table-row fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="pspnr" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="typ" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="bezeichnung" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="plananfang" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="planende" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="planaufwand" //fo:block /fo:table-cell fo:table-cell fo:block font-size="10pt" text-align="center" space-before="0.25cm"xsl:value-of select="plankosten" //fo:block /fo:table-cell /fo:table-row /xsl:for-each /fo:table-body /fo:table!-- ENDE TABLE "AUFWANDS- ZEITPLANUNG" -- -Ursprüngliche Nachricht-Von: Rhett Aultman [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 30. September 2002 16:29An: [EMAIL PROTECTED]Betreff: RE: large tables loop problem I'm actually trying to shore up this from happening, but it won't address your situation, since my patch simply terminates the endless loop rather than necessarily finding and making splits more aggressively. Could you post a copy of the FO data that is triggering the endless loop? I'd like the opportunity to analyze it. Putting in a bug in Bugzilla and attaching some sample data there would be even better. -Original Message-From: Tobias Kuhn [mailto:[EMAIL PROTECTED]]Sent: Monday, September 30, 2002 10:25 AMTo: [EMAIL PROTECTED]Subject: large tables loop problem hello, i successfully embed tables in my created pdf File using
Re: Antwort: fo wysiwig editor
Hi, I agree with Marc. It's not robust enough and combersome to figure out. Mark - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 30, 2002 8:05 AM Subject: Re: Antwort: fo wysiwig editor Hi, I checked out XSLfast. It's a nice start. But not advanced enough for professional print in my opinion. Marc - Original Message - From: Oleg Tkachenko [EMAIL PROTECTED] Date: Monday, September 30, 2002 12:50 pm Subject: Re: Antwort: fo wysiwig editor [EMAIL PROTECTED] wrote: Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. btw, guys from jCatalog, which actually developed fop's awt viewer ended up with xslfast, see http://www.jcatalog.com/products/xslfast/index.htm. I cherish a hope *someday* our clumsy awt viewer will grow into a full-fledged xsl editor :) -- Oleg Tkachenko Multiconn International, Israel --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: large tables loop problem
Tobias Kuhn wrote: This is the part of the code creating the tables which will not fit in one page in some cases... I can't reproduce the problem. Posting snippets form the XSLT is unwise, you should post the result of the XSL transformation, after trimming it to the part which actually demonstrates the problem, and perhaps anonymizing company data. I guess you'll spot the problem yourself when looking at the XSLT result. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/datatypes IDNode.java IDReferences.java
pietsch 2002/09/30 13:54:23
Modified:src/org/apache/fop/datatypes Tag: fop-0_20_2-maintain
IDNode.java IDReferences.java
Log:
Use the formatted page number string instead of the
raw number in IDReferences/IDNode, so that a
page-number citation gets the formatted number.
Revision ChangesPath
No revision
No revision
1.4.2.2 +7 -6 xml-fop/src/org/apache/fop/datatypes/Attic/IDNode.java
Index: IDNode.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/datatypes/Attic/IDNode.java,v
retrieving revision 1.4.2.1
retrieving revision 1.4.2.2
diff -u -r1.4.2.1 -r1.4.2.2
--- IDNode.java 2 Aug 2002 20:28:47 - 1.4.2.1
+++ IDNode.java 30 Sep 2002 20:54:23 - 1.4.2.2
@@ -15,8 +15,9 @@
private PDFGoTo internalLinkGoTo;
-private int pageNumber = -1, xPosition = 0,// x position on page
-yPosition = 0; // y position on page
+private String pageNumber;
+private int xPosition = 0;// x position on page
+private int yPosition = 0;// y position on page
/**
@@ -34,8 +35,8 @@
*
* @param number page number of node
*/
-protected void setPageNumber(int number) {
-pageNumber = number;
+protected void setPageNumber(String pageNumber) {
+this.pageNumber = pageNumber;
}
@@ -45,7 +46,7 @@
* @return page number of this node
*/
public String getPageNumber() {
-return (pageNumber != -1) ? new Integer(pageNumber).toString() : null;
+return pageNumber;
}
1.14.2.2 +3 -3 xml-fop/src/org/apache/fop/datatypes/Attic/IDReferences.java
Index: IDReferences.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/datatypes/Attic/IDReferences.java,v
retrieving revision 1.14.2.1
retrieving revision 1.14.2.2
diff -u -r1.14.2.1 -r1.14.2.2
--- IDReferences.java 2 Aug 2002 20:28:47 - 1.14.2.1
+++ IDReferences.java 30 Sep 2002 20:54:23 - 1.14.2.2
@@ -145,7 +145,7 @@
+ area.getTableCellXOffset() - ID_PADDING,
area.getPage().getBody().getYPosition()
- area.getAbsoluteHeight() + ID_PADDING);
-setPageNumber(id, area.getPage().getNumber());
+setPageNumber(id, area.getPage().getFormattedNumber());
area.getPage().addToIDList(id);
}
}
@@ -307,7 +307,7 @@
* @param id The id whose page number is being set
* @param pageNumber The page number of the specified id
*/
-public void setPageNumber(String id, int pageNumber) {
+public void setPageNumber(String id, String pageNumber) {
IDNode node = (IDNode)idReferences.get(id);
node.setPageNumber(pageNumber);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: character
-Original Message- From: Tony Graham [mailto:[EMAIL PROTECTED]] Sent: September 30, 2002 10:09 AM To: [EMAIL PROTECTED] Subject: Re: character Peter B. West wrote at 30 Sep 2002 13:28:18 +1000: Tony Graham wrote: [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300: ... That means -, #12235 , etc are characters, while '1' is not. #12235; is a character reference. '#12235' is how you talk about a character's code point, although the hexadecimal representation is usually preferable. In XSL terms, '1' is a one-character string literal, but while you could claim that it is one character, there's no XSL conversion from a string to a character, so fo:character character='1'/ should fail. Tony, I don't think this gets us out of difficulty. A casual inspection Forgive me, but I wasn't trying to get anybody out of any difficulty, I was just trying to keep the terminology accurate. ... So how do I represent a character? To me, the cleanest, least ambiguous way is to represent a character attribute assignment value with 'character' - a string literal of length 1. Except that you know that that's not specified among the allowed conversions. The interesting thing is that 'character' doesn't appear in the productions in Section 5.9, Expressions, of the XSL Recommendation. Now there's a question for [EMAIL PROTECTED]! I think that you represent a character as a single character, e.g., character=c, or as a numeric character reference, e.g., character=#xA;. I agree with this last, after having digested everything. Point is well taken that we have some points to nitpick with xsl-editors, mostly about disambiguating some of the language. Arved Sandstrom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: character
Arved Sandstrom wrote: -Original Message- From: Tony Graham [mailto:[EMAIL PROTECTED]] Peter B. West wrote at 30 Sep 2002 13:28:18 +1000: Tony Graham wrote: [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300: ... That means -, #12235 , etc are characters, while '1' is not. #12235; is a character reference. '#12235' is how you talk about a character's code point, although the hexadecimal representation is usually preferable. In XSL terms, '1' is a one-character string literal, but while you could claim that it is one character, there's no XSL conversion from a string to a character, so fo:character character='1'/ should fail. Tony, I don't think this gets us out of difficulty. A casual inspection Forgive me, but I wasn't trying to get anybody out of any difficulty, I was just trying to keep the terminology accurate. ... So how do I represent a character? To me, the cleanest, least ambiguous way is to represent a character attribute assignment value with 'character' - a string literal of length 1. Except that you know that that's not specified among the allowed conversions. The interesting thing is that 'character' doesn't appear in the productions in Section 5.9, Expressions, of the XSL Recommendation. Now there's a question for [EMAIL PROTECTED]! I think that you represent a character as a single character, e.g., character=c, or as a numeric character reference, e.g., character=#xA;. I agree with this last, after having digested everything. Point is well taken that we have some points to nitpick with xsl-editors, mostly about disambiguating some of the language. Arved, Help me here. I must be missing something. What is it that you agree with? That the spec, as worded, leaves us with character=c or character=#x63; which amounts to the same thing? If so, fair enough. Do you also agree that c is an NCName? And that character=- is a parsing error? As far as I can see, the only immediate ways forward are to descend into the mire of context dependent parsing (which the editors have recently formally decided that we must do in respect of format) or apply our own disambiguating condition. How are you intending to implement character? Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Antwort: fo wysiwig editor
Guys, I am one of the users of FOP for a very long time. I would like to get involved in this project as developer, if you guys start it regards Vaidya -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, September 30, 2002 8:39 PM To: [EMAIL PROTECTED] Subject: Re: Antwort: fo wysiwig editor Hi everybody, this discussion is getting too esoteric. I am willing to put effort into a new project as I have stated before. It basically depends on if we are able to gather a strong enough team. However, I think we should soon move the discussion somewhere else rather than polluting fop-dev. Any suggestions? Interested? Marc - Original Message - From: Mark Bitz [EMAIL PROTECTED] Date: Monday, September 30, 2002 4:39 pm Subject: Re: Antwort: fo wysiwig editor Hi, I agree with Marc. It's not robust enough and combersome to figure out. Mark - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 30, 2002 8:05 AM Subject: Re: Antwort: fo wysiwig editor Hi, I checked out XSLfast. It's a nice start. But not advanced enough for professional print in my opinion. Marc - Original Message - From: Oleg Tkachenko [EMAIL PROTECTED] Date: Monday, September 30, 2002 12:50 pm Subject: Re: Antwort: fo wysiwig editor [EMAIL PROTECTED] wrote: Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. btw, guys from jCatalog, which actually developed fop's awt viewer ended up with xslfast, see http://www.jcatalog.com/products/xslfast/index.htm. I cherish a hope *someday* our clumsy awt viewer will grow into a full-fledged xsl editor :) -- Oleg Tkachenko Multiconn International, Israel --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED ONLY FOR THE ADDRESSEE and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are notified that any dissemination, distribution or copy of this communication is strictly Prohibited. If you have received this message by error, please notify us immediately, return the original mail to the sender and delete the message from your system. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
