Re: Extend compliance document
A couple of additional things that could be investigated and documented (in the compliance document and with test cases): - keeps with .within-line (i.e. inline keeps) - the amount of space resolution we do (probably not so much and not too good, see space-before/after.conditionality) On 09.08.2005 17:14:55 Jeremias Maerki wrote: Welcome! What I didn't tell you earlier today when you wrote to me was that Manuel Mall and I have already done most of that work during the last few days. There are still a few TODO items in the compliance document itself some of which Manuel already addressed by writing testcase. There are certainly a few other details left to be sorted out but I think we're almost fine. However, having test cases especially for certain properties (like baseline-shift and the whole whitespace-related set of properties) would be really good to have. What I would like to suggest to you is that you set up FOP Trunk (from SVN) on your machine together with the latest Forrest release. Docs on doc management are here: http://xml.apache.org/fop/dev/doc.html When you're done with that familiarize yourself with the layout engine test cases in the test/layoutengine directory. The following Wiki page will help you understand who that stuff works: http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests About how to find out about the capabilities of FOP trunk is not quite straight-forward because we obviously don't have too much documentation, yet? :-) Source of information are the layout engine test cases, the source code and us developers. Don't hesitate to ask questions. We're glad to have people around us to help us. I assume you're already a FOP user, so if you have FO documents to run through FOP, please do that and help us identify problem points. Creating isolated, minimal test cases out of these problems is a big step towards documenting and fixing them. On 09.08.2005 16:57:52 Patrick Paul wrote: Hi, My name is Patrick Paul and I just joined the fop-dev mailing list. As a first contribution to the project, I would like to extend the compliance document to show 1.0dev capabilities and allow comparison between 0.20.5 and 1.0dev. Afterwards I hope to extend the documentation in general. For now, I have the following question: where do I get the information about the capabilities of FOP-1.0dev ? Patrick Paul Jeremias Maerki Jeremias Maerki
DO NOT REPLY [Bug 36112] New: - [PATCH] Java2d renderers not showing regions other than body
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=36112. 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=36112 Summary: [PATCH] Java2d renderers not showing regions other than body Product: Fop Version: 1.0dev Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: awt renderer AssignedTo: fop-dev@xml.apache.org ReportedBy: [EMAIL PROTECTED] Because RegionReference didn't clone the blocks list, when Java2DRenderer cloned the PageViewport, it lost the start, end, before and after sections of the Page. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36112] - [PATCH] Java2d renderers not showing regions other than body
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=36112. 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=36112 --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 10:34 --- Created an attachment (id=15992) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=15992action=view) Patch for Java2D regions bug, caused by RegionReference blocks list -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 14349] - redesign awt viewer as embeddable viewer bean and application, which uses it
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=14349. 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=14349 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 10:38 --- Fixed with FOP viewer enhancements in 1.0dev. See org/apache/fop/render/awt/viewer/PreviewPanel.java for details. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36067] - [PATCH] Support for relative font sizes
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=36067. 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=36067 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 11:17 --- Applied. Great job! Thanks, Manuel! http://svn.apache.org/viewcvs?rev=231198view=rev -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: Extend compliance document
Cool. Just yell if you need help. On 10.08.2005 14:21:14 Patrick Paul wrote: Thank you for the tip ! I will follow your advice and start by familiarizing myself with the layout engine and existing documentation in the next few days. Then I will get down to work ;-) Regards, Patrick Paul Jeremias Maerki wrote: A couple of additional things that could be investigated and documented (in the compliance document and with test cases): - keeps with .within-line (i.e. inline keeps) - the amount of space resolution we do (probably not so much and not too good, see space-before/after.conditionality) On 09.08.2005 17:14:55 Jeremias Maerki wrote: Welcome! What I didn't tell you earlier today when you wrote to me was that Manuel Mall and I have already done most of that work during the last few days. There are still a few TODO items in the compliance document itself some of which Manuel already addressed by writing testcase. There are certainly a few other details left to be sorted out but I think we're almost fine. However, having test cases especially for certain properties (like baseline-shift and the whole whitespace-related set of properties) would be really good to have. What I would like to suggest to you is that you set up FOP Trunk (from SVN) on your machine together with the latest Forrest release. Docs on doc management are here: http://xml.apache.org/fop/dev/doc.html When you're done with that familiarize yourself with the layout engine test cases in the test/layoutengine directory. The following Wiki page will help you understand who that stuff works: http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests About how to find out about the capabilities of FOP trunk is not quite straight-forward because we obviously don't have too much documentation, yet? :-) Source of information are the layout engine test cases, the source code and us developers. Don't hesitate to ask questions. We're glad to have people around us to help us. I assume you're already a FOP user, so if you have FO documents to run through FOP, please do that and help us identify problem points. Creating isolated, minimal test cases out of these problems is a big step towards documenting and fixing them. On 09.08.2005 16:57:52 Patrick Paul wrote: Hi, My name is Patrick Paul and I just joined the fop-dev mailing list. As a first contribution to the project, I would like to extend the compliance document to show 1.0dev capabilities and allow comparison between 0.20.5 and 1.0dev. Afterwards I hope to extend the documentation in general. For now, I have the following question: where do I get the information about the capabilities of FOP-1.0dev ? Patrick Paul Jeremias Maerki Jeremias Maerki Jeremias Maerki
DO NOT REPLY [Bug 35998] - [PATCH] rtflib independance from FOP
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=35998. 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=35998 --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 14:37 --- Yeah, it is caused by the refactorings described in the previous comments. (Geez, I did not know that the tests were still up-to-date: the link on the dev RTFLib web page were broken so I though it was lost or abandonned during the jfor-to-FOP move! Nice to know ;)...) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36120] New: - fix the height of cell in a table
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=36120. 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=36120 Summary: fix the height of cell in a table Product: Fop Version: all Platform: All OS/Version: other Status: NEW Severity: blocker Priority: P2 Component: general AssignedTo: fop-dev@xml.apache.org ReportedBy: [EMAIL PROTECTED] how do i fix the height of a cell in table. 1.If i use height property then the cell height increases if the text overfows. 2.If i use a block-container then the image in that cell is not displayed. i actually have to fix the position of an image with respect to top or bottom of page. i am using xsl 1.1 version -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36120] - fix the height of cell in a table
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=36120. 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=36120 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 15:10 --- Please don't use Bugzilla to ask questions. Please send your question to the fop-users mailing list next time. Thank you! (In reply to comment #0) how do i fix the height of a cell in table. 1.If i use height property then the cell height increases if the text overfows. That's what the specification defined. A table-cell has to grow in block- progression-dimension (i.e. vertical normally) until the content fits into the cell despite the height property. The height property in this case only defines a minimum. Please see http://www.w3.org/TR/xsl/slice7.html#height and http://www.w3.org/TR/REC-CSS2/tables.html 2.If i use a block-container then the image in that cell is not displayed. i actually have to fix the position of an image with respect to top or bottom of page. i am using xsl 1.1 version More interesting would be what FOP version you use. Can you supply a simple (!) FO file that shows what you tried to do? You can save us a lot of time that way. Thanks. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36082] - [PATCH] Relative URIs are not correctly resolved
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=36082. 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=36082 --- Additional Comments From [EMAIL PROTECTED] 2005-08-10 17:46 --- (In reply to comment #8) - URI resolution using XML Commons Resolver should be possible, i.e. URIResolver and ideally EntityResolver should be supported, i.e. FOP should be able to extract the necessary infos out of Source and InputSource instances when loading images. Are you thinking of having set/getURIResolver methods on FOUserAgent? Exactly. - Investigate ImageIO as an alternative means to load GIF. Hmm, want to look at some other items in the image handling stuff first. That's ok. One thing after the other. :-) You may have seen, I've uploaded the initial ImageIOImage implementation. http://svn.apache.org/viewcvs?rev=231223view=rev -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
