- Inkscape Devel - Inkscape Mailman

Move to Launchpad
by Joshua A. Andler 13 Nov '09

13 Nov '09

Hey All, Please be patient while we are preparing to move to launchpad. I am adding in a number of our most active devs to the dev team to hopefully speed things up once things are ready to go. Please DO NOT act on anything until we send out a green light email (will most likely be sent by Ted). If you were not added by me, please just request to be a member of the team, it's nothing personal. :) Cheers, Josh

2 2

Release note for v0.47.
by Tavmjong Bah 13 Nov '09

13 Nov '09

Hi, I think it is time to start the nagging to get the release notes complete. Here are the things I have noticed missing: 1. Undocumented Live Path Effects Ruler Interpolate subpath 2. Undocumented Extensions Modify Path -> Interpolate Attribute in a Group Web -> JavaScript Generate from Path -> Motion Generate from Path -> Scatter 3. New location of preferences.xml etc. 4. Undocumented Import/Export JavaFX 5. Changes to Tools Sketch mode for Pencil Tool needs expansion. Missing change to Pencil Tool and Pen Tool for dots. 6. SVG Test Suite Compliance Fill out skeleton. 7. Extended input device configuration Does it work? 8. Document Properties Dialog What is purpose of Script tab? Tav

4 5

issues with pdf file size limitation
by Albert Cardona 11 Nov '09

11 Nov '09

Hi all, I am trying to export a large montage of images. The page size is 2148 x 66091 px. The montage contains 4 x 100 images. Inkscape has no problem editing the svg file plus images. But: when I export to PDF, approximately the lower half of the PDF is empty. Why? Or is it just evince not reading/rendering the whole contents? With export to EPS, it's even worse: the page is not read; instead, the original, default A4 page dimensions are used for page. This is inkscape 0.47 as distributed in ubuntu 9.10. Help appreciated. I'd like to print this poster. Albert

1 0

Inkscape 0.47 pre 4, OS X 10.6.1, The fantastic lxml wrapper for libxml2
by Jmx 10 Nov '09

10 Nov '09

Hello, I'm testing the latest 0.47 pre4 on OS X - 10.5.8 at work and perspective works just fine. But at home i have OS X - 10.6.1 and doing perspective fails and gives this message: -------------------------- The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore this extension. Please download and install the latest version from http://cheeseshop.python.org/pypi/lxml/, or install it through your package manager by a command like: sudo apt-get install python-lxml -------------------------- Is something just not finished in the 0.47 or is it something changed in Snow Leopard? Regards :) -- View this message in context: http://www.nabble.com/Inkscape-0.47-pre-4%2C-OS-X-10.6.1%2C-The-fantastic-l… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

6 9

SVN Release Lockdown
by Joshua A. Andler 10 Nov '09

10 Nov '09

Hey All, I have one last commit to make (which of course triggered a rebuild since it touched verbs). In 3 hours, SVN will be locked down for release. Any last minute changes, speak now! Oh, and yes Nicolas, the last commit I have planned will disable the non-functioning menu item for 346721 (boo to a last minute change that triggers a full rebuild). I will be posting again in a few hours with an update. Cheers, Josh

4 3

Prev/Next Zoom shorcut with Japanese keyboards
by Marcel Montes 09 Nov '09

09 Nov '09

Hello, I'm not sure if this is the right place to send this, say, minor bug? annoyance? I've found: The ` and shift-` shortcuts can't be really used with Japanese keyboard layouts, since the backtick is done by shift-@, so as you do "shift-@" inkscape gets the backtick, but since you're pressing shift, it tries to go to "the next zoom" and there's then no shortcut to go to the previous zoom. Also as one would at start be already at the "last zoom", just "no next zoom" is displayed... thus leaving you with pretty much no shortcut to zoom's history unless you went to a previous zoom by the menus. PS: Is not really a feature I'll think I'll use much, I'd just ctrl- mousewheel my zoom, but since I'm starting with inkscape I was following the basic tutorial and found myself unable to do it. Thanks for your time, keep it up with this nice project. Marcel

1 0

[win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)
by ~suv 09 Nov '09

09 Nov '09

The combination of these bugs: [Bug 469180] <https://bugs.launchpad.net/bugs/469180> Significant Differences in exported PDF File Size from 0.46 to 0.47pre3/4 [Bug 388257] <https://bugs.launchpad.net/bugs/388257> Inkscape 0.47Pre: PDF/PS Export 'Text to Paths' gives inconsistent results [Bug 271695] <https://bugs.launchpad.net/bugs/271695> Kerned text embeds too many fonts and blows up the file size in EPS/PS (special case of bug #469180, could potentially cause invalid PDF files if bug #431314 turns out to be a duplicate) leaves Inkscape 0.47(pre) users on win32 platforms with few options to export SVG documents containing text to good quality PDF files with reasonable file sizes. a) text as text: font embedding bug in cairo-win32 blows up file size disproportionally due to unnecessary embedding of fonts. Multiple uses of the same font are not merged into the same subset. b) text to path: the broken export option results in bad quality and huge file size due to text paths being exported multiple times and drawn on top of each other. The only way left at the moment: c) object to path: convert all text objects with the menu command 'Path > Object to Path' before saving as EPS/PS/PDF. How critical is (especially) PDF export for Inkscape 0.47 on win32 platforms? ~suv

9 14

Advice on how to update lxml on OS X
by Chris Mohler 08 Nov '09

08 Nov '09

Hi folks, I have a client who needs a later version of lxml to be picked up by Inkscape* on OS X. Unfortunately, I do not have access to OS X, so I'm not sure how to best acheive this - any advice would be most welcome. I'm not sure what version of OS X, but I'm guessing the procedure will be somewhat similar on all of them... Thanks, Chris * I thought the target system was win32, but we crossed wires somewhere. If I'd known about bug #448285 in the first place, I would have written the extension differently from the start - but as it stands I don't think that I have enough time. His deadline approaches...

3 7

Re: [Inkscape-devel] Advice on how to update lxml on OS X
by Chris Mohler 07 Nov '09

07 Nov '09

On Mon, Oct 19, 2009 at 11:21 PM, ~suv <suv-sf@...58...> wrote: > Just tested and put the lxml and numpy for python 2.5 that I had > compiled with MacPorts into the 0.47pre4 bundle and Inkscape loads them > fine and reports lxml version 2.2.2 :) > > i.e. I could zip them up and add the zip to your bug report for you or > him to download _if_ your client runs 10.5.8 (i386) with python 2.5 or > python 2.6 installed. He just has to unzip them and copy the folders > into the bundle, no need to build them on his machine. If he still uses > Tiger OS X 10.4.x or has a PPC processor then I can't help. > > I haven't built a DMG before - so I would prefer a simple zip... Back on list - just for posterity :) That is good news - I'm still waiting to hear back on his OS X version and arch. I'll report back once I have some more info either way. Thanks for the assistance. Chris

4 15

Upcoming Releases
by Joshua A. Andler 04 Nov '09

04 Nov '09

Hey All, Obviously, we are still waiting on the final patch for 0.47 before it can be released. When we were wanting to release 0.46, we had a similar issue with a Win32 specific issue holding up the release. This brings up something that needs to be addressed before the 0.48 cycle begins. It would be really helpful if for 0.48 we have a temporary policy, please comment on this if you agree, disagree, or have suggestions. For 0.48, it would be nice if anything that is a major change (aside from our GSoC projects) is NOT put into trunk until it has been well tested in a branch and/or privately by other devs/testers (I am willing and excited to test!). It would also be nice if we decide on an open committing period (time before Feature Freeze). For open committing, I would think 8-12 weeks should be sufficient to not break things too badly, yet still give enough time to flesh features out. I know this is much more restrictive than our normal development process, but for 0.48 to be as good and solid as possible (as soon as possible), this route makes the most sense. Obviously, once 0.48 gets out the door and we are onto 0.49, people can go back to committing responsibly... but, it would be nice if we had a policy moving forward of "if you break it, you must fix it". Thoughts? Cheers, Josh

5 10