Re: commenting the Knuth code/centering issue
Glen Mazza wrote: [BTW, I'm considering getting that Digital Typography book by Knuth you had mentioned earlier. Do you recommend it? (I was thinking that given all the time I spend on FOP I should start looking a little more at the scientific aspects of this work.)] Yes, a must read if you are into computer assisted typesetting. J.Pietschmann
DO NOT REPLY [Bug 31206] - [PATCH] Improvements over the new line breaking algorithm
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31206. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31206 [PATCH] Improvements over the new line breaking algorithm --- Additional Comments From [EMAIL PROTECTED] 2004-11-06 14:24 --- Luca, Leaders with content: in the test file leaders.fo I get PDF errors in the SVG parts. I have not checked the calculations of the vertical alignment. The provided test fo files, and some test files I created myself, behave well under the new code. I trust the code is OK. As Finn pointed out, vertical-align is a shorthand property in XSL. The values top, bottom, middle and baseline map to the values before-edge, after-edge, middle and baseline of the property alignment-baseline, with the properties alignment-adjust, baseline-shift and dominant-baseline being at their default values. Therefore I think if the current property vertical-align is renamed to alignment-baseline, the code will keep working fine, and the way is free to implement vertical-align as a shorthand property. InlineLM is now a class (created by Finn on Oct. 19). The hierarchy is: InlineStackingLM - InlineLM - LineLM The class InlineLM is at the position in the hierarchy where I think InlineLM interface should be. Therefore I think InlineLM class can well be merged with the proposed InlineLM interface. I think the code in this patch is OK for committing to CVS. The items noted above can be addressed over time. However, the patch as it is cannot be applied to the current version of CVS HEAD, due to the newly created InlineLM class and extensive changes in property retrieval. If you submit a patch of the same code against the current CVS HEAD, I will commit it. Or you can keep it until you have write access to CVS yourself. Regards, Simon
Re: commenting the Knuth code/centering issue
Jeremias Maerki wrote: No, I don't think Luca has write access, yet. I know by now that the CLA is recorded but the account hasn't been created, yet, although I've already sent a reminder. I have just received the e-mail confirming the creation of my account. I am now reading the http://www.apache.org/dev/ documents, so I should soon be able to work. Regards, Luca
Re: commenting the Knuth code/centering issue
Glen Mazza wrote: [BTW, I'm considering getting that Digital Typography book by Knuth you had mentioned earlier. Do you recommend it? (I was thinking that given all the time I spend on FOP I should start looking a little more at the scientific aspects of this work.)] I think it's very interesting. It is a collection of essays on various topics, and besides the one about line breaking (with fabulous features like paragraphs with different sized lines ...) there is one about bidirectional text, one about fonts ... It is surely an authoritative source on such matters. Regards, Luca
Re: cvs commit: xml-fop/src/documentation/resources/images group-logo.gif logo.jpg
On Nov 6, 2004, at 8:57 AM, [EMAIL PROTECTED] wrote: clay2004/11/06 08:57:40 Modified:.forrest.properties src/documentation sitemap.xmap skinconf.xml src/documentation/content/xdocs compliance.xml graphics.xml resources.xml site.xml src/documentation/resources/images group-logo.gif logo.jpg Log: Updates to achieve a /forrest/ BUILD SUCCESSSFUL for the xml-fop web site. I'm in the process of ironing out the 'final' glitches in the /forrest/ building of xml-fop. In spite of the comment above, we're actually not quite at the BUILD SUCCESSFUL I've been working towards for so many months. Among other issues, I've still got to fix some problems with the transformation of FO SVG files for the Examples Page dev/svg.html... In addition, I'm still working towards getting the Compliance page fixed. I've got it outputting some content, but we're still missing citations and some other stuff. But we're close! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: FOP Web Site Update
On Nov 5, 2004, at 6:41 PM, Glen Mazza wrote: Clay Leeds wrote: Well, it didn't happen next week or even the week after. Getting the FOP Standards Compliance page[1] up to snuff has been, shall we say... challenging. But I've finally got content (the table of 'compliance'!) displaying. Unfortunately, we're still not there, as the link portion (which serves as a veritable Table of Contents for the table) is not being generated yet. More importantly, the color-code system isn't working yet, either (the bgcolor is always 'white'). Also, the Citation links are not generated either. These should all prove relatively simple to resolve (especially if I had some help from someone who knows how to make that portion work: are you listening Keiron, Glen or Christian ;-) wink!). Or, I could just continue plodding through the muck and see if I can figure it out. The compliance page is quite difficult to understand, IIRC one needs to be fairly knowledgable about Cocoon sitemaps. But I last looked at it before I was a committer. I don't think the colors/sorting by compliance level are that important, however. The XSL spec lists each FO (and property, I believe) in terms of one of three compliance levels--but we don't need to duplicate that information on this page anymore. I think most people go to this page to determine if property X or formatting object Y is available, regardless of its listed compliance level in the specification. My intention at this point is to make the page work as well as it did before. Once that is achieved (and the FO + SVG transformations are either resolved or workarounds are made) I will put the new site live. As for the bgcolor of the table-cell I think helps one see, at-a-glance, the level of compliance. That is an important 'feature' to have--bordering on showstopper IMO. On a related note, IIRC I wanted to change the color scheme to Red - Amber - Green (stop light analogy: No - Partial - Full compliance--I'm aware of the argument about something either being compliant or it's not ;-)) [BTW, If you can change to the bright red color for the mouse-hover like the Web Services TLP has that would be nice.] Try it now: http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/ It's not 'bright' red (it's dark red - #66), but I think the contrast is subtle without being brash. Would you prefer #ff? One thing perhaps we should change sometime, is to remove/replace our leading graphic on our home page [1]. For a newbie to XSL, it looks silly: See with FOP, you need to create 75 lines of XSL in order to get one line of output! Hopefully we will have something better to replace it with in the future. Good idea. I recall being perplexed myself with that. Of course, that includes the soup-to-nuts information for an entire page, including page margins and page-sequence. I'm thinking of at least adding an image to the 'page'. Thanks, Glen [1] http://homepage.mac.com/webmaestro/xml-fop/images/document.jpg Thanks for your comments! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
DO NOT REPLY [Bug 32100] - FOP Starter Documents
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32100. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32100 FOP Starter Documents [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
DO NOT REPLY [Bug 32100] - FOP Starter Documents
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32100. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32100 FOP Starter Documents [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2004-11-07 06:00 --- I created this bug and assigned it to myself. Unfortunately, it didn't e-mail fop-dev when I did that. So I just unassigned myself (so fop-dev@ gets a copy), and am now re-assigning it to myself. NOTE: If any of you have 'starter' documents to share, I *would* love to get your ideas and contributions on this.
