Inkscape Wiki - User contributions [en]

AccessibleGraphics

2006-02-09T07:52:25Z

Eloquence: AccessibleGraphics moved to Accessible graphics: more CamelCase title-fixing

#redirect [[Accessible graphics]]

Accessible Graphics

2006-02-09T07:52:25Z

Eloquence: AccessibleGraphics moved to Accessible graphics

What makes Inkscape the ideal tool for creating accessible SVG?

=== background links ===

* inkscape [https://sourceforge.net/tracker/index.php?func=detail&aid=993367&group_id=93438&atid=604309 rfe]
* a [http://www.peepo.co.uk/pmwiki/pmwiki.php/Main/SVG rant] on SVG and Accessibility given at the latest London SVGUG meeting with plenty of links. some concepts were [[http://interactive-kiosks.blogspot.com/ | helpful kiosk sites]] addressed and alpha proof of concept code developed.
*Links to primary [http://www.learningdifferently.com/develop/svg.html documentation] on creating accessible SVG
doing better

AdobeIllustrator10

2006-02-09T07:52:05Z

Eloquence: proper redirect

#REDIRECT [[Adobe Illustrator]]

AdobeIllustrator

2006-02-09T07:51:40Z

Eloquence: AdobeIllustrator moved to Adobe Illustrator

#redirect [[Adobe Illustrator]]

Adobe Illustrator

2006-02-09T07:51:40Z

Eloquence: AdobeIllustrator moved to Adobe Illustrator

Please post links to screenshots and/or insights of this vector graphics application.
We must learn from strengths and mistakes of others.

Adobe Illustrator is one of the most commercially successful vector graphics applications among artists and graphic designers, with [[MacromediaFreehand]] as the main competitor and probably [[CorelDraw]] coming in a third place. (Adobe has since bought Macromedia and it will be interesting to see which Macromedia products will survive.) However, the relative strength of various vector editors depends on the market; for example in Russia and some other markets in Europe, [[CorelDraw]] is more common than Illustrator.

=== Sample Files ===

* [http://rejon.org/projects/inkscape/index.php Versions of Illustrato 3 - 10 files converted from Open Clip Art Library graphics]
* [http://turnipspatch.com/demos/inkscape/illustrator-samples/ Jon Leighton's samples]

=== Screenshots ===

* [http://cabbage.ucsd.edu/~phillipsjd/media/adobeIllustrator10-win32/ Adobe Illustrator 10 win32 Screenshots]

* [http://www.maths.tcd.ie/~horkana/inkscape/illustrator/Adobe-Illustrator-CS/ Adobe Illustrator CS]

=== Links ===

* [http://www.adobe.com/products/illustrator/ Adobe Illustrator Official Site]
* [http://en.wikipedia.org/wiki/Adobe_Illustrator Adobe Illustrator at Wikipedia]

Useful [http://web.syr.edu/~tatoland/illustrator/aimenus.html Introduction to Adobe Illustrator] including screenshots of the menus which I found very useful for reference.

=== License ===

Commercial Proprietary Software.
Retails for roughly $500 USD alone but also available as part of the Adobe Creative Suite.

Although Adobe Photoshop Elements provides a budget alternative to the full price Adobe Photoshop, Adobe makes no attempt to provide any such cut price alternative to Illustrator.

All trademarks and copyrights are the property of their respective owners and used here only for review purposes.

AnnouncingReleases

2006-02-09T07:51:11Z

Eloquence: AnnouncingReleases moved to Announcing releases: more CamelCase title-fixing

#redirect [[Announcing releases]]

Announcing Releases

2006-02-09T07:51:11Z

Eloquence: AnnouncingReleases moved to Announcing releases

== Release Announcements (Informal) ==

* [[ReleaseAnnounce043]]
* [[ReleaseAnnounce042]]
* [[ReleaseAnnounce041]]
* [[ReleaseAnnounce040]]
* [[ReleaseAnnounce039]]
* [[ReleaseAnnounce038]]

== Press Releases (Formal) ==

* [[PressRelease043]]
* [[PressRelease042]]
* [[PressRelease041]]
* [[ArticleIntroducingInkscape0_40]]

* [http://www.stetson.edu/~rhansen/prguide.html guide to writing successful pr]
----

== Places to Announce ==
In general, for linux community receives a general informal announcement. However, for formal press channels we use the more formal 3rd-person press release.

=== Open Source Community (Receive Informal PR) ===

* gnome-office-list@gnome.org
* svg-developers@yahoo.com - must join the list to send (rejon is on)
* SVG.org: antoine@graougraou.com
* svgfaq.org - maxdunn@siliconpublishing.com
* svgfoundation.org - michael (at) svgfoundation.org
* cairo list - cairo@cairographics.org
* gnome-list - gnome-announce-list@gnome.org
* Scribus List (mrdocs) - scribus@nashi.altmuehlnet.de
* osnews.com - http://osnews.com/submit.php
* [[LWN Submission Guide]]
* [http://www.w3.org/Graphics/SVG/SVG-Implementations [[W3C]] SVG Implementations] - chris@w3.org
* newstips@heise.de
* http://slashdot.org/submit.pl
* mozilla svg project
* submit if you have an account: http://svg.org/submitstory/Diary
* http://www.desktoplinux.com/ - http://www.desktoplinux.com/cgi-bin/news_post.cgi
* http://www.svg-cafe.com/ - join and post to news section
* [http://freshmeat.net/ Freshmeat]
* [http://gnomedesktop.org/node/add/story gnome footnotes]
* [http://www.scale-a-vector.de/cont.htm scale-a-vector] - kukofka@scale-a-vector.de

* Art sites
** clipart-list - clipart@freedesktop.org
** [http://www.deviantart.com/ [[DeviantART]]]

* kde sites
** http://dot.kde.org
** http://kde-look.org
** http://kde-artists.org
PR: theobroma@revelinux.com

=== Formal PR Contacts ===

* [http://www.prweb.com/ prweb] - has free pr distribution, but you need to do 2 days in advance unless contribution of $10 or more
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* arts sites? <-- continue looking these up!!!
* news site
* need more magazines
* need more press outlets

=== Magazines (Get formal PR) ===

* I've requested where to send PR and how to get our software reviewed from these magazines.

* http://linuxformat.co.uk/ - webmaster@linuxformat.co.uk
** PR: login and submit news via top of page link
* http://linux-magazine.com/ - info@linux-magazine.com edit@linux-magazine.com
** PR: pr@linux-magazine.com
** Product Reviews: coming soon
* http://linuxjournal.com/ - ljeditor@ssc.com
** PR: newproducts@ssc.com
** Product Reviews: Heather Mead, heather@ssc.com, http://www.linuxjournal.com/xstatic/advertising/prodreviews
* http://linuxmagazine.com/ - editors@linux-mag.com
** PR: ???
** Product Reviews:
* http://linuxuser.co.uk - http://linuxuser.co.uk/index.php?option=com_content&task=view&id=48&Itemid=40
** PR: terry@linuxuser.co.uk
** Product Reviews: martin@linuxuser.co.uk
* http://www.tuxmagazine.com/ - editor@tuxmagazine.com
** PR: ???
** Product Reviews: http://www.tuxmagazine.com/xstatic/advertising/prodreviews
* http://www.linuxworld.com/ - mrhinkle@linuxworld.com tim@linuxworld.com

* http://cmykmag.com/
* http://www.computerarts.co.uk/
** http://www.computerarts.co.uk/contacts
** PR & Product Reviews: dom.hall@futurenet.co.uk
** Gallery and Exposure: richard.llewellyn@futurenet.co.uk
* http://www.layersmagazine.com/

* http://graphicdesign.about.com
* http://graphicssoft.about.com
* http://desktoppublishing.about.com

=== Other Updates ===
* http://en.wikipedia.org/wiki/Inkscape Update the 'Features', 'Interface and usability', & 'Versions'

UnterstuetzteBetriebssysteme

2006-02-09T07:50:52Z

Eloquence: UnterstuetzteBetriebssysteme moved to Unterstützte Betriebssysteme: more CamelCase title-fixing; MediaWiki is fully UTF-8 enabled so umlauts should not be a problem

#redirect [[Unterstützte Betriebssysteme]]

Unterstützte Betriebssysteme

2006-02-09T07:50:52Z

Eloquence: UnterstuetzteBetriebssysteme moved to Unterstützte Betriebssysteme

Inkscape unterstützt die folgenden Betriebssysteme:

=== [http://inkscape.org/download.php Offizielle, herunterladbare Pakete] ===
* Linux
* Windows 95, 98, 98SE, Me, NT, 2000, XP
* Mac OS X (ab [http://prdownloads.sourceforge.net/inkscape/Inkscape-0.42-0.dmg?download Version 0.42])

Falls Ihr Betriebssystem noch nicht in der Liste enthalten ist, können Sie mithelfen, indem Sie Ihr eigenes [[CreatingDists|Paket erstellen]] oder [[CompilingInkscape|Inkscape selbst kompilieren]].

About Inkscape

2006-02-09T07:50:25Z

Eloquence: AboutInkscape moved to About Inkscape

Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, [[PostScript]], JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.

For some great examples of what Inkscape can do, see the [[Galleries|galleries]]. Or why not jump right in, [http://www.inkscape.org/download.php grab a copy], then try the [http://inkscape.org/doc/basic/tutorial-basic.html tutorial]!

To understand more about what Inkscape can do for you, view the [[InkscapeFeatures|feature list]], [[ProjectInfo|project information]], and a few users'

=== German ===

Inkscape ist ein kostenloses, open source, vektororientiertes Zeichenprogramm (SVG). Es ist vergleichbar mir Illustrator, Freehand und [[CorelDraw]]. Es werden viele SVG features unterstützt (Standardformen, Pfade, Text, Alpha, Transformationen, Gradienten und Gruppierung). Inkscape kann verschiedene Formate importieren (z.B. EPS, Postscript, JPEG, PNG, BMP,TIFF). Es exportiert PNG und verschiedene andere vektororientierte Grafikformate.

User:Eloquence

2006-02-09T07:48:38Z

Eloquence:

See my [http://meta.wikimedia.org/wiki/User:Eloquence Wikimedia user page].

TranslationInformation

2006-02-09T07:48:27Z

Eloquence: TranslationInformation moved to Translation information: more CamelCase title-fixing; note that MediaWiki is case-sensitive

#redirect [[Translation information]]

Translation information

2006-02-09T07:48:27Z

Eloquence: TranslationInformation moved to Translation information

= Tutorial translations =

Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:

http://cvs.sourceforge.net/viewcvs.py/inkscape/doc-docbook/

Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.

* If there's already such a file in CVS, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.

* When finished, run <a href="http://xmlsoft.org/xmllint.html">xmllint</a> on your file to make sure it's well-formed.

* Send the file to buliabyak at gmail dot com, and I'll convert it to SVG and HTML and upload it to CVS and the web site.

* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.

= Interface translations =

If you're interested in helping with providing interface translation for Inkscape,
here are a few links to help you getting started:

http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html
http://developer.gnome.org/projects/gtp/l10n-guide/
http://developer.gnome.org/projects/gtp/style-guides/
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

If a .po file for your language does not yet exist, then create one
by copying the inkscape.pot file that gets generated when you run make
in the codebase.

Edit the file to add or correct translations of the English strings, and
then upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):

1. update your local copy of Inkscape in the usual way: "svn update"
2. "./autogen.sh"
3. "./configure"
4. enter the "po" directory: "cd po"
5. generate the current PO template: "intltool-update --pot"
6. merge your existing translations into the new POT file (inkscape.pot):
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* GRand Unified Translation (http://www.kvdb.net/projects/grut/)
* poEdit (http://poedit.sourceforge.net/)

== A few important things to remember ==
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Locale Testing ==
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian this is via "dpkg-reconfigure locale".) If you set the LANG variable and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):

LANG=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:

LANG=es_ES ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

PrintingConsensusPoll

2006-02-09T07:48:12Z

Eloquence: PrintingConsensusPoll moved to Printing consensus poll: more CamelCase title-fixing; note that MediaWiki is case-sensitive

#redirect [[Printing consensus poll]]

Printing consensus poll

2006-02-09T07:48:12Z

Eloquence: PrintingConsensusPoll moved to Printing consensus poll

== Problem ==

Bryce has pointed out the #1 feature need for Inkscape right now is strong support for Adobe Portable Document Format (PDF) and Postscript (PS) in his [http://sourceforge.net/mailarchive/forum.php?forum_id=36054&max_rows=25&style=flat&viewmonth=200511&viewday=30 2005.11.30 email] to the Inkscape mailing lists.
This [[ConsensusPoll]] exists to enable the community to efficiently create and commit to a plan of action to resolve this issue.

== Contract ==

* >= 20 inkscape enthusiasts
* >= 4 developers with commit access
* >= 95% yes
* all conditions in plan are met
* 72 hour GO timer
* 80% cloture

[[ContractExplanation]]

Because this contract defines what it means to participate in this poll it will never be changed. If it turns out to be inadequate, this poll must be canceled and a new poll with a new contract must be drafted.

== Yes-No Poll ==

Participation in this poll is open to anyone who wants to participate.

Voting yes in this poll means that you believe the community created plan is ready for implementation, and that you will do your part to support its execution. Voting no in this poll means that you have outstanding concerns about the community created plan. You can change your vote at any time. All votes are transparent so that those voting yes can listen to the concerns of those voting no.

No ... [[BrandonCsSanders]] - Success needs to be defined (e.g., if all 20 test cases are passed ...)
Yes... [[BryceHarrington]] - Let's do it
No ... [[AlexandreProkoudine]] - There is no plan yet
No ... [[ColinMarquardt]] - There is no plan yet
No ... [[EricWilhelm]] - The plan needs salt
No ... [[MenTaLguY]] - This isn't much of a plan...
No ... [[JonCruz]] - Plan? Not quite yet
No ... [[JonPhillips]] - no plan...
No ... [[NicuBuculei]] - so far the plan is weak
No ... [[RalfWStephan]] - Where are the test cases?
No ... [[AndyFitzsimon]] - I will also pledge $50 once someone defines how we do pledges.
No ... [[TuukkaPasanen]] - There isn't good plan yet.
No ... [[EricJonas]] - There is no plan
No ... [[AdibTaraben]] theAdib - There is no plan
No ... Martin Owens - There is a plan but it's pants.
Yes ....[[Corey Burger]] -plan, what plan?
No ... [[Gustavb]] - The plan is incomplete.

(If you are voting no because the plan is incomplete, please describe what you'd like to see added or changed.)

== Pledges ==

$50 ... [[BryceHarrington]] - I will pledge $50 once someone defines how we do pledges :-)
$50 ... [[AndyFitzsimon]] - I will also pledge $50 once someone defines how we do pledges.
€50 ... [[RalfWStephan]] - whenever the plan has succeeded
$50 ... [[BrandonCsSanders]] - once the plan is done
$100 ... [[EricJonas]] - Just let me know how to pledge

== Plan ==

# Describe the [[Current PDF Support]] and the known [[PDF bugs]]
# Identify [[Required PDF Support]]
# Assemble a few dozen examples to use as [[PDF test cases]]
# Document how each of the current [[PDF tools]] (potential starting points) performs on the suite of test cases
# Determine timeframe
## Start some time in early 2006?
## Expected completion some time in mid/late 2006?
# Select developer with the right skillset
## C[[/C]]++, XML
## PDF file format
## SVG file format
## Able to work under (U.S.) contract
## [[/Other]] skillset requirements?/
# Determine what funding is needed to enable them to complete the work
# Establish a contract with the selected developer to perform the work
# When the developer is done, verify that all test cases pass, then pay developer

== Background Information ==

* [[SOC_Original_Project_Prompts]]
* [[PrintingSubsystem]]
* [[Roadmap]] (Milestone 11) Import[[/Export]] Feature Enhancements

== Adequate Technical Solutions ==

What solutions would be fine?
* Library that integrates directly in to inkscape (and scribus, ...)
** Use [[Cairo]] as the presentation layer and use its support for pdf/ps
*** This may be a first step towards an eventual migration of the backend renderer to Cairo
** See [http://poppler.freedesktop.org/ Poppler] for PDF import.
*** [http://lists.freedesktop.org/archives/poppler/2005-June/000428.html pdftosvg 1]
*** [http://sourceforge.net/mailarchive/message.php?msg_id=14147945 pdftosvg 2]
*** [http://lists.freedesktop.org/archives/poppler/2005-December/001248.html pdftosvg 3]
** Pull out the scribus pdf support into a libpdf (libpdf name has already been used) that can be shared by both scribus and Inkscape
*** Requires conversion of Qt-isms into more neutral widgetset-independent style
* Extend an existing standalone (filter) tool that can be bundled with inkscape
** [http://scratchcomputing.com/projects/uber-converter/ Uberconverter]
** [http://www.solidcode.net/pdf2svg/ pdf2svg]
** [http://www.sodipodi.com/index.php3?section=download/tools ill2svg]
** [http://www.xs4all.nl/~hanwen/public/software/ai2svg.py ai2svg]
** [http://www.accesspdf.com/pdftk/ pdftk]

== Possible Strategies ==

* Raise money and hire a developer to implement it
** Collect pledges, once we are over threshold collect funds (http://fundable.org/)
*** What should the threshhold be? $2000? $5000?
*** Still too early to decide what the threshold should be. We need to know how much it will cost first.
*** Fundable now charges a 10% fee from the amount collected
** Need to decide what the funds would be spent on ahead of time
*** 10-20% - Tester to collect test cases and put together a test suite for developer to use
*** 70-80% - Developer to write the code, document it, and make it pass the tests
*** 5-10% - Liaison to handle the paperwork, collect/distribute funds, track/report progress, and verify the work has been completed adequately
** Mercenaries that would do this for us?

*** [[BrandonCsSanders]] ... I'd do it for $2000, half up front, half once it meets spec. Caveat: it would take me six months to complete because my plate is pretty full right now and I'll be snatching a week here and a week there.
*** [[EricWilhelm]] ... This will be a lovely fit for the [[UberConverter]]. I'm guessing $5k would get it to about the same level as XAR and SVG in chromista. Caveat: Those aren't done yet. Check back in Jan. I would also be happy to oversee/direct the work of someone else wanting to write this as a pair of [[UberConverter]] connectors (crs2pdf, pdf2crs.)
*** /other mercenaries?/
* Hold a [http://www.usemod.com/cgi-bin/mb.pl?BarnRaising [[BarnRaising]]]
** at [http://RecentChangesCamp.org [[RecentChangesCamp]]] in Portland February 3-5
** other location/time?
* Wait for a volunteer to get inspired and just do it

== Questions[[/Brainstorms]] ==

* What about what inkscape earned through the Google Summer of Code? What's the status of this?
** $2000 earned; there has been no plan or consensus for what to use it for
* Does Cairo have PDF export already? What about to use cairo for just this job? and later then use cairo for the whole presentation layer? Instead of creating an interims solution?
** Yes, Cairo has PDF export capabilities; it's unknown if it's significantly better than our current (poor) pdf export functionality
** Cairo Postscript and PDF backends are still experimental and disabled by default in current stable release, but plan is to make them supported in next stable release, expected for the end of 2005. See [http://cvs.cairographics.org/*checkout*/cairo/ROADMAP Cairo ROADMAP]
** A way to test cairo capabilities would be to use librsvg HEAD. See Dom Lachowicz [http://www.advogato.org/person/cinamod/diary.html?start=91 blog entry].
* Investigate ps2ai, pstoedit and ai2svg conversion options (potential EPS support?)
* Import of native [[AdobeIllustrator]] files, which have been PDF based since Illustrator 10 (at least).
* Other [[PDF Bugs | Bugs and RFE's]] related to Import or Export?
* [[UberConverter]]

WorkingWithSVN

2006-02-09T07:47:32Z

Eloquence: WorkingWithSVN moved to Working with SVN: more CamelCase title-fixing; note that MediaWiki is case-sensitive

#redirect [[Working with SVN]]

Working with SVN

2006-02-09T07:47:32Z

Eloquence: WorkingWithSVN moved to Working with SVN

(This began a copy of [[WorkingWithCVS]]; bear with us as it is updated for SVN)

== Subversion (SVN) Basics ==

This node discusses the basics of using SVN.

For information on more advanced usage, see:

* [[WorkingWithSVNBranches]] - making branches and merging between them

=== Concepts ===

==== The Repository ====

SVN stores source code in a shared '''repository''' (in our case on Sourceforge's server). The repository contains all past and present versions of the code, and is shared by everyone.

==== Your Working Copy ====

To work with the source code, SVN requires you to '''check out''' a ''working copy''. This copy is private, so you can make and test any changes you like without disturbing anyone else.

If you have '''write access''' to the repository, when you are finished making your changes, you may '''commit''' your changes to the shared repository, making them available to everyone.

Alternately, you may generate a file containing the changes you made (a ''diff''), and send it to a developer with write access to be incorporated.

You can check out as many working copies as you want; they take up only your own disk space, and they are completely independent of each other.

If you no longer need a working copy, you may simply delete it.

=== Getting Started ===

==== Setting Up ====

==== How Do I Check Out a Working Copy? ====

To check out a copy of Inkscape from the SVN repository, you may use the following command:

svn checkout https://svn.sourceforge.net/svnroot/inkscape/inkscape/trunk inkscape

Here are what the options mean:

"checkout" ("co" means the same thing) specifies the action to take (check out a working copy).

"https://svn.sourceforge.net/svnroot/inkscape/inkscape/trunk" is a repository URL; in this case, it refers to the "main" development branch for Inkscape.

"inkscape" is the name of the directory to check out into

==== Now What? ====

You should have a complete working copy in the '''inkscape''' directory. You can cd to it and try compiling.

:Note: If it is a fresh checkout, you will need to run the ./autogen.sh shell script at the top level to create files needed to compile

When you're inside the working copy, you won't normally need to specify the repository URL, because SVN remembers where the working copy came from.

Note that a Subversion command only applies to the current directory and (possibly) any subdirectories. Normally (particularly for updates, diffs, and checkins), you will want to run the command from the top level of the project.

=== Bringing Your Working Copy Up-To-Date ===

Your working copy will not automatically include changes others have made to the repository since you checked it out.

To ''update'' your working copy, use this command:

svn update

=== Dealing with Conflicts ===

If you've made changes to your working copy, what happens if you update after someone has commited changes to the same files?

Normally, SVN can work this out on its own. Sometimes you have to help it along, though. If SVN says there were conflicts, look for which files have a ''C'' next to them in its progress output. Some of those may have unresolved conflicts. You can also search for '=======' in the files themselves to find any unresolved conflicts.

<<<<<<< ''filename''
The changes in your version will be here
=======
The changes the other person will be here
>>>>>>> ''some version here''

Sometimes you will keep one set of changes and discard the other, and sometimes you will combine the two. It will require a judgement call on your part either way. Talk to the person who made the other set of changes or ask on the mailing list if it's unclear what's going on. Remember that SVN is no substitute for communication.

Also, always make sure to build and test after an update to make sure that the combined changes work as intended!

=== Generating a Diff ===

('''Always''' update before generating a diff!)

From the top-level directory, run the command:

svn diff -x -u3 > filename

-x -u3 specifies which format to use (a unified diff with three lines of context). This is the recommended diff format.

This will create a file describing the changes you have made, though if you have created new files as part of your changes, you will need to include those separately too when emailing them to the list or another developer for inclusion.

=== Automatic Commit Diff ===

[ fixme: how to do this in SVN? ]

To always generate a diff when you commit to CVS, set the environment variable "CVSEDITOR" to the following script:

#!/bin/bash
# get rid of redhat 9 locale ugliness
unset [[LC_CTYPE]]
# Turn on ro access (to stop multiple locks) for local roots
grep @ CVS[[/Root]] >/dev/null 2>&1 || export CVSREADONLYFS=1
# Tell the user what's going on
echo Building diff...
cvs diff -up 2>/dev/null | perl -ne 'print "CVS: $_" unless /^\?/' >> "$1"
exec ${EDITOR:-vi} "$1"

If the above script is named "~/bin/cvsdiffvi", then assuming you run the bash shell, you can add the following your .bashrc file:

export CVSEDITOR=~/bin/cvsdiffvi

Now, every time you commit, the entire diff will be visible to you as you write your commit comments.

=== Applying a Diff ===

A diff file can be applied to the codebase using the 'patch' command.

If the diff was made as <code>inkscape/src/thingy.cpp</code> and you're in the "inkscape" directory, you'll want to use the command:

patch -p1 < thingy.diff

Depending on how many path elements are part of the diff, you'll need to strip them with -p1, -p2, etc.

=== Committing your Changes ===

('''Always''' update before committing!)

If you have write access to the repository, you can commit your changes like this:

Before you commit, please make sure that you describe the changes you have made in the [[ChangeLog]] file at the top-level directory.

svn commit -m "Your description of your changes goes here"

Tip: even if you are committing directly, you still might want to generate a diff. It's a good reference to look at when you're filling out the [[ChangeLog]], since it will remind you of all the changes you've made.

=== Adding Files to the Repository ===

To add new files as part of your commit, you will need to run:

svn add ''files and directories to add go here''

Before you commit. This also goes for new directories.

The actual addition or removal will not take effect until you commit.

=== Removing Files from the Repository ===

svn remove ''files to remove go here''

Inkscape Wiki:About

2006-02-09T07:46:09Z

Eloquence: repl. newbie test with hopefully accurate stub

This is a wiki for development-related information about [http://inkscape.org/ Inkscape], an open source vector graphics application.

ReleaseNotes

2006-02-09T07:40:12Z

Eloquence: ReleaseNotes moved to Release Notes: No more need for CamelCase

#redirect [[Release Notes]]

Release notes/0.44

2006-02-09T07:40:12Z

Eloquence: ReleaseNotes moved to Release Notes

= Inkscape 0.44 =

== In brief ==

Bigger and better.

== Outline mode ==

An Outline ("wireframe") display mode is implemented. Use the View > Display Mode > Outline to activate it. In this mode:

* all paths and shapes are rendered as inverse (black on light background and vice versa) outlines of constant width (1 screen pixel regardless of zoom), without fill;

* text is painted by inverse fill, without stroke;

* bitmaps are shown as is;

* any opacity and gradients are ignored.

The outline mode is usually not drastically faster than regular mode (usually 10% to 50% faster), and in some special cases it may even be slower. However, the value of the outline mode is not only in its speed; it is a good way to get an idea of the structure and objects of your document, and it is convenient for precision node editing and for finding "stray objects".

== Selected style indicator ==

A new control in the left end of the statusbar lets you quickly view and change the fill and stroke of the selected objects. When you have a text selection in Text tool or a gradient handle selected in the Gradient tool, this indicator displays and changes the style of the text fragment or gradient stop, instead of the entire object (it's the same behavior as the Fill&Stroke dialog.)

* The two indicators, labelled F: (top) and S: (bottom), display fill and stroke of the selected object(s) correspondingly. (For gradient handles, they always display the same style.)

* Each fill/stroke indicator can display either a color+opacity swatch (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a text label specifying N/A (nothing selected), None (no fill/stroke), Unset (unset fill/stroke), L Gradient, R Gradient, Pattern (corresponding fill/stroke types), or Different (selected objects have different fill/stroke types).

* Additionally, each indicator may be accompanied by one of two flags, m ("multiple", meaning there are two or more objects all with the same fill/stroke) or a ("averaged", meaning there are two or more objects with different flat colors in fill/stroke, and the indicator shows the average of these colors).

* Left-click on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab (Fill or Stroke) active.

* Right-click on an indicator opens a popup menu with the following items:
** Edit fill/stroke...: Opens or activates the Fill&Stroke dialog with the corresponding tab selected. (Same as left-click.)
** Last set color: Applies to the selected objects the fill/stroke color that was last applied to anythig.
** Last selected color: Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (Allows you to easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".)
** Invert: Sets the fill or stroke to the inverse of the current color (does not affect opacity).
** White, Black: Sets the fill or stroke to the corresponding color (fully opaque).
** Copy color, Paste color: Copies or pastes the fill or stroke color (when it's color) to/from the system clipboard, as text in the <code>#rrggbb</code> hex format.
** Swap fill and stroke: Exchanges fill and stroke (both their types and colors, if any).
** Make fill/stroke opaque: Removes fill or stroke transparency (not master transparency!).
** Unset fill/stroke: Unsets fill or stroke from selected objects.
** Remove fill/stroke: Removes fill or stroke from the selected objects.

* Middle-click on a fill/stroke indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu.

* The Stroke indicator also displays the stroke width of selection (averaged if there are multiple objects selected with different stroke widths), located to the right of the stroke color/transparency swatch. Left-clicking on it opens the Fill&Stroke dialog with the Stroke Style tab selected. Right-clicking on it opens a popup menu which allows you to choose the units for displaying the stroke width, as well as choose one of the presets to assign to selection.

* To the right of the fill/stroke indicators, the Opacity numeric field (labelled "O:") shows and allows you to change the master opacity of the selected object (or the averaged opacity of several selected objects). Right-clicking the numeric field opens a popup menu with preset opacity levels. Middle-clicking on the "O:" label cycles the opacity through the values of 0 (transparent), 0.5, and 1 (opaque).

The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. There's also a window resize handle added at the very end of the statusbar.

== Color palette ==

[joncruz]

== Transform dialog ==

Fixes and improvements in the Transform dialog (Ctrl+Shift+M):

* The Apply to each object separately checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs).

* The Clear button resets the values on the current tab to defaults.

* The Scale tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also, there's a Scale proportionally checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.)

* The Skew tab can now specify the skew as an absolute displacement (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as percentage displacement (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an angle (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal).

* The Matrix tab (previously called "Transform") can either edit the current <code>transform=</code> matrix of an object, or post-multiply the <code>transform=</code> with the matrix you specify, depending on the Edit current matrix checkbox. (As it is now redundant, the transformation matrix in the Object Properties dialog is removed.)

* The dialog now correctly watches selection changes in the active document window and updates its values accordingly.

* The layout of the dialog is simplified, tooltips and mnemonics added for better usability.

* Many bugs are fixed, especially in value conversions between units.

== Remembering the rotation center ==

* The position of the center (axis) of rotation and skewing used by Selector is now remembered for all objects and is restored when you select those objects again (even after save and reload). When you move or scale an object, its rotation center is moved or scaled too, so its position relative to the object always remains the same.

* When you have several objects selected, they use the rotation focus of the first selected object. If the first object does not have center set (i.e. if it's in a default central position), then several objects will rotate around the center of their common bounding box.

* Shift+click on the rotation center resets it back to the center of the object's box.

* Consequently, dragging the transformation center is now an undoable action; you can press Ctrl+Z to undo the drag.

[TODO:

- make use of this in keyboard transforms and Transform dialog;

- make it work smartly for groups: if a group has center not set, return the center of the first object inside group with the center set

- a separate tab in the Transform dialog, with 9 buttons in the square grid (for setting it to object's corners, sides, and center) as well as x/y fields for setting center to any position

- make center snap to grid/guides/objects and to other centers

- make objects snap with their center to grid/guides/objects]

== Align & Distribute dialog: remove overlaps ==

* There is a new button to move the selected objects enough that they don't overlap each other.
This should be a significant addition to Inkscape's usability for diagramming.

[Consider expanding this, comparing with existing Unclump and Distribute edge-to-edge buttons.]

== Document Properties / Metadata dialogs ==

* The Document Preferences dialog is now named Document Properties, and it was split in two: metadata were extracted into the Document Metadata dialog; metadata widgets are now also spread over two pages.

* New controls: the new object snapping features required their own property widgets, and you can set the snapping sensitivity with a slider, or let it snap regardless of distance.

* Rearrangements within Document Properties: everything snapping related was collected on one page; Grid and Guide widgets are on their own, the same page. Due to HIG compliance, all widgets were categorized; especially the widgets on the Page page were completely rearranged in the General/Format/Border categories.

* Bug fixes: grayed out license URI had too low contrast, so it's no longer grayed out; the proprietary license didn't clean the license uri; spinbuttons had no tooltips, and minor grid quirks were removed; data was not updated when a new file replaced another in the same window.

* HIG compliance: much work went into, and now only a few details are missing from full Gnome-HIG compliance.

== Keyboard profiles ==

[mental]

== Path effects ==

[acspike]

== Snapping ==

* [object snap - carl]

* [highlight - mtou]

* [only to visible gridlines - mtou]

* Guidelines are made easier to pick: now you don't need to position mouse exactly over a guideline to activate it, instead there's a small position tolerance (1 screen pixel on each side of the guideline).

== Connectors ==

* The buffer around avoided shapes (used for autorouting connectors) can now be adjusted via the "Spacing" control on the Connector toolbar.

== Important bugfixes ==

* Scaling of objects with stroke in Selector used to cause undesired shifts of the scaled object, as well as scaling it in the dimension which was intended to remain untouched (e.g. slight change in width when you scale only height). All these problems are now fixed, both for interactive scaling by mouse and for numeric scaling via the Controls bar, and for both values of the "Scale stroke with objects" option. Among other things, this means that stroked objects no longer lose snapping on scale, and that the "Default scale origin" option in the Selector tool preferences finally works as designed. Caveat: There may still be problems if you scale a selection that contains objects with different stroke widths.

* Bounding box for text objects did not include stroke width.

* Stroke miterlimit on text objects was misinterpreted in absolute units instead of multiplies of stroke width (resulting in miter joins rendered as bevel).

* [win32 font backend - cyreve]

* Setting dash pattern was broken for transformed objects, and copy/paste of style with dash pattern did not apply correctly to objects with transforms.

* An error caused a complete extra screen redraw after each zoom operation. That is, after you press "+" in a complex drawing, Inkscape redraws, but for some time after that it remains still unresponsive because it does that second redraw (invisibly for you, i.e. nothing changes on the screen). This is fixed.

* Gradient rendering was off by one pixel, which often resulted in visibly wrong gradient rendering for small objects or in zoom-out.

* The SVG path parser could not handle fractional numbers with the initial dot.

* Several pattern rendering bugs are fixed, discovered by working with SVG files exported from Adobe Illustrator.

* Inkscape on Mac OS X will now notice fonts in your ~/Library/Fonts directory, in addition to the other standard places.

* Scaling of stroke didn't work for objects that didn't specify stroke-width and thus had the default 1px stroke.

== Misc improvements ==

* Now you can use Shift+middle button drag in any tool to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with middle button drag (panning), middle button click (zoom in) and Shift+middle button click (zoom out), this completes the set of canvas navigation shortcuts available in any tool or context.

* Document templates (listed in File > New) are now first searched in the <code>templates</code> subdirectory of the user's profile directory (on Linux it's <code>~/.inkscape/templates</code>), then in the system-wide Inkscape templates directory. This allows you to add your own templates on top of the list of standard templates, as well as override the default template with your own one (the <code>default.svg</code> in the profile directory has priority over the system-wide one).

* In Gradient tool, Shift+R reverses the gradient definition (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for elliptic gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result.

* When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a message is displayed in the statusbar explaining what has changed in the program's behavior.

* Zoom commands in the View menu are moved to a submenu; the Zoom In and Zoom Out commands are added to that submenu.

* The contents of the statusbar message are now duplicated as a tooltip that is shown when you hover the mouse over the statusbar. [TODO: need to strip from the tooltips.] Also, the status bar text is now no longer just cut off if there is no room but, at the end position, ellipses (...) are inserted to show there's more (only with Gtk 2.6 and newer).

* Whole thousands above 2000 in the rulers are now displayed as 2k, 3k, 4k etc.

* By popular demand, in Pen tool, if a new path is being drawn but not yet finished, Ctrl+Z cancels that unfinished path (i.e. does the same as Esc), instead of undoing the previous action.

* In Pen tool, Del works the same as Backspace to delete the last created point on the unfinished path.

* In Node tool, the ! key inverts node selection in the current subpath(s) (i.e. subpaths with at least one selected node); Alt+! inverts in the entire path. (This is similar to how these keys work in Selector, with current subpath(s) instead of the current layer.)

* The keyboard shortcut for "Make selected segments curves" in Node tool is changed from Shift+K to Shift+U for better mnemonics.

* In Calligraphic tool, Esc deselects as in most other tools.

* In Selector, Ctrl+Enter enters the selected group (making it a temporary layer). Ctrl+Backspace leaves the current layer and goes one layer up in the hierarchy (but not to root).

* In the Document Preferences dialog, the new object style for each tool is now shown as a style swatch (displaying fill/stroke colors and opacity, stroke width, and master opacity), similar in design to the selected style indicator in the statusbar.

* Simplify threshold in Inkscape Preferences can now be set with more precision.

* [pen tool keys - bb]

* In the Grid Arrange dialog, row/column spacing can now be negative.

* The installation default is now scaling rounded rectangle corners with the rectangles.

* The <code>--query-*</code> command line parameters now return the true SVG bounding box of the object instead of the Inkscape coordinate system bbox (with inverted Y axis). The new behavior makes more sense for scripting use of Inkscape.

* Individual <tspan>s within text objects (including line tspans) can now be selected via the XML editor to view their bounding boxes (though per SVG, you cannot transform them). Also, you can use the <code>--query-*</code> command line parameters to find out the bounding boxes of tspans from a script. (Individual strings within or between tspans are still not selectable, and they cannot have an ID for querying anyway.)

* Objects with clippath show the correct clipped bounding box, instead of the original unclipped bbox as before. (However, this does not apply to objects without clippath of their own which are clipped by being inside a clipped group.)

* [save zip with images - acspike?]

* [about dialog redesign - mental]

* [icons prerendering - joncruz, mental]

* [extensions on windows - ishmal]

* [new icons?]

* [python extensions to work out of the box on windows? - ishmal]

* [new cursors - scislac]

* In the Transform dialog / Rotate tab, the icon was flipped horizontally to be in line with the direction of positive rotation; the change was applied to the default and crispy icon sets.

== Rendering speed ==

Thanks to optimizations in the renderer, Inkscape's screen redraw is faster by at least 10%, and in some cases (such as complex stroked/dashed paths at high zooms) up to three times faster.

== Translations ==

* INX files (containing the UI of the external effects) now allow the user visible strings to be translated. This means that effect dialogs, file type selections, and extension names can all be translated by translators.

== Internal ==

* The Document Properties Dialog code was completely gtkmmified, which lead to dramatic reduction of code size due to usage of widget objects. The used widget objects should be reusable by other dialogs, too, and the code is much more readable.

* Work on optimizing includes in all cpp files started, using the purgeincludes tool specifically written for that purpose, and ended with 40% of include lines removed!

== Beware: defect themes on Linux ==

* Inkscape and other Gtk programs can crash on any Linux, when the gtk2-engines-smooth / libsmooth package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem, however, but it would be nice if you as affected user would inform the gtk-engines maintainers of the problem. See especially http://bugzilla.gnome.org/show_bug.cgi?id=312115 (thanks to Thomas Wood)
* A similar crash happens if the KDE Baghira theme and the package gtk_qt_engine are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.

== Previous releases ==

* ReleaseNotes043 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes043)
* ReleaseNotes042 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042)
* ReleaseNotes041 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes041)
* ReleaseNotes040 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes040)
* ReleaseNotes039 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes039)
* ReleaseNotes038 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes038)
* ReleaseNotes037 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes037)
* ReleaseNotes036 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes036)
* ReleaseNotes035 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes035)