libwpg-devel — libwpg development

[Libwpg-devel] [ANN] libwpg 0.3.1 is out

[David T. <dt...@re...>]

libwpg is a library for import of WordPerfect Graphics images.

List of changes:

- Fix crash when NULL is passed as input stream.
- Use symbol visibility on Linux. The library only exports public functions
  now.
- Fix various crashes and hangs when reading broken files found with the
  help of american-fuzzy-lop.
- Fix some warnings found by Coverity.
- Make --help output of all command line tools more help2man-friendly.

Home page: https://sourceforge.net/p/libwpg/
Download from: https://sourceforge.net/projects/libwpg/files/libwpg/libwpg-0.3.1/

D.

Re: [Libwpg-devel] Scribus uses libwpg

[Kunda L. S. <scr...@gm...>]

On Mon, Jun 16, 2014 at 2:56 AM, David Tardon <dt...@re...> wrote:

> Hi,
>
> On Sat, Jun 14, 2014 at 05:40:11PM -0500, Kunda Loves Scribus wrote:
> > Just an FYI that on the Homeapage under: Projects using libwpg
> > you can add Scribus (http://scribus.net)
>
> We know about Scribus, but thank you for the notice anyway. The simple
> fact is that the homepage is hopelessly obsolete, but nobody has the
> will to update it anymore...
>
> D.
>

Hi David,

I would be happy to update the page for you. If you give me a list of
applications that use libwpg I'll add it. They know me pretty well at the
http://wiki.scribus.net. I'm all over the wiki recent changes. I have some
html skillz that helps me get by so..let me know :)

Cheers,
/Kunda

Re: [Libwpg-devel] Scribus uses libwpg

[David T. <dt...@re...>]

Hi,

On Sat, Jun 14, 2014 at 05:40:11PM -0500, Kunda Loves Scribus wrote:
> Just an FYI that on the Homeapage under: Projects using libwpg
> you can add Scribus (http://scribus.net)

We know about Scribus, but thank you for the notice anyway. The simple
fact is that the homepage is hopelessly obsolete, but nobody has the
will to update it anymore...

D.

[Libwpg-devel] Scribus uses libwpg

[Kunda L. S. <scr...@gm...>]

Just an FYI that on the Homeapage under: Projects using libwpg
you can add Scribus (http://scribus.net)

Cheers,
/Kunda

Re: [Libwpg-devel] Suppress warning/error with llvm/clang

[Ryo O. <ry...@yk...>]

From: David Tardon <dt...@re...>, Date: Mon, 3 Feb 2014 13:14:08 +0100

> Hi,
> 
> On Thu, Jan 30, 2014 at 10:55:47PM +0900, Ryo ONODERA wrote:
>> Hi,
>> 
>> pkgsrc <http://www.pkgsrc.org/> has libwpg patch for clang (attached).
>> See http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/converters/libwpg/patches/patch-src_lib_WPG2Parser.cpp?rev=1.1&content-type=text/x-cvsweb-markup
>> 
>> I think that this patch is good for gcc and clang.
>> Could you integrate this patch?
> 
> This was fixed by commit 5cf190eb365df00a1446738b3ab0d3e55291def3 ~2
> years ago. Also note that the referenced patch has got the parentheses
> wrong.

Thank you and sorry for wrong info.

--
Ryo ONODERA // ry...@yk...
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3

Re: [Libwpg-devel] Suppress warning/error with llvm/clang

[David T. <dt...@re...>]

Hi,

On Thu, Jan 30, 2014 at 10:55:47PM +0900, Ryo ONODERA wrote:
> Hi,
> 
> pkgsrc <http://www.pkgsrc.org/> has libwpg patch for clang (attached).
> See http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/converters/libwpg/patches/patch-src_lib_WPG2Parser.cpp?rev=1.1&content-type=text/x-cvsweb-markup
> 
> I think that this patch is good for gcc and clang.
> Could you integrate this patch?

This was fixed by commit 5cf190eb365df00a1446738b3ab0d3e55291def3 ~2
years ago. Also note that the referenced patch has got the parentheses
wrong.

D.

[Libwpg-devel] Suppress warning/error with llvm/clang

[Ryo O. <ry...@yk...>]

Hi,

pkgsrc <http://www.pkgsrc.org/> has libwpg patch for clang (attached).
See http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/converters/libwpg/patches/patch-src_lib_WPG2Parser.cpp?rev=1.1&content-type=text/x-cvsweb-markup

I think that this patch is good for gcc and clang.
Could you integrate this patch?

Thank you.

--
Ryo ONODERA // ry...@yk...
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3

Re: [Libwpg-devel] libwpg-0.2.2/src/lib/WPG2Parser.cpp:1030: possible bad expression ?

[David T. <dt...@re...>]

Hi,

On Mon, Dec 30, 2013 at 02:02:34PM +0000, David Binderman wrote:
> [WPG2Parser.cpp:1030]: (style) Expression '(X & 0x40) == 0x1' is always false.
> [WPG2Parser.cpp:1031]: (style) Expression '(X & 0x80) == 0x1' is always false.
> 
> Source code is
> 
>     bool granular = (flag & (1<<6)) == 1;
>     bool anchor = (flag & (1<<7)) == 1;

Indeed. I suppose the intent was the same as on lines 1004/1005, i.e.,

bool granular = ((flag & (1<<6))>>6) == 1

. But it is in debug code, so it is not a big deal.

> 
> Maybe
> 
>     bool granular = (flag & (1<<6));
>     bool anchor = (flag & (1<<7));
> 
> might be better code.

Yes, definitely. I committed that change.

D.

[Libwpg-devel] libwpg-0.2.2/src/lib/WPG2Parser.cpp:1030: possible bad expression ?

[David B. <dc...@ho...>]

Hello there,

I just ran the static analysis tool "cppcheck" over
the source code of libwpg-0.2.2. 

It said many things, including

[WPG2Parser.cpp:1030]: (style) Expression '(X & 0x40) == 0x1' is always false.
[WPG2Parser.cpp:1031]: (style) Expression '(X & 0x80) == 0x1' is always false.

Source code is

    bool granular = (flag & (1<<6)) == 1;
    bool anchor = (flag & (1<<7)) == 1;

Maybe

    bool granular = (flag & (1<<6));
    bool anchor = (flag & (1<<7));

might be better code.

Regards

David Binderman 		 	   		  

Re: [Libwpg-devel] librevenge and other generators

[David T. <dt...@re...>]

Hi,

I think this needs clarification:

On Fri, Nov 08, 2013 at 09:09:21AM +0100, Fridrich Strba wrote:
> 1) librevenge uses boost,

Boost is only used internally. It is not (and it shall not be) exposed
anywhere in the public API.

> but we don't want it to be runtime
> dependency, so no linking with it.

IOW, header-only "libraries" from Boost are okay (most of them fall to
this category). Libraries, which require linking, e.g., DateTime,
Filesystem or Threads, are not.

D.

[Libwpg-devel] librevenge and other generators

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

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

Hello, good people,

I just wanted to make public some disparate decisions that we took
around this week:

0) Since the family of libraries that depended on libwpd/libwpg is
growing steadily, we decided to create librevenge (blame me for the
name, but many of the libraries support REVerses ENGineered formats).
This one contains 3 sub-libraries: librevenge librevenge-generators
and librevenge-stream.

  - librevenge has the different api classes + helper types. And for
historical reasons it also has the svg generators (it used to be
internal for many graphic libraries and they were using it liberally).
  - librevenge-generators has raw, html, text generators that many
tools reuse.
  - librevenge-stream has basically the same thing as libwpd-stream in
0.9.x, but including inconditionally the handling of zip and ole2.
Also some of the methods were renamed to express that OLE is not the
only structure we handle.

1) librevenge uses boost, but we don't want it to be runtime
dependency, so no linking with it.

2) We ported the librevenge::RVNGPropertyList to use in the background
boost::property_tree::basic_ptree<std::string,
librevenge::RVNGProperty*>. As the result, this would allow us to make
the API a bit more generic. The RVNGPropertyListVector could be only
an interface over a vector node of that property tree. Making the
RVNGProperty also include RVNGPropertyListProperty and
RVNGPropertyListVectorProperty would allow us to do basically what
json can do. This is not set in stone, since we don't know what
problems might arise, but that is the general idea.

3) libodfgen library depends now exclusively on librevenge and all the
other libraries like libwpd and libwpg are now on the same level as
libvisio, libcdr, libetonyek, libmspub, libfreehand, libwps, libmwaw,
... and are independent from each other (besides libwpd and libwpg,
where libwpg uses libwpd to parse embedded strings in WP file-format).

That's it for today

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.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJ8nDEACgkQu9a1imXPdA/+SACeL8YDLYHKIlQ/xd3qSGk+PgJM
GVsAn0P6ikYRLaO90IGWYZEldfKAKwdB
=+gfa
-----END PGP SIGNATURE-----

[Libwpg-devel] Git migration of libwpg/libwpd complete, I think

[William L. <wr...@gm...>]

I just migrated the following modules to git:

libwpg-www
perfectspot
wpgtest

I think this completes everything, because as far as I know we didn't
want to move the other (obsolete) modules over from CVS. Just in case
I'm wrong, here's the procedure I used to do this, so someone else can
finish the work if I'm busy (obviously substitute your sourceforge
username for mine):

aubergine:perfectspot wlach$ ssh -t
lachancew,li...@sh... create
...
-bash-3.2$
-bash-3.2$ cd /home/scm_git/l/li/libwpg
-bash-3.2$ mkdir <module> # e.g. perfectspot
-bash-3.2$ git --git-dir=<module> init --shared=all --bare

Then, on the client end of things:

aubergine:libwpg-www wlach$ cvs
-d:pserver:ano...@li...:/cvsroot/libwpg login
aubergine:libwpg-www wlach$ git cvsimport -A
~/Documents/libwpg-authors.txt -o master -d
:pserver:ano...@li.../cvsroot/libwpg <modulen>

Where libwpg-authors.txt is a text file containing author info for
libwpg. Here's the one I used for perfectspot, libwpg-www, and
wpgtest:

strbafridrich = Fridrich Strba <fri...@bl...>
ariya = Ariya Hidayat <ar...@kd...>

When you've done that, you're ready to push:

git remote add origin
ssh://lac...@li.../gitroot/libwpg/<module>
git push --mirror origin

And that's it! If there's no further action required, I'll probably be
turning off CVS on sourceforge for libwpd/libwpg in the next week or
so.
-- 
William Lachance
wr...@gm...

Re: [Libwpg-devel] New way of updating web-pages

[William L. <wr...@gm...>]

2010/11/17 Fridrich Strba <fri...@bl...>:
> Hello, good people.
>
> Since the shell access on sourceforge.net is now a bit more difficult to
> script, I came with a different approach to updating the web-pages:
>
> For libwpd: I cloned a read-only libwpd-www git repository to htdocs
> directory and updating is done basically by pushing your local git to
> the server and then pulling it from the shell on the web-space.
>
> For libwpd: I checked out the libwpg-www CVS repository to htdocs and
> the updating is done by committing into the server CVS repo and updating
> it on the web-space.

I assume you mean libwpg here. We really should just by using git for
everything. It looks like I forgot to convert all the modules for
libwpg: I'll try to get to this later tonight.

> This has two advantages:
>
> 1) I hope that it helps us to keep the git repos on the server in sync
> with our local git repos which does not seem to have been the case right
> now :)

Oops, guess I forgot to commit my later changes.

> 2) It works around the new way of accessing the shell services on
> sourceforge.net, where one has to create the shell using "ssh -t
> USERNAME,PR...@sh... create" before being able to
> access that shell for 4 hours. After which it is again destroyed :)
>
> I hope I did not mess up anybody

For libwpd, I'd actually automated the process of updating the web
site using the sync-me script, unfortunately that didn't get pushed:

#!/bin/bash

[ -z $1 ] || UNAME=$1

scp ./*html ./*png ./*jpg ./*css ./*dia
$UNAME,li...@we...:/home/groups/l/li/libwpd/htdocs
ssh $UNAME,li...@we... chmod g+w
/home/groups/l/li/libwpd/htdocs/*

I like the idea of always using what's stored in git for the web site.
Maybe we could write a new shell script that does the pull for you
automatically? What's the manual procedure you're currently using for
that?
-- 
William Lachance
wr...@gm...

[Libwpg-devel] ATTN: libwpg 0.2.0 released

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

Hello, good people,

It is a pleasure and honour to announce the release of libwpg-0.2.0, the
next generation of libwpg.

Libwpg 0.2.0 is not backward compatible with libwpg-0.1.3 and both the
0.1.x and 0.2.x series can be installed in a parallel way on the same
machine (except the wpg2* tools).

The new features of this release can be summarized as follows:

- Rewrite the library to reuse wherever possible the libwpd types and
APIs.
- Rewrite the libwpg API to be similar to the libwpd API where the
arguments are passed as pairs of attribute name and values.
- Convert the embedded text inside graphics.
- Remove implementation of stream abstraction class and use the libwpd's
  WPXInputStream implementations.

Moreover, many bug fixes and improvements took place in this version.

Please, note that libwpg project does not distribute anymore the wpg2odg
standalone converter. the converter is not part of the writerperfect
sources distributed by libwpd <http://libwpd.sourceforge.net> project.
Since libwpd based solutions use libwpg to convert images embedded in
WordPerfect files and since libwpg used libwpd to parse the WordPerfect
documenent fragments embedded in WP Graphic files, it would be just a
pointless dupplication of code not to join the wpd2odt and wpg2odg into
the same module. And this has been done in writerperfect module in
libwpd's git.

The "perfectspot" CVS HEAD is buildable against the libwpg 0.2.0 and
libwpd 0.9.0 combo and it can display WPG files just fine.

We hope that you will enjoy this release and stay tuned for more
exciting news from libwpg front.

Cheers

Fridrich

[Libwpg-devel] New way of updating web-pages

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

Hello, good people.

Since the shell access on sourceforge.net is now a bit more difficult to
script, I came with a different approach to updating the web-pages:

For libwpd: I cloned a read-only libwpd-www git repository to htdocs
directory and updating is done basically by pushing your local git to
the server and then pulling it from the shell on the web-space.

For libwpd: I checked out the libwpg-www CVS repository to htdocs and
the updating is done by committing into the server CVS repo and updating
it on the web-space.

This has two advantages:

1) I hope that it helps us to keep the git repos on the server in sync
with our local git repos which does not seem to have been the case right
now :)

2) It works around the new way of accessing the shell services on
sourceforge.net, where one has to create the shell using "ssh -t
USERNAME,PR...@sh... create" before being able to
access that shell for 4 hours. After which it is again destroyed :)

I hope I did not mess up anybody

Cheers

Fridrich

[Libwpg-devel] Git migration nearly complete

[William L. <wr...@gm...>]

I moved the two remaining "interesting" libwpd modules (libwpd-www and
libwpd-bindings) to git today. I have NOT converted some legacy
modules (libwpd, testing, wpd2sxw, writerfilter). This means that when
I turn off CVS for libwpd (hopefully sometime soon) these will no
longer be accessible. Let me know if this is a problem, I personally
don't think it is as no production software depends on them.

I also gave the libwpd web site some long overdue updates, mainly to
reflect this, but also to take into account other things that have
changed (and also remove some things which are either no longer true
or just too boring to mention). :)

My plan for tomorrow is do the same for libwpg. I see a whole bunch of
modules here:

http://libwpg.cvs.sourceforge.net/viewvc/libwpg/

Which ones are important besides libwpg itself? libwpg-www,
perfectspot, wpg2odg at least I'd guess. Any others? As with libwpd,
are we ok with losing access to the modules which are no longer
important?

When this is done, my plan is to write a blog post on how awesome the
next version of libwpd will be, then mostly step back from the release
process (except for helping to squash bugs) while Fridrich and others
take over the reins.
-- 
William Lachance
wr...@gm...

[Libwpg-devel] Conversion to git

[William L. <wr...@gm...>]

It being 2010 and all, Fridrich and I have decided it time to migrate
libwpd and its sister project, libwpg, to a new version control
system: git (http://git-scm.com). This should make future libwpd
development faster, more pleasant, more secure, and maybe even more
welcoming to new contributors. To minimize disruption, we've decided
to keep using sourceforge.net's infrastructure: only the version
control system is different.

The new repositories for libwpd and libwpg are:

git://libwpd.git.sourceforge.net/gitroot/libwpd/libwpd (libwpd itself,
this was the libwpd2 module in CVS)
git://libwpd.git.sourceforge.net/gitroot/libwpd/regression (regression
testing suite)
git://libwpd.git.sourceforge.net/gitroot/libwpd/writerperfect
(writerperfect openoffice.org importer)
git://libwpg.git.sourceforge.net/gitroot/libwpg/libwpg (libwpg)

A few modules remain to be converted in both projects (libwpd-bindings
for libwpd and perfectspot, wpgtest for libwpg) but this can come
later. I also expect to deactivate the CVS repositories after a short
transition period.

-- 
William Lachance
wr...@gm...

[Libwpg-devel] Perfectspot changes

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

Hello, good people,

This e-mail is to indicate that I changed quite substantially how the
perfectspot draws the images internally. Until now, we had a listener
class that was listening to the events from libwpg and drawing the image
using corresponding Qt primitives. This was meaning that with the
change/addition of new callbacks in libwpg, one had to modify this
listener class. It meant for me quite a work since I am not as
conversant as Ariya with Qt. So, I decided to change that and use the
QtSvg module that supports pretty well the SVG that libwpg API
generates. Now we basically load the document, convert it to SVG into
memory and render that SVG using QtSvgRenderer class.

Please, shout louldly if you object

Cheers

Fridrich

[Libwpg-devel] Imminent release of libwpd 0.9.0 and libwpg 0.2.0

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

Hello good people,

On Friday, February 11 2005 we announced the release of libwpd 0.8.0 and
writerperfect 0.7.0, which later showed to be the most stable release
cycle libwpd had. The API was so well designed that we were able to add
support of several new WP file-formats and add an impressive list of new
converted features without touching the API at all. And we were able to
increase our stability and we are able to convert documents that
WordPerfect refuses to deal with
http://fridrich.blogspot.com/2006/07/upcomming-libwpd-086-more-robust-than.html

Now, 5 years later, it is time to close a chapter and release a new
series. Libwpd 0.9.x and libwpg 0.2.x underwent a lot of development and
QA testing and are getting ready to be released. They will support some
password protected documents, they will convert embedded images, text
boxes, comments and annotations and more other embedded objects.

Because of this close release, I would really love you to check the api
of libwpd:

Parser class:
http://libwpd.cvs.sf.net/viewvc/libwpd/libwpd2/src/lib/WPDocument.h?view=markup

Listener interface:
http://libwpd.cvs.sf.net/viewvc/libwpd/libwpd2/src/lib/WPXDocumentInterface.h?view=markup

and libwpg:

Parser class:
http://libwpg.cvs.sf.net/viewvc/libwpg/libwpg/src/lib/WPGraphics.h?view=markup

Listener interface:
http://libwpg.cvs.sf.net/viewvc/libwpg/libwpg/src/lib/WPGPaintInterface.h?view=markup

and give your comments and suggestions before I set them to stone for,
maybe, another 5 years.

Unlike libwpg 0.1.x, libwpg 0.2.x will depend on libwpd fully. The
reasons are that libwpd is not not depending on any platform dependent
stack, just on a normal C++ STL implementation. And it is just not wise
to dupplicate the structures of data in several libraries. Since this
approach would just increase the maintenance cost. It also helps us to
convert text embedded in WPG files, since the text is stored in the WPG
files as fragment of WPD (version 5 or version 6+).

Please, if you can, test the CVS head of libwpd2, libwpg and
writerperfect and give feedback (wpg2odg and wpd2odt both live in
writerperfect module).

Looking forward to your suggestions

Fridrich

Re: [Libwpg-devel] LIBWPG fork and scribus

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

Sounds fine, please, follow the development at
http://libwpg.cvs.sourceforge.net and give me hints if you want some
features that I did not include for the while.

Cheers

Fridrich

On Mon, 2009-09-07 at 22:40 +0200, Franz Schmid wrote:
> In reply to Craig i want to say that my current planing is the
> following:
> 
> - As long as libwpg-0.2 isn't released i want to use my fork for Scribus.
> 
> - Later on, when libwpg-0.2 is released i will change the build system
>   and the code of the plugin to use the libwpg.

[Libwpg-devel] LIBWPG fork and scribus

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

Hello, 

I am the maintainer and one of the authors of libwpg. I was pointed to
this thread http://bugs.scribus.net/view.php?id=8377 today. I was really
surprised that the development of libwpg was declared as stalled and
that you forked it. It is true that I committed the last code into the
HEAD about in December 2008 and that I am actively working on libwpg
rewrite to make the API more friendly for possible bindings from other
languages. Nevertheless, I am not really happy with a fork. It is true
that in FOSS, one can fork whatever one wants, but it would be just
polite at least to write an e-mail to the project developers that are
listed on the SourceForge page to ask about the status.

Libwpg as it is is used actively by inkscape, AbiWord, and GoOo version
of OpenOffice.org. The 0.2.0 version should be released pretty soon (in
2009) along with libwpd 0.9.0 and libwps 0.2.0. Why it is delaying?
Because libwpd 0.8.x and the dependent libraries were so stable that I
am running any attempt to release through a thorough testing including
fuzzing documents, so that we are sure that we don't crash with invalid
input.

Now, what about following: I propose that we simply work together to
discuss and incorporate the changes that are necessary for you in the
upcomming 0.2.0 release.

Cheers

Fridrich Strba
libwpg maintainer

[Libwpg-devel] [tbm@cyrius.com: Bug#505024: FTBFS with GCC 4.4: missing #include]

[Rene E. <re...@de...>]

Hi,

JFYI.

Regards,

Rene

[Libwpg-devel] ATTN: libwpg-0.1.1 is released

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

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

Hello,

Just to give you heads up about the recent release of libwpg-0.1.1.

This is a minor bugfix release that addresses a build issue with gcc
4.3. We profited to backport into this release the buffered file stream
implementation from libwpd. It means that a bulk conversion using
wpg2foo tools should be faster now.

Enjoy and cheers

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

iD8DBQFHVG/pu9a1imXPdA8RApaqAJ9cikS5SvB4fmTl5ApEDNC4SghBSQCfXC2v
NSAAgTyA4oaM3j531zzi1Ys=
=3OE3
-----END PGP SIGNATURE-----

[Libwpg-devel] Bugfix 0.1.1 early next week

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

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

Hello,

Early next week I will push a bugfix release of libwpg and wpg2odg 0.1.1

For the while only fixes to allow build with gcc 4.3 are in, if you have
something, just commit before that to the STABLE-0-1-0 branch for libwpg
and to the head for wpg2odg.

Cheers

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

iD8DBQFHUSlIu9a1imXPdA8RAsU9AKCAerY3kb3Ke4ybMolVfDwzU/ZuDgCfRjT5
1xhV20Ieuez12VA4KJqnUgQ=
=uje2
-----END PGP SIGNATURE-----

Re: [Libwpg-devel] [Libwpd-devel] Positioned objects in WPD files

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

Ariya,

Ariya Hidayat wrote:
> Fantastically cool! Really a good job, Fridrich!

Don't thank me, doing just my job :-)

> BTW, what do you think about my recent proposal to split the stream library?

Yes, as we agreed, working towards it. With the libwpd 0.9.0 release,
the stream library will be a separate one. I am separating it gradually,
since I have to maintain also the 0.8.x series and backporting starts to
be a tedious task as the head and stable branch start to look to
different. And also, I don't like to do too much infrastructure work in
one single session, because build systems are not something I really
find very fun these days.

But, having said this, from today on, in head, the WPXStream.h header
and the stream implementations do not use any of the libwpd headers
(libwpd_types.h are a purely internal header now). So, separation is a
question of a short time :-) And libwpg HEAD does not have the stream
implementations others then the internal one anymore.

So, cut short, working on it little by little.

Cheers

Fridrich

P.S.: If someone feels like writing an equation parser and eventually
output MathML-ish callbacks can be a fun, be my guest. I will give you
the doc for the old-style WP equations.