I inserted io.h into the list of include headers. That works on win32 and should not break the Linux.

BTW: Ted I noticed that you enclose global include files by " instead of '<' . Any special reason?

HTH,

Adib.

J.B.C.Engelen@...1578... schrieb:

SVN rev. 16051 errors with:

============================= Make error line 181: problem compiling: src/extension/implementation/xslt.cpp: I n member function 'virtual void Inkscape::Extension::Implementation::XSLT::save( Inkscape::Extension::Output*, SPDocument*, const gchar*)': src/extension/implementation/xslt.cpp:209: error: 'close' was not declared in this scope

I did not look into the details of the error. Thanks for fixing it, Johan

...

-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Ted Gould Sent: woensdag 12 september 2007 8:38 To: Inkscape Devel List Cc: Toine de Greef Subject: [Inkscape-devel] NEW: XSLT Input/output extension support

While it's been on my TODO list for a while, I finally realized how easy it was and finally did it. Using libxslt (which we already link to) Inkscape can now use XSLT stylesheets for input and output. (I thought about effects, is that useful to anyone?)

I've also included into the build a couple of SVG stylesheets I was interested in:

• AI SVG: cleans up Adobe SVG to only have in it the "good stuff"

• XAML: Toine de Greef posted on his blog[1] a set of XSLT

sheets to convert to and from SVG and XAML. What's really exciting to me about this is that they might be usable to finally bring SVG to IE using Silverlight[2] (at least what XAML supports). But, I think this makes Inkscape the first XAML editor outside of Expression.

More are out there. I know that Adobe had a ChemML to SVG stylesheet somewhere, but I've been unable to find it...

--Ted

[1] http://sanpaku72.blogspot.com/2007/09/having-fun-with-xaml-sil verlight-and.html [2] http://members.chello.nl/~a.degreef/xaml/svg_using_sliverlight.html

---

This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

J.B.C.Engelen@...1578... schrieb:

Thanks! But now:

Make error line 181: problem compiling: src/extension/internal/ps.cpp:83: error: 'std::libintl_fprintf' has not been declared

I couldn't find pjrm's mail address quickly.

Johan

I am also trapped there.

I reverted partly patch 16042. (the part regarding include files)

std::fprintf needs some intl part of the std library one i18n is added (I think).

pjrm pls review.

Adib. ---

Ted,

First, this is really great, but whan I write an email with a NEW: in subject, that email is usually just a copy of what I just added to the Release Notes :) Please always describe all your additions there in detail (and please fill in a wpg library placeholder marked as yours too).

On 9/12/07, Ted Gould <ted@...11...> wrote:

While it's been on my TODO list for a while, I finally realized how easy it was and finally did it. Using libxslt (which we already link to) Inkscape can now use XSLT stylesheets for input and output.

I tried to load the attached xaml file found on the net but I get a stream of errors:

runtime error: file /usr/local/share/inkscape/extensions/xaml2svg/properties.xsl line 160 element attribute xsl:attribute : node already has children

and then crashes:

*** glibc detected *** double free or corruption (!prev): 0x0a8dab20 ***

Emergency save activated!

(I thought about effects, is that useful to anyone?)

It may be useful, so if it's not too difficult please enable xslt effects too :)

On Wed, 2007-09-12 at 12:55 -0300, bulia byak wrote:

First, this is really great, but whan I write an email with a NEW: in subject, that email is usually just a copy of what I just added to the Release Notes :) Please always describe all your additions there in detail (and please fill in a wpg library placeholder marked as yours too).

Wasn't WPG added in 0.45?

I tried to load the attached xaml file found on the net but I get a stream of errors:

runtime error: file /usr/local/share/inkscape/extensions/xaml2svg/properties.xsl line 160 element attribute xsl:attribute : node already has children

and then crashes:

*** glibc detected *** double free or corruption (!prev): 0x0a8dab20 ***

Emergency save activated!

I can't comment on the XSLT stuff, hopefully Toine can. I'll figure out the crash though.

...

(I thought about effects, is that useful to anyone?)

It may be useful, so if it's not too difficult please enable xslt effects too :)

No, it shouldn't be too bad. I'll add that. Would this be an easier way to add filter effects?

--Ted

On Sep 12, 2007, at 11:05 AM, Ted Gould wrote:

Basically, I think the usage of them is pretty arbitrary. I try to provide some guidance of how I'm splitting inside and outside. I think in this file it was "inside Inkscape".

Yes, a bit.

I think that '<' '>' is for "system" includes, such as libraries. On certain platforms such as Netware, that was a lot clearer. :-)

I was thinking one rule of thumb was that if the .h comes from an installed .rpm or .deb on the system, then we go for '<'.

So I was thinking the subtle strangeness is a bit more of "system" vs "user" as opposed to "inside app" vs "outside app"

LCMS, for example, qualifies for angle brackets. Then again, some of the code of libs we've included in our source tree might qualify also.

Fun!

On 9/13/07, Ted Gould <ted@...11...> wrote:

On Wed, 2007-09-12 at 12:55 -0300, bulia byak wrote:

...

I tried to load the attached xaml file found on the net but I get a stream of errors:

I installed an update from Toine that fixes this. :)

Thanks, now it works!

Another problem (I assume it's an XSLT problem too): when I load the Lion.xaml file, edit it, and save as xaml again, the result gets transformed (scaled and moved). Comparing the files, I see that Canvas.RenderTransform in the original file was correctly converted to the transform of the top-level group in SVG, but that transform got lost when converting back to xaml.

Regarding the release notes addition for this, it would be perfect if you or the author of the XSLT convertor could list all the features which are successfully converted xaml<=>svg and all features that are lost in translation, with any tips and caveats you might think necessary. Thanks!

Ted,

more troubles with transforms in xaml conversion, as well as crashing on windows, please have a look:

http://sourceforge.net/tracker/index.php?func=detail&aid=1798193&gro...

On 9/13/07, bulia byak <buliabyak@...400...> wrote:

On 9/13/07, Ted Gould <ted@...11...> wrote:

...

On Wed, 2007-09-12 at 12:55 -0300, bulia byak wrote:

...

I tried to load the attached xaml file found on the net but I get a stream of errors:

I installed an update from Toine that fixes this. :)

Thanks, now it works!

Another problem (I assume it's an XSLT problem too): when I load the Lion.xaml file, edit it, and save as xaml again, the result gets transformed (scaled and moved). Comparing the files, I see that Canvas.RenderTransform in the original file was correctly converted to the transform of the top-level group in SVG, but that transform got lost when converting back to xaml.

Regarding the release notes addition for this, it would be perfect if you or the author of the XSLT convertor could list all the features which are successfully converted xaml<=>svg and all features that are lost in translation, with any tips and caveats you might think necessary. Thanks!

-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org