Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

On Mon, Dec 05, 2005 at 09:10:06PM +0800, Manuel Mall wrote: > Luca, > > Glyphs are only allowed to be merged if they carry the same / matching > set of property values. Personally I would not be concerned if we > therefore limit that logic to within a LM. While it is possible that > someone co

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

Manuel Mall wrote: I wonder if the same argument does apply to kerning as well? The moment you change font-size, text-decoration, background-color, alignment and the like, which is what fo:inline is mainly for, you create a barrier with respect kerning. Or to put it differently, I believe kern

Re: ToUnicode table for CID embedded fonts patch available

Hello Jeremias, >> javax.xml.transform.TransformerException: >> file:/D:/Work/Digitech/IWS%209.x%20redesign/IWS-redesign.fo:2:24687: >> Error(2/24687): No element mapping definition found for fox:outline >> Exception javax.xml.transform.TransformerException: >> org.apache.fop.apps.FOPException: >>

Re: Using Docbook stylesheets in FOP

Simon wrote: > The docbook stylesheets seem to be a pain for most XSLT > processors. Restricting myself to Java XSLT processors, I > have only been successful with Saxon6. Xalan and the Xalan processor > built into Java 5 cannot compile the docbook/fo stylesheets. I managed to pass over that probl

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

AFAIK, there's no such flag in XSL-FO. In 0.20.5 this was simply controlled per font over its configuration. We'd have to create an extension property to locally switch off kerning once it's available. On 05.12.2005 16:18:25 Manuel Mall wrote: > Side note: Does XSL-FO provide any user control ove

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

On Mon, 5 Dec 2005 10:53 pm, Luca Furini wrote: > First of all, thanks for your comments: I really tend to forget in a > short time all the details concerning white space! > > Manuel Mall wrote: > > Glyphs are only allowed to be merged if they carry the same / > > matching set of property values. P

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

On 05.12.2005 15:53:51 Luca Furini wrote: > First of all, thanks for your comments: I really tend to forget in a short > time all the details concerning white space! > > Manuel Mall wrote: > > > Glyphs are only allowed to be merged if they carry the same / matching > > set of property values.

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

First of all, thanks for your comments: I really tend to forget in a short time all the details concerning white space! Manuel Mall wrote: Glyphs are only allowed to be merged if they carry the same / matching set of property values. Personally I would not be concerned if we therefore limit t

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

Luca, great summary and I appreciate you taking a serious look into this problem. Some comments below. On Mon, 5 Dec 2005 05:48 pm, Luca Furini wrote: > Manuel Mall wrote: > > After that we really need to redesign the line breaking stuff. Not > > the Knuth approach (and the implemented algorithm

4.3.2 Overconstrained space-specifiers

You will have seen that I've been working on overconstrained documents. 5.3.4 Overconstrained Geometry is more or less implemented, so now I need to have a look at 4.3.2 which proves quite difficult to understand. At least I can't make much sense of it ATM. Here's what I found out so far with a som

Re: DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

Manuel Mall wrote: After that we really need to redesign the line breaking stuff. Not the Knuth approach (and the implemented algorithms related to that) but the way we arrive at the Knuth sequences and iterate and process the text elements. This needs to be done to be able to do white-space-t

DO NOT REPLY [Bug 37743] - exception: border-style (shorthand)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu