How do you edit your XML files?
(I was tenpted to send this also to the xml-dev list which I also read, in the sense of admire the post that swoosh way over my head, as there has just been a short thread on XML editors; but I cross-post no more often than I spam). A curious ommission from the Apache's XML project is an Open Source XML editor. Perhaps the majority of people here use emacs/PSGMLS. But there must be many who do not wish to. vi users for a start. A 'proper' XML editor/IDE would be very useful for examining XML and FO files, parsing and validating them and processing with XSLT. Is there already a project in existence that does this? Would people here contribute to one? I am interested in The XML Editor, one that would run on the platforms that I use MacOS and KDE, and also ones that coworkers use, (MS Windows 98). If so, how should it be licensed, so as to be compatible with (as a minimum Xerces and Xalan) both now and in the future? Any thoughts or advice gratefully received. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Pls help....str.getBytes()
With reference to the following, does anyone know whether one must replace every reference to str.getBytes(), or r there some selected ones we can do only? http://marc.theaimsgroup.com/?l=fop-devm=99587281428987w=2 This message contains information intended solely for the addressee, which is confidential or private in nature and subject to legal privilege. If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message or any file attached to this message. Any such unauthorised use is prohibited and may be unlawful. If you have received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter delete the original message from your machine. Furthermore, the information contained in this message, and any attachments thereto, is for information purposes only and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of Dimension Data (South Africa) (Proprietary) Limited or is subsidiaries and associated companies (Dimension Data). Dimension Data therefore does not accept liability for any claims, loss or damages of whatsoever nature, arising as a result of the reliance on such information by anyone. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information transmitted electronically and to preserve the confidentiality thereof, Dimension Data accepts no liability or responsibility whatsoever if information or data is, for whatsoever reason, incorrect, corrupted or does not reach its intended destination. I am really only writing to refer you to the Stupid Disclaimers page URL: http://www.goldmark.org/jeff/stupid-disclaimers/ , as you changed 'are' to 'r' to save two 7-bit bytes! The short answer is that this is a java problem. I hope that FOP will not move away from 100% pure java without very good reason. If adding the requested encoding is machine/OS specific then should we encapsulate this issue by deriving from String? Either way, any change should be fully consistent with FOPs internationalisation mechansims. I would guess that the medium length answer is yes, all of them you might be better catching the exception at an appropriate point and reporting it. If you are not familar with encoding in java, then you might want to look here URL: http://www.oreilly.com/catalog/javanp2/chapter/ch11.html , or URL: http://users.erols.com/eepeter/chinesecomputing/programming/java.html URL: http://java.sun.com/products/javamail/FAQ.html where encoding is mentioned in passing. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PROPOSAL] linebreak
At 2:58 pm + 26/2/02, ewitness - Ben Fowler wrote: [ snip ] In FO, you could write fo:block space-before=3pt fo:block space-before=0some line/fo:block fo:block space-before=0next line/fo:block /fo:block OK I have tried the FO in the attached file, giving the expected PDF result. Even if I haven't the facility that I want, There is a good, and fairly logical work-around. Ben. line-break.fo Description: Binary data line-break.pdf Description: Adobe PDF document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PROPOSAL] linebreak
[EMAIL PROTECTED] (ewitness - Ben Fowler) wrote: [snip] I don't mind admitting that as an outsider to the XML standard, this looks like a bad, even a really bad, idea. My reading of your commentary is Whitespace is sometimes respected, and only a langauge lawyer can tell you when. Well, in some sense you are right, there are a lot of really bad ideas hidden in this area. However, you have to see this in context. I most certainly am looking at it in context. I was trying to do something simple and intuitive and it turned out gnarly and difficult. XML is meant to build on other things such as SGML, DSSSL and HTML by avoiding their mistakes. A *real* typesetter doesn't care about whitespace and line feeds, he thinks in paragraphs and columns and pages of flowing text, with various indentations and margins and such. Exactly so, and he thinks of leading and line height, and he thinks of paragraphs with 'space before' and 'space after'. I am prepared to argue that FO is a 'real' typesetter here, and should 'think' the same way. TeX was practically written to support this view, and this is the default how FO processors work. Quoting from the XML-dev list, a gentleman wanted to play space cadets and we got unix, another gentleman wanted to distribute his phone list and we got the WW web. Pretty much every worthwhile advance in the computer field has come from one person with a problem to solve. TeX came about because Professor Knuth URL: http://www-cs-faculty.stanford.edu/~knuth/ knew that computers could aid typesetting: it was written with one practical aim, rather than supporting a view. I don't see how you can argue that because TeX has \newline and \par it follows that FO should not have a semantic br / or forced line-break. The problem: not everybody is a typesetter, many people don't even know about how to set indents and hanging indents and margins and this stuff, but they have a space and an enter key sitting squarely on their keyboard. I may have misread you, but I think that you have intertwined two, possibly three things. 1. Not everybody is a typesetter ... Exactly, this is why there is a division of skill or labour. Authors write and typesetters mark up and set text. This is TeX 101, exempli gratia URL: http://www.ideography.co.uk/library/seybold/WYS_intro.html , and URL: http://www.ecn.wfu.edu/~cottrell/wp.html The author of a text should, at least in the first instance, concentrate entirely on the first of these sets of tasks. That is the author's business. Adam Smith famously pointed out the great benefits that flow from the division of labor. Composition and logical structuring of text is the author's specific contribution to the production of a printed text. Typesetting is the typesetter's business. This division of labour was of course fulfilled in the traditional production of books and articles in the pre-computer age. The author wrote, and indicated to the publisher the logical structure of the text by means of various annotations. The typesetter translated the author's text into a printed document, implementing the author's logical design in a concrete typographical design. One only has to imagine, say, Jane Austen wondering in what font to put the chapter headings of Pride and Prejudice to see how ridiculous the notion is. Jane Austen was a great writer; she was not a typesetter. You may be thinking this is beside the point. Jane Austen's writing was publishable; professional typesetters were interested in laying it out and printing it. You and I are not so lucky; if we want a printed article we will have to do it ourselves (and besides, we want it done much faster than via traditional typesetting). Well, yes and no. We will in a sense have to do it ourselves (on our own computers), but we have a lot of help at our disposal. In particular we have a professional-quality typesetting program available. This program (or set of programs) will in effect do for us, for free and in a few seconds or fractions of a second, the job that traditional typesetters did for Shakespeare, Jane Austen, Sir Walter Scott and all the rest. We just have to supply the program with a suitably marked-up text, as the traditional author did. I am suggesting, therefore, that should be two distinct ``moments'' in the production of a printed text using a computer. First one types one's text and gets its logical structuration right, indicating this structuration in the text via simple annotations. This is accomplished using a text editor, a piece of software not to be confused with a word processor. (I will explain this distinction more fully below.) Then one ``hands
RE: [PROPOSAL] linebreak
[EMAIL PROTECTED] (ewitness - Ben Fowler) wrote: [snip] [snip ] I meant correct way to express the presentational aspects with XSLFO. There was no intention to feed this to a Pascal compiler. The use case was I have some Foo source code and want to include it in my printed manual O.K. I was a bit harsh there, but I was trying to make the point that some blocks in a ideal presentational system, such as comments would flow, but others such as code statements and expressions would not. If you want to have your specific (XML) data presented on a 2D area like paper sheets or a computer monitor screen, you probably have to 1. Assign some presentational semantic to your specific data elements like para or proc or record or author 2. Apply some commonly used concepts like kerning, space justification, word wrapping and such stuff XSL, both T and FO, attempts to make this possible, and XSLFO is the second part: a vocabulary for describing the presentation of stuff on a 2D area, perhaps splitted into a page stream (disregard audible properties, whose inclusion is just plain silly). (divided, or divided up rather than splitted) My gripe is that your (2) above should include kerning, ligatures, justification, bidi, word wrapping, hyphenation, forced line break, rubber space, widow/orphan control, keeps, insert space and such stuff. Depending on your point of view, you can see either of the two steps or both together as the equivalent of typesetting. Which is why I say [RETURN] for end of paragraph - /p, and [SHIFT][RETURN] for end of line - br /; to make the easy way the right way. XSLFO does not assign semantics to FOs beyond what's necessary to get them layed out. It does not have a concept of paragraph, and the concept of line is not necessarily the same as what for example software manual writers or java compilers use. Note that there is no fo:line and no fo:para, just a fo:block, which is *not* a paragraph. (laid out) And from my POV, that is a pity. I do think of a block as a paragraph, and my enter key or ETAG ending a paragraph and inserting the specified vertical space. 'lines' are largely the result of layout engine working with line length against word wrap, hyphenation and forced line break. I don't dispute the practicality of what you describe, I merely question the benfits of it. Further note that HTML p has paragraph semantics, this means some space before and after by default. Also, in early HTML there was no possibility at all to restrict the, well, lets call it page width. Therefore you could not simply write psome line pnext line in order to get a managable line length, it would result in a line spacing making it unreadable. In FO, you could write fo:block space-before=3pt fo:block space-before=0some line/fo:block fo:block space-before=0next line/fo:block /fo:block if you want to have your content formatted this way. I can't see a need for a br equivalent in FO. 'Page width' is set by the user, he or she can set the width of the browser to what suits that person, it is little to do with HTML. If I can use HTML as an example, (which is not in general a good idea), then this fragment H1MacHTTPBR An early web server/H1 really needs the BR, as H1MacHTTP/H1 H1An early web server/H1 is not the same in structure or presentation, and there is no other way (outside of CSS) of getting the required presentation. Obviously FO does not have this problem. Your example is interesting might work for me. The outer blocks represent paragraphs and the inner ones (typically only one) lines. I will try this before posting again. Another note: in TeX, semantic markup and presentational aspects are mixed in a sometimes annoying way. True Conclusion: If you want to write documents, use DocBook, not XSLFO. DocBook btw contains linebreak elements, probably for some reasons already mentioned, and apparently there are no difficulties to map them to FOs. Again I will check that. I was working from a starting point of generating/editing FO by hand. Certinly, I would recommend DocBook for serious authoring. FO is so like WordPerfect codes, that it seems a shame to make it gratuitously non-editable In order to clean up the seemingly contradiction that FO also allows for interpretation of LF characters: If you have already properly marked up text for lines, you can transform it (probably easily) into FO blocks. If you pull in whitespace formatted data from a file or DB or something, you might want to have the FO processor respect the existing formatting rather than to analyze and properly transform the whole stuff. That's a quick hack to fill a gap. I already experienced some times that the result is not as good as it should be and someone still has to wade through the data and convert it to properly marked up (or at least properly structured) data (usually leading to hot debates about what *is* the structure behind the formatting?) Which is also (I
RE: [PROPOSAL] linebreak
I guess the reason nobody thought fo:br/ or fo:newline/ would be required is because a U+000A will do the trick. [ snip ] In any case, a linefeed (LF) must be honoured, and result in a linebreak. _If_ the conditions are right. What that means is, the initial value for linefeed-treatment is treat-as-space, which _does_ do a conversion of U+000A to U+0020 (space). So you would want to specify linefeed-treatment='preserve' on an ancestor flow object (possibly fo:root) and allow it to propagate to the FOs of interest, as it is inheritable. The whitespace-* properties do not affect the linefeed, and suppress-at-line-break can also be left as it is. But essentially the LF is there to accomplish what you want to do. The initial setting of linefeed-treatment acts to give us LaTeX-like behaviour, but unlike LaTeX we can switch to something different in this regard, rather than use new markup. The answer that you gave is also to be found a few lines down from the first URL I gave you 4. Forced line-breaks are respected. Specifically, if A is the glyph-area generated by a fo:character whose Unicode character is U+000A, then A must be the last area in its containing subset Si. I don't mind admitting that as an outsider to the XML standard, this looks like a bad, even a really bad, idea. My reading of your commentary is Whitespace is sometimes respected, and only a langauge lawyer can tell you when. How should this be interpreted? Do you think that HTML would be improved if the BR element was replaced with a feature that said You can get the effect of a forced linebreak by setting 'linefeed-treatment' to 'preserve' in the body of the page (or other container as required), which causes all unix line feeds to be rendered instead the br / element which is what was done? From my POV this has an inhibiting effect on all editors and pretty printing utilities, which must also respect exisiting white space (as XSL processors do) and never introduce line feeds, in case this setting was ever turned on. From my POV, a formatter should always ignore the formatting of the source, unless notified that it is preformatted as in the case of PRE and CDATA, exempli gratia URL: http://archive.ncsa.uiuc.edu/SDG/IT94/Proceedings/Autools/sperberg-mcqueen/sperberg.html , (1994) about half way down. Do you happen to know whether this was ever discussed (id est objections sought and answered) or whether this was one person's idea that was incorporated as is. I have a related 'issue' which is that the normalize-string( ) function in XSL does two things. It trims leading and trailling newlines and other whitespace, and it normalises internal white space. I have a need for an operation that does the former, but not the latter. (In fact I have an implementation which appears to be buggy and replaces 'Miss A Burgrave' with Miss ABurgrave', but handles 'Miss A Burgrave' correctly. In short, XML processors including ones that produce XML-FO files should pass through all whitespace, and processors such as fop which are also XML processors, but adjusted so that they do not produce XML, should (at least in general) normalise whitespace. Where the output file format respects whitespace then it should be supplied as fo:text or as some break (as my original suggestion) The present situation is that the latter type of processor may not normalise whitespace, because some newlines are significant. Incidently, you have not made (or reported) a case against my suggestion: unless it is harmful (or confusing) there is no real reason why both styles of indicating significant breaks could not be used, is there? Using FOP derived from version 0.14, I get this report when I tried the following .fo WARNING: property 'linefeed-treatment' ignored WARNING: property 'linefeed-treatment' ignored setting up fonts formatting FOs into areas [1] rendering areas to PDF (source) ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; text-align=justified font-size=12pt font-family=serif linefeed-treatment='preserve' fo:layout-master-set fo:simple-page-master margin-right=50pt margin-left=100pt margin-bottom=25pt margin-top=75pt master-name=all fo:region-body margin-bottom=50pt / fo:region-after extent=25pt / /fo:simple-page-master /fo:layout-master-set fo:page-sequence id= hyphenate=true master-name=all language=en fo:flow flow-name=xsl-region-body fo:block linefeed-treatment='preserve' Bilbo Baggins,
RE: [PROPOSAL] linebreak was Re: REDESIGN: where I have beenhiding
This would be useful in writing addresses exempli gratia: ?xml version=1.0 encoding=UTF-8? fo:root text-align=justified font-size=12pt font-family=serif fo:block Bilbo Baggins,fo: newline / Bag End,fo: newline / Underhill,fo: newline / Hobbiton,fo: newline / Westfarthing of the Shire. /fo:block /fo:root At present, I can get the effect I want with tables. Ben. -end of Original Message- I guess the reason nobody thought fo:br/ or fo:newline/ would be required is because a U+000A will do the trick. Thank you. I had assumed that that character would count as white space, and would be normalised away. I will try it. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DocBook XML-FO, getting started was Re: Clueless Newbie is lost!
Assuming you really are a 'Newbie', you will profit from reading the famous 'Choosing good subject lines' post, archived here URL: http://www.perl.com/CPAN-local/authors/Dean_Roehrich/subjects.post , and won't be offended by my pointing you to it. Assuming you really are Clueless (which is an insult on my side of the Atlantic), I guess that you have perused Phil Greenspun's site on technical book authoring, and someone other than yourself has determined that the World needs yet another book on HTML. URL: http://philip.greenspun.com/wtr/dead-trees/story.html Folks, I am writing a textbook on HTML, and want to include a chapter on XML. People who are 'switched on', and ready to write sites based on their information content should already be using XML, in the form of the W3C XHTML. Indeed, you might be able to find evidence that HTML 4.0 is entering 'End Of Life'. I hope that this chapter was the first chapter of your forthcoming book. URL: http://www2.widener.edu/Wolfgram-Memorial-Library/webevaluation/inform.htm I am trying to get the following code (DocBook) to generate a PDF file. After a LONG struggle I managed to xsltproc to use my XML and get the HTML to render...but the PDF eludes me. Can y'all see anything wrong with the following code? When it is generated, by someone who knows what he is doing, the block quote stuff just disappears...the cite stuff renders just fine??? What I am trying to do is simply show my student/readers how XML can be used. I have spent over 70 hours trying different software to no avail. Ideas welcome! What I really need is a reliable tool-chain to take XML and generate HTML, PDF, and maybe one other format that I could capture and show the students. I can't answer precisely the question on the tool chain. In the case of SGML, the identical operation is typically done by jade URL: http://openjade.sourceforge.net/doc/index.htm (Note: It is a couple of years since I last looked at jade, and it has moved on a fair bit. It is possible jade might in fact do what you want, but I doubt it). I believe that cocoon URL: http://xml.apache.org/cocoon/index.html will simultanenously produce (amongst other things) PDF, HTML and RTF - this is probably what you want. Furthermore, cocoon runs inside the apache web server, which ties in with the topic of your book Can anyone help? Thanks in advance! tim ?xml version=1.0? ... [ snip ] I am using the docbook that came with the Duck book, which is version 315. This is possibly too old for serious work. When I attempted to validate your document, I got this (one) error. XML-Validity: Your XML is a well-formed document, but it conflicts with the DTD: Element 'blockquote' (blockquote There were many paths that lead up into those mountains, a) didn't contain the element 'beginpage', which it should have done. DTD constraint: !ELEMENT blockquote (title?, attribution?, (calloutlist | glosslist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | informalequation | informalexample | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | anchor | bridgehead | comment | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+) This error might not be present on your system The Duck book CD has a file called 'docbook.xsl' in the folder 'DOCBOOK:style:xsl:docbook:fo:docbook.xsl' and this is the one that I used. It is right next to the ::html:docbook.xsl that you used to get the html. I processed your document with MacXSLT to get a .fo file. URL: http://catcode.com/macxslt/ , and then processed the resulting .fo file with MacFOP, which is a Mac FOP executable that is not (nor will ever be) ready for public performance. There were some major things to fix, of which the most obvious was the fact that the xsl produced page-master-name but FOP wanted master-name and in fact I was not able to get a clean rendition of your document, but I think that I could do so if it were important. MacXSLT is based on xalan exempli gratia URL: http://www.xml.com/pub/r/183 , and unless you are using a Mac, in which case you could also use MAcXSLT, I suggest you get an XSLT processor for your platform, based on xalan. This may not be quite enough to get you started, in which please post again. BTW, there was nothing wrong with your question, and you get extra credit for having enlisted the help of your local expert, but your below average Subject line probably meant that those who know about docbook - FO probably read no further. Ben. P.S. Rather than publish a new
Generating output from XML was Re: Clueless Newbie is lost!
Thierry, I guess I am so new to this that I don't know what you mean by formatting? I thought that XML was formatless (if that is a word), in that the DTD and the style sheets did all the formatting? Not the DTD (which is optional for XML), and provides constraints for an xml file. Yes, a stylesheet is needed for formatting (though in fact a style sheet can do any transformation). I wouldn't describe XML as formatless. XML, I would say, is format agnostic, in that it can exist without any presentational elements or attributes at all, or it can have full formatting information as an .fo file does. The usual elementary XML book recommendation is the chick book, which is reviewed here URL: http://training.gbdirect.co.uk/book_reviews/learning_xml_review.html , you want to have a glance through the whole of it, because the author seemed to run out of steam (or pages) at around the point that he got to the areas we are discussing; but the early chapters are so good, that you may not feel that this is a problem. If you check through some of the current discussions on the XML list, you will see that the ability to write XML, like the ability to write in plain text, depends on having something worth saying, and knowing how to say it. It is not a magic bullet. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Working on an Open Source Project was RE: Seeking Comments onStatus of Project
So what is your point? - that we need a whole lot more people working on this. We already know, either people will volunteer or they won't. - that you don't know how to help. You said you can see problems. Tell us you are going to fix those problems. Then do it. Well, now that I consider it more, I have to say that I guess I am just used to a corporate way of developing software that has a definite administrative structure and plan of action with people assigned specific tasks. Since I've never worked on an Open Source project, it justs seems sort of anarchistic to me. Maybe it'll be fun -- it justs seems like a lot of code, documentation, and examples to just jump into. There is some introductory guidance on this, exempli gratia: URL: http://www.advogato.org/article/429.html URL: http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/ URL: http://www.kbasic.org/1/join.php3 URL: http://www.newsforge.com/article.pl?sid=01/07/11/185221 URL: http://www.mozilla.org/hacking/ Though Mozilla is more organised and disciplined than a lot of OS developers prefer URL: http://www.tuxedo.org/~esr/faqs/hacker-howto.html This may be a bit too general. URL: http://www2.abisource.com/mailinglists/abiword-dev/99/December/0264.html This contains the single best description of how not to look out of place on an OS project, really the OS Initiative URL: http://www.opensource.org/ ought to be invited to get the authors permission Paul Rohr ([EMAIL PROTECTED]) and place a version of it somewhere on their site. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Help with footer only on first page - please help
At 8:50 am +0200 25/1/02, [EMAIL PROTECTED] wrote: Hi all, Could someone please help me with the correct way to implement a footer only on the first page? I believe that you need to establish two sequences of master pages, and use one (which has the footer) on the first page, and the other for the remainder. This might be an FAQ. You can certinly find helpful info on the web exempli gratia URL: http://www.dpawson.co.uk/xsl/sect3/headers.html Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Please help...
At 9:15 am + 23/1/02, Nick Winger wrote: hi ! i have three questions using fop ( with tables ): 1. i want to generate a pdf dynamically using java. now first i write a dynamically fo file (formatted objects): on the pages there is always a text ( form start to the middle of the page) and below ( the other half os the page) an image: now when i write the text in java: how can i recognize when i reach the half of the page ? should i divide the half page points with the font-height and count the rows ? I don't think that FOP can do this. Would you get what you wanted if you put the image in a footer. I doubt that counting the rows is the way to go. 2. is it possible to have two different font-sizes in one column of a table? Yes. 3. can i turn the bottom cell line (border) of a cell off ? I don't know. Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: refocusing fop-dev and fop-user?
Yes, I'll ensure this happens. Arved On Friday 25 January 2002 10:26, Jens von Pilgrim wrote: . . . On http://xml.apache.org/mail.html is only the fop-dev listed - is there also a user list? This is probably the cause - AFAIK fop-user is alive and kicking, just not listed in the proper places. Can anyone clarify the situation and/or make sure fop-user is listed in the right places? - Bertrand I read both lists, and what I find more curious is that people post development related questions to the user list: there must be little chance of an answer, and no chance of a good answer. The user list is advertised here URL: http://xml.apache.org/fop/index.html . Ideally, the fine folk at Apache could be requested to also advertise the developers list and point to both charters fop-user is currently not at URL: http://xml.apache.org/mail/ , as implied above; but none of the user lists are, only -dev and -cvs; so maybe the Apache people are happy with the arrangements for archiving the lists. The fop-dev list is searchable at URL: http://marc.theaimsgroup.com/?l=fop-dev as is fop-user URL: http://marc.theaimsgroup.com/?l=fop-user fop-dev and fop-user are properly referenced from the FOP resources page, URL: http://xml.apache.org/fop/resources.html . The Cover pages have a page of SGML lists and groups which has fop-dev but not fop-user. URL: http://www.oasis-open.org/cover/lists.html Ben. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: inserting unicode checkbox characters
I'm trying to add some Unicode check boxes to a PDF document created by FOP. If I use #x2610; or #x2612; then only a pound sign (#) is printed where I expect the check boxes to appear. I tried setting the XML encoding to UTF-16 in my XSL document, like this: I think that I have met the same problem, which I solved by using decimal numbers, exempli gratia these entities #8220 #8221 are left and right double quotes. Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
