Activity for WordPerfect Document importer
-
Edward Mendelson posted a comment on discussion Open Discussion
And here is the bad SVG output, attached.
-
wpg2odg produces the correct ODG output when converting the attached WPG1 file from WPDOS 5.1 wpd2svg, unfortunately, produces an SVG file with triangular artifacts and black fill. Is it possible to fix this?
-
Fridrich Strba merged merge request #2 on Code
some more const ups
-
Caolán McNamara created merge request #2 on Code
some more const ups
-
const up some things
-
const up some things
-
a const up
-
a const up
-
I've posted a bash script that builds static-linked macOS executables for libwpd under macOS: https://github.com/emendelson/libwpd-build-macos/tree/main I hope someone finds it useful.
-
Missing cstdint include in libodfgen's src/OdfGenerator.cxx
-
Integrated
-
Missing include
-
Sam James posted a comment on ticket #27
Patch attached.
-
Missing cstdint include in libodfgen's src/OdfGenerator.cxx
-
Update NEWS
-
WPDocument::isFileFormatSupported returns WPD_CONFIDENCE_EXCELLENT for an HTML with éééé
-
https://sourceforge.net/p/libwpd/code/ci/bc3050ad804b4f9f60ccfaf425f469fc095033dc/
-
https://sourceforge.net/p/libwpd/code/ci/bc3050ad804b4f9f60ccfaf425f469fc095033dc/
-
Besides plain text documents, try to reject a documents that only contain valid utf-8
-
Fix a debug build
-
Make work with newer astyle
-
Mike Kaganski created ticket #26
WPDocument::isFileFormatSupported returns WPD_CONFIDENCE_EXCELLENT for an HTML with éééé
-
I finally got around to filing a bug with LibreOffice, where it's most likely to get attention: https://bugs.documentfoundation.org/show_bug.cgi?id=158793
-
You are right. Libwpd contains a WP4.x parser, but it doesn't seem to handle extended characters correctly, and the file libwpd_internal.cpp has a table of WP42 extended characters, but wpd2odt and LibreOffice do not (as you say) seem to use it correctly. The table seems to be correct, but it seems that wpd2odt doesn't correctly recognize WP4.2 files - and that isn't surprising, because the only way to do so would be to scan the file for some specific codes that may not be there at all.
-
You are right. Libwpd contains a WP4.x parser, but it doesn't seem to handle extended characters correctly, and the file libwpd_internal.cpp has a table of WP42 extended characters, but wpd2odt and LibreOffice do not (as you say) seem to use it correctly.
-
Libwpd doesn't try to convert WPDOS 4.x documents, and there's almost no way for LibreOffice to recognize that a file is a WP 4.x file, becuase it won't have a file header that identifies it. The only current applications that can open these correctly is probably WordPerfect for Windows, and it will prompt you to confirm that the file is a WP 4.2 file.
-
Peter Janes created ticket #25
French accented characters not converted correctly
-
This is correct now. Thank you. I think it can be applied to LibreOffice now...
-
Actually, I am the one confused. Most likely, I ran the "make astyle" with unsaved changes and reloaded the file afterwards. Now it should be ok.
-
another attempt to fix this correctly
-
I may have may things confusing; if so, I apologize. The latest commit doesn't correct line 808 of libwpd_internal.cpp. The line should read: 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03ae, 0x03af, Notice that the seventh code is 0x03ae, NOT 0x03a5 as it is now. This is the only thing that needs to be changed. Thank you for this!
-
Revert a part of commit introducing error already fixed
-
Thank you! One character is now incorrect, because the code before the old commit had an error that was later fixed. To clarify, the second of the three changed lines should NOT have the change from 0x03ae to 0x03a5 shown below: 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03ae, 0x03af, <--CORRECT 0x03a8, 0x03c8, 0x03a9, 0x03c9, 0x03ac, 0x03ad, 0x03a5, 0x03af, <-- WRONG The other two changed lines now have the correct code. I built your latest commit under macOS and can confirm that only one...
-
I reverted the commit. Please verify whether this did not change a character that was correct to something wrong.
-
Document the revert
-
Fix tdf#153034: Three wrong Greek characters in WordPerfect 5 import
-
For what it's worth, I've posted a guide to building the libwpd/libwpg/writerperfect executables under Windows: http://www.columbia.edu/~em36/wpdos/libwpd.html Notice that the address begins with "http://" If you get a 404 error, that's because your browser changes http:// to https:// Change it back to http:// and the page will open.
-
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
-
alonso laurent modified ticket #24
libwpg: fix configure.ac to build in Windows
-
Thank, I just commit 29244c855c26f6a7e699ffe8fa313b026a57c6d4 to correct this problem
-
Trying to build under Windows
-
After personal discussions, the problem seems to concern libwpg, so I closed this ticket.
-
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
-
libwpg: fix configure.ac to build in Windows
-
I've done some further testing, and the change definitely should be reverted, because it substituted the correct characters with characters that would print in an obsolete program that got it wrong. Both Corel (in current WordPerfect for Windows) and Microsoft (with its WP import filter) use the original mapping that got changed incorrectly. Here is a WordPerfect for DOS 5.1 file with the four relevant characters: https://www.dropbox.com/s/hogzhfhx4ulm8wr/GREEKWP5.WP?dl=0 Here is the same file opened...
-
Update: thanks to the generous and patient help of Laurent Alonso, I was able to build WriterPerfect 0.9.6 under both MinGW and Cygwin. I needed to make three changes in the source code, and will post a patch when I've got the details correct.
-
I get the same error message when I try to configure in cygwin and WSL Ubuntu. Is it possible that something is wrong in the code? Has anyone built current libwpd for Windows?
-
Trying to build under Windows
-
WordPerfect Document importer released /librevenge/librevenge-0.0.5/librevenge-0.0.5.tar.bz2
-
-
-
-
David Tardon committed [885c8c] on librevenge
add an empty line
-
bump micro version
-
prepare for a release
-
gdb: fix generation of autoloaders
-
do not distribute generated files
-
configure: fix pretty printers' enablement
-
gdb: support newer python versions
-
gdb: handle extraction from shared_ptr better
-
gdb: do not break on failed extraction from shared_ptr
-
It's easy to test which is right. Export the Greek character set from WP5 (perhaps using LibreOffice to producde the output) and see if those characters match the unicode glyphs with the same name. You'll see that the two characters I mentioned are incorrect. The report on the change was made so that output from a commercial product called Printer Polyglott looked right; it seems that Printer Polyglott had mistakes that LibreOffice and modern Linux doesn't have.
-
configure: cannot guess build type
-
This was an intentional change: https://sourceforge.net/p/libwpd/code/ci/0bacfbb3e035174308cb7dd87acfca320dda3912 . But I've no idea which variant is correct. It is all greek to me... (Sorry, couldn't resist.)
-
Wrong characters in WP5 Greek character set
-
Coelacanthus posted a comment on ticket #21
Just generate new tarball with new autotools.
-
avimitin posted a comment on ticket #21
Affected project: libwpd, librevenge, libodfgen
-
configure: cannot guess build type
-
Miklos Vajna committed [c42512]
Add support for libdrawio
-
Ryan Qian posted a comment on ticket #20
Thanks for your reply. For .pdb, here are some examples, and all can be opened by fbreader. For .qxp, I don't know the exact version... maybe the tested file is created by an unsupported version.
-
I cannot tell without seeing the files. Judging by the errors, the pdb file may be damaged (the AportisDoc format is really simple, so there's not much that could go wrong during parsing), while the qxp file is probably a version not supported by libqxp (libxpp only supports documents written by QuarkXpress 3.0-4.1. One reason is that these versions were the most widespread, the other one is that every version starting with 3.1 added a new obfuscation bits into the file format, making it progressively...
-
Is writerperfect able to convert PalmDoc Ebook(.pdb) and QuarkXpress(.qxp) Documents?
-
librevenge SVG page size uses 72dpi instead of 96dpi
-
Add viewbox to svg to fix the user unit to inch ratio
-
Nathan Lee created ticket #19
librevenge SVG page size uses 72dpi instead of 96dpi
-
Add a note about font subgroups used by WPG1
-
ALONSO Laurent committed [8717c4]
paragraph style: retrieve style:writing-mode's property.
-
ALONSO Laurent committed [c6b774]
Avoid a division by zero for empty elliptical arc...
-
-
-
-
ALONSO Laurent committed [811903]
configure.ac: update micro revision to prepare a release...
-
ALONSO Laurent committed [6d82aa]
appendXML: try to retrieve the main namespace...
-
ALONSO Laurent committed [03c5ee]
cppcheck: correct some warnings...
-
ALONSO Laurent committed [208f71]
update README/NEWS files...
-
ALONSO Laurent committed [7de53e]
astyle: ...
-
ALONSO Laurent committed [424983]
configure.ac: HAVE_VISIBILITY must be always defined...
-
ALONSO Laurent committed [2edf8a]
GraphicStyle.cxx: try to retrieve style:print-content
-
Parth Kapadia posted a comment on discussion Help
Hey, I am new to libwpd. I want to extract text from wpd files in a C++ program. I installed libwpd using sudo apt-get install libwpd-dev I am including these header files in my code, but it gives the error that WPXStreamImplementation.h not found #include <libwpd/WPDocument.h> #include <libwpd/WPXStreamImplementation.h> These are the flags I used in my code -I/usr/local/include/librevenge-0.0 -I/usr/include/libwpd-0.10 -L/usr/local/lib -lwpd-0.10 -lrevenge-0.0 (generated from pkg-config --libs --cflags...
-
I am trying to install libabw, and facing a similar problem.(Ubuntu 19.10) I also did apt-get install librevenge-dev, but it still shows the same error: No package 'librevenge-0.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables REVENGE_CFLAGS and REVENGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details.
-
I am trying to install libabw, and facing a similar problem. I also did apt-get install librevenge-dev, but it still shows the same error: No package 'librevenge-0.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables REVENGE_CFLAGS and REVENGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details.
-
If you want any help, you'll have to describe what you are doing. What do you mean by "install"? What action(s) lead to that message?
-
Ian Van Giesen modified a comment on discussion Open Discussion
Thanks Mikhail, people like you make this experience a lot better! Unfortunately, I'm so new to do doing all this stuff, I must be missing something simple. I'm running Bash on Ubuntu on Windows, so yum install ... didn't work and neither did sudo apt install. I installed the librevenge onto a separate folder in /Code/librevenge and when I run ls I get: AUTHORS astyle.options configure librevenge-stream.pc.in COPYING.LGPL autogen.sh configure.ac librevenge.pc.in COPYING.MPL autom4te.cache createBuildNumber.pl...
-
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"><meta content="Microsoft Word 15 (filtered medium)" name="Generator"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only;}...
-
Mikhail T. posted a comment on discussion Open Discussion
Ubuntu may be following the same anti-developer principles of splitting packages, but the naming is different. The apt-get install librevenge-dev should work on a regular Ubuntu/Debian, not sure about the "Ubuntu on Windows"...
-
Thanks Mikhail, people like you make this experience a lot better! Unfortunately, I'm so new to do doing all this stuff, I must be missing something simple. I'm running Bash on Ubuntu on Windows, so yum install ... didn't work and neither did sudo apt install. I installed the librevenge onto a separate folder in /Code/librevenge and when I run ls I get: AUTHORS astyle.options configure librevenge-stream.pc.in COPYING.LGPL autogen.sh configure.ac librevenge.pc.in COPYING.MPL autom4te.cache createBuildNumber.pl...
-
Unlike better operating systems (like FreeBSD), RedHat splits most third-party packages into foo and foo-devel. The former is sufficient to use the programs built by others, the latter is required to build new ones. Whenever I have use a RedHat/CentOS/Fedora machine, I hold my nose while adding the devel counterpart to each installed package. Only then does the system become usable for building from source -- which should be the only way to install open source software. So, Ian, what David was saying...
-
What do you mean? I've run into the same problem, and I have no idea what to do here.
-
Miklos Vajna committed [aa738b]
Make these member functions static
1 >