Re: How do I get the height of a character?
Manuel Mall wrote: The font class provides a width method to determine the width of a character but how do I figure out the height of a character? IIRC the height of an individual character doesn't matter. Well, for the possible exceptions of characters leaking outside the font boxes, like uppercase umlauts and many other accented characters. For all other cases, only the font height measurements should matter, For leader-style=dots everything is basically user agent defined. Fop uses the dot character from the current font which is a sensible selection IMO. I think there is a difference between leaders using the dot character (for the foo...page 19 style) and a leader which is a dotted line (rule-style=dotted). THe rule-thickness only applies to the second leader style. J.Pietschmann
Re: How do I get the height of a character?
On Sun, 18 Sep 2005 05:30 pm, J.Pietschmann wrote: Manuel Mall wrote: The font class provides a width method to determine the width of a character but how do I figure out the height of a character? IIRC the height of an individual character doesn't matter. Well, for the possible exceptions of characters leaking outside the font boxes, like uppercase umlauts and many other accented characters. For all other cases, only the font height measurements should matter, For leader-style=dots everything is basically user agent defined. Fop uses the dot character from the current font which is a sensible selection IMO. I think there is a difference between leaders using the dot character (for the foo...page 19 style) and a leader which is a dotted line (rule-style=dotted). THe rule-thickness only applies to the second leader style. Not so sure here - I think the rule-thickness property applies only to leader-style=rule however according my understanding of 6.6.9 Trait Derivation the rule-thickness trait applies always unless leader-style=use-content. Therefore the question arises what is the appropriate value for the rule-thickness trait for leader-style=dots. My understanding is that this would be user agent specific as are most properties with respect to leader-style=dots, e.g. the size of the dots. IMO using the font-size gives a far too big rule-thickness for the dots. Therefore I was thinking of using the actual vertical size of the black part of the dot character. It appears that this information is not readily available. So I decided to make it square, i.e. use the character width as rule-thickness. This seems to give reasonable results (as long as the dot glyphs of the selected font are square or round as well). BTW, this only becomes relevant if someone wants to paint a background or padding or border around the leader or chooses a bigger font-size for the leader than for the rest of the line as in that case the rule-thickness may determine the overall height of the line. All of that are not very common scenarios I would think, so its really just tidying up a very small and not important loose end. J.Pietschmann Manuel
[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 8 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/gump_work/build_xml-fop-maintenance_xml-fop-maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-18092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-18092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-18092005.jar - Buildfile: build.xml init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 0.20.5 [1999-2003] prepare: [echo] Preparing the build directories [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir:
[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 8 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/gump_work/build_xml-fop-maintenance_xml-fop-maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-18092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-18092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-18092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-18092005.jar - Buildfile: build.xml init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 0.20.5 [1999-2003] prepare: [echo] Preparing the build directories [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir:
Re: svn commit: r289865 - in /xmlgraphics/fop/trunk/src/java/org/apache/fop: fo/ fo/flow/ fo/properties/ layoutmgr/table/
On Sep 18, 2005, at 21:58, Finn Bock wrote:
Hi Finn,
+if( pList.getExplicit(PR_COLUMN_NUMBER) != null ) {
+((TableFObj) parent).setCurrentColumnIndex(
+
pList.getExplicit(PR_COLUMN_NUMBER).getNumeric().getValue());
+}
Why is explit specified values different? In all other cases in FOP,
the fo object only needs the computed values.
Normally, if the value wasn't explicitly specified and the
column-number received the initial value in ColumnNumberPropertyMaker
(via the call to getCurrentColumnIndex()), the current column index for
the parent at that point --whether it's a TableRow or a TableBody--
will obviously be the very same as the property's value.
It's only in the case where a column-number was explicitly specified on
the FO, that the parent's columnIndex will be 'out-of-sync'. The
column-number for the next cell should be the current cell's
column-number plus it's number-columns-spanned. The 'plus
number-columns-spanned' part is dealt with automatically when the cell
is added to the parent's list of child nodes.
Earlier on, I had tried to solve this by comparing the current cell's
column-number with the parent's columnIndex, but this didn't work for
all cases... So I needed a way to check whether the value was generated
as a default, and bumped into getExplicit() which turned out to be the
answer.
But I think I know what you mean: apart from the check *whether* the
explicit value is null,
maybe it's better to use
setCurrentColumnIndex(columnNumber.getValue()).
Sorry, I have a tendency to make things more complicated than they
actually are :-)
Does this address your concern?
Cheers,
Andreas
Bug report for Fop [2005/09/18]
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) |
| | +-+
| | | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-+
| | | | Date Posted |
| | | | +--+
| | | | | Description |
| | | | | |
| 635|Opn|Nor|2001-02-18|Doesn't support id= attribute in fo:page-sequence |
| 953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files|
| 1180|New|Maj|2001-04-02|Problem with monospaced font |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood |
| 2150|Ass|Maj|2001-06-13|New page with a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in fo:table-row|
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly |
| 2909|New|Maj|2001-07-30|Gradient render error |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body |
| 3497|New|Cri|2001-09-07|id already exists error when using span=all attr|
| 3824|New|Blk|2001-09-25|MIF option with tables|
| 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S|
| 4126|New|Nor|2001-10-12|FontState.width() returns pts instead of millipts |
| 4226|New|Nor|2001-10-17|The orphans property doesn't seem to work |
| 4388|New|Nor|2001-10-24|Nullpointer exception in the construction of new D|
| 4415|New|Nor|2001-10-25|scaling=uniform does not work on images... |
| 4510|New|Nor|2001-10-30|fo:inline common properties ignored? |
| 4535|New|Maj|2001-10-31|PCL renderer 1.13 not rendering SVG |
| 4767|New|Nor|2001-11-09|SVG text is distored in PDF output|
| 5001|New|Nor|2001-11-21|content-width and content-height ignored? |
| 5010|New|Enh|2001-11-21|Better error reporting needed |
| 5124|New|Maj|2001-11-27|fo:block-container is not rendered properly using |
| 5335|Opn|Min|2001-12-10|Text with embedded CID fonts not retrievable from |
| 5655|Ass|Nor|2002-01-02|text-decoration cannot take multiple values |
| 6094|Opn|Maj|2002-01-29|0.20.3rc hangs in endless loop|
| 6237|Opn|Nor|2002-02-05|#xFB01 (fi ligature) produces a sharp? |
| 6305|New|Nor|2002-02-07|Using fo:table-and-caption results in empty output|
| 6427|New|Enh|2002-02-13|Adding additional Type 1 fonts problem|
| 6437|New|Maj|2002-02-13|Tables without fo:table-column don't render |
| 6483|New|Nor|2002-02-15|Table, Loop, footer could not fit on page, moving|
| 6844|New|Nor|2002-03-04|No line breaks inserted in list-item-label|
| 6918|New|Enh|2002-03-06|reference-orientation has no effect |
| 6997|New|Nor|2002-03-09|[PATCH] Row-spanned row data breaks over a page wi|
| 7140|New|Enh|2002-03-15|page-position attribute set to last on condition|
| 7241|New|Nor|2002-03-19|keep-with-previous, keep-with-next only working on|
| 7283|New|Nor|2002-03-20|Table border misaligned when using margin-left in |
| 7337|New|Nor|2002-03-21|border around external image leaves empty space |
| 7487|New|Nor|2002-03-26|break-before=page for table inserts empty page |
| 7496|New|Nor|2002-03-26|The table header borders are not adjusted to the b|
| 7525|New|Cri|2002-03-27|table with spans inside a list-block |
| 7919|New|Cri|2002-04-10|problem to use attribute linefeed-treatment and li|
| 8003|Ass|Maj|2002-04-12|FopImageFactory never releases cached images |
| 8050|New|Nor|2002-04-13|Soft hyphen (shy;) is not handled properly |
| 8321|New|Nor|2002-04-19|from-parent('width') returns 0 for nested tables |
| 8463|New|Nor|2002-04-24|SVG clipping in external.fo example doc when rende|
|
FOray fonts / axslFonts / baselines / FOP fonts
Vincent, this is more just for the record. To do all this alignment stuff (XSL-FO spec 7.13) correctly we need various baseline information (tables). And it all starts with the font, i.e. for each font we need to know its default baseline and where all the other baselines are for that font (actually on a per glyph basis or at least on a per script basis). None of this information is currently exposed in the font API, neither the current FOP Font nor AFAICT in axslFont. There is certainly no point in modifying the current FOP Font object as it will be superseded by your work in due course. So I hope axslFont and its first implementation FOray Font will take a lead here :-). This is further complicated by most fonts not having this sort of information embedded in their font files. So there must be other means of deriving it as well (algorithmic?, external font config files?, ...). Manuel
