Your message dated Mon, 12 Sep 2011 13:28:38 +0200
with message-id
<CA+7wUswT+rGP-OK5F1AEgqrG6cfrCOOZWtWt1L7nLf+AP=t...@mail.gmail.com>
and subject line Fwd: picks wrong title language for metadata
has caused the Debian Bug report #519592,
regarding fop: picks wrong title language for metadata
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
519592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fop
Version: 1:0.95.dfsg-4
Severity: normal
When I specify RDF metadata in my XSL-FO file, I can specify several
different dc:title tags, each with a different xml:lang tag (or none at
all). If I specify
<rdf:Description rdf:about="" xmlns:dc="http://purl.org/dc/elements/1.1/";>
<dc:title>An Orange in Flight</dc:title>
<dc:title xml:lang="x-default">An Orange in Flight</dc:title>
<dc:title xml:lang="en">An Orange in Flight</dc:title>
<dc:title xml:lang="es">Una Naranja en Vuelo</dc:title>
<dc:creator>The Barefoot Waif</dc:creator>
</rdf:Description>
fop chooses the last title, even though the language for the XSL-FO
document is "en". The XMP metadata (as well as the /Info data) in the
PDF comes out as
<dc:title>
<rdf:Alt>
<rdf:li xml:lang="x-default">Una Naranja en Vuelo</rdf:li>
</rdf:Alt>
</dc:title>
which is completely wrong.
Obviously, I want it to pick one of the other three. My preference is
that fop picks the tag without an xml:lang attribute; then the tag with
xml:lang="x-default"; then the tag with the language of the document,
according to the language attribute on an enclosing fo element; and then
some other language (which one I don't care).
This doesn't happen if dc:title contains an rdf:Alt with rdf:li elements
that have xml:lang attributes, as the XMP specification requires.
However, the fop page on metadata[0] demonstrates metadata that does not
comply with the XMP standard, so it is reasonable to assume that fop
will properly fix up metadata that isn't strictly conforming.
[0] http://xmlgraphics.apache.org/fop/0.95/metadata.html
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-rc7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fop depends on:
ii default-jre [java2-runti 1.5-31 Standard Java or Java compatible R
ii java-gcj-compat [java2-r 1.0.80-1 Java runtime environment using GIJ
ii java-wrappers 0.1.13 wrappers for java executables
ii libavalon-framework-java 4.2.0-4 Common framework for Java server a
ii libbatik-java 1.7-2 xml.apache.org SVG Library
ii libbsf-java 1:2.4.0-2 Bean Scripting Framework to suppor
ii libcommons-io-java 1.4-1 Common useful IO related classes
ii libcommons-logging-java 1.1.1-2 commmon wrapper interface for seve
ii libxalan2-java 2.7.1-2 XSL Transformations (XSLT) process
ii libxerces2-java 2.9.1-2 Validating XML parser for Java wit
ii libxml-commons-external- 1.3.04-2 XML Commons external code - DOM, S
ii libxmlgraphics-commons-j 1.3.1.dfsg-2 reusable components used by Batik
ii libxp6 1:1.0.0.xsf1-2 X Printing Extension (Xprint) clie
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension
ii openjdk-6-jre [java2-run 6b14-1.5~pre1-3 OpenJDK Java runtime, using Hotspo
Versions of packages fop recommends:
ii libsaxon-java 1:6.5.5-5 The Saxon XSLT Processor
Versions of packages fop suggests:
ii fop-doc 1:0.95.dfsg-4 Documentation for fop
ii libservlet2.4-java 5.0.30-8 Servlet 2.4 and JSP 2.0 Java class
-- no debconf information
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
tag 519592 wontfix
thanks
---------- Forwarded message ----------
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
the first place, so it is *possible* that FOP could do these things.
However, it is not consistent with FOP semantics that it should do so,
since FOP does not make choices between *any* content based on
language, and since FOP does not perform *any* fix-ups for
non-compliant content.
You should perform the content selection process during the front-end
XSLT stage, or, if you are feeding FO directly to FOP, then do it when
you create the FO input file. That is, you should not expect this
extension to implement the semantics of rdf:Alt.
--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
