DO NOT REPLY [Bug 17521] New: - Fonts in PDF
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=17521. 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=17521 Fonts in PDF Summary: Fonts in PDF Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am creating a standard template, the metrix of which are: Page height: 9 inches Page width: 6 inches Margin top: 4 picas Margin bottom: 6 picas Left margin: 4 picas Right margin: 4 picas If the font height is 10 pts and line height is 12 pts, the number of lines that must be rendered on a single page are 44 (according to standard calculation). However, the below mentioned font families generate different number of line: Times (Adobe font) generates 47 lines Helvetica (Adobe font) generates 39 lines Garamond (true Type font converted using FOP font converter) generates 39 lines I would really appreciate if someone could suggest as to where the problem lies and what could be the possible solution(s). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17521] - Fonts in PDF
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=17521. 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=17521 Fonts in PDF --- Additional Comments From [EMAIL PROTECTED] 2003-02-28 15:40 --- Created an attachment (id=5088) Testcase - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17521] - Fonts in PDF
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=17521. 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=17521 Fonts in PDF [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2003-02-28 15:43 --- Confirmed. I have attached a testcase for further investigations. Interesting thing is that it works as expected in the redesign (44 lines). :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Help with Forrest
I have been able to eliminate the need for frames in my documantation by getting dynamic inline frames to work in NS7.0, Mozilla 1.2.1 and IE6. This requires that a javascript file be included in each of the affected files. I need some advice on how best to get this to work with Forrest. Do I need to include some form of redundant lining to the htmlized code files? Can I otherwise express such files (with javascript: links) in XML? Does anyone know how I can get JavaSRc that Nicola mentioned. I would like to clean up the documentation as much as possible. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Help with Forrest
Not a specialist on Forrest or Cocoon, yet, but I think it probably needs among other things an additional map:match element with a custom stylesheet, such as the one for the compliance document. So if you converted the HTML to XHTML you could probably write an XSLT stylesheet to add the JavaScript stuff. Just what's going though my head. I hope it helps anyway. Probably best if you asked on Forrest mailing list, too. Is this what you're looking for? http://sourceforge.net/projects/javasrc/ On 28.02.2003 16:55:12 Peter B. West wrote: I have been able to eliminate the need for frames in my documantation by getting dynamic inline frames to work in NS7.0, Mozilla 1.2.1 and IE6. This requires that a javascript file be included in each of the affected files. I need some advice on how best to get this to work with Forrest. Do I need to include some form of redundant lining to the htmlized code files? Can I otherwise express such files (with javascript: links) in XML? Does anyone know how I can get JavaSRc that Nicola mentioned. I would like to clean up the documentation as much as possible. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17521] - Fonts in PDF
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=17521. 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=17521 Fonts in PDF --- Additional Comments From [EMAIL PROTECTED] 2003-02-28 17:19 --- The understanding of what 12pt means that is implied by the bug report is incorrect. 12pt fonts do not all occupy the same amount of vertical space when their leading is factored in. You can play around with 12pt fonts in Microsoft Word, for instance, to see this easily. More to the point, any college students out there who have played with margins, fonts, and line spacing trying to get an essay to be the proper length know that Adobe's Times font is the bane of papers that are too short. It uses considerably less vertical space than Palatino, Garamond, Helvetica, etc. Microsoft's Times New Roman and Arial occupy the same vertical space, but Adobe's Times and Helvetica never have. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15985] - Hyphenation pattern files appear to be invalid
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=15985. 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=15985 Hyphenation pattern files appear to be invalid [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-01 00:30 --- Mismatch caused by build system change, fixed in 0.20.5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14351] - It would be nice to allow FOP users to see xsl-fo sources.
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=14351. 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=14351 It would be nice to allow FOP users to see xsl-fo sources. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-01 00:31 --- XSLT batch commands added to the distribution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14809] - Static content in body on blank pages
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=14809. 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=14809 Static content in body on blank pages [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-03-01 00:35 --- Static content must not go into the body region. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14979] - Make links availble for examples on website
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=14979. 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=14979 Make links availble for examples on website [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: HTML to FO
Hi, the url is http://html2fo.sf.net Enrico Am Donnerstag, 27. Februar 2003 22:44 schrieb Ken Masters: Hi, Could you give some more information on where I can get hold of this tool. I did a search for htmlfo on Google and found a stylesheet that is in some other langauage to do with DSSSL. Ken there is a tool called htmlfo which does that.. -Original Message- From: Swapan Golla [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 1:04 PM To: [EMAIL PROTECTED] Subject: HTML to FO I am having a need to convert html ( or xhtml ) to fo documents and then to pdf. Any suggestions on the best ways to achieve this ? I should be able to use/call this from my java program. Thanks in advance, Swapan. _ Express yourself with cool emoticons http://messenger.msn.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
