- Inkscape Devel - Inkscape Mailman

static prerelease builds?
by bulia byak 30 Oct '04

30 Oct '04

It's very nice to see the overwhelming response to the bug review call. Thanks everyone. Now, the other thing we need to do is, of course, finding more bugs to fix :) With the recent bugfixes, I think the time to test it in earnest has come. So I would like to ask if anyone is capable of providing periodic builds of Inkscape to be uploaded to SF as a testing/prerelease series, the same as Ted did for 0.39. However the important thing about the 0.40 testing builds is that they must be linked statically. With all the new libraries we now use, and with all the reported incompatibilities of their versions, it is critically important that at least Boehm and libsigc++ are static, and maybe also gtkmm and others. This will make it so much easier for people to try out the builds. We will have to provide static builds of the final release, so why not start testing the static build process right now. Any volunteers?

4 6

Bug summary 10/28
by Bryce Harrington 29 Oct '04

29 Oct '04

Bug ID Pts Title ------------------------------------------------------------------------ 1029755 3 png resolution not imported 1039109 9 various problems with text after refactoring 980065 6 Garbled display in "pattern" fill dialog 1048802 6 2 find dialogs 1029530 (dup) WIN CVS: crash on file | import 1051350 (dup) Crash when open a file 990659 6 ill2svg fails without Image/Magick 1054270 9 Win32: Aligning objects causes crash 1048614 6 export: "selection" not toggled with text 931496 6 image URL not updating 998672 (dup) printing broken on Windows XP 1001279 6 Version: 0.39-suse91.0 rpm needs libpopt.so.0 1012089 6 CVS snapshots no longer available 996493 (dup) .39 Inkscape freezes 992962 3 Build Warning: Extensions warnings 992986 3 Build Warning: deprecated functions 992987 3 Build Warning: missing constructors 992985 3 Build Warning: unused variables/functions 1004134 6 'Changed' flag cleared when save not successful 1041643 3 Files fail to open on Gnome 2.8 1048151 6 Union destroy objects in some cases 984096 9 Assertion failures with calligraphy tool 1045067 3 --without-gui crashes if home dir not writable 1038932 6 Export silently fails when file cannot be created 984854 9 crashes with non-existent gradient in gradient editor 1000350 9 --print option can attempt to open dialogs and segfault 1041757 (dup) undefined symbol: gdk_threads_lock 993294 9 RDF improperly exported with plain SVG 1024915 9 glib-2.5.2: crashes on clicking fill and stroke dialog ======================================================================== Total: 144 Goal: 150pts (96% towards goal)

1 1

Relative paths
by Jon A. Cruz 29 Oct '04

29 Oct '04

I've hit two issues 1) There appears to be a bug in sp_relative_path_from_path that chokes when you go up above the current directory. Like if you try to reference and image you'd expect to end up "../../other/thing.png" 2) Image paths currently are 'fixed' to be relative when you save svg. For problem #1 I know what to do. However, for problem #2 I'd want to confirm desired behavior. I was thinking that the proper thing would be to fixup to relative paths whenever a file is first imported. Does this sound reasonable?

2 1

No Snap for transforming
by David Christian Berg 29 Oct '04

29 Oct '04

Hi guys, esp. Bulia, Pressing Alt while moving allows you not to snap to grid... but with my build it doesn't work for other transformation. Is that still the case? If so I'll file a bug for you hunt... probably an easy to fix :) David

2 1

Inkscape 0.40 release planning
by Bryce Harrington 29 Oct '04

29 Oct '04

At the beginning of this month we kicked around the idea of doing an interim release, because even though we're not 100% done with the goals, there's a lot of new features and the time feels right for a new release. :-) We considered either calling it 0.39.5 and keeping with the roadmap as is, or calling it 0.40 and bumping the roadmap a bit. I believe there was a rough concensus for the latter at the time - this still true? In any case, the two tasks facing us right now are the same: 1. Finish up current work 2. Fix bugs (esp. the more noticeable ones) Like we've done in past releases, I'll begin posting critical bug summaries daily from now until the release so we can track our progress. How do we want to track it? * Fix X % of the critical bugs (e.g. fix 50% of crits)? * Reduce the bug list to a threshhold (e.g. 100?)? * Identify N specific bugs to fix? I browsed through the bug list yesterday, and we seem to be in fairly good shape (thanks most likely to the continuing attention the bug list receives). There are fewer crash bugs listed than we've had in the past, and most of those occur only in special situations (such as Win32-only), but some of the remaining bugs are particularly hard ones to fix. In any case, let me know what you think we should set as the goal for this release, and I'll start posting our progress on that by the 26th. Bryce

8 34

RE: [Inkscape-devel] caption for Layer - not readable (extended) more questions
by Taraben, Adib 29 Oct '04

29 Oct '04

Ok I changed from verdana 6.5 to verdana 10. looks better. If I uncomment this line I get best results (System default) Questions: - what are the small (I guess) buttons left to the layer combobox. They work like select boxes (check, uncheck) - what is the meaning of the two comboboxes ? - the first caption of the dropped-down combobox what should there be ? "root" as in the more left combobox ? Thanks, Adib. -----Original Message----- From: inkscape-devel-admin(a)lists.sourceforge.net on behalf of Michael Wheeler Sent: Thu 10/28/2004 17:34 To: bulia byak; Inkscape ML Subject: Re: [Inkscape-devel] caption for Layer - not readable Changing the name of the etc\gtk-2.0\gtkrc file seems to restore the font sizes to normal on my system (win2k). Looking at the contents of gtkrc it seems like it would not be too much trouble to set the font face and size from within that file. -Michael bulia byak wrote: >> My problem I cann not read the caption on the layer-combo-box on the >>statusbar. The Font is to small or hiroglyphic ?? >> >> attached screenshot. >> >> > >In this screenshot all fonts are much smaller than on Linux while the >height of the statusbar is the same. There was another report of fonts >being too small on Windows (smaller than in 0.39). Can anyone with a >Windows build confirm/investigate this? The font size is likely >settable somewhere. > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Sybase ASE Linux Express Edition - download now for FREE >LinuxWorld Reader's Choice Award Winner for best database on Linux. >http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click >_______________________________________________ >Inkscape-devel mailing list >Inkscape-devel(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

3 3

rendering-color-space; SVG 1.2 Last Call Comments
by MenTaLguY 29 Oct '04

29 Oct '04

I understand there had been some debate about including rendering-color-space in this version of the standard... I just wanted to note that for us (the Inkscape project) at least there is strong desire for the inclusion of rendering-color-space; in practical terms ICC colors aren't much use for our intended audience without it; this is particularly true in the case of for-print CYMK work. Our ground rule so far has been to adopt no extensions that affect rendering; if we can't do compositing in a CYMK color space within the confines of the standard, we would probably end up putting off support of ICC colors altogether. -mental

1 0

[Fwd: SVG WG announces Last Call of SVG 1.2]
by Jon Phillips 29 Oct '04

29 Oct '04

Do we have any comments for the SVG 1.2 spec??? Now is the time if we want to push for new things or tweaks to the spec. Jon -------- Original Message -------- Subject: SVG WG announces Last Call of SVG 1.2 Resent-Date: Wed, 27 Oct 2004 21:39:54 +0000 Resent-From: www-svg@...157... Date: Wed, 27 Oct 2004 23:39:51 +0200 From: Chris Lilley <chris@...157...> Reply-To: Chris Lilley <chris@...157...> Organization: W3C To: chairs@...157... CC: www-svg@...157... Dear Chairs, On behalf of the SVG Working Group [1], I am pleased to announce the publication of the 27 October 2004 "Scalable Vector Graphics (SVG) 1.2" Last Call Working Draft. The document is available at: http://www.w3.org/TR/2004/WD-SVG12-20041027/ Review start date : 27 October 2004 Review end date : 24 November 2004 Mailing list : www-svg@...157... (public archive [2]) Please find below the following information: * Which groups should review this document * Decision to advance to Last Call * Patent disclosures * The abstract and status section For more information on the purpose of a Last Call review, please consult section 7.4.2 of the W3C Process Document [3]. The SVG WG looks forward to your review comments, Chris Lilley Chair, SVG WG Dean Jackson Staff Contact, SVG WG [1] http://www.w3.org/Graphics/SVG/Group/ [2] http://lists.w3.org/Archives/Public/www-svg/ [3] http://www.w3.org/2004/02/Process-20040205/tr.html#last-call ======================================== Which groups should review this document ======================================== The TAG welcomes review from all interested parties including implementors of SVG renderers, of SVG authoring tools, content designers, and the interested public. In particular, we request review from the following W3C groups: CSS WG [Bert Bos, Chair] Compound Document Formats WG [Vincent Hardy, Chair] Device Independence WG [Rhys Lewis, Chair] HTML WG [Steven Pemberton, Chair] Internationalization WG [Addison Phillips, Chair] Multimodal Interaction WG [Deborah Dahl, Chair] QA WG [Karl Dubost, Chair] SYMM WG [Yoshihisa Gonno, Guido Grassel, co-Chairs] Timed Text WG [Glenn Adams, chair] Voice Browser WG [Jim Larson, Scott McGlashan, co-Chairs] WAI P&F WG [Alfred Gilman, Chair] XForms WG [Steven Pemberton, Chair] XML Core WG [Paul Grosso, Norm Walsh co-Chairs] XML Schema WG [David Ezell, Chair] The Chairs of some of these groups have already confirmed with the SVG WG their intent to review the document, at the Friday 22 October Hypertext CG call [4] or individually [5]. For other groups, the W3C Director will appreciate a response (sent to www-svg@...157...) with or without review comments. [4] http://lists.w3.org/Archives/Member/w3c-html-cg/2004OctDec/0012.html [5] http://lists.w3.org/Archives/Member/w3c-svg-wg/2004OctDec/0524.html In addition, the following external groups are explicitly requested to review SVG 1.2: 3GPP [Robin Berjon, SVG<->3GPP Liaison] OMA [Vincent Mahe, SVG<->OMA Liaison] ================================= Decision to advance to Last Call ================================= The SVG WG decided to advance to Last Call, with no objections and one abstention, at their Thursday 21 October 2004 telcon. [6] Resolution: Publish Last Call with unmerged spec. [6] http://lists.w3.org/Archives/Member/w3c-svg-wg/2004OctDec/0491.html ================== Patent disclosures ================== First public working draft of this specification [7] was 15 November 2002. A patent disclosure page is maintained at [8] Per the W3C Patent Policy, Working Group participants have 60 days from the publication of the Last Call Working Draft to exclude any claims made essential by the Last Call Working Draft not included in earlier drafts. The deadline for such exclusions is 26 December 2004. [7] http://www.w3.org/TR/2002/WD-SVG12-20021115/ [8] http://www.w3.org/Graphics/SVG/Disclosures ============================================== Abstract of Scalable Vector Graphics (SVG) 1.2 ============================================== SVG is a modularized XML language for describing two-dimensional graphics with animation and interactivity, and a set of APIs upon which to build graphics-based applications. This document specifies version 1.2 of Scalable Vector Graphics (SVG). ========================== Status section ========================== This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This is a W3C Last Call Working Draft of the Scalable Vector Graphics (SVG) 1.2 specification. The SVG Working Group plans to submit this specification for consideration as a W3C Candidate Recommendation after examining feedback to this draft. Comments for this specification should have a subject starting with the prefix 'SVG 1.2 Comment:'. Please send them to www-svg@...157..., the public email list for issues related to vector graphics on the Web. This list is archived and acceptance of this archiving policy is requested automatically upon first post. To subscribe to this list send an email to www-svg-request@...157... with the word subscribe in the subject line. Comments are accepted until 30 November 2004. This document lists the changes from SVG 1.1. It is not a complete language description. This document has been produced by the SVG Working Group as part of the Graphics Activity within the W3C Interaction Domain. This document was produced under the 23 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy. Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. -- Chris Lilley mailto:chris@...157... Chair, W3C SVG Working Group Member, W3C Technical Architecture Group -- Jon Phillips KOREA.PH.010.3140.7483 USA.PH.858.361.2811 jon@...235... http://www.rejon.org Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org) CVS Book (http://cvsbook.ucsd.edu) Scale Journal (http://scale.ucsd.edu)

4 3

Update spanish translation
by Lucas Vieites 28 Oct '04

28 Oct '04

Hi there, I attached an update es.po. I'd like to do a full revision of this file to see if the translations are correct in their context. For this purpose I would need to compile the cvs version of inkscape. What other packages do I need? I haven't compiled inkscape from cvs since pre-0.39. Thank you, -- Lucas Vieites Fariña Dept. Desarrollo <lucas@...212...> Asix Informática <http://www.asixinformatica.com/> Tel/Fax: +34 986 54 26 98

2 1

cvs snapshots?
by Kees Cook 28 Oct '04

28 Oct '04

How come the CVS tarball snapshots aren't updating? It shows the most recent at Jul 12th. -- Kees Cook @outflux.net

4 8