DO NOT REPLY [Bug 16156] - 0.20.5rc SVG example does not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16156 0.20.5rc SVG example does not work --- Additional Comments From [EMAIL PROTECTED] 2003-01-16 11:09 --- Cannot reproduce the problem, provide more details - how do you run FOP, what is debug trace etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ready for 0.20.5 from my side
Victor Mote wrote: Isn't it just copying xml-fop directory back? I don't understand. Copying it back from where? Do you mean: 1. We should make our own backup copy on the server before doing the surgery? If so, that makes sense. Space is tight on that x1 filesystem, but it looks like that directory is only about 97 MB its probably very compressible. Yes, that's what I've meant. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Feeding the dogs
'But the woman came and did him homage, saying, Lord, help me. He said in reply, It is not right to take the food of the children and throw it to the dogs. She said, Please, Lord, for even the dogs eat the scraps that fall from the table of their masters.' (Mt 15:25-27) A recent incident involving a new open source implementation of XSL-FO raised, for me, a number of issues about the relationship between the various tiers of developers in open source implementations. I detail this event only to draw attention to the general principles. One of the editors recently announced, on behalf of the major corporation by which he is employed, a new implementation with the code slated for publication. What raised a few eyebrows was that there was in progress on SourceForge another implementation realised in a similar software environment, and to that point, there had been no hint of the existence of the corporate project. In the conversations that followed, the editor explained that the lack of communication between him and the SourceForge developers was mandated by procedures within his corporation. This raises a number of interesting issues about the relationship between those corporations which are active in open source development, the high profile open source foundations like Apache, and the large group of committed open source developers. However, it was the fact that corporate implementor is also one of the editors of the specification that intrigued me. I have no idea what life is like for implementors of other W3C Recommendations, but down here in XSL-FO land it's kinda tough. The spec is complex and, quite understandably, has required many clarifications on quite significant points, not to mention relatively minor points. Implementing this spec was always going to be difficult. I cannot speak for other implementors. but for me personally, it has turned out to be extremely difficult. It may be an unusual view, but in my experience, successful implementation requires that a model of the specification and its resolution be built up at many levels, from the most general and abstract to the most particular. Some have it that the levels can be constructed in isolation, but if that were the case, there would be no requirement for implementation support before a W3C Recommendation were accepted. In fact the models at different levels interact in shockingly intimate and often unpredictable ways. The better understood the basic processes being modelled, the more likely that such interaction and the design groping, probing, trial and backtracking that underlies all software development will become merely the ancestral memories of 'patterns' and other well-tested habits of software thought. For whatever reasons, that is not the case with XSL-FO. Because such is not the case, design sketches have been very fragile and highly susceptible to discoveries made during the detailed design of fragments. I have always found in such circumstances that the models I construct to guide the implementation must be as comprehensive as I can possibly make them. One has to be aware of every wrinkle in the development of the models if one hopes to keep control of the design, but awareness often comes only after traversing a number of blind alleys. Once all of this has been done, the result will hopefully look clean, modular, robust and obvious. The process of getting there will be anything but. I am trying to paint a picture of the peculiar agony of difficult software design, as I have experienced it. My experience may be peculiar in the extreme, though I doubt that. Think of riding a unicycle on a high-wire between the twin towers, clasping a copy of the spec and making notes while trying to keep track of seven different references with the fingers of one hand. To this obviously unstable configuration, add a number of ambiguities in the spec, and watch what happens. I would have thought all of this more or less self-evident, as I would have thought obvious the impact on effectiveness and motivation of developers of the presence of long-unresolved questions about the spec. It seems, however, that I may have been too sanguine in this assessment. The editors do not seem to appreciate it. That is too bald a statement. At least one of the of the editors, to my knowledge, has expressed a concern about the speed of resolution of developers' enquiries. For all I know, this concern is shared by all of the editors. Nonetheless, the problem remains. It can take a number of months to get responses to questions. That's not the worst of it, because often enough the response will raise further questions. What to do? When one is on the design unicycle, the only way to stay upright is to keep moving. After a few of these experiences, one gives up on the nineteenth century pace of conversations with the editors, and takes a punt on the interpretation of certain design features. At least one can proceed. If every
Re: Ready for 0.20.5 from my side
Oleg Tkachenko wrote: Jeremias Maerki wrote: I'll continue to do the directory moves in the redesign and I'm still hoping for a volunteer to do the server side move/copy of the src/org directory to src/java/org. It's easy, but we'll loose ability to build old revisions then (didn't we yet?). If it's not an issue, all we have to do is to move the I think it's an issue and therefore I'm favouring local moving (which will lose history and revision numbers, see http://www.loria.fr/~molli/cvs/doc/cvs_7.html#SEC64 ) But is it worth the effort? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: File size improvements for PS renderer
Arnd Beißner wrote: Hi Jeremias, I just submitted the PS renderer fix/enhancement I recently mentioned to BugZilla, bug #16130 [..] Hope you can still get this into 0.20.5, I just tested your patch and it looks good. I'm inclined to commit the patch. Other opinions? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
generate pdf files and print them to a specific paper bin
I want to generate pdf files and print them to a specific paper bin. How can I do this? Can I do this while using fop to generate the PDF. When the PDF is printed I want the first page to be printed on letter head paper and all the others on plain paper. Any help will be appreciated. Thanks Manoj Unnikrishnan __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Benoit, In the FOP schema I developed, there's a set of switches that you have to edit in order to differentiate between what is and is not supported in FOP. The schema, as I provided it, validates for the full FO spec. You need to go in and comment out the templates with a name of ???_NOT in order to exclude those elements that are not supported. There are also individual comments on some elements and values as to whether specific values are supported. For instance, check in the schema for Inherit In most cases, the spec says that it is a valid value and yet FOP rejects it as invalid and then inherits anyway. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: generate pdf files and print them to a specific paper bin
Manoj Unnikrishnan wrote: I want to generate pdf files and print them to a specific paper bin. How can I do this? When the PDF is printed I want the first page to be printed on letter head paper and all the others on plain paper. No, this is not possible - at least not in an automatic kind of way. PDF by itself doesn't support this in the file format. You could try to remote-control the Acrobat Reader while printing the document. You can get this to work in a controlled environment, but I wouldn't recommend this for production use. In theory, PJTF (job tickets extension for PDF) could be the answer to your problem, but as far as I know paper bins are not defined yet. For a customer who urgently needed the same kind of thing, we switched to PostScript output with FOP and extended (well, so far it's rather a hack) FOP's PS renderer to support PPD commands. Hope this helps, Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Feedback
I just wanted you all to know that I've been using FOP as the chief enabling technology in a product I'm building, and it has been very useful and powerful. Granted, I have to live within some of the limitations (like the blind tables business), but I've been able to get some very nice things done even so. You've done a great job. If my product finds a market[1], I should have the time in a few months to contribute to FOP's further development. I'm particularly in need of inline containers, and, of course, better keep/break handling would be nice (as if that wasn't already known). Thanks for all of your work and dedication. Patrick Rusk [1] If it doesn't find a market, I'll have to find a real job... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Yes, I read your comments, and the comparison I posted earlier take this into consideration. (Unless something went wrong in my XSLT, that is) What my XSLT does is to look for each element or attribute whether it is referred to in a group or attributeGroup named ???_Not. If it is the case, then it wrote no, otherwise yes. Of course I don't consider the annotations to generate yes/no value, but it's ok: it's equivalent to partial support. The clear yes/no differences are more interesting to look at for possible corrections of either your schema or the compliance.xml file. Now, if FOP itself is lying about what it supports, that's another story ;-) I take this opportunity to thank you once again, Chuck, for your very valuable work on this schema. Benoit Maisonny Chuck Paussa wrote: Benoit, In the FOP schema I developed, there's a set of switches that you have to edit in order to differentiate between what is and is not supported in FOP. The schema, as I provided it, validates for the full FO spec. You need to go in and comment out the templates with a name of ???_NOT in order to exclude those elements that are not supported. There are also individual comments on some elements and values as to whether specific values are supported. For instance, check in the schema for Inherit In most cases, the spec says that it is a valid value and yet FOP rejects it as invalid and then inherits anyway. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- .. Benoit Maisonny[EMAIL PROTECTED] Director Consultant http://synclude.com Synclude Ltd. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
PS Renderer Enhancement
SEG_QUADTO was not implemented in PSGraphics2D.java, which resulted in the rendering of text portion of SVG unpredictable. Unlike the SEG_CUBICTO which has a corresponding curveto PS command, QUADTO doesn't have a PS command to be directly related to. But we can use curveto PS command to achieve the QUADTO effect by treating the first two control points as the same point. ( i.e. P1, P1, P2, curveto == P1, P2, QUADTO ) The actual implementation is very simple. 832a833,839 psRenderer.write(PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[2]) + + PDFNumber.doubleOut(1000 * vals[3]) + curveto); George 832a833,839 psRenderer.write(PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[2]) + + PDFNumber.doubleOut(1000 * vals[3]) + curveto); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16182] New: - PSGraphics2D: SEG_QUADTO implementation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16182. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16182 PSGraphics2D: SEG_QUADTO implementation Summary: PSGraphics2D: SEG_QUADTO implementation Product: Fop Version: 0.20.5 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: svg AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Simple implementaion of SEG_QUADTO segment in PSGraphics2D.java. Using curveto command to replace QUADTO. psRenderer.write(PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[0]) + + PDFNumber.doubleOut(1000 * vals[1]) + + PDFNumber.doubleOut(1000 * vals[2]) + + PDFNumber.doubleOut(1000 * vals[3]) + curveto); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: xml.apache.org refactoring #1
On Thu, 16 Jan 2003, Ted Leung wrote: We ask each subproject to nominate 1 (or 2) people from that project to be a part of the XML PMC. From my experience, I think that it will be better to have 2 people rather than one in order to share workload, etc. Another task we need nominees for (or will let default to these people) is that of security contact for each the respective projects. What this implies is that you will act as a filter and coordinator to deal with the often time criticial, and not always entirely public, process of analysing a vulnerability; confirming it and working the likes of CERT to prepare an advisory. Calling in your peers when neccesary. Should you have any questions about this role; Ben Laurie ([EMAIL PROTECTED]) leads the ASF wide security coordination effort. Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
