Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Tony Graham
On Mon, Sep 21 2009 23:30:17 +0100, jonathan.levin...@intersystems.com wrote: ... > If inherit is allowed to be a value then the grammar truly becomes ambiguous > since each of these can have the value inherit and we don?t know which ones > are > omitted and must take the value normal. 'inherit'

Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Vincent Hennebert
Hi Jonathan, Jonathan Levinson wrote: > Hi Vincent, > > You make excellent points, however for font-style, font-variant and > font-weight the initial value (the default value) is normal, not inherit. > > http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#font-style > > http://www.w3.org/TR

Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Peter B. West
On 23/09/2009, at 12:13 AM, Jonathan Levinson wrote: Hi Vincent, You make excellent points, however for font-style, font-variant and font-weight the initial value (the default value) is normal, not inherit. http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#font-style http://www.w3.

RE: ambiguity of grammar for font shorthand?

2009-09-22 Thread Jonathan Levinson
Hi Vincent, You make excellent points, however for font-style, font-variant and font-weight the initial value (the default value) is normal, not inherit. http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#font-style http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#font-variant http:/

DO NOT REPLY [Bug 46705] [PATCH] Enhancement: PDF Accessibility

2009-09-22 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=46705 --- Comment #21 from Vincent Hennebert 2009-09-22 04:59:24 PDT --- I've just noticed that the structure tree stored in the IF XML is not re-parsed. Running FOP with the IF as input (-afin) and the -a switch even leads to a NPE. So tagged P

Re: PDFFontDescriptor Ascent Descent and FontBBox

2009-09-22 Thread Vincent Hennebert
Hi Alexander, Alexander Kiel wrote: > Hi Max, > > thanks for pointing me to fontbox. As I did not find a repository with a > trunk, I had a look into fontbox-0.8.0-incubating. They have quite clean > code to parse TrueType files. But they are also not able to read any > OpenType data. They are ev

Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Vincent Hennebert
Hi Jonathan, Jonathan Levinson wrote: > Hi Vincent, > > > > As I read the grammar for the font shorthand it is ambiguous, though not > fatally so as long as one excludes the value of "inherit" from > individual properties in the font short hand. > > > > For instance the first optional arg

Re: PDFFontDescriptor Ascent Descent and FontBBox

2009-09-22 Thread Alexander Kiel
Hi Max, thanks for pointing me to fontbox. As I did not find a repository with a trunk, I had a look into fontbox-0.8.0-incubating. They have quite clean code to parse TrueType files. But they are also not able to read any OpenType data. They are even not able to read kerning data as FOP can alrea

Re: PDFFontDescriptor Ascent Descent and FontBBox

2009-09-22 Thread Max Berger
Alexandar, on a completely different note: It may be interesting to also look into fontbox (part of pdfbox), which is now also an apache project, and therefore we could use source synergy. http://incubator.apache.org/pdfbox/ For the issue you've mentioned: This may be due so some issues with CI

Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Alexander Kiel
Hi, > I think it is probably the case that in the context of the font short > hand – the font properties cannot take the value of inherit, since > this renders the grammar irreducibly ambiguous. While such an > exclusion is not mentioned in the spec, it makes sense that inherit > must be exclude

Re: ambiguity of grammar for font shorthand?

2009-09-22 Thread Alexander Kiel
Hi, > Also, in your message you said we could ignore a value for font of > caption, icon, etc., as the standard tells us to do, but the standard > discusses these values and their relation to system fonts. Was this > an oversight on your part or am I mis-reading the spec? [1] > > [1] http://www.w