From: Edward M. <em...@co...> - 2011-04-23 02:23:17
|
Fridrich On 22 Apr 2011, at 5:12 PM, Fridrich Strba wrote: > > 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. Your instructions worked perfectly. I built a portable wpd2odt that runs on any other OS X 10.6 system. Thank you! I've written a bash script that updates libwpd and writerperfect with git and then compiles and builds all three components, so I can update this whenever you update The conversions work extremely well. Thank you! Question: is it possible to guess which version of LibreOffice will have the new version of libwpd? Edward Mendelson |