- Inkscape Devel - Inkscape Mailman

SVG standards and Sodipodi cruft
by Alan Horkan 25 Oct '05

25 Oct '05

There has been a user complaining in several reports in the bug tracker about the Inkscape SVG giving away more information than he would like and the Plain SVG not including as much information as needed and I think it raises various questions. How plain should Plain SVG be? Should it include metadata? (Based on SVG having a metadata tag I think it probably should include some form of metadata) Inkscape has as a stated goal conforming closely to the SVG specificiation but inlcudes a whole lot of information in the Sodipodi and Inkscape namespace. The stock response is this someone helps compatability with Sodipodi but is this really true anymore? Surely some of it like including the sodipodi version number is just as likely to confuse the matter? The old sodipodi docbase attribute seem like it could have been useful to avoid link breakage if a the drawing file has been moved around. Is this actually doing anything useful? Users have expressed privacy concerns as it effectively embeds the path to their homedirectory including username in every document. It seems there must be a way to express a lot more of the old sodipodi metadata using SVG (or Dublin Core or other parts of XMP we are already using). If the old timers ;) could clarify if any of this cruft is useful anymore it would make it easier to write clear bug reports and break into much smaller parts which bits might be replaced (hopefully making the same information available in Plain SVG where possible). Given the importance of the OpenDocument standard and how they are essentially using their XML namespaces to fill out gaps not covered by SVG might it be better to include their namespaces rather than adding any more to the Inkscape (or Sodipodi) namespace? I hope people can clarify what old bits are still needed and what could potentially be cleaned up and replaced with standard SVG. With a bit more information hopefully I will be able to add useful comments to bug reports and perhaps add some goals for clearing out the old non-standard cruft somewhere on the Roadmap. Sincerely Alan Horkan Inkscape http://inkscape.org Abiword http://www.abisource.com Dia http://gnome.org/projects/dia/ Open Clip Art http://OpenClipArt.org Alan's Diary http://advogato.org/person/AlanHorkan/

9 15

Re: [Inkscape-devel] Inkscape 0.43pre1
by Ted Gould 25 Oct '05

25 Oct '05

Lucas Vieites wrote: > there still are several translation updates pending in the tracker. > Could these be included in cvs before final release? Yeah, I don't see any reason why not. Does anyone know a reason that the translations aren't checked in? (besides lack of time :) Can I just check them all in? --Ted

1 0

Inkscape 0.43pre1
by Ralf Stephan 25 Oct '05

25 Oct '05

desktop.cpp:83:47: error: jabber_whiteboard/session-manager.h: No such file or directory desktop.cpp: In member function ‘void SPDesktop::init(SPNamedView*, SPCanvas*)’: desktop.cpp:297: error: invalid use of undefined type ‘struct Inkscape::Whiteboard::SessionManager’ desktop.h:55: error: forward declaration of ‘struct Inkscape::Whiteboard::SessionManager’ desktop.cpp: In member function ‘void SPDesktop::destroy()’: desktop.cpp:371: warning: possible problem detected in invocation of delete operator: desktop.cpp:371: warning: invalid use of undefined type ‘struct Inkscape::Whiteboard::SessionManager’ desktop.h:55: warning: forward declaration of ‘struct Inkscape::Whiteboard::SessionManager’ desktop.cpp:371: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined. make[2]: *** [desktop.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2

2 1

Translators - Calligraphy tutorial update
by Joshua A. Andler 24 Oct '05

24 Oct '05

Attached is the diff from the xml docbook file to assist translators to know what has changed. Other than added information, a number of contractions were removed to make translation a little more straightforward as well. Unfortunately I didn't get to put examples for pressure and tilt in due to tilt being funky with current gtk on win32 (and it makes sense to add the examples together). -Josh Index: calligraphy/tutorial-calligraphy.xml =================================================================== RCS file: /cvsroot/inkscape/doc-docbook/calligraphy/tutorial-calligraphy.xml,v retrieving revision 1.2 diff -u -r1.2 tutorial-calligraphy.xml --- calligraphy/tutorial-calligraphy.xml 30 Apr 2005 18:59:03 -0000 1.2 +++ calligraphy/tutorial-calligraphy.xml 24 Oct 2005 16:58:03 -0000 @@ -2,8 +2,8 @@ <chapter id="CALLIGRAPHY"> <title>Calligraphy</title> -<author>bulia byak, buliabyak@...859...</author> - +<authors>bulia byak, buliabyak@...859... and josh andler, scislac@...859...</authors> +<!-- Copyright (C) 2004-5 bulia byak, buliabyak@...859... and josh andler, scislac@...1050...> <abstract> <para> @@ -67,17 +67,34 @@ <title>Hardware</title> <para> -You'll get the best results if you use a <firstterm>tablet and pen</firstterm> -(e.g. Wacom). However, even with mouse you can do some beginning calligraphy, though you -will have difficulty producing fast sweeping strokes. +You will get the best results if you use a <firstterm>tablet and pen</firstterm> +(e.g. Wacom). Thanks to the flexibility of our tool, even those with only a mouse can do +some fairly intricate calligraphy, though there will be some difficulty producing fast +sweeping strokes. </para> <para> -Inkscape does not yet use <firstterm>pressure sensitivity</firstterm> of a tablet pen, -but that's not a problem because a traditional calligraphy pen (unlike a brush) is also -not very sensitive to pressure. Inkscape calligraphy pen can be sensitive to the -<firstterm>velocity</firstterm> of the stroke (see "Thinning" below), so if you are -using a mouse, you'll probably want to zero this parameter. +Inkscape is able to utilize <firstterm>pressure sensitivity</firstterm> and <secondterm> +tilt sensitivity</secondterm> of a tablet pen that supports these features. The sensitivity functions are disabled by +default because they require configuration. Also, keep in mind that calligraphy with a +quill or pen with nib are also not very sensitive to pressure, unlike a brush. +</para> + +<para> +If you have a tablet and would like to utilize the sensitivity features, you will need +to configure your device. This configuration will only need to be performed once and +the settings are saved. To enable this support you must have the tablet plugged in +prior to starting inkscape and then proceed to open the <firstterm>Input Devices...</firstterm> +dialog through the <emphasis>File</emphasis> menu. With this dialog open you can choose the +preferred device and settings for your tablet pen. Lastly, after choosing those settings, switch +to the Calligraphy tool and toggle the toolbar buttons for pressure and tilt. From +now on, Inkscape will remember those settings on startup. +</para> + +<para> +The Inkscape calligraphy pen can be sensitive to the <firstterm>velocity</firstterm> of +the stroke (see "Thinning" below), so if you are using a mouse, you'll probably want to +zero this parameter. </para> </sect1> @@ -85,9 +102,10 @@ <title>Calligraphy Tool Options</title> <para> -Switch to the Calligraphy tool by pressing <keycap>Ctrl+F6</keycap> or by clicking on -its toolbar button. On the top toolbar, you will notice there are 6 options: Width & -Thinning; Angle & Fixation; and Mass & Drag. +Switch to the Calligraphy tool by pressing <keycap>Ctrl+F6</keycap>, pressing the <keycap>C</keycap> +key, or by clicking on its toolbar button. On the top toolbar, you will +notice there are 6 options: Width & Thinning; Angle & Fixation; and Mass & Drag and two +buttons to toggle tablet Pressure and Tilt sensitivity on and off (for drawing tablets). </para> <figure> @@ -113,8 +131,9 @@ <para> Since pen width is changed often, you can adjust it without going to -the toolbar, using the <keycap>left</keycap> and <keycap>right</keycap> arrow keys. The best thing about -these keys is that they work while you're drawing, so you can change +the toolbar, using the <keycap>left</keycap> and <keycap>right</keycap> arrow keys or with a +tablet that supports the pressure sensitivity function. The best thing about +these keys is that they work while you are drawing, so you can change the width of your pen gradually in the middle of the stroke: </para> @@ -160,8 +179,10 @@ <para> After width, <firstterm>angle</firstterm> is the most important calligraphy -parameter. It is the angle of your pen in degrees, changing from 0 (horizontal) to 90 -(vertical counterclockwise) or to -90 (vertical clockwise): +parameter. It is the angle of your pen in degrees, changing from 0 (horizontal) to +90 (vertical counterclockwise) or to -90 (vertical clockwise). Note that if you +turn tilt sensitivity on for a tablet, the angle parameter is greyed out and +the angle is determined by the tilt of the pen. </para> <figure> @@ -175,9 +196,10 @@ Each traditional calligraphy style has its own prevalent pen angle. For example, the Unicial hand uses the angle of 25 degrees. More complex hands and more experienced calligraphers will often vary the angle while drawing, and Inkscape makes this possible -by pressing <keycap>up</keycap> and <keycap>down</keycap> arrow keys. For beginning -calligraphy lessons, however, keeping the angle constant will work best. Here are -examples of strokes drawn at different angles (fixation = 1): +by pressing <keycap>up</keycap> and <keycap>down</keycap> arrow keys or with a tablet that +supports the tilt sensitivity feature. For beginning calligraphy lessons, however, +keeping the angle constant will work best. Here are examples of strokes drawn at +different angles (fixation = 1): </para> <figure>

1 0

About screen for 0.43
by Jon A. Cruz 23 Oct '05

23 Oct '05

I'm tracking down bug 1310742 It appears that the SVG is slightly corrupted. It looks like a chunk of the file got lost. Doing a quick restoration of "text44" (the item that appears to be picking up after the missing part), I see that it is mainly "the vector is mightier than the Bitmap", written in a script font. This problem may have been in the initial editing, or may have happened later. If anyone might have different versions laying around, can you check if they do not have this problem? The following will check for the main problem point: grep -l "preser," * If nobody has a better version (or at least for that part), then I'll just go with cutting out "text44", since it appears to be cruft anyway.

1 0

Inkscape 0.43pre0
by Ted Gould 23 Oct '05

23 Oct '05

First prerelease of all the goodness being expected in Inkscape 0.43. This is not recommended for production use, it still has known bugs in it. It is recommended that you download it, play with it, and find more bugs. If all packagers could try to make packages from this tarball, that would be helpful for removing packaging bugs. I think that I missed some from the last time 'round, so if you could put them in the tracker that would be excellent. https://sourceforge.net/project/showfiles.php?group_id=93438&package_id=991… MD5 Sums: ed274d011189a2f496c93b84c9a30d7a inkscape-0.42+0.43pre0.tar.bz2 02b6199ce64d830d288e21ad2a0d6e07 inkscape-0.42+0.43pre0.tar.bz2.sig bb962f1c6d019ed747231015869ca315 inkscape-0.42+0.43pre0.tar.gz 06d97f80b5ef59a97af73e154e688147 inkscape-0.42+0.43pre0.tar.gz.sig Have fun, Ted

8 10

RE: [Inkscape-devel] RE:Xara Announcement
by Charles Moir 22 Oct '05

22 Oct '05

> > This would be a good opportunity to pimp another project that Inkscape's > > been participating in, called create.freedesktop.org.... > > > > http://create.freedesktop.org/wiki/index.php/Main_Page > > > > The idea is > > interoperability; despite our differences, all of us open source > > graphics tools can be stronger by sharing art resources. > > > > Anyway, put that in your todo list to check out next month or so when > > some of the fires have died down. Long term you'll want XaraExtreme to > > be part of, or at least aware of, those discussions. > > Hi Charles...if you or any other xara devs. have questions about the > Create Project, you can ask me or join the create mailing list from the > URL above. > > Also, it would be good to dicsuss integration with Open Clip Art Library > in the near future...its time to build up our community, right! > These are all good things. I have some issues about quality control on OpenClipart, but the principle is great. We will support these as much as we can. Exactly the type of working together that helps everyone. Charles

5 4

[CharlesM@...1042...: [XaraXtreme-dev] Updated Xara LX download]
by Bryce Harrington 21 Oct '05

21 Oct '05

----- Forwarded message from Charles Moir <CharlesM@...1042...> ----- Date: Fri, 21 Oct 2005 17:51:10 +0100 From: Charles Moir <CharlesM@...1042...> To: xara-dev <dev@...1048...> Subject: [XaraXtreme-dev] Updated Xara LX download We've updated the Xara LX viewer download to version 0.1b. http://www.xaraxtreme.org/download/ This includes support for the (almost) full range of Xara fill types, along with a number of other fixes which means it should now load and render a much wider range of Xara documents. We've also updated the Designs folder to include some more examples such as the famous Microscope design. There's also a Fill Types.xar example that shows off some of the wide range of basic object fill types that Xara supports (one of the distinguishing aspects of the Xara rendering engine is its very wide range of basic fill types). Apart from progressing the Xara LX preview build, we've been continuing to work on the source codes files, documentation etc in preparation for making this Open Source. We hope to start this process within a week or two. Charles ----- End forwarded message -----

1 0

Win32 filename fixup
by Jon A. Cruz 21 Oct '05

21 Oct '05

For those who are interested in building and testing the Win32 changes I'm doing for filename fixups, I just checked in a much better version. What I had before was mainly code to check things, not change things, and was placed *after* the main app instance was created with the args. Moving the code up above the instance creation made things much happier. It still has a major problem in that things are stripped to bare filenames with no path preceding them, so files need to be placed in the same location as inkscape.exe to be tested. However, it should get things working with all Unicode names (not just those in the current ANSI code page). The other thing to check is in src/io/sys.cpp at line 129. To get things opening correctly, we can probably simplify the code now that we're using GTK+ 2.6 or later on Windows. Change if ( PrintWin32::is_os_wide() ) to if ( false ) and that should finish fixing things (aside from the full-path issue, of course). If anyone can verify that the sys.cpp change keeps things working with different names (non-ASCII, non-Cp1252, etc) that would be very good to hear.

2 1

Re: [Librsvg-devel] Re: [Inkscape-devel] Plain SVG as default ?
by Christian Fredrik Kalager Schaller 21 Oct '05

21 Oct '05

Hi John, If you want a pretty good indication on the current status of the different rendering engines you could take a look at my comparison chart here: http://www.linuxrising.org/svg_test/test.html It lists all the SVG engines discussed in this thread and I updated the librsvg-cairo one just an hour ago. I also hope someone in the Inkscape community gets motivated to start working on the compliance tests as afaict there have been little progress on Inkscape's SVG standard compliance over the last few months (tons of other improvements though :). Christian On Wed, 2005-10-19 at 03:33 -0600, John Taber wrote: > Dominic Lachowicz wrote: > >>I can barely make time for testing a new lib under cairo so can't afford > >>to get involved with trying to get hooked into cvs etc - if libsvg is > >>deprecated and librsvg is really in flux, what is Gnome using in current > >>development (v2.11) for rendering svg? > > > > Gnome has always used librsvg. It has never used libsvg. Gnome's > > development version is 2.13, not 2.11. > > > > The version of librsvg that Gnome uses renders via libart and not cairo. > > > Now I get it - I was thinking Gnome was now rendering svg via cairo. So > for now I'll use libsvg-cairo knowing that it may have some problems and > knowing that it is planned to be replaced with librsvg-cairo sometime in > near future. When a version of librsvg-cairo becomes available outside > of cvs or I have time to fool with the cvs settings, I'll try it out and > feedback to the librsvg list. thks. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Librsvg-devel mailing list > Librsvg-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/librsvg-devel

5 7