Re: picks wrong title language for metadata

2011-09-12 Thread Glenn Adams
There are two questionable assumptions you seem to make below: (1) that FOP chooses (filters) metadata elements based on lang, i.e., FOP implements the semantics of rdf:Alt; (2) that FOP would fix-up non-conforming metadata; Of course, the functionality in question is an extension to XSL-FO in

Re: picks wrong title language for metadata

2011-09-12 Thread Glenn Adams
the following would not be valid XML, so would produce an XML parsing error On Sun, Sep 11, 2011 at 3:48 PM, Terence M. Bandoian tere...@tmbsw.comwrote: Does it make sense to specify something like the following? dc:title rdf:Alt rdf:li xml:lang=\x-default\An Orange in Flight/rdf:li

Re: picks wrong title language for metadata

2011-09-12 Thread Terence M. Bandoian
On 9/12/2011 6:20 AM, Glenn Adams wrote: the following would not be valid XML, so would produce an XML parsing error On Sun, Sep 11, 2011 at 3:48 PM, Terence M. Bandoian tere...@tmbsw.com mailto:tere...@tmbsw.com wrote: Does it make sense to specify something like the following?

Re: picks wrong title language for metadata

2011-09-12 Thread Glenn Adams
nope, just the backslashes are the problem On Mon, Sep 12, 2011 at 12:54 PM, Terence M. Bandoian tere...@tmbsw.comwrote: On 9/12/2011 6:20 AM, Glenn Adams wrote: the following would not be valid XML, so would produce an XML parsing error On Sun, Sep 11, 2011 at 3:48 PM, Terence M.

picks wrong title language for metadata

2011-09-11 Thread Mathieu Malaterre
Dear all, I am trying to fix a bug in fop debian package (#519592). I am copying the exact bug report here (*). Does anyone knows what is going on ? Should I simply fill in a bug report with this information ? The aoif.fo attached allowed me to reproduce the issue with fop 1.0. thanks (*)

Re: picks wrong title language for metadata

2011-09-11 Thread Terence M. Bandoian
On 9/11/2011 7:31 AM, Mathieu Malaterre wrote: Dear all, I am trying to fix a bug in fop debian package (#519592). I am copying the exact bug report here (*). Does anyone knows what is going on ? Should I simply fill in a bug report with this information ? The aoif.fo attached allowed me to