https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&user=DavidCary&feedformat=atomInkscape Wiki - User contributions [en]2024-03-29T09:56:29ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=Google_Summer_of_Code&diff=78038Google Summer of Code2012-02-20T23:56:10Z<p>DavidCary: clarify (I hope)</p>
<hr />
<div>= Welcome to Inkscape! =<br />
<br />
For a few years Inkscape was successful in participating in [http://code.google.com/soc/ Google Summer of Code].<br />
<br />
GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.<br />
<br />
We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.<br />
<br />
The Inkscape team plans to focus this summer on codebase cleanup and refactoring. This will affect the type of projects we can accept this year; we're looking for ones that either won't affect core code too significantly (such as Extension scripts, or File Input/Output formats) or that would actually result in improving the state of the codebase (adding tests, modularization, etc.). Students who have already been active developers in Inkscape previously will be allowed more latitude to work on core code (particularly if it will result in cleanup/refactoring of their past work).<br />
<br />
= Student Applications =<br />
<br />
* Google program information<br />
** Summer of Code Application form<br />
* Inkscape-specific information<br />
** [[SOC Application Template]]<br />
** [[Roadmap | Inkscape Roadmap]] - to see our overall objectives<br />
** [[SOC Writing Project Proposals]] - some guidelines for proposals<br />
** [[SOC Selection Criteria]] - how we rate applications<br />
<br />
= Successful SOC Projects from Previous Years =<br />
* 2005<br />
** Connectors<br />
** Inkboard<br />
** [http://www.openclipart.org/ Open Clip Art Library (OCAL)] Interface<br />
** DXF Import / Export<br />
* [[Google Summer of Code 2006|2006]]<br />
** Support for SVG Filters<br />
** Filter Effects<br />
** PDF export<br />
** Inkboard Protocol Spec / Lib Conversion<br />
* [[Google Summer of Code 2007|2007]]<br />
** Text Style Improvements<br />
** PDF import<br />
** Live Path Effects<br />
** 3D Box Tool<br />
** UI for SVG Filter Effects<br />
** Raster Functionality<br />
** Importing from, and Exporting to, a remote ccHost instance<br />
* [[Google Summer of Code 2008|2008]]<br />
** SVG Fonts support<br />
** 2Geom refactoring project - port most geometry code to 2Geom<br />
** lib2geom: interactive applications showing off the power of lib2geom<br />
** Tech drawing abilities<br />
** A test suite<br />
* 2009<br />
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]<br />
** D-Bus scripting API<br />
** Connector tool improvements<br />
** ICC/CMYK workflow<br />
* 2010<br />
** Cairo-based rendering<br />
** C++ification of SP Layer<br />
* 2011<br />
** Rendering caching<br />
** Javascript support improvements<br />
** CSS support improvements<br />
<br />
= The "two patches" rule =<br />
<br />
We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).<br />
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it. <br />
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!<br />
You can join our jabber/IRC channel and ask developers for help.<br />
To get you started on Inkscape development, here is a list of (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program.<br />
<br />
== Suggested "easy" bug fixes or improvements ==<br />
<br />
* [https://bugs.launchpad.net/inkscape/+bug/530957 Bug #530957 “Save as dialog regression with filename”]: (MS Windows) File save dialog - the "save/save as/save a copy" dialog should fill in a suggested file name *without* extension. For example, if I am working on a file "hello.svg", and press "save a copy", the file name input field should have the text "hello" in it.<br />
<br />
* [https://bugs.launchpad.net/inkscape/+bug/408566 Bug #408566 “Program won't save files without given extension on Win32”]: (MS Windows) A folder in the path with a dot '.' in its name prevents automatic adding of the file name extension and saves the file without suffix.<br />
<br />
* [https://bugs.launchpad.net/inkscape/+bug/561503 Bug #561503 “Setting grid origin has no effect”]: (all platforms)<br />
<br />
= Suggested Ideas =<br />
<br />
== Generic ideas ==<br />
<br />
* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]<br />
* [https://blueprints.launchpad.net/inkscape/+spec/new-from-template-dialog 'New From Template' dialog]<br />
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices<br />
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/guides-improvement Guides Improvements]<br />
<br />
== Import/export projects ==<br />
<br />
* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]<br />
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape<br />
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps<br />
<br />
== Internal work & performance improvements ==<br />
<br />
* Continue C++ification.<br />
* Improving 2Geom where necessary (e.g. boolops).<br />
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.<br />
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.<br />
* Units (inch, cm, px): the codebase has 4 different pieces of code for handling units! Refactoring into *one*.<br />
<br />
== Better SVG standard coverage ==<br />
<br />
* Full SVG viewbox support<br />
* [[multipage | Multiple Page support]]<br />
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].<br />
* Improve handling of CSS. We use [http://www.freespiders.org/projects/libcroco/.example.com libcroco] which is unmaintained. Inkscape SVG output is full of unnecessary style attributes.<br />
<br />
== Improve Inkscape SVG for use on Web ==<br />
<br />
A proposal should fix most if not all of these problems:<br />
<br />
* Fix "plain" SVG to not remove <script> section, etc.<br />
* Fix saving SVG to not modify CDATA (e.g. don't change &amp; to &amp;amp; inside CDATA).<br />
* Add option to set viewbox attribute to Document Properties.<br />
* Font fallbacks.<br />
* Easily add/edit hyperlinks.<br />
* Better CSS support.<br />
* Option to add title to SVG (searchability and accessibility).<br />
* Remove XML prolog/DOCTYPE.<br />
* Move sodipodi namespace items to Inkscape namespace.<br />
<br />
== Live Path Effects related ==<br />
<br />
* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.<br />
<br />
== Tools and shapes related ==<br />
<br />
* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]<br />
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for morphing Inkscape PATH shapes.<br />
* Add a palette of objects to Inkscape. Such a palette would contain often used objects and would allow categorizing such objects. Examples of categories: UML, electric, network.<br />
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)<br />
* Arrowhead/marker improvements<br />
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]<br />
* Add Mesh gradients in Inkscape name space with appropriate editing interface. (Note that Cairo now supports meshes and [http://tavmjong.free.fr/SVG/MESH/Mesh.html here] is a WORK IN PROGRESS of a proposed mesh syntax for svg.) It would be advised to base work on the existing cairo rendering branch for Inkscape.<br />
<br />
Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!<br />
<br />
For more ideas, please see https://blueprints.launchpad.net/inkscape/</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=Installing_Inkscape&diff=77618Installing Inkscape2012-02-12T04:15:08Z<p>DavidCary: difference between the various Windows downloads?</p>
<hr />
<div>== Installing on a Mac ==<br />
<br />
There are two steps needed to install on a Mac.<br />
<br />
<br />
=== Getting The Right Inkscape Installer ===<br />
<br />
You need to download the right installation file from the Inkscape [http://www.inkscape.org/download/ download] page. Note that this page has a separate version for Panther (10.3.9 only), and Tiger (10.4.x) and above. The Panther version is PPC only, while the Tiger version is ''Universal Binary'', meaning it installs on either older PPC or newer Intel Macs. The Tiger version will also work on Leopard (10.5.x)<br />
<br />
Once you have the Inkscape installation package, double click on it and it will open a window with an Inkscape icon on one side, and a shortcut to the Applications folder on the other side. You need to drag the Inkscape icon across and drop it on the Applications folder. This will copy the file to the Application folder.<br />
<br />
To make a shortcut on your Dock, open the Applications folder, and drag the Inkscape icon to the place you want it on the dock.<br />
<br />
<br />
=== Getting The Right X11 Installer ===<br />
<br />
To run Inkscape, you will also need to install X11. This is an environment that provides Unix like X-Window support for applications, including Inkscape (For more about X11 see [http://en.wikipedia.org/wiki/X11 Wikipedia]). A native Mac OSX version that doesn't need X11 will be available sometime in the future (see [http://www.nabble.com/attachment/14733036/1/Inkscape%20OSX%20PL.gif here] or [http://jo.irisson.free.fr/?p=34 here] or [http://jo.irisson.free.fr/?p=62 here] for a sneak peek). But for now you need to do one of the following, depending on your OSX version.<br />
<br />
<br />
==== For Panther (10.3.x) ====<br />
<br />
You can download a suitable version of X11 from [http://www.apple.com/downloads/macosx/apple/macosx_updates/x11formacosx.html Apple] or mirrored at [http://inkscape.modevia.com/macosx-snap/X11User_Panther.dmg Modevia].<br />
<br />
<br />
==== For Tiger (10.4.x) ====<br />
<br />
You can install X11 from your original Install Disc 1. Scroll down the Finder window which opens when the DVD is inserted; double clic "Optional Installs"; go through the license agreement and destination selection; on the "Custom install" page select Applications -> X11 and deselect everything else; hit Install. To see what this looks like, see [http://overstimulate.com/ Jesse Andrews'] article entitled [http://overstimulate.com/articles/2005/11/04/installing-x11-on-os-x-10-4-tiger Installing X11 on OS X 10.4 Tiger]).<br />
<br />
Alternately, you can download a version for [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_PPC.dmg PPC], or [http://inkscape.modevia.com/macosx-snap/X11User_Tiger_Intel.dmg Intel] from Modevia. These files are able to be freely re-distributed because X11 is open source.<br />
<br />
'''Notes:'''<br />
*Once installed, you should also update your X11 to version [http://www.apple.com/support/downloads/x11update2006113.html 1.1.2]from Apple. This requires the earlier version, so you cannot just install the update.<br />
*A heavily improved version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] is expected to be available for Tiger some time in 2008. This will bring X11 on Tiger (10.4.x) into line with Leopard (10.5.x). See [http://trac.macosforge.org/projects/xquartz/roadmap here] for a roadmap of that project.<br />
<br />
<br />
==== For Leopard (10.5.x) ====<br />
<br />
Leopard officially ships with a version of X11 called [http://trac.macosforge.org/projects/xquartz/ XQuartz] pre-installed, however the preinstalled version has some problems. Starting from January 2008, the XQuartz community released several updates to the XQuartz package in Mac OS X 10.5.x on [http://trac.macosforge.org/projects/xquartz Mac OS Forge]. These releases significantly improve X11 on the version of XQuartz found in the original Leopard release.<br />
<br />
On February 11 2008, Apple released an official XQuartz update in the [http://www.apple.com/support/downloads/macosx1052comboupdate.html Mac OS X 10.5.2 update]. This update addresses [http://docs.info.apple.com/article.html?artnum=307430 two security issues], although it is still somewhat behind the current XQuartz releases, upon which the official update is based. The [http://trac.macosforge.org/projects/xquartz XQuartz site] notes that "''10.5.2's version of X11 is somewhere between the 2.1.1 and 2.1.2 packages released through this site''". It also warns that "''Installing versions prior to X11 2.1.2 onto OS-X 10.5.2 may work but is not supported.''"<br />
<br />
XQuartz 2.2.1 was released on May 1 2008. This version requires OS X 10.5.0, however if you install the 10.5.2 update (or other updates) after XQuartz, you will probably need to reinstall XQuartz.<br />
<br />
For optimal performance and security, it is always best to install the latest Mac OS X updates, and then install the latest XQuartz over the top. This is what XQuartz is designed to do.<br />
<br />
'''Notes:'''<br />
*Because of changes to launchd, you will need to logout and re-login after installing XQuartz.<br />
*For the keen, pre-release candidates and recent deprecated versions of XQuartz are available [http://xquartz.macosforge.org/downloads/ here]. Information on a given release or release candidate is normally available at http://trac.macosforge.org/projects/xquartz/wiki/X112.2.x (change x to suit)<br />
*The XQuartz release roadmap is available [http://trac.macosforge.org/projects/xquartz/roadmap here].<br />
*For more technical information about X11 on Mac, a good place to go is http://homepage.mac.com/sao1/X11/index.html<br />
<br />
<br />
==== For Snow Leopard (10.6.x) ====<br />
<br />
Everything is ok.<br />
<br />
<br />
==== For Lion (10.7.x) ====<br />
<br />
Everything is ok.<br />
<br />
<br />
=== Problems After Installation ===<br />
<br />
<br />
==== Keyboard mapping or Using the Alt key ====<br />
<br />
Create or edit the file ~/.Xmodmap with:<br />
<br />
! To make Alt keys "work" again.<br />
keycode 66 = Alt_L<br />
clear Mod1<br />
add Mod1 = Alt_L<br />
! The right Alt key is already mapped to Mode_switch (at least on my box). Uncomment the next line, if it's mapped differently on your Mac.<br />
! keycode 69 = Mode_switch<br />
clear Mod2<br />
add Mod2 = Mode_switch<br />
<br />
''X11'' > ''Preferences'' > Disable "'''Use the system keyboard layout'''" and "'''Enable keyboard shortcuts under X11'''" options<br />
<br />
<br />
==== Copy & Paste doesn't work well with Inkscape objects ====<br />
<br />
''X11'' > ''Preferences'' > Disable "'''Update Pasteboard when CLIPBOARD changes'''" options<br />
<br />
<br />
==== On Leopard (10.5) with XQuartz 2.2.1 ====<br />
<br />
Some users have reported problems loading Inkscape 0.46-2 with XQuartz 2.2.1 as [https://bugs.launchpad.net/inkscape/+bug/226355 Inkscape Bug #226355]. This problem occurs because XQuartz 2.2.1 has changed fontconfig.<br />
<br />
There are two possible fixes:<br />
<br />
<br />
1. Michael Whybrow, the packager of Inkscape for Mac suggests this:<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type the following<br />
mkdir ~/.fontconfig<br />
b. Rerun Inkscape.app<br />
<br />
<br />
2. Another solution originally posted [https://answers.launchpad.net/inkscape/+question/28776 Inkscape Answer #28776] suggests editing an Inkscape configuration file:<br />
<br />
a. Open Terminal.app (in Applications -> Utilities) and type<br />
nano /Applications/Inkscape.app/Contents/Resources/script<br />
b. Press CTRL+V (scrolls down a page)<br />
<br />
c. Change the code (use the arrows keys to get to the right part) from:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig || exit 12<br />
"""<br />
<br />
to:<br />
<br />
"""<br />
else<br />
# Leopard onwards...<br />
<br />
# Warn the user about time-consuming generation of fontconfig caches.<br />
test -d ${HOME}/.fontconfig<br />
"""<br />
d. Save changes by pressing CTRL+O and then ENTER to confirm<br />
<br />
e. Run Inkscape and wait for first-time caching<br />
<br />
Also it seems that having the "''authentificate connexion''" option checked in Preferences -> Securtity tab does interfere with Inkscape launch. Uncheck it if Inkscape doesn't launch.<br />
<br />
<br />
==== I've installed X11 on OS X but Inkscape keeps asking for it ====<br />
<br />
On Panther (10.3), you may need to uninstall/reinstall or upgrade X11. Use [http://www.osxgnu.org/software/pkgdetail.html?project_id=244 OSXPM] to uninstall X11 - Install OSXPM and select the Uninstall tab, scroll down to X11User, select it and hit Uninstall. Then you can install X11 properly.<br />
<br />
== Installing on Unix like systems ==<br />
<br />
=== Using Precompiled Packages (For Normal Users) ===<br />
<br />
==== Ubuntu Linux ====<br />
Probably the easiest way to install on Ubuntu is to use the apt command. <br />
<br />
Open a terminal and type;<br />
sudo apt-get update (enter)<br />
sudo apt-get install inkscape (enter)<br />
<br />
==== Ubuntu Linux Development Versions ====<br />
<br />
As it approaches release, nightly i386 and AMD64 builds of the latest Inkscape development version are<br />
provided at http://ubuntu.cafuego.net. On that site, one should<br />
select the appropriate Ubuntu or Debian release, then the Inkscape<br />
link, and finally the provided package.<br />
<br />
'''Note:''' Development versions offer some nice new features, but can be somewhat unstable, so save often. Inexperienced users will also quite possibly have problems installing them.<br />
<br />
==== openSUSE ====<br />
<br />
openSUSE includes Inkscape in the Gnome repositories. The newest version of Inkscape releases is in Gnome:Apps.<br />
<br />
==== Slackware Linux ====<br />
<br />
Binary packages (0.46+) are available for [http://www.linuxpackages.net/search_view.php?by=name&name=inkscape&ver=12.1 Slackware 12.1], [http://www.linuxpackages.net/search_view.php?by=name&name=inkscape&ver=12.2 12.2], [http://www.linuxpackages.net/search_view.php?by=name&name=inkscape&ver=13.0 13.0] y [http://www.linuxpackages.net/search_view.php?by=name&name=inkscape&ver=13.1 13.1] en [http://www.linuxpackages.net/ LinuxPackages.net].<br />
<br />
-- [[User:smaug|smaug]] 01:27, 27 Nov 2010 (GMT-4)<br />
<br />
I used the [http://sourceforge.net/project/showfiles.php?group_id=93438&package_id=99112&release_id=426990 precompiled rpm] provided by Inkscape for the 0.44 release as my gcc wouldn't compile it. All you need to then do is run rpm2tgz at the command line on the package, eg " rpm2tgz inkscape-0.44-0.i686.rpm" and then install with "installpkg inkscape-0.44-0.i686.tgz".<br />
<br />
-- [[User:Pbhj|Pbhj]] 13:29, 1 July 2006 (PDT)<br />
<br />
=== Compiling Your Own (For The Techies) ===<br />
<br />
<br />
NOTE: this isn't finished. I currently have two screwed up systems from fooling with bleeding edge GTK+ stuff, I don't know how that happened. !! :) I'll get to the end over the next few days tho. Setting up a more stable home network atm.<br />
-- <br />
Tsingi<br />
<br />
<br />
This was written building an InkScape snapshot on a new RedHat Linux installation. If you find that it doesn't answer your needs exactly, please update this file when you solve your particular problem.<br />
<br />
<br />
'''Installing libraries'''<br />
<br />
If you are running a debian based system, and have something like synaptic that lists recent enough versions of the libraries below, use that. If you want the latest libs, which you may need, especially if you are installing a snapshot or building from svn, you will want to download sources. Generally you will get a ''foo.tar.bz2'' or ''foo.tar.gz'' or ''foo.tgz'' file that you will need to unpack and build.<br />
<br />
''bz2'' files are the smallest. Uncompress them first by typing ''bunzip2 foo.tar.gz'' then unpack the remaining tar file by typing ''tar -xvf foo.tar''<br />
<br />
''foo.tar.gz'' files and ''foo.tgz'' files can be extracted in one operation by typing ''tar -xvzf foo.tar.gz'' <br />
<br />
Change to the directory that you just created ''foo''. type ''./configure'' then ''make'' then, as root, ''make install''<br />
<br />
Sometimes that is all you will need to do.<br />
<br />
Sometimes you will run into dependancy errors because you need a library you haven't installed yet. If you try installing inkscape without some of these dependancies, you will get a list of what you need. hopefully the instructions below will help you solve these dependancies.<br />
<br />
<br />
'''Running ldconfig'''<br />
<br />
after installing libs, (as root) you need to run ''ldconfig'' so that the linker can find the libraries that you have just installed. If you aren't logged in as root (i.e. if you became root by typing su) you may not have the /sbin/ directory in your path. so if ''ldconfig'' isn't working for you try typing ''/sbin/ldconfig''<br />
<br />
<br />
'''pkg-config'''<br />
<br />
''pkg-config'' is a utility that lists dependancies for libraries that sets up flags and paths for compiling. When it's working right it's wonderful. Getting it to work right is a pain in the ass if you don't know how. It's amazing how silent an IRC channel will get when you mention it.<br />
<br />
''pkg-config'' references pc files that applications install to give information about them. These are called metadata files, metadata means data about data. For a list of libraries that pkg-config sees, type ''pkg-config --list-all'' Having done that and looking at a list of pc files on my system (using ''find /usr -name "*.pc" > find.pc'', then browsing find.pc) I see that I also have a directory called ''/usr/lib64/pkgconfig/'' I might as well get that in there while I'm at it since none of those libs show up in a listing either and that's where most of them are.<br />
<br />
Depending on what shell you use, there are different ways of doing this. I'm adding a couple lines to my /etc/profile file:<br />
<br />
''PKG_CONFIG_PATH=/usr/lib/pkgconfig/:/usr/share/pkgconfig/:/usr/lib64/pkgconfig/:/usr/local/lib/pkgconfig/''<br />
<br />
''export PKG_CONFIG_PATH''<br />
<br />
Note that I have a new 64 bit system, which is why I'm going through all this. You probably won't have a ''/usr/lib64/pkgconfig/'' unless you do too, so don't just copy what I did. Also note that on a Windows system PATH type environment variables use semi-colons ";" for delimiters as opposed to colons ":"<br />
<br />
Using bash, to immediately source the file in the shell you are using, type ''. /etc/profile'. This won't test to see if the path gets put into your environment when open a shell though, so maybe a better thing to do is close your terminals and open new ones to see that it is actually set automagically.<br />
<br />
Ahh, I can now configure glibmm. The hair on the back of my neck is laying flat again, I think I'll have a coffee. :)<br />
<br />
<br />
<br />
'''libgc'''<br />
<br />
download and install the latest version of libgc[[http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/]]<br />
<br />
libgc installs in /usr/local/lib by default. If you have installed it and it is still not linking, you may not have that in your library path. There is a LD_LIBRARY_PATH environment variable, or alternatively you can make sure that /usr/local/lib is listed in the file /etc/ls.so.conf<br />
<br />
<br />
<br />
'''libsig++'''<br />
<br />
download and install libsig++ [http://libsigc.sourceforge.net/stable.shtml]<br />
<br />
this should be fairly straightforward.<br />
<br />
<br />
<br />
'''glibmm''' <br />
<br />
This is where, if you haven't wrestled with pkg-config on your system you start scratching your head. Because when you run configure on glibmm you may an error like this <br />
<br />
''checking for GLIBMM... configure: error: Package requirements (sigc++-2.0 >= 2.0.0 glib-2.0 >= 2.8.0 gobject-2.0 >= 2.8.0 gmodule-2.0 >= 2.8.0) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you<br />
installed software in a non-standard prefix.''<br />
<br />
''Alternatively you may set the GLIBMM_CFLAGS and GLIBMM_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for<br />
more details.''<br />
<br />
It seems that most packages install in a non standard prefix, in direct defiance of everything we have been led to believe regarding the concept of standard, so you may have to deal with this. See the note on ''pkg-config'' above.<br />
<br />
<br />
<br />
''gtkmm'' [http://www.gtkmm.org/]<br />
<br />
----<br />
(Ben) Tsingi, you are writing in the 'User Documentation' section. Most of this material is only appropriate for Developers and some would be better on the Mailing List. You will probably find that when you have finished, this page will be edited and pruned back. FWIW, I was expecting to find information about 'apt-get' (Debian) 'emerge' (Gentoo) and AutoPackage (the others).<br />
<br />
==== Build Dependencies (K/Ubuntu) ====<br />
<br />
NOTE: '''This list may not be complete''', please add any packages you might need in addition!<br />
<br />
To install the dependencies under Ubuntu (9.10), execute the following commands as root (sudo). Keep in mind that for other versions of Ubuntu this may not apply.<br />
<br />
sudo apt-get update<br />
<br />
sudo apt-get install build-essential libxslt1-dev libgsl0-dev libgtkmm-utils-dev \<br />
libpangomm-1.4-dev libboost-dev libpopt-dev<br />
<br />
In addition to those dependencies you need libgc (as mentioned above). Just download the latest version and build it.<br />
<br />
wget http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc.tar.gz<br />
<br />
tar -xvf gc.tar.gz<br />
<br />
cd gc*<br />
<br />
./configure --prefix=/usr/local<br />
<br />
make<br />
<br />
sudo make install<br />
<br />
Now you (should) have all the requirements to build Inkscape from source. To do that, run:<br />
<br />
wget http://inkscape.modevia.com/svn-snap/inkscape-current.tar.bz2<br />
<br />
tar -xvf inkscape-current.tar.bz2<br />
<br />
cd inkscape*<br />
<br />
./configure --prefix=/usr/local<br />
<br />
make<br />
<br />
sudo make install<br />
<br />
That should do it.<br />
(If the configure script tells you it requires an additional library, look for it via <code>sudo apt-cache search ''some-name''</code>, install the package via <code>sudo apt-get install ''some-package''</code>, and don't forget to add it to the list above.)<br />
<br />
[[Category:User Documentation]]<br />
<br />
== Installing on a Windows system ==<br />
=== Stable version ===<br />
You can find the installer from [http://www.inkscape.org/download/ download page]. Installing should be an easy step-by-step (next-next-finish) process.<br />
<br />
''Say a few words here about the difference between the traditional Windows "Inkscape installer", and the designed-for-USB-flash-drive "Inkscape Portable".''<br />
''( [[Release_notes/0.47#Packaging_Improvements]] ).''<br />
<br />
=== Unstable development version===<br />
First be warned. Unstable and development mean you likely will encounter crashes, usability problems and sometimes lose data. Ctrl+S will become your friend. If you cannot take this risk, please use the stable version instead.<br />
<br />
If you are still reading, you are probably one of the brave ones who wants to be on the bleeding edge. If so, follow these steps:<br />
==== 1. Download the latest build ====<br />
On [http://www.inkscape.org/download/ download page] there is a section named "Development Versions". Find the "Mirrored Win32 Builds" link. This points you to Inkscape's server at inkscape.modevia.com. There is information about builds and naming conventions at the top of this page. Further down the page there are links to files. Get the .7z file with latest date on it.<br />
===== Exremely small build =====<br />
If the build is significantly smaller than previous ones, the build most likely is broken and you should get the latest one which is of normal size (currently over 40MB and growing).<br />
==== 2. Extract the .7z archive ====<br />
Extract the archive using the [http://www.7-zip.org/ 7zip unpacker]. You will get a directory which contains several files including inkscape.exe.<br />
==== 3. Run inkscape ====<br />
Run the inkscape.exe file by double clicking it. That's it. <br />
You can also drag files to inkscape.exe to have these opened.<br />
<br />
'''Don't forget:''' please help Inkscape by reporting bugs, encouraging developers or fixing bugs yourself.<br />
<br />
==== Multiple versions for testing ====<br />
For testing purposes it is good to be able to test multiple versions of Inkscape to find when and where some problem first appeared. For this reason you are able to store and use as many parallel versions of Inkscape as your disk has room for.</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=WikiNode&diff=13806WikiNode2007-03-06T21:33:29Z<p>DavidCary: other related wiki pages</p>
<hr />
<div>Welcome to the [[Inkscape]] wiki!<br />
<br />
Inkscape is an open source drawing tool.<br />
Inkscape uses the scalable vector graphics format (SVG).<br />
Inkscape also imports several formats like EPS, PostScript, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
'''Key Points of Interest:'''<br />
<br />
* [[About Inkscape]] <br />
* [[FAQ]]<br />
* [[Galleries]]<br />
* [[UserManual]]<br />
* [[HelpWanted]]<br />
(what should go here?)<br />
<br />
'''Neighboring Wiki:'''<br />
<br />
* [http://www.protocol7.com/svg-wiki/ow.asp?WikiNode SVG wiki]<br />
* [http://www.openclipart.org/cgi-bin/wiki.pl?WikiNode Open Clip Art Project]<br />
* [http://visual.wiki.taoriver.net/moin.cgi/WikiNode Visual] - visual language<br />
* [http://wiki.services.openoffice.org/wiki/ OpenOffice.org wiki] - is it possible to substitute Inkscape for the "Draw" application in this suite? ''needs wikinode''<br />
* [http://freedesktop.org/wiki/ the freedesktop.org wiki] "freedesktop.org is open source / open discussion software projects working on interoperability and shared technology for X Window System desktops." Perhaps Inkscape could use the open-source Chinese fonts hosted there? ''needs wikinode''<br />
* [http://geda.seul.org/wiki/ gEDA] is a specialized CAD drawing program. ''needs wikinode''</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=WebSiteTranslation&diff=8278WebSiteTranslation2006-09-05T15:38:27Z<p>DavidCary: +WebsiteEditing</p>
<hr />
<div>Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
= Translation of web site =<br />
# There are two ways of getting files that you need to translate website:<br />
## Checkout actual svn version of inkscape_web module ([http://inkscape.org/svn.php Working with SVN]). To checkout the inkscape_web module use command: <pre>svn co https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk inkscape_web</pre> You need subversion client to do this. Be aware that the module is about 40MB to download because of screenshots!<br />
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.<br />
## Files you probably want to translate are:<br />
##* includes/localized.inc (file contains string to translate menu)<br />
##* index-en.inc (main page of inkscape.org)<br />
##* discussion-en.inc<br />
##* download-en.inc<br />
##* mailing-lists-en.inc<br />
##* report-bugs-en.inc<br />
##* submit2webmaster-en.inc<br />
##* submit2webmaster-en-form.inc<br />
##* svn-en.inc<br />
##* screenshots/*<br />
##* showcase/*<br />
##* docs/* (at least main page for docs)<br />
# Copy these files and replace "en" string in their name according to the ISO code of your language ("de" for german, "fr" for french, etc...).<br />
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.<br />
# If you have the file translated and really want to submit it, read it once more and correct errors ;)<br />
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.<br />
# Announce the translated file in the patch tracker in inkscape-translator(and optionally in inkscape-devel) mailing list. Persons responsible for updates of website will reply to you and/or submit the new "patch" directly.<br />
If the translation of website is new, the process of making new translation available can take a bit longer because of a need to create corresponding flag and check consistency of the translation.<br />
== Translating news and status ==<br />
News and status information are available for translation too. News items are stored in the /news directory of inkscape_module in separate subdirectories named by language version. The structure of directory with news is:<br />
<pre><br />
/news<br />
- en<br />
\- 2005<br />
- 2006<br />
\- 04<br />
- 05<br />
\- 001.inc<br />
- 002.inc<br />
...<br />
- de<br />
- fr<br />
</pre><br />
To translate news into your language download/checkout 00x.inc file from "en" directory, translate and submit to the directory of your language(file has to be in UTF-8 encoding) or submit to the patch tracker and announce on the inkscape-translator list.<br />
If you want to translate status information, the structure of directories is like in the case of news, only the name of directory is different.<br />
<br />
= Wiki =<br />
<br />
Translating the pages of the wiki is quite straightforward.<br />
<br />
In a few steps :<br />
- start by creating a main page for your language: create a new page (with an explicit translated title), and provide a link to it from the [[http://wiki.inkscape.org/wiki/index.php/Main_Page main wiki page of Inkscape]].<br />
- then, start a new page for each wiki page translation, and link translated page to the main page of your language.<br />
<br />
Don't forget to get some information about wiki syntax before creating/modifying some wiki pages.<br />
<br />
= Release notes =<br />
[[http://wiki.inkscape.org/wiki/index.php/Release_Notes Release notes]] simply consist in a wiki page.<br />
You can apply the process stated [[http://wiki.inkscape.org/wiki/index.php/WebSiteTranslation#Wiki above]] for translating this content.<br />
<br />
<br />
= Translation information =<br />
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.<br />
<br />
<br />
== See also ==<br />
<br />
* [[WebsiteEditing]]</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=Editing_Inkscape%27s_website&diff=8276Editing Inkscape's website2006-09-05T15:37:52Z<p>DavidCary: clarified (I hope)</p>
<hr />
<div>Anyone can edit the Inkscape wiki.<br />
<br />
Once you have developer-level access to the project, you can also help with maintenance of the non-wiki parts of the Inkscape website.<br />
<br />
== SVN Checkout of the Website Module ==<br />
<br />
To checkout the website cvs module:<br />
<br />
:Type <pre>svn co https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk inkscape_web</pre> after you have logged in with your username/password<br />
<br />
For more info, see See [[WorkingWithSVN]].<br />
<br />
== Testing your website changes locally ==<br />
<br />
Once you have checked out (see previous heading) the website module, then make a symbolic link to your web root directory. To do this for apache on redhat9 the best way is to navigate to <pre>/var/www/html</pre> and then type:<br />
<br />
:<pre>ln -s /usr/src/inkscape-project/inkscape_web</pre> (NOTE: that the path you pass should be relative/absolute to the inkscape_web module you just checked out)<br />
<br />
Thus, once you have done this, then you will be able to view the Inkscape website at <pre>http://localhost/inkscape_web/</pre> on your computer via a web browser.<br />
<br />
Hopefully, you have apache configured properly and it is running.<br />
<br />
== Making Your Changes Live on Inkscape.org ==<br />
<br />
# Make your changes to your local inkscape_web module.<br />
# Commit your changes, ensuring that you provide ample notes in your commit log message.<br />
# ssh -l <your sf username> ssh.sourceforge.net *<br />
# cd inkscape/inkscape_web<br />
# ./publish_web.sh<br />
<br />
(*)<br />
If you haven't done this before, you need to set up a link to the inkscape_web folder in your home directory.<br />
ln -s /home/groups/i/in/inkscape inkscape<br />
<br />
== Adding News to the Site ==<br />
<br />
If you have SVN access, you can add news to the site. First, you should add your signature to /includes/signatures.inc.<br />
<br />
Create your news in english always! create a new file in the news/en/<this-year>/<this-month> folder, and give it the next highest number. (if there are files named 001.inc and 002.inc, name yours 003.inc) You can use this as a template:<br />
<nowiki><pre><br />
<d i v class="item"><br />
<h3>HEADER</h3><br />
<b>MONTH DAY, YEAR</b><br />
<p>MESSAGE<br />
</p><br />
<?php echo $[[SIG_YOURNAME]]; ?><br />
</d i v><br />
</pre></nowiki><br />
Add new paragraphs if needed and dont forget to change the signature.<br />
<br />
If you want, translate the news to your language and save it in news/XX/<this-year>/<this-month><br />
<br />
If you really want to add news only in your language (not english), it might probably be the better way to modify your localized header (/index.xx-header.php). If you really think you need to have a local-only news, then please add an empty file with the same name (number) in the english directory and add a comment:<br />
<br />
<!-- This news is for xx users only --><br />
<br />
Make your changes live as described above.<br />
<br />
== Adding Screenshots to the Site ==<br />
<br />
The best way to add screenshots to the website is not by emailing them to the list or to any one developer unless you are not a developer. Instead, the best way is to create a screenshot for whatever screen size your system is set to (preferably a standard size like 1024 by 768), creating it in the PNG file format and then give it a descriptive name.<br />
<br />
Then the resulting thumbnail should be of the resolution 267 pixels wide by 200 pixels high in PNG format. The naming must be in relationship to the screenshot.<br />
<br />
Naming convention is:<br />
<br />
:inkscape-<version>-<id>-<name>.png<br />
:inkscape-<version>-<id>-<name>_thumb.png<br />
<br />
Example:<br />
<br />
:inkscape-0.43-01-myfeature.png<br />
:inkscape-0.43-01-myfeature_thumb.png<br />
<br />
<id> is ment to be something like 01, 02, 03... but you can also use 10a, 10b, 10c. this affects the order in the gallery. use zzz to place a sceenshot on top.<br />
(NOTE: <id> wasnt there before. but i suggest using it beginning with 0.43)<br />
<br />
save your shot into the "screenshots/gallery" folder, the thumb into "screenshots/gallery/thumbs".<br />
<br />
<br />
Once the graphics are in the right folder, my lovely PHP script will display them automatically on the main page of the website.<br />
They also appear on the screenshots/index.php page, therefore you must create a description file:<br />
<br />
:inkscape-<version>-<id>-<name>.en<br />
<br />
You may also create translations of description files. Just replace .en with the language code. Example:<br />
<br />
:inkscape-0.43-01-myfeature.en<br />
:inkscape-0.43-01-myfeature.de<br />
:inkscape-0.43-01-myfeature.es<br />
<br />
Store them in "screenshots/gallery/info"<br />
<br />
Then make sure that you add your new images and description files and any changes to the SVN repository. For more info, see [[WorkingWithSVN]].<br />
<br />
== Translating the Inkscape Website ==<br />
<br />
1. Do a CVS checkout of the website module.<br />
<br />
IMPORTANT: all files you change MUST be UTF-8 encoded!!! <br />
else, you will get broken output.<br />
See UT-8 note below, please.<br />
<br />
2. Add your language by these steps:<br />
- update the following line includes/header.php<br />
$LANGUAGES = array("en", "de", "es"); // available languages<br />
<br />
- Add a flag for your language in the images directory. It should be named inkscape_web/images/flag-XX.png. (where XX is your language code). Size is 34x20px.<br />
<br />
- Add a line to css/base.css, similar to the following: (place your flag 50px left of the others)<br />
#lang-xx { left:225px; }<br />
<br />
<br />
- Add a link for your flag in includes/header.php<br />
<br />
- create a copy of includes/localized-en.inc for your language. (like includes/localized-fr.inc) and translate the values of the strings.<br />
<br />
- copy and translate index.en-header.php to your language.<br />
<br />
- copy the subdirectory structure news/en/ to news/xx/ and, if you want, translate the news. (you can delete all news that you will not translate. the script will use the original news of /news/en then)<br />
<br />
- you may add a signature to includes/signatures.inc and use it for news you create.<br />
<br />
3. Look into other pages to see what needs to be done to translate them. (in general you need to create an inclusion file)<br />
Files you need to translate: (at least you must create a copy for your language, or those pages will fail to open)<br />
discussion-en.inc<br />
download-en.inc<br />
mailing_lists-en.inc<br />
report_bugs-en.inc<br />
submit2webmaster-en.inc<br />
submit2webmaster-en-form.inc<br />
doc/index-en.inc<br />
status/index-en.inc<br />
<br />
You also may translate news, screenshot comments and status files.<br />
<br />
Note: The tutorial translations in the doc/ directory are handled<br />
separately from the website translation. These are the files in<br />
inkscape_web/doc/*/ that have .XX.html extensions. You do not need<br />
to do anything about these pages.<br />
<br />
Note: The translation of doxygen, wiki, and the various SF pages<br />
are separate from the website translation. You do not need to do<br />
anything about these pages.<br />
<br />
5. Add a news item to the index page announcing your translation. You are encouraged to write it in both English and your native language. Use UTF-8 character set (or character entities if you prefer).<br />
You do this by adding a file like /news/en/200x/xx/0xx.inc and write your announcement.<br />
<br />
<br />
IMPORTANT: all files you change MUST be UTF-8 encoded!!! <br />
else, you will get broken output.<br />
See UT-8 note below, please.<br />
<br />
Note: Even if the announcement does not need to be translated, <br />
you should copy it to your languages folder also.<br />
Reason: Same news must have same file names. If your announcement <br />
is 010.inc, and then the next news is 011.inc, if you translate <br />
that news only, your announcement will no more be shown. This is <br />
because if you have 11 localized news and there are 12 in /en/, <br />
the 11th will be shown in english. Now, if the 11th file in your <br />
folder is the translation of the 12th file in /en/, it will be <br />
displayed wrong<br />
<br />
6. If you have CVS access, then commit your changes to the site. See the Website Editing and Working With CVS documentation for directions.<br />
<br />
If you do not have CVS access, then show your translation to one of the Inkscape administrators for review. They will then give you access to CVS and the website, so you can deploy your changes.<br />
<br />
== There are no UTF-8 entities !!! ==<br />
<br />
As different people have talked about UTF-8 entities, this should be clarified: THERE IS NO SUCH THING!<br />
<br />
An accented letter can be stored as:<br />
<br />
* a "HTML entity": <pre> &amp; (& a m p ;) --- ř (& # 3 4 5 ;) --- &Auml; (& A u m l ;)</pre><br />
* "character stored as UTF-8": & ř Ä<br />
* (and a multitude of other conflicting standards, which the above two were designed to make obsolete).<br />
<br />
HTML entities are a (somewhat) human readable transliteration.<br />
The cool thing about HTML entities is that you don't need to care about encoding with them, as only the lower 128 of 256 ASCII characters are used to describe characters that normally are in the upper 128 or even don't exist in ASCII. The upper 128 are different (for example, in Windows codepages); at least, they are system-dependent.<br />
<br />
Now, if we talk about UTF-8, this is an encoding! And it's one for UNIcode. The 8 means, that the most important characters need 8 bits (in particular, the lower 128 are the same as ASCII). All the other UNIcode characters are stored using 2, 3, or 4 bytes. And if your editor is not capable of UTF-8, youll see a mess instead of special characters like äüößéńí etc.<br />
<br />
So, if you edit existing pages, you need to have an UTF-8 capable editor. (Kate is capable, but you might need to check the encoding in the extras menu.)<br />
<br />
<strong>Please use UTF-8 encoding!</strong><br />
<strong>Please do not use HTML-entities!</strong> We should all use the same system. If you have questions about this, please ask.<br />
<br />
Reference: HTML Entities: http://www.w3schools.com/tags/ref_entities.asp<br />
<br />
== See also ==<br />
<br />
* [[WebSiteTranslation]]<br />
<br />
[[Category:Help Wanted]]</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=Tricks_and_tips&diff=8274Tricks and tips2006-09-05T14:41:24Z<p>DavidCary: how do you switch languages?</p>
<hr />
<div>== Generic tricks and tips ==<br />
<br />
The tips and tricks are collected to share/tutorials/tipsandtricks.svg and made apart of the release. If you want to contribute further, please add your tips and tricks to the SVN copy of the aforementioned. Also, you can add them below and they will be collected from time to time as a part of that tutorial.<br />
<br />
----<br />
<br />
== New Tips and Tricks Scratchpad ==<br />
<br />
Please enter your new tips and tricks here...<br />
<br />
== changing languages ==<br />
<br />
Remember when you first installed inkscape, and there were a bunch of language options?<br />
To switch to Espanol, select ...<br />
<br />
== Adjusting the Canvas Size to Fit Your Image ==<br />
<br />
So, you've done a bunch of drawing, and now the canvas is too big/small.<br />
<br />
* File->Document Preferences<br />
<br />
:* Check "Show canvas border" if not already checked, just to get some feedback.<br />
<br />
:* Set Canvas size to "Custom".<br />
<br />
* Back in the Document window drop-down select box to the right of the height/width boxes, set the units to the same units as shown in the Document Preferences window.<br />
<br />
:* Edit->Select All in All Layers<br />
<br />
* Copy the Width and Height now shown in the Document window into the Width and Height of the Document Preferences window. Press the enter key after changing each number.<br />
<br />
* Back in the Document window change the X and Y coordinates, both, to 0. Again, press the enter key after changing each number.<br />
<br />
* Clean up after yourself:<br />
<br />
:* Edit->Deselect<br />
<br />
:* Close Document Preferences window<br />
<br />
Note: Starting with version 0.44, you can use instead the button "Fit Page to Selection" under File>Document Properties. If nothing is selected then the page is adjusted to the whole drawing.<br />
<br />
== Position guides ==<br />
Position a guide roughly, then double click it to bring up a dialog box in which you can enter the desired position. --[[User:Pbhj|Pbhj]] 13:00, 1 July 2006 (PDT)<br />
* ''AFAIK you can't do this any other way ... I've been using Inkscape since not long after the split from sodipodi and I just today (1st July 06) found this out! Super! This was in the AI users tips.''<br />
<br />
==Adding fill to Shapes drawn with the Calligraphic Pen tool ==<br />
<br />
Quick tut on how to add fill to shapes you've drawn with the calligraphic pen.<br />
Please reupload tut on this topic --[[User:GigaClon|GigaClon]] 20:42, 19 June 2006 (PDT)<br />
<br />
== Printing or Producing PDFs in ISO A4 rather than US Specific Letter Paper ==<br />
<br />
I've been messing with this for ages, and as it turns out it's got a very simple solution (much easier than emailing your SVG to a friend with Illustrator ;-).<br />
<br />
With Inkscape 0.42, if you create an A4 canvas and print it, it will quite happily print properly on an A4 printer. It'll even produce suitable PostScript too. However, if you produce a PDF (either by Save As... or by using the command line ps2pdf or by using Adobe Acrobat) you'll always get a US Letter PDF. I think this is because the PostScript doesn't mandate A4 or suggests Letter, after all, most .ps files will convert perfectly like this. However, you can force ps2pdf to use A4, although sadly not in Inkscape. Do it on the command line after printing PostScript to a file:<br />
<br />
ps2pdf -sPAPERSIZE=a4 myfile.ps<br />
<br />
(it'll produce myfile.pdf, which should be an A4 PDF rather than the default Letter).<br />
<br />
Hopefully one day, Inkscape will have a dialogue asking you what paper size you'd like when it produced PDFs (much like saving .eps asks you a couple of things). After all, Inkscape just uses ps2pdf to produce PDFs anyway, so it ought to be able to pass in the paper size specification when it does so.<br />
<br />
[http://www.coofercat.com/wiki/InkScape ...Coofer Cat]<br />
<br />
== Mirror modelling ==<br />
<br />
Inkscape is a drawing application, not CAD, so maybe the word "modelling" is not appropriate.<br />
<br />
http://khiraly.4242.hu/tmp/mirrorModellingDone.png<br />
<br />
If you want to play with the image, the inkscape source available [http://khiraly.4242.hu/tmp/mirrorModelling.tar.gz here].<br />
<br />
== How to make an edge ==<br />
<br />
http://khiraly.4242.hu/tmp/joinTwoNodes.png<br />
<br />
Source is [http://khiraly.4242.hu/tmp/joinTwoNodes.tar.gz here].<br />
<br />
Comment : <br />
# This doesn't explain anything to me. HOW do you break apart a node? HOW do you join two nodes? I see steps I through III, but those little graphics don't explain how to do it.<br />
# I think this is trying to explain how to [apparently] join something to a closed loop; I'd like to see n-way nodes for this (is that in the spec?). What they are doing is taking a node on that loop and making it in to two nodes in the same place using -0-0- (that's my ASCII art for the node duplicate icon! it's on the menu bar when you are using the node edit tool on a path). Then we split using -0 0-. Then join one of the coincidental nodes to the other shape. It now looks like you have a spur off from your closed loop. But you don't. Is that it, do I get a cookie?? --[[User:Pbhj|Pbhj]] 15:08, 7 July 2006 (PDT)<br />
<br />
== How to rotate and duplicate == <br />
<br />
Need more appropriate name, like: how to make a swatch.<br />
<br />
Not finished yet.<br />
<br />
[[Khiraly]] - Feel free to comment on tips, if its not clear. Any comment are useful.<br />
<br />
[[Category:User Documentation]]</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=User_manual_information&diff=8272User manual information2006-09-05T14:39:11Z<p>DavidCary: gather "translations" under one heading</p>
<hr />
<div>This is mainly a scratchpad to begin working out the [[UserManual]]. We can post ideas and fragments of text up here, but the real deal will be in CVS so that it can be checked out and worked on.<br />
<br />
Other manuals and tutorials are [http://inkscape.org/cgi-bin/wiki.pl?OtherProjects#outsidetut listed here].<br />
<br />
: Why not write the manual here? Use wiki as a versioning & collaboration tool -- that's what it's for :) You can then use a script to turn raw wiki pages into whatever format you need for the distribution<br />
<br />
* [[VectorAndBitmap]]<br />
* [[IllustratorUsers|Inkscape for Illustrator Converts]]<br />
* [[TricksAndTips]]<br />
* [[KeyboardShortcuts]]<br />
* [[InkscapeColor]]<br />
<br />
We need to work now on an update of this Manual and have a specific version for Inkscape.<br />
<br />
* Queries about Manual can be added here or sent to cedric@le-radar.com<br />
<br />
== Translations of the manual ==<br />
<br />
<br />
Currently in CVS there is a manual (or beginnings of a manual) that was written in French for SodiPodi. Has anyone looked at it? What are your thoughts?<br />
<br />
<br />
[http://inkscape.org/doc/ Manuals are available in many languages]:<br />
english<br />
English,<br />
deutsch<br />
German,<br />
français<br />
French,<br />
Italian,<br />
espanol<br />
Spanish,<br />
Nynorsk<br />
Norwegian,<br />
and<br />
Japanese.<br />
<br />
* [http://wiki.inkscape-forum.de/handbuch German] already started by [[User:Fzap]]<br />
<br />
== Inkscape tutorial paginated for printing == <br />
<br />
In SVG, each page is a layer. Make one page visible and others invisible. (The Wiki would not accept the PDF because the files are too big.)<br />
<br />
These tutorials were adapted from Inkscape 0.41.<br />
<br />
* upload:inkscape-tutorial-basic.svgz <br />
* upload:inkscape-tutorial-shapes.svgz<br />
<br />
<br />
<br />
== Where can I find the latest update? ==<br />
* If you want to contribute, download the USER_MANUAL part of SVN (http://svn.sourceforge.net/viewcvs.cgi/inkscape/user_manual/trunk/)<br />
* If you just want to browse to find a subject, you can go to http://www.le-radar.com/?mm/inkscape_inkscape.rss and choose your language. It is the most up2date.<br />
* An alternative, in-progress, unofficial version can be found at http://www.angelfire.com/mi/kevincharles/inkscape/<br />
<br />
== How to Help ==<br />
<br />
* Adding new information to the manual : write your files in docbook or in plain text that we'll convert (please follow [[Manualguidelines.html|guidelines]])<br />
* translating pages<br />
* contact a contributor or add your name in the follow list and have a look at the [[Manualwip.Html|WIP]]<br />
<br />
<br />
* If you want to contribute, download the USER_MANUAL part of SVN<br />
* To view actual state in html, type "make your_language" (notice that xsltproc is needed). If nothing is generated, it is that your language is actually not added to the manual. Thanks to begin one, ad become responsible for this part ;)<br />
* edit the trunk/xml/inkscapeUTF.xml file. All languages are inside.<br />
* Just read the file, choose the language reference you want to use (en, fr...) and translate by duplicating the node and changing lang attribute to yours.<br />
* For pictures, you may use the "images/sshot_yourlanguage" directory or create it if necessary".<br />
* when finishing editing, if necessary edit the Makefile and add your language to the Makefile. In every case test your file with some tools (xmllint...) or just type again "make your_language" : syntax errors will be displayed : please correct them.<br />
* svn commit<br />
<br />
== FAQ ==<br />
'''Why is there only one xml file?'''<br />
The single XML file has now been split into language-specific versions, please only edit these.<br />
<br />
'''How can I produce HTML output from the XML file?'''<br />
Type "make your_language" to have truncated html file (one file per sect1), or "make singleYour_language" to have all the manual in one html file.<br />
<br />
'''Can I export to PDF?'''<br />
Yes. Make a single HTML file as described above and run "make pdfYour_language". This depends on htmldoc. If anyone wants to work on a different XSL stylesheet that produce language specific XML file and use db2pdf, it is welcome.<br />
<br />
== Misc ==<br />
* automated screenshot taking: maybe via [http://people.redhat.com/zcerza/dogtail/ Dogtail] (see [http://www.redhat.com/magazine/020jun06/features/dogtail/] and [http://www.redhat.com/magazine/021jul06/features/dogtail/]) or [http://ldtp.freedesktop.org/ LDTP]?<br />
<br />
The [http://inkscape.org/doc/inkscape-man.html Inscape "man page"].<br />
<br />
== People ==<br />
'''[[User:Cedric|Cedric Gemy]]''' - main contributor - ''cedric at le-radar.com''<br />
<br />
'''John''' - Author and French/British translation <br />
<br />
'''Ernesto''' - Spanish translation - ''celise at prodigy.net.mx''<br />
<br />
'''Antonio''' - Italian translation - ''antonio.angelo at poste.it''<br />
<br />
'''Bryce''' - English translation/editing - ''bryce at bryceharrington.com''<br />
<br />
'''Kevin''' - English translation/editing - ''inkscape.docs at wixsonit.com''<br />
<br />
'''[[User:Colin Marquardt|Colin Marquardt]]''' - volunteer for a German translation from English, help with xml2po if needed. Especially interested in [[Embedded_Help]].<br />
<br />
'''[[User:vonHalenbach|vonHalenbach-de]]''' - volunteer for a translation of pygmees manual from English to the german language.<br />
<br />
[[Category:User Documentation]]<br />
[[Category:Needs Work]]</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=Inkscape&diff=8268Inkscape2006-09-05T14:09:32Z<p>DavidCary: revert spam</p>
<hr />
<div>This is a freeform area for Inkscape development and discussion. <br />
Curious about [[WikiSyntax]]?<br />
<br />
Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf Deutsch]]...<br />
<br />
<table cellspacing="11" width="100%"><tr valign="top"><br />
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF"><br />
=== About Inkscape ===<br />
* [http://www.inkscape.org/ Inkscape Homepage]<br />
* [[About Inkscape]]<br />
* [[InkscapeFeatures]]<br />
* [[FAQ]] - Frequently Asked Questions<br />
* [[ProjectInfo]]<br />
* [[SupportedOperatingSystems]]<br />
* [[Tools]] - Supporting Tools and Applications<br />
* [[Galleries]]<br />
* [[ArticlesAndPresentations]]<br />
* [[TestimonialComments]]<br />
* [[InkscapePopularity]]<br />
* [[ContactInfo]] our heroes<br />
<br />
</td><td style="width:33%;;background-color: #FFF1EF; padding:.5em; border: 1px solid #FFC7BF;margin:.5em"><br />
<br />
=== User Documentation ===<br />
* [[InstallHelp]]<br />
* [[InkscapeTerminology]]<br />
* [[UserManual]]<br />
* [http://inkscape.org/doc/ Tutorials]<br />
* [[InkscapeSVG|Inkscape SVG vs. Plain SVG]]<br />
* [[GettingExtensionsWorking]]<br />
* [[GettingEffectsWorking]]<br />
* [[WhatEffectsDo]]<br />
* [[UsingTheConnectorTool]]<br />
* [[Installing Fonts as a User]]<br />
* [[EmergencySave]]<br />
* [[ReleaseNotes045|Release Notes]] for 0.45 (unstable)<br />
* [[ReleaseNotes044|Release Notes]] for 0.44 and past<br />
* [[Announcing Releases]] for 0.44 and past<br />
* [[ArticleIntroducingInkscape0_40|Introducing Inkscape 0.40]]<br />
* [[TricksAndTips]]<br />
</td><td style="width:33%;background-color: #FFFAE5; padding:.5em; border: 1px solid #FFFF66; margin:.5em"><br />
<br />
=== Help Inkscape Without Coding === <br />
<br />
* [[PrintingConsensusPoll]]<br />
* [[HelpWanted]]<br />
* [[CreatingDists]]: how to build packages<br />
* [[WebsiteEditing]]<br />
* [[UpdatingTrackerItems]]<br />
* [[TutorialIdeas]]<br />
* [[How_To_Start_A_Page]] how to use the wiki<br />
* [[TestingInkscape]]<br />
<br />
</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAE5; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px"><br />
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em"><br />
<br />
=== Developer Documentation ===<br />
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em"><br />
==== General ====<br />
* [[DeveloperManual]]<br />
* [[CompilingInkscape]]<br />
* [[WorkingWithSVN]]<br />
* [[HandlingPreferences]]: creating and using preference values<br />
* [[AddSPObject]]: how to add a new SPObject type<br />
* [[ReprListeners]]: responding to XML doc changes<br />
* [[ErrorsAndWarnings]]: how to deal with reporting errors, warnings, and other messages<br />
* [[DebuggingTips]]: random tips to help debug problems<br />
<br />
* [[DeveloperTitles]]: terms for various roles in Inkscape<br />
* [[InkscapeJanitors]]: small tasks that need doing<br />
* [http://livarot.sourceforge.net/ Livarot]: for boolean ops<br />
* [[ExtensionAttributes]]: currently defined attributes in Inkscape's XML namespace and what they do<br />
* [[MakingAnExtension]]: how extension must work and how to write an INX file<br />
* [[ExtensionsRepository]]: an Internet central for Inkscape Extensions<br />
* [[OtherProjects]] (outside links)<br />
<br />
</td><td style="width:50%;padding:.5em"><br />
<br />
==== Development Discussion ====<br />
* [[Roadmap]]: the main todo list<br />
* [[NewFeatureProposals]]<br />
* [[ExtensionArchitectureProposals]]<br />
* [[Coding Style|Coding Style Discussion]]<br />
* [[FileTypes]]<br />
* [[ApplicationIcons]] ( Application + Interface )<br />
* [[InkscapeColor]]<br />
* [[PrintingSubsystem]]<br />
* [[SVG Competitors Plan]] - MS WVG vs SVG, etc<br />
* [[SVG Tiny Compliance]]<br />
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite<br />
* [[CSS Support]]<br />
* [[OpenVG]] Standard (draft)<br />
* [[OpenDocument proposal]]<br />
* [[Googles Summer Of Code]]<br />
* [[UI MockupScreenshots]]<br />
* [[lib2geom]]<br />
<br />
</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em"><br />
<br />
==== User Interface Discussion ====<br />
* [[Translation_information]]<br />
* [[AccessibleGraphics]]<br />
* [[ObjectManager]]<br />
* [[DialogsReorganization]]<br />
* [[DialogReplacement]]<br />
* [[ModalInterfaces]]<br />
* [[TextUsability]]: text tool /dialog dialog<br />
* [[KeyboardShortcutsToDo]]<br />
** [[KeyboardProfiles]]: how you can help <br />
* [[StatusbarAPI]]<br />
* [[Animation-(Timeline)]]<br />
* [[Free Desktop Graphic Suite]]<br />
<br />
</td><td style="width:50%;padding:.5em"><br />
==== Rearchitecture Discussion ====<br />
* [[SubsystemRearchitecture]]<br />
* [[GtkMMification]]: replace C boilerplate with gtkmm objects<br />
* [[PathRepresentation]]<br />
* [[Cairoification]]<br />
* [[ScribusInteroperability]]<br />
<br />
</td></tr></table><br />
<br />
----<br />
* [[WikiAttic]]: pages that are no longer relevant but kept for historical value<br />
<br />
__NOTOC__<br />
<br />
[[Category:About Inkscape]]<br />
[[Category:User Documentation]]</div>DavidCaryhttps://wiki.inkscape.org/wiki/index.php?title=TufteStylePresentation&diff=5147TufteStylePresentation2005-10-07T03:10:40Z<p>DavidCary: revert</p>
<hr />
<div>= Edward Tufte Style Presentation of Inkscape Overview =<br />
<br />
All slides for this type of presentation are in share/examples/presentation/, included in the latest CVS copies of Inkscape. Please edit/add/change them to fit your need and commit upgrades to the content of each slide.<br />
<br />
=== 1. Introduction ===<br />
<br />
This chart shows three stunning screenshots of Inkscape displaying some of the incredible variety of graphics <br />
that Inkscape can make. In stylistic, artistic lettering the chart reads, "Inkscape is a Scalable Vector Graphics<br />
program written in Open Source C++ that runs on Linux, UNIX, Mac OS X, and Windows."<br />
<br />
At the bottom of the page is a timeline showing how the codebase has evolved from its Gill and Sodipodi<br />
origins, with graphical indication of quantity of people involved in development up to today.<br />
<br />
=== 2. Scalable Vector Graphics (SVG) ===<br />
<br />
This slide compares vector graphics to raster. The left side shows the source format, the right shows images, with vector on the<br />
top and raster on the bottom. Both images include a "zoomed in" highlight that emphasizes the pixilated nature of raster images<br />
vs. the perfect scalability of SVG. Show XML syntax of SVG with example of the square.<br />
<br />
<br />
=== 3. Open Source ===<br />
<br />
* Open Source means:<br />
** The source code is available for free to the whole world<br />
** The development process is open to all to participate in and enjoy<br />
<br />
In faint text in the margins around the page are some of the open source mantras, like "With enough eyes, all bugs are shallow,"<br />
"Patch first, discuss later", "Release Early, Release Often," "KISS," "SPOT."<br />
<br />
<br />
=== 4. Uses of Inkscape: Vector Graphics / Vector Aesthetics ===<br />
Show several specific examples of this type of drawing<br />
* Vectoralized photos<br />
* Cartoons<br />
* typography<br />
* tattoos<br />
<br />
=== 5. Uses of Inkscape: Symbology + Signage ===<br />
Show several specific examples of this type of drawing<br />
* Logos<br />
* Flags<br />
* Street Signs<br />
<br />
=== 6. Uses of Inkscape: Web Graphics ===<br />
Show several specific examples of this type of drawing<br />
<br />
=== 7. Uses of Inkscape: Technical Graphics ===<br />
Show several specific examples of this type of drawing<br />
* Visually Attractive Maps<br />
* Diagrams<br />
* Technical Drawings<br />
<br />
=== 8. Why is Inkscape important? ===<br />
* In order to discuss this, one must define the community to which this is important.<br />
* GNOME/OSS<br />
** A production ready vector-software does not exist in the GNU/Linux world.<br />
** As most ppl would be concerned, this type of tool doesn't exist!<br />
* Art Community<br />
** It is free.<br />
** It is high quality and production ready!<br />
** Supports positive ideals!<br />
*** Copyright is what it is, but we would like to see more opened up tools and codebases. Promotes development and honesty.<br />
* Scientific Community<br />
** Visualizations<br />
** equations<br />
<br />
=== 9. Development Community/Process ===<br />
<br />
Show graphs of activity based on the Inkscape Status metrics and screenshots of Wiki, the Mailing List archives, Jabber, and the Bug Tracker. In a corner include the text: "Inkscape is a collaborative open source project involving dozens of developers from all over the world, that embodies the Best Practices of the open source development process."<br />
<br />
Maybe include something that puts the viewer "in the picture", like a web/network of people, with "YOU" as a node being added to the edge.<br />
<br />
<br />
=== 10. Common Misconceptions (Low Hanging Fruit) ===<br />
<br />
* Isn't this just an open source Illustrator?<br />
* Isn't there X, Y, and Z projects that already do this?<br />
* Open Source doesn't innovate, it only imitates.<br />
<br />
=== 11. Future ===<br />
<br />
* extension system<br />
** quicker development<br />
** don't have to know as much about the internals<br />
* networked editing (shared space)<br />
* XMP Metadata Integration<br />
* layers<br />
* clipart.freedesktop.org<br />
<br />
=== 12. Conclusion ===<br />
<br />
* Can use your help!<br />
** Testing<br />
** Join as a Developer!<br />
<br />
<br />
<br />
--<br />
I cannot find this presentation in the cvs!?</div>DavidCary