Goodrick
2012-04-13 19:38:22 UTC
Hi,
I don't know anything about the docbook generation stuff that was
added as part of 2.6, but the file
fvwm-2.6.4/doc/docbook-xsl/html/biblio-iso690.xsl
encoding entry on the first line of the file
<?xml version="1.0" encoding="*windows-1250*"?>
is breaking the build of fvwm on my solaris platform (as *windows-1250*
is not recognized as a valid encoding, at least on my solaris machine).
This problem seems to occur whether you enable or disable document
generation.
As a hack, I changed it to read
<?xml version="1.0" *encoding="ISO-8859-1"*?>
which seems to work fine. Could someone take a look at this as its stopping
me from upgrading from 2.4 to 2.6 because it won't build out of the box.
Platform: "SunOS 5.10 Generic_142901-04 i86pc i386 i86pc"
Unfortunately the machine I am trying to build on is not externally
networked so
can't use the fvwm-bug script to send in a bug report.
Best regards
Bob Goodrick
I don't know anything about the docbook generation stuff that was
added as part of 2.6, but the file
fvwm-2.6.4/doc/docbook-xsl/html/biblio-iso690.xsl
encoding entry on the first line of the file
<?xml version="1.0" encoding="*windows-1250*"?>
is breaking the build of fvwm on my solaris platform (as *windows-1250*
is not recognized as a valid encoding, at least on my solaris machine).
This problem seems to occur whether you enable or disable document
generation.
As a hack, I changed it to read
<?xml version="1.0" *encoding="ISO-8859-1"*?>
which seems to work fine. Could someone take a look at this as its stopping
me from upgrading from 2.4 to 2.6 because it won't build out of the box.
Platform: "SunOS 5.10 Generic_142901-04 i86pc i386 i86pc"
Unfortunately the machine I am trying to build on is not externally
networked so
can't use the fvwm-bug script to send in a bug report.
Best regards
Bob Goodrick