Re: [Libwpd-devel] Results for wpd2odt with some real-world WPMac files

[Fridrich S. <fri...@bl...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward,

On 22/04/11 16:15, Edward Mendelson wrote:
> However, I also tried the conversion with two real-world files that I was sent by the person who first asked about this. These real-world files are here:
> http://dl.dropbox.com/u/271144/Attachments.zip

They exposed a bug in libwpd that was assuming that the Text Font
function's "font name" pascal string contains only ascii characters. I
saw in the file, that if the character code is between 0x20 (space) and
0x7f, it is an ascii character, when it is bigger or equal to 0x80, it
is basically the higher byte of a double byte script. I fixed the font
name reading to work accordingly. Those documents have some font names
encoded in CJK characters and the xml that we were producing by
writerperfect was not a valid xml because the character strings were not
a valid UTF-8 due to our misunderstanding that I mentioned above.

It is now enough to pull libwpd again doing:

	git pull -r

inside the libwpd directory and rebuild that one.

BTW, to the question how to build a static everything, configure all
(libwpd, libwpg and writerperfect) using --enable-static
- --disable-shared configure options. You can even change the installation
location by using --prefix=/path/where/you/want/to/have/them.
Note, that in that case, you will have to adapt your PKG_CONFIG_PATH
variable accordingly.

Cheers

F.

- -- 
Please avoid sending me Word, Excel or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk2x7y4ACgkQu9a1imXPdA9q4ACbBWdxSa/BnaC8TUiTkDN+AuDz
BykAn0V0PPOfEWZ9tU9lWL32Aj8aLdv5
=cLWD
-----END PGP SIGNATURE-----