March 2008 - Inkscape Devel - Inkscape Mailman

linux devs pls. double check: [Fwd: [Bug 200782] Re: revert blur to bitmap option in pdf output dialog for 0.46.0]
by Adib taraben 10 Mar '08

10 Mar '08

Hello Linux devs, I introduced one late nearly cosmetic patch. But that needs to be double-checked as well. So if one could test this patch and confirm if that works it would be great. Many thx. so far. Adib. --- -------- Original-Nachricht -------- Betreff: [Bug 200782] Re: revert blur to bitmap option in pdf output dialog for 0.46.0 Datum: Mon, 10 Mar 2008 22:41:54 -0000 Von: theAdib <theAdib@...400...> Antwort an: Bug 200782 <200782@...1882...> An: theAdib@...400... Referenzen: <20080310224155.882.1077.malonedeb@...1895...> ** Attachment added: "The attached patch reverts the option in the export dialog." http://launchpadlibrarian.net/12555909/revert_blur2bitmap_option.patch ** Changed in: inkscape Importance: Undecided => Low Target: None => 0.46 -- revert blur to bitmap option in pdf output dialog for 0.46.0 https://bugs.launchpad.net/bugs/200782 You received this bug notification because you are a direct subscriber of the bug.

1 0

Translation for 0.46 frozen
by Luca Bruno 10 Mar '08

10 Mar '08

Hi all, release is now quite imminent, so I'm just closing the window for translations to be committed for 0.46. No more i18n update will happen on branch. Here some general statistics for you all: ***** Total number of localizable strings: 3466 Average translated: 1950 ( 56 %), fuzzy: 596 ( 17 %), untranslated: 909 ( 26 %) Total number of PO files: 61 Significantly translated PO file count: 26 Average number of strings translated: 3286 ( 94 %) Significantly translated locales: bg br ca de en_GB eo es eu fi fr he hu it km nb pl pt pt_BR ru sk sl sr sr@...1894... uk vi zh_CN ***** 0.46 will also come with many translated tutorials, localized about screens and translated win32 installer. Kudos to all translators and local teams for their great job! I'd like to heartily thanks Adib for taking care of translation status with me for this release cycle, Cmarqu who built the tutorial and Juca who provided all those nice translated about screens. Thank you all and happy hacking, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno : :' : The Universal O.S. | lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer

1 0

Input needed for snapping related matter
by Diederik van Lierop 10 Mar '08

10 Mar '08

Hi All, If you care about snapping, then please have a look at https://bugs.launchpad.net/bugs/174046 We could use some input here because we're about to make some design choices affecting the usability. To understand the discussion you only have to read the messages from March onwards. Thanks, Diederik -------- Original Message -------- On Mon, Mar 10, 2008 at 9:30 AM, Diederik van Lierop <mail@...1689...> wrote: > Bulia, another consideration: suppose a user is again using visual > bboxes in the selector tool, and that has created a path of which the > nodes are snapped and aligned to a grid. Next, when translating the > path's nodes will snap to the grid again. But when he tries to scale it, > the nodes won't snap. We cannot expect that any user would immediately > realize that he needs to switch to geometrical bboxes, or can we? So the question is, do people really need node snapping when scaling. I'm really not sure of that. Even with ellipse center - scaling an ellipse to snap its center is imho a very contorted way to act, I would assume most people would first move it to snap the center and then scale it around the center, which is much more natural. So I would vote for disabling node snapping for scaling, perhaps adding a checkbox to snapping option s, under Snap ndodes, "Snap nodes even when scaling in Selector" if people want to override that at the expense of not keeping the origin (as should be explained in the tooltip). However, I'm not a heavy user of snapping, so perhaps we need more input before committing to this. -- Rectangles do not snap accurately to grid https://bugs.launchpad.net/bugs/174046 You received this bug notification because you are a bug assignee.

1 0

Snapping to nodes (within same path)
by unknown＠example.com 10 Mar '08

10 Mar '08

Hi all, Mostly to Diederik: can nodes of a path snap to nodes of the same path when nodeediting them? It seems they can't, but perhaps I should switch another toggle somewhere? Regards, Johan __________________________________________________ ir. J.B.C. Engelen PhD student Micro Electromechanical Systems (MEMS) TST EWI, University of Twente The NETHERLANDS e-mail: j.b.c.engelen@...1887...

4 12

Format of path names in SVG files?
by Hannes Schniepp 10 Mar '08

10 Mar '08

Dear all, I recently noticed that embedded bitmaps in SVG files exported from (Windows) Corel X3 (=v.13) get the windows-typical backslashes rather than forward slashes in their file references in the generated SVG files. Therefore these files do not show the bitmaps when opened on Inkscape in Linux. It can be fixed by manually replacing the forward slashes by backslashes (which is tedious, however). Is that defined in the SVG standard? Is Corel goofing, or is inkscape not correctly considering files generated on a different platform? Shouldn't there be a platform-independent standard for the path names? PS: I recently got note from microUgly that the Windows version of Inkscape also produces backslashes.

2 1

python.exe or pythonw.exe
by unknown＠example.com 10 Mar '08

10 Mar '08

Hi all, Currently, on windows, pythonw.exe should be used according to the code in /src/extension/implementation/script.cpp. However, build.xml only copies python.exe to the dist dir. The strange thing is: Inkscape needs python.exe, and does not want pythonw.exe. Something wrong with the #ifdef in script.cpp? It would be nice to fix this, because it removes the DOS popup when running an effect (nice for live preview). Thanks, Johan

3 2

0.46 release debate
by rygle 10 Mar '08

10 Mar '08

Just my two cents worth on the release being held back by Windows; I think that, regardless of your position on Windows as an operating system, or Windows users, that putting out a release that is crippled would be downright humiliating to the *whole* Inkscape project. Let's ask, what is pushing us so hard to get the next release out? In a lot of these projects there is an impetus based on saving face, which is about bringing new features to fruition. IMHO, the saving face needs to be done by being a little patient, or at the very least not releasing 0.46 for Windows until it is pretty right. Again, what is the aim? Is it purely to further the name of Inkscape, or is there at least some desire to further SVG as a viable option is a largely proprietary world? I have heard that said a number of times, and used as a reason to include or reject features. This project is meant to be about a good SVG editor, and the rest is a nice by-product. Again, a good reason to hold off just a little. Let us also ask, if Linux users are so technically superior, aren't they already using the release candidate, which offers pretty much what the release will? Surely even the nightlies are very stable by now if all the bugs are ironed out. If so, in at least one sense who cares if there's a release if the RC is working and those who want the release are already using it! Linux users are well and truly used to beta and release candidates, and in fact the pure only use the bleeding edge stuff and look down on those who don't. Or are we next going to start railing against Ubuntu users for their lack of technical expertise, and because they need a packaged version? Afterall, isn't Ubuntu trying to attract that Windows-like person? Lets please hold off just a little, at the very least on the Windows release. For many Linux users it makes no difference whether or not there's an official release, because the pre2 package is stable. For the Windows users, and the reputation of Inkscape, SVG, and even FOSS, it makes a huge difference. -- View this message in context: http://www.nabble.com/0.46-release-debate-tp15773115p15773115.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

22 49

Automake files
by Bob Jamison 10 Mar '08

10 Mar '08

Hi, I committed some more code tonight, including a new Makefile_insert in /src/bind. We played with this for hours trying to get the wrinkles out, and I -think- it works now. But if anyone has any problems, and they know how to work with automake, please look at /src/bind/Makefile_insert and where it is referenced by /src/Makefile.am. I think that the general rule is that every time a Makefile_insert is added, Makefile.am needs to be touched, or autogen run. Thanks. bob

1 0

Additions to build.xml
by Bob Jamison 10 Mar '08

10 Mar '08

Hi all. This is just a note to let users of buildtool that I added a few things to build.xml to enable the building of the JVM binding. I commented the 3 places that allow /src/bind to be built, so it shouldn't break your builds. However, the new <javac> tag and and <property environment=""/> tag might require you to compile buildtool.cpp again to avoid parse errors. Let me know if you have any problems. bob(ishmal)

3 8

Extended input and "keys"
by Jon A. Cruz 09 Mar '08

09 Mar '08

Hi, I'm trying to find out if anyone has successfully gotten the "keys" settings under the "Input Devices..." dialog to actually do anything. So far on Ubuntu 7.10 I've been unable to get them reacting with my Wacom. I'm very interested in anyone getting them to work, since I'm doing a replacement for that dialog and am almost ready to check in the first round. Thanks for any feedback.

1 0