Inkscape Wiki - User contributions [en]

Release notes/0.46

2007-02-21T06:26:43Z

KeesCook: /* [print dialog - kees] */

=Inkscape 0.46=

=Tools:=
==Gradient Tool:==
[- johan]
*Stops in gradients can be added, deleted, and edited on-canvas now.
**Stops can be added by double clicking on the gradient line or by Ctrl+Alt+Click on the line.
**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for the selected stop(s).
**More than one stop can be selected at a time.
***Can be moved together if next to each other.
***Can be deleted at the same time.
***When you have one of the '''gradient handles selected''', its style (color and opacity) is reflected by the selected style indicator (left of the statusbar) and the Fill&Stroke dialog. Previously, opacity of a gradient handle was reflected as fill-opacity and stroke-opacity; now it is reflected as '''master opacity''' (the "O:" spinbutton in the selected style indicator, the "Master opacity" slider in Fill&Stroke). This makes it much easier to view and change opacity of gradient handles using only the selected style indicator in the statusbar.
****When multiple gradient stops are selected, the selected style indicator (in the statusbar) displays and controls the averaged color and opacity of the selected stops.
*If the selected object(s) have gradient in fill or stroke, the '''selected style indicator''' in the bottom-left corner of the editing window now displays a '''live gradient preview''' prefixed by '''R''' or '''L''' to indicate Radial or Linear gradients (instead of displaying "L Gradient" or "R Gradient" text labels as before). Also, this and other similar widget now use italic font face to indicate <i>None</i> and bold to indicate <b>Unset</b>.

==Node Tool:==
[sculpt profiles - bbyak]

==Text Tool:==
[text toolbar - deadchip]

=Renderer:=
* '''Smart redraw:''' With complex images and/or on slow computers, you may have noticed that Inkscape redraws the screen image in horizontal strips, and these strips are painted sequentially top to bottom. Now this direction is automatically changed based on where your mouse cursor is. In particular, if mouse is closer to the bottom of the area to redraw, strips will be painted in the bottom-to-top order. This significantly improves the responsiveness and interactivity in some situations. For example, when you are node-editing the bottom part of a complex path, the entire path needs to be redrawn on each change, but now this redraw starts from the bottom and therefore the you see the effect of your changes at once - i.e. while screen redraw may still lag behind your mouse movement, this lag is less noticeable.

* [faster blur - jasper]

* In this version, Inkscape starts using the [http://www.cairographics.org cairo] library for rendering. It is now used for '''outline mode''' display which, thanks to using cairo and other optimizations, redraws faster by about '''25%'''.

* [smoother scrolling and panning - bbyak]

=Filters & Effects=
==[more filters - kiirala, haa_rodrigues]==

=UI:=
==[markers - bryce]==
* stock markers now appear in the "recently used markers" section of the marker selector dropdowns in the Fill & Stroke dialog. Before, any markers with stock id's (including markers modified by the user) were hidden, making it difficult to work with modified stock markers.

==[toolbars - joncruz]==

* '''Print Dialog''': The GTK Unix Print Dialog has been hooked up! From the dialog, you can select any of the Postscript-capable printers known to your system and configure them as with any other GTK application.

=Bitmap export=

* '''Batch export''': The Bitmap Export dialog (Ctrl+Shift+E) got a new checkbox, ''Batch export all selected objects''. This checkbox is available when two or more objects are selected. If it is checked, instead of exporting selection as a whole, Inkscape exports each selected object separately into its own PNG file. This uses each object's export hints (i.e. export filename and DPI) if they are remembered from a previous export; otherwise, the filename is created from the object ID and the DPI is 90 pixels per inch. '''Caution:''' Unlike regular export, batch export overwrites all existing PNG files without warning.

:This makes it possible to implement all kinds of '''image slicing''' and automated export scenarios. For example, if you are working on a web site design, you can create a separate "export" layer. In that layer, "slice" your web page image into separate areas by creating invisible rectangles with no fill and no stroke. Select each rectangle (by Tab/Shift+Tab, or by switching to Outline mode where even an invisible rectangle can be selected by clicking on its outline) and export it into the corresponding filename (which gets saved as that object's export hint). After that, if you do any changes to your graphics, it's very easy to reexport all the slices: just switch to the "export" layer, select all in that layer (Ctrl+A), and export with the ''Batch export selected objects'' checkbox on.

=Even more improvements=
* '''[if enabled! - mental]''' A new cairo-based PDF exporter has been added to Inkscape. Inkscape 0.46 can export shapes, strokes, transparency, gradients, patterns, text, and images correctly to cairo. While clipping paths and masks are known to be faulty or missing. cairo will write a PDF with vector graphics when possible and fall back to raster graphics when needed. What can be exported as vectors and how much of the image will be rasterized when the fallback kicks in depends on your version of cairo. cairo version 1.2 with the pdf backend compiled in is the minimum requirement for any cairo-based PDF exports.

* '''Gnome VFS Improvements''': Gnome VFS Non-Local files are now usable through all of our file choosers in Open, Save and Export. This compile-time option allowed people to open any Gnome-VFS-based URI from the command-line in the past, but not non-local resources (WebDAV, SFTP, etc) and this now allows for all the lovely possibilities Gnome-VFS provides.

* In previous versions, Inkscape didn't allow you to '''group a single object.''' Yet in some cases, this operation is useful (for example, to blur the clipped edged of an object). So now this limitation is removed.

* The somewhat cryptic "F:" and "S:" labels in the selected style indicator (at the left end of the statusbar) and in tool's style swatches are now spelled out as '''Fill:''' and '''Stroke:'''. We believe this makes the interface, even if less space-efficient, a bit more friendly for newbies.

* The '''style swatches''' at the right end of object-creating tools' control bars now open the Preferences page of the corresponding tool when clicked. Also, now these swatches display a tooltip explaining its purpose (e.g. "Style of new rectangles", "Style of new calligraphic strokes", etc.)

CompilingUbuntu

2006-07-30T19:32:45Z

KeesCook: describe how to build libgc

== Dapper ==
If you're going to build Inkscape, you'll need to have a full complement of build requirements. This is very easy to do in Ubuntu Dapper:

<pre>
sudo apt-get build-dep inkscape
sudo apt-get install liblcms-dev libboost-graph-dev build-essential
echo "deb-src http://ftp.us.debian.org/debian/ unstable main" >> /etc/apt/sources.list
sudo apt-get update
apt-get source libgc-dev
cd libgc*
fakeroot dpkg-buildpackage -uc -us
sudo dpkg -i ../ligbc*.deb
</pre>

If you want version 0.44 from Debian Unstable, you can compile it in the same way as libgc above:

<pre>
apt-get source inkscape
cd inkscape*
fakeroot dpkg-buildpackage -uc -us
sudo dpkg -i ../inkscape*.deb
</pre>

To build the SVN snapshots:

<pre>
# Untar and navigate to the inkscape source folder
./configure
make
sudo make install
</pre>

Instead of doing "make install", on Debian-based distributions (such as Ubuntu) it is better to do
<pre>
sudo checkinstall
</pre>
since checkinstall first builds the .deb package and then installs it, thus making the package system aware of the newly installed inkscape.
If you get the "command not found" message, do
<pre>
sudo apt-get install checkinstall
</pre>

'''Notes:'''
build-dep gets all the dependencies for the version of Inkscape that comes with Ubuntu. We're not building the same version, but most of the dependencies are the same.

libcms-dev was required for ./configure to work, and libboost-graph-dev was needed for "network connector layout functionality"

This was done on a recently installed Dapper (Ubuntu 6.06) system. I built Inkscape version 0.44.

The following packages are need to compile cvs inkscape under a default Ubuntu Hoary/Breezy/Dapper system:
apt-get install cvs build-essential intltool libtool libgtkmm-2.4-dev libglib2.0-dev libpng12-dev libxslt1-dev libsigc++-2.0-dev libpopt-dev libgc-dev

Inkscape requires libgc-6.7.

Breezy uses 6.4, Dapper uses 6.6.

Hoary uses version 6.3, which is provided in the Repos. (Is there somewhere to get a .deb for 6.4?)

To overwrite libgc-6.3 with libgc-6.4:
Download gc6.4
./configure --prefix=/usr
make
sudo make install

== Old libgc 6.5 debs for Breezy ==

http://inkscape.modevia.com/ap/libgc-dev_6.5-1_i386.deb
http://inkscape.modevia.com/ap/libgc1_6.5-1_i386.deb

[[Category:Developer Documentation]]

Translation information

2006-05-18T01:41:56Z

KeesCook: /* Locale Testing */ add new LANGUAGE variable requirement

= 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 [http://xmlsoft.org/xmllint.html xmllint] 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/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables 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 LANGUAGE=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 LANGUAGE=es_MX 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.