DO NOT REPLY [Bug 27773] New: - [PATCH] Hyphenation
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=27773. 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=27773 [PATCH] Hyphenation Summary: [PATCH] Hyphenation Product: Fop Version: 1.0dev Platform: PC OS/Version: Windows XP Status: NEW Severity: Enhancement Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have tried to solve a few problems concerning hyphenation: - show the '-' at the end of the hyphenated lines - use the fo:hyphenate property to enable hyphenation, instead of the alignment - specify the hyphenation character using the fo:hyphenation-character property With this simple .fo file it is possible to see that before changes the result is the opposite of what expected: hyphenation is done when it shoud not, and not when it shoud. ?xml version=1.0 encoding=iso-8859-1? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simple margin=0.5in fo:region-body margin=1in/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=simple fo:flow flow-name=xsl-region-body fo:blockThe following block has language=it, hyphenate=false and text-align=justify; it should NOT be hyphenated./fo:block fo:block start-indent=0.2in end-indent=0.2in language=it hyphenate=false text-align=justifyLunghissime parolone esagerevoli costringerebbero sillabazione auspicabilmente: precipitevolissimevolmente transatlantico catastrofico./fo:block fo:blockThe following block has language=it, hyphenate=true and text-align=start; it should be hyphenated./fo:block fo:block start-indent=0.2in end-indent=0.2in language=it hyphenate=true text-align=startLunghissime parolone esagerevoli costringerebbero sillabazione auspicabilmente: precipitevolissimevolmente transatlantico catastrofico./fo:block fo:blockThe following block has language=it, hyphenate=true, text- align=justify and hyphenation-character=_./fo:block fo:block start-indent=0.2in end-indent=0.2in language=it hyphenate=true text-align=justify hyphenation-character=_Lunghissime parolone esagerevoli costringerebbero sillabazione auspicabilmente: precipitevolissimevolmente transatlantico catastrofico./fo:block /fo:flow /fo:page-sequence /fo:root This is the diff: Index: xml-fop/src/java/org/apache/fop/fo/PropertyManager.java === RCS file: /home/cvspublic/xml- fop/src/java/org/apache/fop/fo/PropertyManager.java,v retrieving revision 1.24 diff -w -u -r1.24 PropertyManager.java --- xml-fop/src/java/org/apache/fop/fo/PropertyManager.java 27 Feb 2004 17:57:40 - 1.24 +++ xml-fop/src/java/org/apache/fop/fo/PropertyManager.java 18 Mar 2004 12:43:55 - @@ -494,6 +494,9 @@ textInfo.textTransform = this.propertyList.get(PR_TEXT_TRANSFORM).getEnum(); +textInfo.hyphChar = this.propertyList.get( + PR_HYPHENATION_CHARACTER).getCharacter(); + } return textInfo; } Index: xml-fop/src/java/org/apache/fop/fo/TextInfo.java === RCS file: /home/cvspublic/xml-fop/src/java/org/apache/fop/fo/TextInfo.java,v retrieving revision 1.6 diff -w -u -r1.6 TextInfo.java --- xml-fop/src/java/org/apache/fop/fo/TextInfo.java27 Feb 2004 17:57:40 - 1.6 +++ xml-fop/src/java/org/apache/fop/fo/TextInfo.java18 Mar 2004 12:43:55 - @@ -50,8 +50,8 @@ /** fo:letter-spacing property */ public SpaceVal letterSpacing; -/** can this text be hyphenated? */ -public boolean bCanHyphenate = true; +/* the hyphenation character to be used */ +public char hyphChar = '-'; /** fo:text-decoration property: is text underlined? */ public boolean underlined = false; Index: xml-fop/src/java/org/apache/fop/layoutmgr/LineLayoutManager.java === RCS file: /home/cvspublic/xml- fop/src/java/org/apache/fop/layoutmgr/LineLayoutManager.java,v retrieving revision 1.15 diff -w -u -r1.15 LineLayoutManager.java --- xml-fop/src/java/org/apache/fop/layoutmgr/LineLayoutManager.java18 Mar 2004 00:22:40 - 1.15 +++ xml-fop/src/java/org/apache/fop/layoutmgr/LineLayoutManager.java18 Mar 2004 12:44:00 - @@ -20,6 +20,7 @@ import org.apache.fop.datatypes.Length; import org.apache.fop.fo.PropertyManager; +import org.apache.fop.fo.Constants; import org.apache.fop.fo.properties.CommonMarginBlock; import org.apache.fop.fo.properties.CommonHyphenation;
Web Start
Fops, Does anyone have any detailed knowledge of Web Start? It occurred to me that it may be a way to resolve some of the licensing issues we (and other projects) are running into. Any educated thoughts on the matter? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Another licensing issue
Jeremias et al, I would like ti use the Unicode Character Database as a source for names of characters. At the moment, ...fonts.Glyphs contains a static table of String pairs containing the Unicode character and its name, respectively. The names are not the Unicode Character Database names, and I thought it might be a good idea if they were. However, there seems to be no way to get the canonical UCD name from Java, although java.lang.Character and java.lang.Character.UnicodeBlock have extensive support for various characteristics of the UCD. The problem with deriving the names from the UCD is another one of licensing. Any ideas about how we might approach this? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Web Start
Peter B. West schrieb: Fops, Does anyone have any detailed knowledge of Web Start? It occurred to me that it may be a way to resolve some of the licensing issues we (and other projects) are running into. Any educated thoughts on the matter? Peter I didn't know about Web Start--looks very interesting [1], but I don't see where this would help FOP w.r.t. licensing--we would still be redistributing L/GPL and other license-incompatible software, even if automated by Web Start, correct? Glen [1] http://www.javaworld.com/javaworld/jw-07-2001/jw-0706-webstart.html
Antwort: Web Start
Hi Peter, we use Web Start in a customer project. It's a good solution to deploy Java applications as a JAR file, even with native code and such. Some caveats: -The security manager can get in your way if you want things like filesystem access. You have to sign your jar and each user has to accept your signature once per application. - You cannot catch uncaught exceptions in JNLP applications. This is useful for GUI applications, so you can catch and for example log these exceptions. With JNLP, AWT/Swing creates its own thread group so you're out of luck there. Maybe not an issue for fop. - Only comes with JRE 1.4 by default, and older WebStart version are quite buggy in my experience. So far I cannot see how exactly WebStart would be useful for FOP regarding licensing stuff, because your sources for parts like hyphenation libs still need to be JNLP jars, so you still need someone to actually provide these jars and thus take responsibility regarding legal issues. As for as I see it, you don't gain anything. But if you have something more concrete in mind, please feel free ask more concrete WebStart questions. Hope this helps, -- Arnd Beißner Cappelino Informationstechnologie GmbH Peter B. West [EMAIL PROTECTED] schrieb am 18.03.2004 15:40:19: Fops, Does anyone have any detailed knowledge of Web Start? It occurred to me that it may be a way to resolve some of the licensing issues we (and other projects) are running into. Any educated thoughts on the matter? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
cvs commit: xml-fop/src/java/org/apache/fop/svg SVGUserAgent.java package.html
gmazza 2004/03/18 16:53:38 Modified:src/java/org/apache/fop/image/analyser SVGReader.java src/java/org/apache/fop/render/pdf PDFXMLHandler.java src/java/org/apache/fop/render/ps PSXMLHandler.java src/java/org/apache/fop/svg package.html Added: src/java/org/apache/fop/svg SVGUserAgent.java Removed: src/java/org/apache/fop/fo/extensions/svg SVGUserAgent.java Log: Moved SVGUserAgent back to SVG package (not being used by SVG FO extensions.) Revision ChangesPath 1.5 +1 -1 xml-fop/src/java/org/apache/fop/image/analyser/SVGReader.java Index: SVGReader.java === RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/image/analyser/SVGReader.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- SVGReader.java27 Feb 2004 17:47:30 - 1.4 +++ SVGReader.java19 Mar 2004 00:53:37 - 1.5 @@ -38,7 +38,7 @@ import org.apache.fop.image.XMLImage; import org.apache.fop.image.FopImage; import org.apache.fop.apps.FOUserAgent; -import org.apache.fop.fo.extensions.svg.SVGUserAgent; +import org.apache.fop.svg.SVGUserAgent; /** * ImageReader object for SVG document image type. 1.8 +1 -1 xml-fop/src/java/org/apache/fop/render/pdf/PDFXMLHandler.java Index: PDFXMLHandler.java === RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/render/pdf/PDFXMLHandler.java,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- PDFXMLHandler.java27 Feb 2004 17:52:34 - 1.7 +++ PDFXMLHandler.java19 Mar 2004 00:53:37 - 1.8 @@ -29,7 +29,7 @@ import org.apache.fop.svg.PDFTextElementBridge; import org.apache.fop.svg.PDFAElementBridge; import org.apache.fop.svg.PDFGraphics2D; -import org.apache.fop.fo.extensions.svg.SVGUserAgent; +import org.apache.fop.svg.SVGUserAgent; import org.apache.fop.apps.Document; /* org.w3c.dom.Document is not imported to avoid conflict with 1.11 +1 -1 xml-fop/src/java/org/apache/fop/render/ps/PSXMLHandler.java Index: PSXMLHandler.java === RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/render/ps/PSXMLHandler.java,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- PSXMLHandler.java 27 Feb 2004 17:53:11 - 1.10 +++ PSXMLHandler.java 19 Mar 2004 00:53:38 - 1.11 @@ -36,7 +36,7 @@ // FOP import org.apache.fop.render.XMLHandler; import org.apache.fop.render.RendererContext; -import org.apache.fop.fo.extensions.svg.SVGUserAgent; +import org.apache.fop.svg.SVGUserAgent; /** * PostScript XML handler. 1.2 +1 -1 xml-fop/src/java/org/apache/fop/svg/package.html Index: package.html === RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/svg/package.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- package.html 11 Mar 2003 13:05:07 - 1.1 +++ package.html 19 Mar 2004 00:53:38 - 1.2 @@ -16,7 +16,7 @@ from SVG to a single page PDF document. /P P -SVGElement, SVGElementMapping, SVGObj and SVGUserAgent are used by +SVGElement, SVGElementMapping and SVGObj are used by FOP for handling embedded SVG or external SVG graphics. /P P 1.9 +16 -50xml-fop/src/java/org/apache/fop/svg/SVGUserAgent.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Web Start
Glen, I was thinking that with Web Start, we would not need to hold contentious files in the FOP repository. All we need is a reliable location for them, with appropriate verification. Then the process of installing FOP can transparently (or with loud warnings) include files from non-Apache sources. Peter Glen Mazza wrote: I didn't know about Web Start--looks very interesting [1], but I don't see where this would help FOP w.r.t. licensing--we would still be redistributing L/GPL and other license-incompatible software, even if automated by Web Start, correct? Glen [1] http://www.javaworld.com/javaworld/jw-07-2001/jw-0706-webstart.html -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Antwort: Web Start
Arnd, Keeping in mind that I am utterly ignorant of a lot of these issues, and am tossing straws in the wind, see comments below... [EMAIL PROTECTED] wrote: Hi Peter, we use Web Start in a customer project. It's a good solution to deploy Java applications as a JAR file, even with native code and such. Some caveats: -The security manager can get in your way if you want things like filesystem access. You have to sign your jar and each user has to accept your signature once per application. If the once per application meant once per Fop installation, that would be OK. Can the user allow us file system access once the signature is accepted? - You cannot catch uncaught exceptions in JNLP applications. This is useful for GUI applications, so you can catch and for example log these exceptions. With JNLP, AWT/Swing creates its own thread group so you're out of luck there. Maybe not an issue for fop. I'd have to think about the implications of this. Drawing a blank at the moment. - Only comes with JRE 1.4 by default, and older WebStart version are quite buggy in my experience. This is a show stopper while we are supporting 1.3. So far I cannot see how exactly WebStart would be useful for FOP regarding licensing stuff, because your sources for parts like hyphenation libs still need to be JNLP jars, so you still need someone to actually provide these jars and thus take responsibility regarding legal issues. As for as I see it, you don't gain anything. Let's say, for example, that we approach a TeX distribution with a request that we be allowed to download the TeX hyphenation files, as modified for use with Fop. If they are OK with that, we generate a jar file with the hyphenation files, including the original copyright (and possibly notes about the conversion being done under the auspices of Apache) and drop it on the CTAN servers. Alternatively, we simply jar up the original TeX files, and include a conversion process in the installation. The files are not coming from an Apache server, and they do not carry the Apache license (except for perhaps a Parts copyright... notice). It is a convenience to our users that we download such files transparently from another source on installation. But if you have something more concrete in mind, please feel free ask more concrete WebStart questions. Thanks Arnd. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
DO NOT REPLY [Bug 27794] New: - [PATCH] Merge LayoutProcessor and LayoutManager interfaces
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=27794. 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=27794 [PATCH] Merge LayoutProcessor and LayoutManager interfaces Summary: [PATCH] Merge LayoutProcessor and LayoutManager interfaces Product: Fop Version: 1.0dev Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Team, The following patch merges the LayoutProcessor interface back into the LayoutManager interface, which returns the meaning of the latter into being the minimal interface that a LayoutManager must implement in the LayoutManager layout strategy. (Similar to the Renderer interface in the render packages.) This change is primarily to simplify the Layout code. Keiron separated the two last year in order for their to be more freedom in layout strategies, but this is before Victor already gave us the LayoutStrategy interfaces, which does much the same thing (except doesn't limit you to LayoutManager classes at all.) Keeping separate interfaces isn't buying us anything at this time--rather, we can free up the LayoutManager design by reducing the number of methods within it. (So far, though, that hasn't been a concern.) Peter, would implementing this change have any affect on your Alt-Design and its possible integration in HEAD? I don't think it will, and it will make things easier in HEAD. I'll wait three days, and if no objections, apply this on Sunday (Wash DC time). Thanks, Glen
Re: Another licensing issue
Jeremias, The penny just dropped about the names of the Unicode characters; they are the Adobe Glyph List and the Zapf Dingbats Glyph List names of a subset of Unicode characters. Won't we at some stage need to generalise support for a wider set of glyphs? Or is that entirely a matter for user-defined fonts? Looks as though I'll have to look at user fonts. Peter Peter B. West wrote: Jeremias et al, I would like ti use the Unicode Character Database as a source for names of characters. At the moment, ...fonts.Glyphs contains a static table of String pairs containing the Unicode character and its name, respectively. -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
