Thanks Alan. I'd forgotten about that issue.
I tracked down the problem, but I don't know how to fix it.
In libX11/nls/Compose/el_GR.UTF-8.xml, on line 172:
<row><entry><keycombo
action='seq'><keysym>Multi_key</keysym><keysym>minus</keysym><keysym>minus</keysym></keycombo></entry><entry>"<literal>
</literal>" hyphen</entry></row>
There's a character that looks like a space between the literal tags.
It's not actually a space though space and it fails with '--with-fop'.
Files:
libX11/nls/
Compose/iso8859-1.xml
Compose/iso8859-13.xml
Compose/iso8859-14.xml
Compose/iso8859-15.xml
Compose/iso8859-2.xml
Compose/iso8859-3.xml
Compose/iso8859-4.xml
Compose/iso8859-7.xml
Compose/iso8859-9e.xml
Compose/iso8859-9.xml
Compose/vi_VN.viscii.xml
die because fop doesn't like the soft-hyphens. ­
I'm guessing that first error is also a soft-hyphen.
It looks like it's a known issue with FOP:
http://xmlgraphics.apache.org/fop/knownissues.html
Removing the surrounding <literal> tag seems to work ok. Can we just
remove that tag?
Your thoughts?
Matt
On 01/21/2011 05:11 PM, Alan Coopersmith wrote:
On 01/21/11 03:09 PM, Matt Dew wrote:
Has anyone had trouble building the libX11 documentation?
The HTML docs build and install fine, but the pdf docs do not.
Other pdf docs build fine. bigreqsproto for example, builds ok.
I see this:
...
checking for fop... /usr/bin/fop
...
for the other modules I build, but not for libX11. I'm building with build.sh
Has anyone else had this problem?
Don't forget to set --with-fop, since even if configure finds it, libX11
is set to not use it unless requested, due to the issues we had with the
compose tables docs. (libX11 is the only module that defaults to off for
fop, instead of auto.)
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
