Re: Approaching a release?
Jay, thank you very much for your offer. We don't need to examine any credentials. If you want to help you're more than welcome to do so! I've just got the website refactoring back (off-list) from Patrick Paul and will examine that shortly. When the version split is in place I'll be grateful if you could help sorting out the details. On 13.10.2005 00:22:09 Jay Bryant wrote: Hi, Jeremias, If you need or want an editor for that documentation, let me know. As you know, I use FOP and look forward to the new edition. As you probably don't know, I'm a technical writer and editor (and, these days, half developer) with 19 years experience and a Master's degree in English. My current resume is at http://www.bryantcs.com/resume.html if you need to examine my credentials. I started using FOP because I got tired of paying large sums of money for crappy systems and decided to create my own document production system. Now it produces text, PDF, HTML, and WordML output, all with open-source tools (FOP and Saxon). Jay Bryant Bryant Communication Services - Original Message - From: Jeremias Maerki [EMAIL PROTECTED] To: fop-dev@xmlgraphics.apache.org Sent: Wednesday, October 12, 2005 1:37 PM Subject: Re: Approaching a release? If all had gone as planned we would have done the first preview release last month. As soon as I'm finished with my space resolution task (hopefully this week), I'm going to write all necessary documentation for the redesigned FOP and then we're pretty much ready to release. Note: alpha/preview release only! On 12.10.2005 20:16:43 David Abrahams wrote: As FOP is my only hope for a viable open-source alternative path to PDF, I have been eagerly anticipating your next release. Can anyone give me a sense of how close (or far off) that might be? Jeremias Maerki Jeremias Maerki
Volunteer wanted - disabled-testcases.txt in XML
I've had a idea, hopefully a good one. If the disabled-testcases.txt were rewritten as an XML file additional information could be added to each disabled test case why it is disabled. This information could be transformed by Forrest into a page (known issues) for our website. And it could even be used as content for a release notes document. Example: block-container_reference-orientation_bug36391.xml block_font-stretch.xml becomes: disabled-testcases testcase name=block-container_reference-orientation_bug36391 bugzilla=36391 Blah describes the deficiency of the test case blah. /testcase testcase name=block_font-stretch font-stretch is not implemented, yet. /testcase /disabled-testcases Anyone want to take a stab? No knowledge about FOP internals needed. Jeremias Maerki
Re: hyphenation-present and junit-layout
On Oct 13, 2005, at 21:50, Simon Pepping wrote: But basically, why would anyone want to run regression tests without hyphenation present? Good point. I guess if there weren't any tests that don't require hyphenation support, we wouldn't be having this conversation... Anyway, since we don't distribute any patterns with FOP anymore, enforcing hyphenation to be present would mean that running the basic layout regression test suite straight off the trunk code would always result in failure of the whole target --which sounds a bit drastic. Cheers, Andreas
DO NOT REPLY [Bug 36977] - [PATCH]TextLayoutManager CJK line break
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=36977. 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=36977 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #16627|0 |1 is obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2005-10-14 04:55 --- Created an attachment (id=16694) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16694action=view) new patch This new patch fulfill all rules mentioned in Comment #3 except Typesetting Adjustment R3 and shrink priority of R5. It use java.text.BreakIterator.getLineInstance(locale) to decide line breaking points, and use BreakIterator.getWordInstance(locale) to decide word boundary for implementing Typesetting Adjustment R1. Now, line breaking works well. * ISSUE NEED HELP * All the width of KnuthGlues inserted for Typesetting Adjustment appear at line end instead of their inserted position. I think I make mistakes about KnuthGlue and AreaInfo. I'm trying to dig it out. however, I hope someone can give me some hints. Is it caused by KnuthGlue/AreaInfo has no corresponding string? -- 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.
