Now that Snow Leopard is out, is there any word on whether 0.46 or 0.47pre works on Snow Leopard? Any lucky early upgraders maybe know one way or another?

Because I would rather wait for a compatible version than end up being forced to use Parallels. Is it just a matter of compiling it on the system or what?

The latest stable version doesn't open up for me in Snow Leopard, however, the latest developer snapshot for OS X does. I haven't done anything beyond opening it up, so I can't really say anything else about it, i.e., whether anything actually works.

I upgraded, 46 doesn't work. 47 pre release does work however I'm having issues using the effects such as patterns around a path feature in the Extensions Menu... I get this error.

ScrappyDew wrote:I upgraded, 46 doesn't work. 47 pre release does work however I'm having issues using the effects such as patterns around a path feature in the Extensions Menu... I get this error.

Code: Select all

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

I got that code when I upgraded. (Clarification edit: I cot that code when upgrading Inkscape, not Mac OS X.) I was able to fix it by going into my old copy of Inkscape, right-clicking to Show Package Contents, browsing Contents > Resources > python and copying the contents from there into the new copy of 0.47.

Thanks for testing, guys!

artguy10 wrote:I was able to fix it by going into my old copy of Inkscape, right-clicking to Show Package Contents, browsing Contents > Resources > python and copying the contents from there into the new copy of 0.47.

Questions:

• With which version (build/revision number, build date, see 'Help > About Inkscape…') the Python extensions did not work?
• From which version (build/revision number, build date or download name) did you copy the Python site-packages?
• Which Python version is installed as default on Snow Leopard? Open Terminal.app and type

  Code: Select all

  which python
python --version
  Did you install any additional Python modules or Python versions (like MacPython) yourself?

The latest prerelease build Inkscape 0.47pre1-2 (r21720) for Leopard (from sf.net) includes all Python site-packages for Python 2.3, 2.4, 2.5 and 2.6. If this still doesn't work on a default Snow Leopard install, please file a bug report and include all relevant system info.

~suv

~suv wrote:Questions:

• With which version (build/revision number, build date, see 'Help > About Inkscape…') the Python extensions did not work?
• From which version (build/revision number, build date or download name) did you copy the Python site-packages?
• Which Python version is installed as default on Snow Leopard? Open Terminal.app and type

  Code: Select all

  which python
python --version
  Did you install any additional Python modules or Python versions (like MacPython) yourself?

The latest prerelease build Inkscape 0.47pre1-2 (r21720) for Leopard (from sf.net) includes all Python site-packages for Python 2.3, 2.4, 2.5 and 2.6. If this still doesn't work on a default Snow Leopard install, please file a bug report and include all relevant system info.

Are you asking me?

1. I have no idea. There were no contents in the python folder.
2. I took them from my 0.46 copy of Inkscape, but I actually may have put them into my 0.46 copy originally from 0.45!
3. I didn't get Snow Leopard yet...
I think I did install MacPython, but that didn't help, so I got the python files from my old copy of Inkscape.

artguy10 wrote:Are you asking me?

I thought you had already upgraded to SL since your initial question ;-) But re-reading your comment it could also have meant 'I got that code when I upgraded Inkscape'...

But the same question goes to ScrappyDew, who first reported the python error message. I think if this happens on every new SL install, then the Inkscape bundle has to be adapted before 0.47 is released. That's why I felt the need to ask for more specifics.

Sorry if I misunderstood you,
~suv

~suv wrote:

artguy10 wrote:Are you asking me?

I thought you had already upgraded to SL since your initial question But re-reading your comment it could also have meant 'I got that code when I upgraded Inkscape'...

But the same question goes to ScrappyDew, who first reported the python error message. I think if this happens on every new SL install, then the Inkscape bundle has to be adapted before 0.47 is released. That's why I felt the need to ask for more specifics.

Sorry if I misunderstood you,
~suv

It's ok. I didn't even think about that, so I edited my post for clarity. Yeah, I noticed in the past when I put on a new copy of Inkscape it wouldn't have any python scripts, my OS is Tiger btw. Probably installing Snow Leopard later today or tomorrow.

I'm getting the same error on a clean Snow Leopard install, with the 0.47pre1 r21720 version.

More seriously for my uses is that numerous fonts don't work. Helvetica, Times, and some others give the following behavior:
When the font is selected from the drop-down menu, the font instantly switches to "Sans"
When the font is selected in the "text and font" dialog, the font shown in the preview is Sans, not the selected font
When importing a PDF containing the font, all text using that font is changed to Sans

Arial works though

Anyone else see this behavior, or encountered it before?

a1c78f wrote:More seriously for my uses is that numerous fonts don't work. Helvetica, Times, and some others...

I remember from an earlier article on Ars Technica that Apple has dropped an old font format (.dfont) and added a new one. As font support in Inkscape is realized with the Pango libraries - it might take some time (and definitely new Inkscape builds) to get all system fonts right in Inkscape.

You might try it 'the old way' described in the FAQ to have at least some of the (system supplied) fonts available.

hth, ~suv

thanks, you are correct, it looks like an issue with the .dfont format which I spent this morning figuring out

I downloaded fontforge and used it to create Helvetica.ttf, Helvetica-Bold.ttf, Helvetica-Oblique.ttf, and Helvetica-BoldOblique.ttf files from the dfont file. I then put these files in a directory and added that directory to Inkscape's fonts.conf (so they wouldn't interfere with other applications)

Helvetica mostly works now, the only issue being that it doesn't seem to differentiate between regular and bold. As long as the Helvetica-Bold.ttf file is in the directory, all regular Helvetica fonts show up as bold (oblique and bold oblique work right). I'm working around this by only putting Helvetica.ttf in the directory and not using any other weight. Any thoughts?

I have the same regular/bold issues with some of the system fonts converted to ttf (using fondu) , but don't have a list compiled of all fonts concerned. For example 'LucidaGrande' (which I always have as TTF in '~/.fonts', mainly for the GTK+ theme / 'gtk-font-name') doesn't render in bold, and if 'LucidaGrandeBold.ttf' is present, all text styled with 'Lucida Grande' in Inkscape is rendered bold.

I have searched before, but have not yet found an explanation or workaround - this might be due to my lack of knowledge in the area of font handling under X11 - with components as fontconfig, freetype, pango, cairo and what else I don't know of - might contribute to the font woes of GTK+ applications under OS X ;-)

But I'd be interested to hear about any available workarounds or possible configure options to test...
~suv

[edit content="additional link"]
a quick google search lead me to this thread on the [gtk-i18n-list] mailing list from 2006(!). See the attachment in the second mail - looks like the same underlying issue as today... Pango has added support for 'dfont' to some extent I think since then, but there are still rendering flaws regarding regular/bold.
OTOH - the screenshot also mentions the compile flag '--with-old-mac-fonts' for freetype - X11/XQuartz has just dropped that in its latest release.
[/edit]

Follow-up question: I'm still on OS X 10.5.8, Xquartz 2.4.0, so I can't test it myself: are any of the '*.ttc' font collections recognized by Inkscape 0.47pre1-2? As far as I can see I have not one ttc font on Leopard and didn't bother yet to find an example 'in the wild'... Besides I had forgotten about the font changes in SL until you mentioned it here.

BTW - you might consider filing a bug report with Inkscape or a font library upstream like Pango if Snow Leopard causes serious font failures with Leopard builds of GTK applications... ;-)

fonts are recognized, similar issues with bold/regular not being distinguished properly. for example, I can't get Futura medium to show up, I appear to get a bold variant.

I got Inkscape to recognize bold/regular Helvetica by manually editing the info for the HelveticaBold.ttf file in fontforge and changing the settings to make it clear that it's the bold variant. maybe this would work for the .ttc fonts too

Thank you for reporting back!

a1c78f wrote:fonts are recognized, similar issues with bold/regular not being distinguished properly

Is it then correct to say that Inkscape 0.47pre1-2 on Snow Leopard works ok, with

• the known limitations of font support as on Leopard
• failure of the included Python site-packages for the 'lxml' and 'numpy' modules ?

a1c78f wrote:I got Inkscape to recognize bold/regular Helvetica by manually editing the info for the HelveticaBold.ttf file in fontforge

good to know - but kind of absurd imagining every inkscape user on a mac unpacking all 'dfont' and 'ttc' font collections and changing the 'bold' (and maybe other) variant settings in fontforge ;-) i.e. I am still hoping for updates in pango...

~suv (bracing up for the expected new bug reports about Inkscape on SL in the bug tracker)

~suv wrote:]Questions:

• With which version (build/revision number, build date, see 'Help > About Inkscape…') the Python extensions did not work?
• From which version (build/revision number, build date or download name) did you copy the Python site-packages?
• Which Python version is installed as default on Snow Leopard? Open Terminal.app and type

  Code: Select all

  which python
python --version
  Did you install any additional Python modules or Python versions (like MacPython) yourself?

The latest prerelease build Inkscape 0.47pre1-2 (r21720) for Leopard (from sf.net) includes all Python site-packages for Python 2.3, 2.4, 2.5 and 2.6. If this still doesn't work on a default Snow Leopard install, please file a bug report and include all relevant system info.

~suv

Question 1: Inkscape 0.47pre1 r21720, built Jul 20 2009

Question 2: Not sure

Question 3: /Library/Frameworks/Python.framework/Versions/Current/bin/python and Python 2.5

artguy10 wrote:

ScrappyDew wrote:I upgraded, 46 doesn't work. 47 pre release does work however I'm having issues using the effects such as patterns around a path feature in the Extensions Menu... I get this error.

Code: Select all

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

I got that code when I upgraded. (Clarification edit: I cot that code when upgrading Inkscape, not Mac OS X.) I was able to fix it by going into my old copy of Inkscape, right-clicking to Show Package Contents, browsing Contents > Resources > python and copying the contents from there into the new copy of 0.47.

Thanks for testing, guys!

Thanks for that info on transferring the old python files to the new inkscape 47 and it worked.

I have Snow Leopard on my iMac and I have installed Inkscape Beta pre1-2.

Unfortunately i can't copy or paste in .SVG documents. Is here somebody that can help me?

Many tanks!

SnarfFlevoland wrote:I have Snow Leopard on my iMac and I have installed Inkscape Beta pre1-2.

Unfortunately i can't copy or paste in .SVG documents. Is here somebody that can help me?

Many tanks!

I noticed that as well. As of now I'm using Duplicate.... It cuts and duplicates fine... It may copy fine but just not pasting.

Inkscape FAQ: Copying and pasting in Inkscape creates pixellated images instead of copying the vector objects?

a1c78f wrote:fonts are recognized, similar issues with bold/regular not being distinguished properly. for example, I can't get Futura medium to show up, I appear to get a bold variant.

I got the Futura to show up as not-bold by opening the code editor and removing the "font-weight" (like in CSS) entry for the text.

Hello,

I got the same problem with the new inkscape 0.47 and the textext extension. Same message.
I tried to copy the python folder from 0.46-leopard-package in my 0.47 folder but it didnt change anything... what should I do ?
I have Python 2.6.1 so it musnt be the problem...
Im under Snow Leopard too, thats why I installed Inkscape 0.47 version (0.46 doesnt work).

thanks,
Psilo.

Psilo wrote:Im under Snow Leopard too, thats why I installed Inkscape 0.47 version (0.46 doesnt work).

It is a known issue that most of the extensions (all that require the python modules lxml and numpy) don't work with the current 0.47preX-LEOPRAD+ builds on Snow Leopard. The osx package maintainers are aware of the problem and working on a solution for the final release of 0.47.

Ok sorry, I though that someone found a solution.
many thanks !
Psilo

I managet to make effects run on Snow Leopard (47pre4) following these steps:
http://wiki.inkscape.org/wiki/index.php ... rom_source
(download/tar xvzf/sudo setup....)

Packages downloaded:
lxml-2.2.4.tar.gz
numpy-1.3.0.tar.gz

python --version: Python 2.6.1

I cannot ensure it is going to work for you, but it did for me. If you are interested, my Snow Leopard comes from an upgrade. There is a lot of software installed/upgraded/removed, so my environment is far, far away from a clean one. It's a macbook pro with some scratches on the upper right side (but probably you don't need to hurt your computer in order to make things run... but one never knows)

I'm neither a python expert nor a inkscape one, but I have a strong background on *nix os. Feel free to ask any question.

Pep Pla