Inkscape Wiki - User contributions [en]

XML Repair

2005-11-24T10:04:02Z

194.167.139.18: update with new invalid files and suppressed old ones which were mistakes

= XML Repair and Validation service =

The [http://sourceforge.net/tracker/index.php?func=detail&aid=1119025&group_id=93438&atid=604309 RFE 1119025 repair broken xml on load] and the [http://sourceforge.net/tracker/index.php?func=detail&aid=1326574&group_id=93438&atid=604306 bug 1326574 bogus transform on a bitmap from "create bitmap copy"] both provide examples of situations where Inkscape's intented behaviour would be to correct or warn about badly formated svg files. The aim of this page is to give examples of such files and to discuss the progress made on repairing them inside Inkscape and how to do it.

This page is written without having a clue of what is already done when inkscape opens of saves a file so please add whatever is necessary.

----

== What kind of "wrong" XML? ==
At least two types of wrong files could be defined:
# non valid XML files which Inkscape cannot parse
# valid XML files which Inkscape can open but which cause editing or viewing problems

In the first case current behavior is not to open the file. In second case, current behavior is to let thee user find out what is wrong.

----

== What to do about them? ==
=== Case 1: ===

[http://sourceforge.net/tracker/index.php?func=detail&aid=1119025&group_id=93438&atid=604309 RFE 1119025] is about trying to repair the file at startup and recover what is recoverable. The intended behavior would be to have a message of the form:

'''Document <name> contains errors. Do you want to attempt to repair it?'''

'''[Cancel] [Repair]'''

There could also be a button to show a more detailed explaination:
"Inkscape can create a new document from any
readable objects contained in your file. Your original file will not
be touched. Inkscape will open a new window called
<name> [Recovered]. You might want to export the
recovered objects into a new file before proceeding.
Note: You may be able to obtain better results using an
XML editor or text editor."

Deciding to recover the file will parse it with a more permissive XML parser and recover what can be recovered. What cannot be recovered should be preserved as an XML comment.

=== Case 2: ===

The example of some valid files with problems was discussed on a [http://sourceforge.net/tracker/index.php?func=detail&aid=1326574&group_id=93438&atid=604306 bug report] and on several threads of the devel mailing list: [http://sourceforge.net/mailarchive/forum.php?thread_id=8578063&forum_id=36054 zooming bug], [http://sourceforge.net/mailarchive/forum.php?thread_id=8602372&forum_id=36054 zooming bug bis], [http://sourceforge.net/mailarchive/forum.php?thread_id=8602956&forum_id=36054 sanity checking on file open], [http://sourceforge.net/mailarchive/forum.php?thread_id=8606155&forum_id=36054 what should zoom to content do], [http://sourceforge.net/mailarchive/forum.php?thread_id=8629987&forum_id=36054 artificial limits]. All started from a bug in Inkscape which produced one object with insane bounding box which itself induced a strange zooming behavior. The bug itself was corrected by bulia. The discussion which followed was focused on the fact that such files can be encountered in the "wild" and that some Inkscape feature could help dealing with them.

The intended behavior in this case would be to issue visible warnings and to provide solutions (even is they basically redirect the user to the XML editor). The problem about when to warn occurs and the suggestion was to build a "Validate file" or "Repair File" feature which would validate the XML, detect strange cases and ask the user what he wants to do about it (correct or suppress or...). The discussion is about adding to this features artifical limits, human defined, above which some bounding box for example is considered insane.

The two cases could obviously share some features.

----

== Example files ==
In this section, files which cause particular problems can be linked and described.

=== Non valid XML ===

???

=== Valid XML with problems ===
'''Inkscape file with a bug''': This [http://jo.irisson.free.fr/dropbox/inkscape/schema_bilan.svg file with one object having a huge bounding box] was generated following a bug in Inkscape (fixed already) but some other might be encountered. It should look like [this ]

'''Files converted from EPS/PS by pstoedit'''
Most scientific software output EPS or PS and pstoedit can make SVG from them but they behave strangely in Inkscape. Here are links to a sequence of files in a workflow based on scilab (a free numerical computing software, similar to matlab and octave):
[http://jo.irisson.free.fr/dropbox/inkscape/scilab.eps original EPS][http://jo.irisson.free.fr/dropbox/inkscape/scilab.png PNG of what it looks like][http://jo.irisson.free.fr/dropbox/inkscape/scilab_pstoedit.svg converted to SVG by pstoedit][http://jo.irisson.free.fr/dropbox/inkscape/scilab_pstoedit_parsedbyinkscape.svg SVG parsed by Inkscape][http://jo.irisson.free.fr/dropbox/inkscape/diff_between_original_and_copypasted.txt diff][http://jo.irisson.free.fr/dropbox/inkscape/scilab_pstoedit_parsedbyinkscape_copypasted.svg SVG copy-pasted in a new Inkscape document].
The original file is generated by Scilab 3.1.1, converted by pstoedit version 3.40 / DLL interface 108 (build Oct 10 2005 - release build) and parsed by Inkscape CVS 20051123 on mac OS X.
Many transform matrices look like: transform="matrix(2.007003e-3,0.000000,0.000000,-2.007003e-3,-6.079619e-2,1.461081)". Probably related to this, every new object or text looks huge and dashes cannot be applied to lines. But some "magic" happens: when copying all objects and pasting them in a new document, everything is fine! You have the diff between the two file to see what changed.

----

== Developement status ==
* 17 Oct 2005: The issue is raised ;-)

Extension requirements

2005-11-10T12:22:15Z

194.167.139.18: added how to for python effects on os x

Setting Up Effects in Inkscape 
For effects to work you need to be using inkscape .42 or a recent nightly build. 
For info about what effects can do, screenshots, and how to make your own go to [http://www.ekips.org/comp/inkscape/ Aarons Site]

Unhide the Effects menu 
- On the "Misc" tab of the "Inkscape Preferences" dialog check the box labeled "Enable script effects" (0.41+CVS onwards only)
- Close and reopen Inkscape

Python Effects 
on Debian GNU / Linux
- apt-get install python python-xml

on Microsoft Windows
- [http://www.inkscape.org/cgi-bin/wiki.pl?GettingEffectsWorking/Windows Tutorial on Getting Effects to work on Windows]

on Mac os X
- See [http://wiki.inkscape.org/cgi-bin/wiki.pl?CompilingMacOsX Mac OS X compiling page] (at the bottom)

Perl Effects 
on Debian GNU / Linux
- apt-get install perl libxml-xql-perl

on Gentoo GNU / Linux
- emerge -a XML-XQL

on Microsoft Windows
- install [http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl ActivePerl]
- install XML::XQL::DOM (perhaps like this?)
1: install prereqs with ppm:
install xml-dom
install parse-yapp
install datemanip
2: download xml-xql from:
http://www.cpan.org/authors/id/T/TJ/TJMATHER/XML-XQL-0.68.tar.gz
3: open command prompt and locate perl"s lib directory with:
perl -e "print qq(@INC)" (mine was C:/Perl/site/lib)
4: unpack xml-xql archive
5: copy contents of XML-XQL-*\lib\XML into C:\Perl\site\lib\XML
6: copy XML-XQL-*\XQLParser\Parser.pm to C:\Perl\site\lib\XML\XQL

Plugin Effects 
- I have absolutely no idea. Please record your success here. :)

What if it doesn't work? 
- Run Inkscape from the console
- Use the error messges printed to the console to diagnose the problem (very often missing dependencies)
- On Windows you will have to redirect output to a text file like this: "inkscape > output.txt"

CompilingMacOsX

2005-11-10T12:07:41Z

194.167.139.18: *

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

'''Note''': Inkscape won't link properly on OS X 10.4.x using gcc 4 (the default) since many of the libraries it needs in fink are still built with gcc-3.3. Thus, Tiger users will probably want to modify a couple of lines:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>

Then, open a Terminal and, in the directory where you created the file <code>set_variables</code>, type:
<pre>
bash
source set_variables
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Configuring''':

Cd to Inkscape's sources directory and type
<pre>
./configure --prefix=/path/to/build/products/ --enable-osxapp
</pre>
The <code>--prefix</code> option sets the directory where the build products are placed. It must be somewhere you have write access to. The option <code>--enable-osxapp</code> allows you to package Inkscape into an <code>.app</code> bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards.

'''Building''':
<pre>
make
make install
</pre>

'''Packaging''':

Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Enabling python effects ==

Many "effects" in the Effect menu of Inkscape use python as a scripting language. Mac OS X ships with python but not with pyXML which is needed by Inkscape effects. To install it you need to
# download the source code from [http://sourceforge.net/project/showfiles.php?group_id=6473 sourceforge]
# unpack the <code>.tar.gz</code> file
# cd into the newly created directory
# set the variable <code>MACOSX_DEPLOYMENT_TARGET</code> to the number of your operating system (10.3 for Panther, 10.4 for Tiger. It probably won't work on previous systems). In bash syntax this means typing:<pre>MACOSX_DEPLOYMENT_TARGET=10.?
export MACOSX_DEPLOYMENT_TARGET</pre>
# move the python files and build C extensions<pre>python setup.py build</pre>
# install (the install is system wide so you need administrator rights)<pre>sudo python setup.py install</pre> and type your password.

----

== Interesting links ==

Some packaging links:

http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html

http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/

http://gimp-app.sourceforge.net/gimp.app.howto.txt

CompilingMacOsX

2005-11-10T12:05:01Z

194.167.139.18: added how to building pyXML

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

'''Note''': Inkscape won't link properly on OS X 10.4.x using gcc 4 (the default) since many of the libraries it needs in fink are still built with gcc-3.3. Thus, Tiger users will probably want to modify a couple of lines:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>

Then, open a Terminal and, in the directory where you created the file <code>set_variables</code>, type:
<pre>
bash
source set_variables
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Configuring''':

Cd to Inkscape's sources directory and type
<pre>
./configure --prefix=/path/to/build/products/ --enable-osxapp
</pre>
The <code>--prefix</code> option sets the directory where the build products are placed. It must be somewhere you have write access to. The option <code>--enable-osxapp</code> allows you to package Inkscape into an <code>.app</code> bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards.

'''Building''':
<pre>
make
make install
</pre>

'''Packaging''':

Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Enabling python effects ==

Many "effects" in the Effect menu of Inkscape use python as a scripting language. Mac OS X ships with python but not with pyXML which is needed by Inkscape effects. To install it you need to
# download the source code from [http://sourceforge.net/project/showfiles.php?group_id=6473 sourceforge]
# unpack the <code>.tar.gz</code> file
# cd into the newly created directory
# set the variable <code>MACOSX_DEPLOYMENT_TARGET</code> to the number of your operating system (10.3 for Panther, 10.4 for Tiger. It probably won't work on previous systems). In bash syntax this means typing:<pre>MACOSX_DEPLOYMENT_TARGET=10.?
export MACOSX_DEPLOYMENT_TARGET</pre>
# move the python files and build C extensions<pre>python setup.py build</pre>
# install<pre>python setup.py install</pre>

----

== Interesting links ==

Some packaging links:

http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html

http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/

http://gimp-app.sourceforge.net/gimp.app.howto.txt

CompilingMacOsX

2005-11-10T10:57:50Z

194.167.139.18: minor

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

'''Note''': Inkscape won't link properly on OS X 10.4.x using gcc 4 (the default) since many of the libraries it needs in fink are still built with gcc-3.3. Thus, Tiger users will probably want to modify a couple of lines:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>

Then, open a Terminal and, in the directory where you created the file <code>set_variables</code>, type:
<pre>
bash
source set_variables
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Configuring''':

Cd to Inkscape's sources directory and type
<pre>
./configure --prefix=/path/to/build/products/ --enable-osxapp
</pre>
The <code>--prefix</code> option sets the directory where the build products are placed. It must be somewhere you have write access to. The option <code>--enable-osxapp</code> allows you to package Inkscape into an <code>.app</code> bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards.

'''Building''':
<pre>
make
make install
</pre>

'''Packaging''':

Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Interesting links ==

Some packaging links:
http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
http://gimp-app.sourceforge.net/gimp.app.howto.txt

CompilingMacOsX

2005-11-10T10:56:16Z

194.167.139.18: slight refactoring of the page to add --enable-osxapp

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

'''Note''': Inkscape won't link properly on OS X 10.4.x using gcc 4 (the default) since many of the libraries it needs in fink are still built with gcc-3.3. Thus, Tiger users will probably want to modify a couple of lines:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>

Then, open a Terminal and, in the directory where you created the file <code>set_variables</code>, type:
<pre>
bash
source set_variables
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Configuring''':

Cd to Inkscape's sources directory and type
<pre>
./configure --prefix=/path/to/build/products/ --enable-osxapp
</pre>
The <code>--prefix</code> option sets the directory where the build products are placed. It must be somwhere you have write access to. The option --enable-osxapp allows you to package Inkscape into an <code>.app</code> bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards.

'''Building''':
<pre>
make
make install
</pre>

'''Packaging''':

Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Interesting links ==

Some packaging links:
http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
http://gimp-app.sourceforge.net/gimp.app.howto.txt

XML Repair

2005-11-05T15:15:15Z

194.167.139.18: added some new files

= XML Repair and Validation service =

The [http://sourceforge.net/tracker/index.php?func=detail&aid=1119025&group_id=93438&atid=604309 RFE 1119025 repair broken xml on load] and the [http://sourceforge.net/tracker/index.php?func=detail&aid=1326574&group_id=93438&atid=604306 bug 1326574 bogus transform on a bitmap from "create bitmap copy"] both provide examples of situations where Inkscape's intented behaviour would be to correct or warn about badly formated svg files. The aim of this page is to give examples of such files and to discuss the progress made on repairing them inside Inkscape and how to do it.

This page is written without having a clue of what is already done when inkscape opens of saves a file so please add whatever is necessary.

----

== What kind of "wrong" XML? ==
At least two types of wrong files could be defined:
# non valid XML files which Inkscape cannot parse
# valid XML files which Inkscape can open but which cause editing or viewing problems

In the first case current behavior is not to open the file. In second case, current behavior is to let thee user find out what is wrong.

----

== What to do about them? ==
=== Case 1: ===

[http://sourceforge.net/tracker/index.php?func=detail&aid=1119025&group_id=93438&atid=604309 RFE 1119025] is about trying to repair the file at startup and recover what is recoverable. The intended behavior would be to have a message of the form:

"'''The document <name> could not be read in its entirety because it has errors, or some data are missing. Do you want to recover the readable data in this file?'''

Inkscape can create a new document from any
readable objects contained in your file. Your original file will not
be touched. Inkscape will open a new window called
<name> [Recovered]. You might want to export the
recovered objects into a new file before proceeding.
Note: You may be able to obtain better results using an
XML editor or text editor."

Deciding to recover the file will parse it with a more permissive XML parser and recover what can be recovered. What cannot be recovered should be preserved as an XML comment.

=== Case 2: ===

The example of some valid files with problems was discussed on a [http://sourceforge.net/tracker/index.php?func=detail&aid=1326574&group_id=93438&atid=604306 bug report] and on several threads of the devel mailing list: [http://sourceforge.net/mailarchive/forum.php?thread_id=8578063&forum_id=36054 zooming bug], [http://sourceforge.net/mailarchive/forum.php?thread_id=8602372&forum_id=36054 zooming bug bis], [http://sourceforge.net/mailarchive/forum.php?thread_id=8602956&forum_id=36054 sanity checking on file open], [http://sourceforge.net/mailarchive/forum.php?thread_id=8606155&forum_id=36054 what should zoom to content do], [http://sourceforge.net/mailarchive/forum.php?thread_id=8629987&forum_id=36054 artificial limits]. All started from a bug in Inkscape which produced one object with insane bounding box which itself induced a strange zooming behavior. The bug itself was corrected by bulia. The discussion which followed was focused on the fact that such files can be encountered in the "wild" and that some Inkscape feature could help dealing with them.

The intended behavior in this case would be to issue visible warnings and to provide solutions (even is they basically redirect the user to the XML editor). The problem about when to warn occurs and the suggestion was to build a "Validate file" or "Fix file" feature which would validate the XML, detect strange cases and ask the user what he wants to do about it (correct or suppress or...). The discussion is about adding to this features artifical limits, human defined, above which some bounding box for example is considered insane.

The two cases could obviously share some features.

----

== Example files ==
In this section, files which cause particular problems can be linked and described.

=== Non valid XML ===
# Octave (a free numerical computing software) can produce plots directly to SVG and it seems that even [http://jo.irisson.free.fr/dropbox/inkscape/octave_svg.svg a very simple one] cannot be opened in Inkscape. It might well be octave fault but the file is here for you to check.

=== Valid XML with problems ===
# [http://jo.irisson.free.fr/dropbox/inkscape/schema_bilan.svg file with one object having a huge bounding box]. This file was generated following a bug in Inkscape but some other might be encountered.
# [http://jo.irisson.free.fr/dropbox/inkscape/sampling.svg file with many insane transform matrices]. This file was generated as eps by Scilab, a scientific plotting software, and converted to svg by pstoedit version 3.40 / DLL interface 108 (build Oct 10 2005 - release build). Many transform matrices look like: transform="matrix(2.007003e-3,0.000000,0.000000,-2.007003e-3,-6.079619e-2,1.461081)". Probably related to this, every new object or text looks huge and dashes cannot be applied to lines.
# Another file with many insane transform matrices converted from an eps file. The [http://jo.irisson.free.fr/dropbox/inkscape/R_plot.eps eps file] was generated by R, a free, cross platform statistics software which is quite well known and standard in statistics studies. Then it was converted to an [http://jo.irisson.free.fr/dropbox/inkscape/R_plot_pstoedit.svg svg file] by pstoedit. Finally it was parsed by inkscape and saved to [http://jo.irisson.free.fr/dropbox/inkscape/R_plot_pstoedit_inkscape.svg Inkascape SVG]. This file induces any new object to be insanely big and dashes cannot be applied to any stroke (already present or newly created).
# And agin a file with many insane transform matrices converted from an eps file. The [http://jo.irisson.free.fr/dropbox/inkscape/octave_ps.ps ps file] was generated by Octave, converted to an [http://jo.irisson.free.fr/dropbox/inkscape/octave_ps_pstoedit.svg svg file] by pstoedit and parsed by inkscape to [http://jo.irisson.free.fr/dropbox/inkscape/octave_ps_pstoedit_inkscape.svg Inkascape SVG]. As the others, this file induces any new object to be insanely big and dashes cannot be applied to any stroke (already present or newly created).
#

----

== Developement status ==
* 17 Oct 2005: The issue is raised ;-)

CompilingMacOsX

2005-10-06T10:37:41Z

194.167.139.18: *

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables.sh</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CFLAGS="-I$FINK/include -O3 -Wall"
export LDFLAGS="-L$FINK/lib"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="$CXXFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

Then, open a Terminal and, in the directory where you created the file, type:
<pre>
bash
source set_variables.sh
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Building''':

Open a Terminal and cd to Inkscape's sources directory. Type:
<pre>
./configure --prefix=/some/directory/
make
make install
</pre>

You have to put your build products somewhere you have write access to (for example you home directory) in order to be able to package the application from there afterwards. That is what the <code>--prefix</code> option is for.

'''Packaging''':

The process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Interesting links ==

Some packaging links:
http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
http://gimp-app.sourceforge.net/gimp.app.howto.txt

CompilingMacOsX

2005-10-06T09:11:48Z

194.167.139.18: update of the configuring section

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release, note that from version 0.42 of Inkscape a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from Inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get Apple's X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape Inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem useful.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
popt popt-shlibs �
gc gc-shlibs automake 1.8
</pre>

You need automake 1.8 and not the latest in fink (1.9.6-1). Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are in bash syntax. You can create a file named <code>set_variables.sh</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="gcc"
export CXX="g++"
export CFLAGS="-I$FINK/include -O3 -Wall"
export LDFLAGS="-L$FINK/lib"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="$CXXFLAGS"
</pre>

Optionaly, to speed up the compilation a bit you could use <code>ccache</code> if you have it installed:
<pre>
export CC="ccache gcc"
export CXX="ccache g++"
</pre>

Then, open a Terminal and, in the directory where you created the file, type:
<pre>
bash
source set_variables.sh
</pre>

Then you need to build the configure script. Cd to Inkscape's source directory and run:
<pre>
autogen.sh
</pre>

'''Building''':

Open a Terminal and cd to Inkscape's sources directory. Type:
<pre>
./configure --prefix=/some/directory/
make
make install
</pre>

You have to put your build products somewhere you have write access to (for example you home directory) in order to be able to package the application from there afterwards. That is what the <code>--prefix</code> option is for.

'''Packaging''':

The process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----

== Interesting links ==

Some packaging links:
http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
http://gimp-app.sourceforge.net/gimp.app.howto.txt

CompilingMacOsX

2005-10-03T14:07:59Z

194.167.139.18: removed a duplicate in the "fink install" section

CompilingMacOsX

2005-09-17T15:03:50Z

194.167.139.18: update of the compilation how to and clear separation between howto and compilation history

= Compiling and Packaging Inkscape under Mac OS X =

== Before you start ==
If you want an Official Release of inkscape, note that from version 0.42 of Inkscape, a Mac OS X package (in .dmg form) will be available. In addition, regular Development Versions will be build. Both can be downloaded from inkscape's downloads page:

:http://www.inkscape.org/download.php

Inkscape for Mac OS X is an X client: it runs under the [http://en.wikipedia.org/wiki/X_Window_System X Windows System]. You will need an X Windows Server installed for it to work. You can get the Apple X Server (requires Mac OS X 10.3 or above) here:

:http://www.apple.com/downloads/macosx/apple/x11formacosx.html

----
----

== Compiling How To ==

'''Note''': You could use the [http://fink.sourceforge.net/pdb/package.php/inkscape inkscape package] from the [http://fink.sourceforge.net Fink project] to install Inkscape from source but this package is usally older that the precompiled Development Versions and even that the Official Release so this does not seem usefull.

'''Requirements''':
#Mac OS X 10.3 of higher
#A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
#Inkscape source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ CVS snapshot] or a copy of the [http://sourceforge.net/cvs/?group_id=93438 cvs repository] (the module name is "inkscape")

'''Installing dependencies''':

In a Terminal type:
<pre>
fink install �
intltool �
glib2 glib2-dev glib2-shlibs �
gtk+2 gtk+2-shlibs gtk+2-dev �
libpng3 libpng3-shlibs �
libsigc++2 libsigc++2-shlibs �
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs �
libtool14 libtool14-shlibs �
libxml2 libxml2-shlibs �
libsigc++2 libsigc++2-shlibs �
popt popt-shlibs �
gc gc-shlibs
</pre>

Fink installs many packages from source so this is usually long.

'''Setting the build environment''':

You need set the following environment variables (taken right out of fink's <code>.info</code> file) for the compilation to work. They are is in bash syntax. You can create a file named <code>set_variables</code> for example and copy/paste this inside:
<pre>
#!/bin/bash
FINK="/sw"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export CC="ccache gcc"
export CXX="ccache g++"
export CFLAGS="-I$FINK/include -O3 -Wall"
export LDFLAGS="-L$FINK/lib"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="$CXXFLAGS"
</pre>

Then, open a Terminal and, in the directory where yhou created the file, type:
<pre>
bash
source set_variables
</pre>

'''Building''':

Open a Terminal and cd to Inkscape's sources directory. Type:
<pre>
./configure --prefix=/some/directory/
make
make install
</pre>

You have to put your build products somewhere you have write access to (for example you home directory) in order to be able to package the application from there afterwards. That is what the <code>--prefix</code> option is for.

'''Packaging''':

The process is automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh /path/to/bin/inkscape ../Info.plist macosx
</pre>

You will end up with two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

-- Kees Cook, Michael Wybrow, Jean-Olivier Irisson

----
----

== News and History about compiling under OS X ==

----

Since gc 6.4 is needed, once fink is updated, you can install: "fink install gc gc-shlibs", but until then, you'll need to compile it yourself. :(

Some packaging links:
http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/

-----

See the new Info.plist.in file in CVS, as well as packaging/osx-app.sh for building an .app directory. I have no idea what I'm doing, and I'm doing it blind, so any help is appreciated. I'm guessing at appropriate paths in src/path-prefix.h, which get activated with configure's --enable-osxapp now.

Also, we probably need to do all this stuff too:
http://gimp-app.sourceforge.net/gimp.app.howto.txt

------

I have succesfully built Inkscape 0.40-1 via Fink under Mac OS X 10.3

After I have moved to "~/Desktop/Inkscape.app/Contents" following the way explained for the Gimp.app

The application lauches itself with a double-click and it is available there http://niwaconcept.free.fr//x11/Inkscape.zip

But if it can be stored there that would be better. The file is 60 Mb do dwnload, and then 280 Mb for the software itself.

M-Rick

upload:inkscape-0.40-2.jpg
upload:inkscape-0.40-1.jpg

----

I've downloaded the zip and copied the resulting .app to /Applications.

Running it gives the following errors:

<pre>/Applications/Inkscape.app/Contents/MacOS robmyers$ ./Inkscape
dyld: ./Inkscape can't open library: /Volumes/Utilisateurs/Users/aymeric/Desktop/Gimp/ScriptExec/build/ScriptExec.build/ScriptExec.build/Objects-normal/ppc/libstdc++_ZeroLink.dylib
(No such file or directory, errno = 2)
Trace/BPT trap</pre>

- robmyers .

----

Strange ....
And it puts all the path of my computer ...

And scriptExec is the script used by gimp.app, once compiled it is said to change the name.

When I ran inkscape from my computer, I did from many locations and no problems, I will see I have errors feedbacks.

I am not specialized in programming so if someone wants to help no problem.

M-Rick

----

Ok it's done.

Anyway, there are a few bugs, also present in Fink :

Some menus appear behind the windows.

Impossible to export as bitmap, there is an error message "The chosen area to be exported is invalid" and I have it even if I change the path.

I made a DMG, you can download and test it there http://niwaconcept.free.fr//x11/Inkscape.zip

M-Rick

----

That works perfectly. And the .dmg window looks very good, it's a perfect Mac installer.

Thanks!

- robmyers .

----

Erk! But when I try it on a machine without Fink installed, I get the following error:
<pre>
dyld: /Applications/Inkscape.app/Contents/Resources/bin/inkscape can't open library: /sw/lib/libgtkmm-2.4.1.dylib (No such file or directory, errno = 2)
</pre>

This despite the fact that libgtkmm is present in the Inkscape.app/Contents/Resources/lib/ directory.

- robmyers .

----

Yes, I just made an update for it. I tricked it, because it is looking for a sw folder, so i made a link to the software, just double-click it and and it will create it automatically for you, until I find the way to not have to do this.

M-Rick

----

Does Gimp.app do this? What happens if someone uses Fink and /sw already exists?

Downloading, running and installing, this now works after a couple of runs. Don't know if I was being impatient. :-)

- Inkscape MacOSX Testing Team (i.e. robmyers :-) ).

----

No Gimp.app doesn't do that. Inkscape does that because I haven't found yet the way it tries to find the share folder.
If you already have Fink installed, well, it will not erase it just add the link.

Inkscape.app has a problem with the GTK pixmaps location, so I have made a script inside the software that will create a link automatically. So for the first launch, it is better to launch under an admin session.
But if you have Fink already installed, it won't work unless you are root, so if you don't want to login as root, you can change the settings of the folders /sw and /sw/share to Group/Admin and Acces/Read and Write.

If someone finds the way to correct this, we won't have to do this trick anymore.

M-Rick

----

I think the program will need to add the pixmap location dynamically to $GTK_PATH on startup using setenv before starting Inkscape proper?

- robmyers .

----

I've installed inkscape.app. It works quite well on Japanese environment. "KANJI" can be used!

Ken

upload:japanese.jpg

-----

I've installed it and it works. Very nice. The background image in the DMG is a nice touch, though you could maybe add the standard 'drag this icon to your applications folder' text to that. I still find Inkscape rather slow -- with the Windows version I assumed it was just a porting issue. Is the same true here? I have an SVG document with about 1000 objects. BTW, curious bug -- tooltips for floating palettes appear ''below'' them!

-----

Damn, I'm at work and don't have my mac with me! Can't wait to get home and install this!!! I'll see what I can do about some of these problems, too.

-----

I gave the DMG a try on my PowerBook running 10.3, with Fink and Gimp.app installed. It seems to work ok, except most of the tool icons don't show up. When I hover over them I get a blue Aqua-lozenge background and the tooltip, but the icon never shows up. The only ones that do are New File, Open File, Save, Print, Undo, Redo, Copy, Cut, and Paste. FYI.

-Ken-ichi

-----

A note about the icons: the app icon is fantastic, as is the inkscape SVG document icon. The other document icons are good too, but the file extension badge shouldn't stick out from the page image (see [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGIcons/chapter_5_section_2.html#//apple_ref/doc/uid/20000967/TPXREF117]).

------

Has anyone besides me noticed that inkscape loads VERY slowly (>1.5 minutes)? Is this normal?

Marcus Collins

------

On my PowerBookG4 12in 867MHz, loading time of Inkscape(fink): 20 sec, Inkscape.app: 135 sec. VERY slowly.(v_v)

Ken

----

Well yes it is very slow. Even via Fink, the delay in launch time is due to library checking .... I ond't know how to solve it, so if someone is ready to check the sources it's OK. I don't know the exact command it uses to check them. Once this corrected, it will launch fast as in Fink.

For the pixmaps, it's because of the problem just above, since I don't know how it checks the lib paths, the pixmaps checking is wrong, so you must make a link from Inkscape.app/Contents/Resources/lib/libgtkmm-2.4.1.dylib to /sw/lib

M-Rick

----

I've added Inkscape to FreeSMUG (Free Software Mac User Group) directory:
http://www.freesmug.org/review/inkscape

Happy MhACking.

Gand.

----

About freesmug.org you talk about menus that appears behind windows. It appears only if you use quartz-wm. For people who have for example kde, it works fine, but it's slower to launch/use.

Darwinports has the 0.41 package now. It still has awfull dependencies (why compiling ALL gnome just to get inkscape?). But it works fine. I didn't try your .dmg file thou.

iznogoud_

----

Dose Inkscape.app work well on Tiger?

Ken
----
I have tried, and tried again, but I am unable to compile Fink on Tiger. I know it's early days (only been out for a week) but I find it interesting that compilation fails - what has changed? Does it involve the new compiler? (GCC 4.x) Error is:

object-edit.cpp: In function `void sp_spiral_outer_set(SPItem*, const
NR::Point&, const NR::Point&, unsigned int)':
object-edit.cpp:842: error: `__isfinite' undeclared (first use this function)
object-edit.cpp:842: error: (Each undeclared identifier is reported only once
for each function it appears in.)
make[2]: *** [object-edit.o] Error 1
make[1]: *** [all-recursive] Error 1

I am busy downloading Inkscape.app with the hope that it will work.

Dawid Loubser
----
Help! Please help me get this to work. I need Inkscape!

If you need Inkscape and inkscape.app isn't working, try fink. You'll need to install the unstable branch, but this works on 10.3 and 10.4 just fine. http://fink.sourceforge.net

----
Problems with isnan and isfinite again. New fink package should build fine on tiger.

If you are compiling yourself, to save you an hour, add -D__LONG_DOUBLE_128__ to you CPPFLAGS.

Peter

Hi. Try to compile with darwinport. Some warnings and an error :
gc.cpp: In function `void Inkscape::GC::init()':
gc.cpp:190: error: assuming cast to type 'void* (*)(size_t)' from overloaded function
make[2]: *** [gc.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Tried gcc 4.0 and 3.4. Tried the -D__LONG_DOUBLE_128__ as well. Got this error or the one above. I'll try fink

-----

Can anyone help?

I've just installed inkscape through fink on Tiger and all works fine except that when I run inkscape I get the following errors (in a dialogue box):

One or more extensions failed to load...

A look in the error-log file: extension-errors.log, shows the following:

Extension "Postscript Input" failed to load because a dependency was not met.
Dependency::
type: extension
location: path
string: org.inkscape.input.sk

Extension "EPS Input" failed to load because a dependency was not met.
Dependency::
type: extension
location: path
string: org.inkscape.input.ps

I really need eps and postscript support (there are also a couple of other extensions missing, but these are less important). Did anyone else have this problem or know a work around. Fink says all my packages are up to date... and I have gs and pstoedit installed already...

Justin.

----

I'm having a problem running inkscape app on Mac OS 10.4.1. Here's the crash log:

<pre>
Host Name: iMac
Date/Time: 2005-05-26 22:14:32.458 +0200
OS Version: 10.4.1 (Build 8B15)
Report Version: 3

Command: inkscape-0.40
Path: /Users/karl/Desktop/Inkscape.app/Contents/Resources/bin/inkscape-0.40
Parent: Inkscape [1029]

Version: ??? (1.0)

PID: 1030
Thread: Unknown

Link (dyld) error:

Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
Expected in: /Users/karl/Desktop/Inkscape.app/Contents/Resources/lib/libJPEG.dylib
</pre>

-- Karl

-----

On Tiger, I have downloaded the .dmg image of Inkscape and
dragged it into /Applications.

Then remove or rename a few libraries inside the Inkscape directory:
<pre>
cd /Applications/Inkscape.app/Contents/Resources/lib/
mv libjpeg.dylib libjpeg.dylib.original
mv libtiff.dylib libtiff.dylib.original
mv libpng.dylib libpng.dylib.original
</pre>

Then, as root (sudo sh), link the "share" directory to the place
where Inkscape expects it:
<pre>
cd /sw/share
ln -s /Applications/Inkscape.app/Contents/Resources/share/inkscape inkscape
</pre>

Start Inkscape, have patience (1-2 minutes, no idea why), and it
will start.

-- Alex.

----

I have downloaded the latest package on this page, but it doesn't do a thing. When I start inkscape inside the package, it starts up, starts x11 if that wasn't up yet, and after a couple of seconds it quits. Running it from the Terminal does the same thing, and I'm not getting any errors on the stdout/stderr. Has someone experienced similar problems with inkscape on Tiger? And maybe someone has found a solution?

I can't find inkscape in fink, either.

Update I should hit myself... The above post by Alex told me how to get inkscape to run on Tiger, and I simply didn't see it. So for all other people having similar problems: try Alex' tips! I had to wait for 1-2 minutes on this pbook as well, but it finally shows up and runs fine.

Has anyone figured out why some drop down boxes and such do show up behind the dialogs? Has this anything to do with the aggresive behavior of those windows to always be on top of other windows? I have tried several options in the inkscape preferences pane, but this didn't do away with the boxes-behind-dialogs problem. Is there a way this can be disabled while running or at compile time?

Anthony,-

----

Confirm Inkscape.dmg is looking good on tiger, congratulations

edited Alex's message as a second 'inkscape' is needed ~:" thanks Alex and the team

not clear why inkscape is not in fink packages though.

Peepo

----
Inkscape is in fink's unstable tree. It is not in the binary release because it requires some packages that are not in the stable tree yet.

Note that I belive the startup time will improve with Mac OS X 10.4.2

Peter

(Suggest dividing this page up: The category CompilingMacOsX ought to comprise only instructions for compiling on Mac OS X! -Ben).

(Also the material specific to verion 0.40 et cetera should be removed, it is not going to be expected here -Ben)

(Arguably Tiger material goes into a new area: 'For thill seekers' or, if Tiger is now mainstream, the whole page is re-organised on that basis, and the Panther material placed somewhere else! -Ben)