Inkscape Wiki - User contributions [en]

Release notes/0.46

2007-03-01T11:43:41Z

Luci: /* Inkscape 0.46 */

=Inkscape 0.46=
'''(not released yet)'''

=Tools:=

==Paint Bucket tool==

The new Paint Bucket tool works exactly as you would expect: click in any area bounded on all sides and it will '''fill it with color'''. Being a vector tool, however, Inkscape's Paint Bucket just creates a new ''path'' that "fills in" the area in which you clicked.

It is important to note that the tool is '''perceptual''', not geometric. That is, when looking for the boundaries around the point you clicked, it takes for such boundaries any ''visible'' color changes. This means that filling will stop at gradients, blurs, and even the color edges in the imported bitmaps, but will ignore any paths or other objects that are fully (or almost) transparent and do not stand out from the background. In short, it will work exactly as if you were filling a rasterized version of your image in a bitmap editor like Photoshop or GIMP - but will give you a vector object to work with.

For example, now you can scan a pencil sketch, import the bitmap into Inkscape, and quickly fill all its cells with colors even without tracing the bitmap first. This is a very convenient and interactive way of digitizing your paper drawings, making the traditional bitmap tracing unnecessary in many cases.

Internally, the tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas, then tracing the resulting fill using [[potrace]] and placing the traced path into the document.

It places the rendered path onto the current layer, so you can have a layer on top (for example, "Inks") and select the layer below ("Colors") and do the fills so that they always appear below the Inks.

The resolution of the bitmap image used to perform the trace is dependent upon your document zoom level -- the more zoomed in to an area that you are, the higher the resolution of the bitmap-based flood fill. So, if you are got a fill that is too imprecise, has rough corners, or don't go into small nooks and appendices where it is supposed to go, just undo, zoom in closer and repeat filling from the same point. Conversely, if the fill leaks out through a small gap, zoom out to make the gap less visible and fill again.

Like all object-creating tools, the Paint Bucket may use the last-set style for the objects it creates (this is the default), or it can use its own fixed style. You can switch between these modes on this tool's page in Inkscape Preferences (Ctrl+Shift+P). In the right-hand end of the tool's Controls bar, a swatch shows the style that will be used for the next created fill object.

Some potential improvements to the tool are:

* If the [Ctrl] key is held down, clicking on an object changes the fill color to the current fill color, and [Shift]-[Ctrl] changes the stroke color to the current stroke color

==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 None and bold to indicate Unset.

==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%'''.

* Several improvements make '''canvas panning and scrolling''' smoother and more interactive in complex slow-rendering documents:

:* When panning by the middle mouse button, Inkscape no longer attempts to redraw the canvas while your mouse button is pressed. Any redrawing only happens after you release the mouse. As a result, the newly revealed parts of the canvas are somewhat more "dirty" but the '''panning is smoother than before''', with few if any "hiccups".

:* Previously, if you start panning with middle button while Inkscape is still redrawing screen in a complex drawing, panning sometimes completely failed or moved canvas just a little step. Now it is '''guaranteed to pan the canvas all the way''' from mouse-press point to mouse-release point in any case, even if sometimes it fails to show the intermediate positions.

:* When pressing and holding Ctrl+arrows to scroll canvas, Inkscape normally accelerates scrolling so that each next scrolling step is bigger than the previous. Previously, in complex drawings this acceleration sometimes got interrupted, which made scrolling annoyingly bumpy and slow. Now this is fixed so that '''scrolling is smoothly accelerated''' even in a slow-rendering document.

:* The default '''starting speed and acceleration''' of Ctrl+arrows scrolling are slightly increased. (They are both settable in Preferences.)

=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.

* '''Hide all except selected''': A new checkbox allows you to hide in the exported image everything except selected object(s).

=Import/Export=

* [new wpg - ted gould]

=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.)

* [more snapping: drawing rects]

Release notes/0.45

2007-03-01T11:40:36Z

Luci: /* Inkscape 0.45.1 changes with respect to 0.45 */

= Inkscape 0.45.1 changes with respect to 0.45 =
'''(not released yet)'''

*Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
*Patch [ 1666532 ]: Broken link in inkview man page
*Patch [ 1665447 ]: fix for the blur quantization bug 1617082
*Patch [ 1664849 ]: fix for 1662589: increase blur margins
*Patch [ 1664004 ]: embedimage.py with fixed search order
*Patch [ 1662649 ]: markers.svg with reversed order
*Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
*Patch [ 1659404 ]: Set locale directory from environment variable
*Patch [ 1657072 ]: fix for bug 1654495
*Patch [ 1654636 ]: defocus dropper checkboxes
*Updated slovak translation
*Adding japanese.nsh and russian.nsh into files that should go into the release tarball
*Correct russian translation
*Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
*Patch [ 1651752 ]: fix dropper tool
*Pattern along path extension fixed on Windows

= Inkscape 0.45: overview =

This release brings the exciting new features developed by the Google Summer of Code 2006 participants, as well as tons of other improvements across the board. Here are the highlights:

* '''Gaussian blur''' is the first SVG filter supported by Inkscape. You can blur any object to any extent - yet it remains vector and fully editable. This gives a huge boost to Inkscape as a creative art tool.

* '''Display speed and interactivity''': not only does Inkscape render faster, but it can now respond to user input before it finished redrawing the screen, which greatly improves the responsiveness (perceived speed or interactivity) of the program.

* '''History dialog''' makes it easy to to review your editing session and jump to any step of it, undoing and redoing multiple actions with one click.

* Several important tool features are added, notably the new selection mode in '''Node tool''' and the adjustable rounded caps in '''Calligraphic pen'''.

* '''Bitmap tracing''' works better for multi-color traces, sports a redesigned dialog and several new options.

* Many new '''extension effects''' are added, including '''Color effects''' and '''Pattern along path'''.

* The '''Outline mode''' has got many fixes and improvements, including a keyboard shortcut.

* Several new commands in '''Help''' menu open various Inkscape-related pages in your default browser, making Inkscape reference information more accessible as you work.

* Dozens of smaller '''features''' are added throughout the program, and hundreds of '''bugs''' are fixed.

= SVG filters: Gaussian blur =

Thanks to Google's Summer of Code program, Inkscape now has basic support for [http://www.w3.org/TR/SVG11/filters.html SVG filters]. The only filter enabled so far is '''Gaussian blur'''.

With it, you can softly and naturally blur any Inkscape objects: paths, shapes, groups, text, images. Clones inherit blurring from their original, but they can also be blurred independently from the original (you can create blurred clones with Tile Clones, too). Both the fill and stroke of an object are blurred together, creating semitransparent margins that smoothly blend into the background.

Gaussian blur enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect.

* To blur selected objects, open the Fill and Stroke dialog (Ctrl+Shift+F) and use the '''Blur''' slider. The blur value is a percentage, with 100% corresponding to a blurring radius (standard deviation of Gaussian function) of 1/8 of the object's bounding box' perimeter (that is, for a square, a blur of 100% will have the radius equal to half a side, which turns any shape into an amorphous cloud).

* The '''Tile Clones''' dialog also supports blurring. On the '''Blur & opacity''' tab, you can set the blur percentage per row or per column of your tiling, as well as randomize blurring and make it alternate (all the same options as for Opacity).

* The quality of on-screen blur display is controlled by the '''Blur quality''' option on the new '''Filters''' tab of Inkscape Preferences (Ctrl+Shift+P). The available options range from best quality/slowest display to worst quality/fastest display, the default being in the middle of the range. Any setting except the "best quality" may introduce some rendering artifacts, especially when blurring thin strokes; on the other hand, the "best quality" setting may make Inkscape extremely slow at high zooms. These settings only affect the screen display of blurred objects; bitmap export always uses the best quality (and may therefore become quite slow for images with a lot of blur).

Here are a few tips on using blur:

* '''Masks and clipping''' are applied ''after'' blur. That is, if you clip an object and then blur it (or blur it first and then clip - it makes no difference), the clipped edges will remain crisp. Often, this is what you want. If, however, you want to blur the clipped/masked edges too (possibly with a different radius), you can use grouping: group the clipped object with some other object (which you can then delete from the group) and blur the group.

* A simple '''drop shadow''' is now very easy to do: just copy the object, paint the copy black, blur it, shift away a bit and lower it to the bottom. However, such a shadow does not update when you edit the foreground object. If your object is already black (or, more generally, if you want the shadow to be the same color as the object), you can clone instead of copy to make the shadow auto-updating. But what if your foreground object is not black but you need an auto-updating black shadow? Here's a recipe: unset the object's fill (it becomes black); create ''two'' clones of it; put one clone on top and paint any color you want; put the other clone at bottom, blur it and shift sideways. Now you can edit the unset-fill original (use Alt+click to select it) and everything will update.

* If an object has a fill that you don't want to blur (e.g. pattern, or if it's a bitmap), but you just want to '''feather the edges''', use a blurred transparency mask. For this, copy the object; paint it white; blur it as needed; scale the blurred copy down so its blur margins are entirely within the original object; select both the original and the blurred mask; do Object > Mask > Set.

* '''Transforming''' a blurred object '''transforms its blur''', too. This applies to a non-uniform scaling as well, so by squeezing a blurred object you make its blur squeezed as well. So, the easiest way to blur a path horizontally more than vertically is this: stretch it upwards without blur, then apply blur and squeeze it back into the original shape. (This only works if the stretched path does not already have a Transform attribute.)

* You can combine '''blurring with gradients'''. For example, an ellipse with elliptic opacity gradient will look much softer and more natural when blurred. An object with a horizontal linear opacity gradient, when blurred, will look as if it's more blurred on its transparent side than on its opaque side.

* A '''clone of a blurred object''' inherits the blur of the original. Therefore, such a clone can be blurred ''more'', but you can't "unblur" it to make the clone sharper than its original (unless, of course, you unlink it). The Fill and Stroke dialog shows you the amount of the blur applied to this particular object; however, if the object is a clone of an already blurred original, the dialog does not reflect that.

* Note that '''Firefox 2.0''' does not support SVG filters, so your files will be displayed in Firefox 2.0 without blur. However, filter support has been added in the current development version and will be included in Firefox 3.0. The Opera web browser, as well as librsvg (used by Wikipedia) and Batik, support filters correctly in their current versions.

= Undo history =

* Inkscape now features a History Dialog accessible via Ctrl+Shift+H or Edit > Undo History. All changes made to the document since it was opened are recorded here.

:* In the dialog, changes are listed from the '''oldest (top)''' to the '''newest (bottom)'''.

:* The type of each change is indicated by an '''icon''' and a short '''description'''.

:* For readability, consecutive changes of the same type are placed in a '''collapsible branch''' showing a triangle marker and the number of the hidden actions in the branch.

:* By clicking on an event in the list, you can easily '''move through the undo history''', i.e. undo or redo any number of actions with one click.

* The Undo and Redo commands in the Edit menu display the descriptions of the commands to be undone and redone, correspondingly. (These are the same descriptions that you see in the History dialog.)

= Rendering improvements =

* Interruptible display: Previously, Inkscape could not do anything until it finishes the current screen redraw. Now the redraw is made interruptible, so that Inkscape responds to mouse and keyboard input and can abort the current redraw and start over if you do some screen-changing operation. As a result, Inkscape now feels '''much snappier and more interactive'''. This interruptibility is fine-tuned for some continuous-drag operations (such as node dragging) so that a balance is achieved between responsiveness and completeness of display.

* Screen render is faster by '''2-3%''' overall:

:* Complex drawings with '''transparency''' are faster by up to '''5%'''.

:* '''Radial gradients''' are rendered faster by at least '''10%'''.

* Rendering (compositing) quality has been improved. This is most visible with (partially) transparent gradients: '''banding''' is a lot less pronounced now. Speed has also been improved in some cases.

* Display is more responsive when working at high zoom levels when using a tablet.

= Tools =

== Node tool ==

* You can grow or shrink node selection by hovering the mouse pointer over a node and using mousewheel (up = grow, down = shrink) or the keys PageUp (grow) and PageDown (shrink). ''Growing'' adds the closest unselected node to the selection; shrinking deselects the farthest selected node. There are two modes that differ by how the closest/farthest nodes are chosen:

:* Spatial selection (mousewheel, PageUp/PageDown): distances to nodes are measured directly, regardless of which subpath a node belongs to.

:* Linear selection (Ctrl+mousewheel, Ctrl+PageUp/Ctrl+PageDown): node distances are measured ''along the path'', and only the nodes belonging to the same subpath as the hovered node are considered (i.e. other subpaths are never selected).

:This technique is convenient for quickly selecting an area in a complex path starting from a center - for example, for node sculpting.

== Dropper ==

* Instead of the confusing toggle button, now the Controls bar for the Dropper tool has two checkboxes, '''Pick alpha''' and '''Set alpha''', which work as follows. Suppose you have an object selected and, using Dropper, click on an object which has red (#FF0000) fill and 0.5 opacity (half-transparent).

:* If the "Pick alpha" checkbox is off, the selected object will get the fill color #800000 (i.e. faded-out red) and fill opacity will be at 1.0 (opaque).

:* If the "Pick alpha" checkbox is on but "Set alpha" is off, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 1.0.

:* If both "Pick alpha" and "Set alpha" are on, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 0.5 (half-transparent).

:If you Shift+click instead of click, the same changes will be made to stroke color and stroke opacity, correspondingly. Note that in no situation can Dropper change the ''master opacity'' of the selected object(s) (only the fill/stroke opacity), although it can pick it just as it does any other kind of opacity.

== Calligraphy ==

* A new numeric parameter, Caps, controls the amount of protruding at the ends of calligraphic strokes. This parameter can range from 0 (flat caps, default behavior in previous versions) through 1 (approximately half-circle caps) and up to 5 (long elliptic caps). Rounded caps much improve the look of low-fixation strokes, simulating a rounded pen.

* The "Drag" parameter has been renamed to Wiggle with a value inversion (i.e. low drag corresponds to high wiggle, and vice versa). Increase this parameter (default is 0) to make the pen waver and wiggle in curly patterns.

* As a first step towards a redesign of the tools' controls, the '''Controls bar of the Calligraphy pen''' has been upgraded. Now it no longer prevents the Inkscape window from resizing narrower than the bar. The items on the far right end of the bar which didn't fit in a narrow window are still accessible through an '''expansion menu''' which allows you to toggle switches, select commands, and set values of numeric fields. Also, each editable numeric value field has a new '''right-click menu''' with some common values which often allows you to set a desired value much faster than by scrolling the control or typing the value into it.

* With low or zero Fixation parameter, some users of tablet pens experienced "blobs" (brief reversals of a stroke's right/left edges, causing "holes" and "bubbles" in a calligraphic stroke), especially often at the start of a stroke. Hopefully this problem is now fixed without reducing the responsiveness of the tool.

= Outline mode =

* A new menu command (View > Display Mode > Toggle) and a new keyboard shortcut (Ctrl+<keypad 5>) switch the display mode from Normal to Outline and back.

* The window title displays "(outline)" next to the file name when that editing window is in Outline mode.

* An object with mask and/or clipping path, when viewed in Outline mode, now displays both the object itself and its clipping path and mask as objects, using different outline colors. By default, clippaths use green outlines, and masks use blue.

* Images in Outline mode are displayed as red (by default) frames with two diagonals.

* An object with no fill and no stroke, invisible and not selectable by mouse clicking in normal mode, can now be picked by a mouse click in the Outline mode using its visible outline.

* The bug whereby stroked shapes didn't change stroke width when switching to Outline mode or back is fixed.

* All outline colors are changeable by editing the "wireframecolors" group inside "options" in the preferences file (~/.inkscape/preferences.xml). The "onlight" and "ondark" attributes set the colors of the regular object outlines on light and dark backgrounds (default black and white correspondingly); the "images", "clips", and "masks" attributes set the colors of images, clipping paths, and masks (defaults are red, green, and blue correspondingly). Each attribute is a decimal integer corresponding to the hex RRGGBBAA of the color.

* To cater for specialized uses, such as preparing input for personal media cutters, Inkscape now has an option to start in the Outline mode upon launch. To enable this, add the following line to your preferences.xml file:

:: <group id="startmode" outline="1"/>

:placing it after the <group id="options"> opening tag.

= Keyboard profiles =

The previous release allowed sets of keybindings (keymaps) to be created for Inkscape in the style of other applications. Two more keymaps have been added:

* '''Adobe Illustrator'''
* '''Macromedia Freehand'''

Of course not every feature in these other programs has a direct match to features in Inkscape; so, if you can, please '''help us out''' by reporting any problems you may have or improvements you would like to request.

Additionally, a keymap that focuses on tablet-based illustration and drawing work has been added:

* '''right-handed-illustration.xml'''

This keymap places all commonly-used commands under the left hand, so that the user's hands rarely leave the keyboard or the tablet/stylus.

(To enable a profile, copy it into <code>default.xml</code> in the same directory, overwriting the old file. To restore the default Inkscape set, copy <code>inkscape.xml</code> into <code>default.xml</code>.)

More of Inkscape's keys are implemented as actions and are therefore available for remapping via keyboard profiles. New actions include '''EditSelectNext''' and '''EditSelectPrev''' for selecting next/previous object or node (by default, they are bound to Tab/Shift+Tab; as a result of becoming global actions, these keys now work in all tools and not only in Selector and Node tool as before).

= Extension effects =

Inkscape's extension effects, written in Python using the '''inkex''' utility class, are currently a major growth point of the project. They allow new developers to create functionality very quickly, without having to learn Inkscape's huge C/C++ codebase. However, eventually we plan to move many of these effects into the core of Inkscape, which will make them much faster and more interactive. From this viewpoint, effects can be considered a quick way to prototype and test the algorithms and UI controls of the future Inkscape features. However, this does not prevent effects from being genuinely useful in everyday work, and in this version we have several excellent additions.

== New effects ==

* '''Pattern along path''': A new powerful extension in the "Generate from path" submenu allows you to bend, repeat and/or stretch a pattern object (which can be a path or a group) along a "skeleton" path. This makes it easy to create a variety of patterned and shaped strokes. (This obsoletes the old "Kochify" extension which is removed.)

:Effect's parameters include:

:* ''Copies of the pattern'' selects one of the four modes: '''Single stretched''': one copy of the pattern is placed on the skeleton path and stretched/squeezed to match its length; '''Repeated stretched''': as many copies as would fit are placed along the skeleton path and stretched to fit exactly; '''Single''' and '''Repeated''': same but without stretching.

:* ''Deformation type'' can be one of: '''Snake''' bends the pattern flatly in the plane of the drawing, the width not depending on direction; '''Ribbon''' bends it as a vertical ribbon or like a calligraphic stroke with maximum fixation, so that width depends on direction (minimum for vertical parts of the stroke, maximum for horizontal).

:* Several parameters allow you to adjust spacing between the copies of the pattern (for Multiple modes) and their offset in two directions (along the skeleton path and perpendicular to it).

:* Normally the effect assumes that the pattern object is horizontal and bends its horizontal axis (at mid-height) along the skeleton path. There's a checkbox that allows you to use a '''vertical pattern''' instead.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-patternalongpath.png].

* '''Color effects''': A new group of extensions in the '''Color''' submenu of the Effects menu allows you to adjust all colors of a selection at once. These commands affect both fill and stroke colors, including gradients (but not bitmaps). The commands include:

:* a full set of '''HSL adjustments''' (increasing/decreasing hue, saturation, or lightness by 5%),

:* '''Brighter''' and '''Darker''' (adjust brightness up or down by 10%),

:* '''Desaturate''',

:* '''Grayscale''',

:* '''Negative''',

:* commands for removing or swapping the '''Red''', '''Green''', '''Blue''' channels,

:* a '''Custom''' command where you can set your own formulas for modifying the color channels.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-coloreffects.png].

:Note: undoing color changes on gradients exposes a bug where an object seems to "disappear"; this is only a display issue (caused by the order in which gradients and their users are restored on undo) not causing any loss of information. Also, on large documents and large selections with gradients, Python's XPath code may get quite slow. Despite these shortcomings, we decided to add this extension, because it's genuinely useful functionality which was so far missing in Inkscape.

* Recent fixes in the processing of SVG <defs /> have made it possible to implement the often requested '''Color Markers to Match Stroke''' effect. It is no longer necessary to hand-edit XML to recolor arrowheads; just change the stroke color of your path and call this effect to recolor its markers to match.

* '''Lorem ipsum''' (in "Render" submenu) is a new extension that creates the traditional Latin-like random text for design mock-ups. The number of paragraphs, the number of sentences per paragraph and the possible fluctuation of the number of sentences (for uneven paragraphs) can be adjusted. If no flowed text element is selected, a new one in a new layer is created, matching the size of the canvas.

* '''Fractalize''' (in "Modify Path" submenu) replaces each segment of the selected path by a crooked line, subdivided to the given depth, with randomly displaced nodes.

* '''g2png''': The new group-to-PNG Python extension (g2png) is an easy way to export any group or layer to individual PNG files. It was first created for use in the [http://www.le-radar.com/?mm/inkscape Inkscape User Manual] (also available in SVN in the user_manual module) but is also interesting for many other uses. If e.g. you have to draw a set of icons, you can draw them in the same document, thus making copying, duplicating, cloning etc. easier. Then just create a group for each icon, and with the extension, each group ends up in its own PNG file.

== Improved effects ==

* The '''Function Plotter''' has been extended, providing greater flexibility in x- and y-range definition.

* The '''Measure Path''' extension is improved with several new parameters added (units, scale, precision, distance from path).

* The '''Extract One Image''' extension is fixed to automatically append filename extension to the created bitmap file.

* The "Blur Edge" extension is renamed into '''Inset/Outset Halo''' to avoid confusion with the real Gaussian blur that we now support, as well as to better describe what this extension actually does: From the selected path, it creates a group of inset and outset paths that form a stepped "halo" around the object.

== Infrastructure ==

* '''3 new parameter types''' have been added to the extension effect UI: '''tabs''', '''enumerations''' and '''optiongroups''' (radio buttons). Examples are available of how to use these parameters in INX files: the new Function Plotter uses tabs; enumerations are used by the Pattern along path extension; and a small developer example is given to illustrate the use of optiongroups (identical to enumerations).

* In an extension's INX file, you can specify <code><effects-menu hidden="yes"/></code> to hide that extension from the Effects menu. However, such a "hidden" extension can still be assigned a keyboard shortcut (by using its <code>id</code> as an "action" in your <code>~/.inkscape/keys/default.xml</code>).

* In an extension's INX file, you can add <code>needs-document="no"</code> attribute to the <code><effect></code> element. This indicates that the extension does not process the current SVG document, and Inkscape will not bother saving and restoring the document from a temporary file which allows this extension to run faster and smoother. (This is used for the new open-in-default-browser Help menu commands which are technically implemented as extensions.)

= Export formats =

== AI import/export ==

* We only support AI import and export for Adobe Illustrator 8.0 and older. This has been clarified in the Open and Save As lists.

== PDF export ==

Inkscape's PDF exporter has been improved:

* '''New features:''' bitmap images can be embedded; PDF files can be exported from command line using the <code>--export-pdf</code> parameter.

* '''Changed behavior:''' the pointless text to path question is gone.

* '''Fixed bugs:''' save failure is now detected, miter limits are now >= 1, PDFs with transparent gradient are now embeddable, eccentric elliptic gradients fixed, dash style inheritance fixed, transparency inheritance fixed.

== PS/EPS export ==

There's a new option to embed the fonts used in the document in the PS or EPS exported file. As of now, this works for Type 1 fonts only, not TrueType. The option is available when performing the export from the GUI as well as from the command line via the <code>--export-embed-fonts</code> option.

== EMF export ==

Inkscape has a limited support for exporting EMF (Enhanced Meta File) format. This works only on Windows, and only exports strokes and fills with constant colors. No text, no images, no gradients, no transparency.

= SVG output =

For specialized uses, several aspects of Inkscape's SVG output can now be customized via editing the preferences.xml file (there's no UI for these options). A <group id="svgoutput"> inside <group id="options"> can have the following attributes:

* usenamedcolors (default is 0). If nonzero, Inkscape uses symbolic color names (such as "white" or "lime") and three-digit color designations (such as $dfe) where appropriate; otherwise, it always uses six-digit colors (such as $d0f0e0). Note that in 0.44, the default was to use named colors, which created problems for some extension effects.

* numericprecision (default is 8). This is the number of significant digits written for each number into SVG. You can lower this number to get slightly more compact SVG at the expense of precision.

* minimumexponent (default is -8). In transform= attributes, any number whose absolute value is less than 10 to the power of minimumexponent (i.e. less than 10-8 by default) is written as 0.

* indent (default is 2) controls the number of spaces that each level of nesting in SVG is shifted. Set this to 0 to disable indentation.

* inlineattrs (default is 0). If nonzero, attributes are placed on the same line as their tags; otherwise they are separated by newlines.

= Bitmap tracing =

* A '''new color quantization algorithm''' for multiscan traces works faster (especially for large numbers of colors) and gives more adequate results with less colors used. This improves tracing results both for full-color photographs and for limited-color drawings.

* The Trace Bitmap dialog now provides access to three more tracing parameters:

:* '''Suppress speckles''': If set, spots or speckles larger than the given size (in pixels) are suppressed in the trace.

:* '''Smooth corners''': This parameter controls how much smoothing is applied to corners in the traced path.

:* '''Optimize paths''': If set, trace paths are optimized by joining adjacent Bezier segments with the given tolerance.

* All controls in the Trace Bitmap dialog are reorganized to be easier to find. The dialog is redesigned to use two main tabs: '''Mode''' (where you select the tracing mode, such as brightness cutoff or color multiscan) and '''Options''' (where you set various tracing options, such as corner smoothing). The preview is placed horizontally to the right of the tabs. Most labels and tooltips are rewritten for clarity. The trace preview image is made twice larger.

= Even more improvements =

* The '''opacity''' of objects is now displayed as percentage, '''from 0 to 100''', both in the Fill & Stroke dialog (with one fractional digit) and in the statusbar style indicator (with no fractional digits), instead of from 0 to 1.0 as before. This makes opacity values easier to read, type, and say.

* A '''Save a copy''' command has been added to the file menu, similar to the 'Save a copy' functionality of e.g. Adobe Illustrator. With this command, you can save your document under a new filename, but Inkscape will then "forget" it has done this: later saves will be to the old filename. The default shortcut assigned to this function is '''Shift+Ctrl+Alt+S'''.

* Text and flowed text objects behave more consistently. Now you can put a flowed text on path or (re)flow it into a shape just as you would do with a regular (unflowed) text. Previously, the need to convert a flowed text to text before these operations was a stumble for many users.

* Several commands were added to the '''Help menu''', providing the long-missing access to basic information about Inkscape and SVG right from the program: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php Inkscape manual], [http://inkscape.org/doc/inkscape-man.html Command line options], [http://wiki.inkscape.org/wiki/index.php/FAQ FAQ], Release notes, [http://inkscape.org/report_bugs.php Bug report page], and the [http://www.w3.org/TR/SVG11/ SVG 1.1 specification]. All these commands open the corresponding web pages in the user's default web browser.

* Exported PNG images have the correct '''resolution''' set in the header.

* The Path -> '''Union''' (Ctrl++) operation now functions when only a '''single object''' is selected. Use this to '''remove self-intersections''' in path objects.

* We removed the "hacked" '''filename entry field''' that we had added to the Open and Save dialogs because starting from version 2.10, GTK+ has finally restored this field in their '''standard file dialog'''. The standard field at the top of the dialog supports type-ahead find and performs the default dialog action (open or save) by pressing Enter, which means you can now do a quick '''Ctrl+O, Ctrl+V, Enter''' sequence to open the file whose path is in your clipboard (this closes a long-standing usability bug). Those who use older versions of GTK are advised either to upgrade to 2.10 or use Ctrl+L to open a pop-up filename box. (Our Windows builds are shipped with GTK+ 2.10.)

* The '''Create Bitmap''' function (Alt+B in the default keymap) is made more useful. Unless you have specific resolution or minimum size set for this command in preferences.xml (<code><group id="createbitmap"/></code>), it will take the '''resolution hint''' from the object whose bitmap copy you are creating (in other words, it will use the resolution that you specified for that object when exporting it via the Export Bitmap dialog), or the default '''90 dpi''' if that object was not yet exported. Also, a 90 dpi bitmap (with its pixels exactly 1 px in size) will be '''snapped''' to the pixel grid. This makes it easy to use Create Bitmap for quick '''rasterization preview''' of an object or document. (Note: if you have used a previous version of Inkscape, your preferences.xml may contain <code>minsize="250"</code>; delete this for objects' resolution hints to work.)

* Using extended input (i.e. tablet pressure and tilt) can now be disabled via Preferences (Misc tab). This is intended to be a last-resort option for those platform/hardware combinations that are not properly supported by GTK. With extended input disabled, you can still use your tablet as a mouse.

* Simplify Path now has two modes when working with a group of paths: the default mode, which treats all of the paths as one large object to simplify, or the new mode, which acts the same as using Simplify on each path in a group separately. In preferences.xml, set '''options.simplifyindividualpaths''' to 1 to get the new mode.

* For long Simplify operations (more than 20 paths at a time), Inkscape provides user feedback via the status bar as to how many paths have been simplified. This change also prevents Inkscape from appearing to have locked up during the operation.

* New '''templates''' added for '''video formats''' (PAL, NTSC and HDTV 1080) as well as DVD cover templates that were not installed in the previous version. This will help video and DVD authoring with Inkscape. The business card 85×54 template is now installed as well.

* "Other" license type was added to the metadata/license dialog so that people know that they are entering a URI to an "other" license.

= Examples =

* With all the recent additions - clipping, masking, and especially blur - Inkscape is now able to produce extremely photorealistic art. In the share/examples folder in Inkscape distribution, you will find two brand new, stunningly realistic images of shiny cars: car.svgz by Konstantin Rotkevich and gallardo.svgz by Michael Grosberg.

* Inkscape 0.45 does not yet have gradient meshes. But with the addition of Gaussian Blur, this feature suddenly got within reach. A new example file, gradient-mesh-experimental.svgz, explains the approach Inkscape will likely take to implement this feature in a fully SVG-compatible way.

* Although Inkscape does not support animation yet, you can add any animation scripts and attributes to your SVG file manually in a text editor - and the file will still be editable in Inkscape. Tavmjong Bah used this technique to create animated-clock.svg which, when loaded in an SVG viewer supporting animation (such as Firefox, Opera, or Batik), demonstrates the intricate moving clockwork of a watch - and shows real time to boot! If loaded in Inkscape, the image is static, but instead you can freely edit any of the objects.

= Translations, tutorials, templates =

* Remarkable improvements are in the '''Danish''', '''Finnish''', '''Nepalese''' and the '''Vietnamese''' translations of the user interface. They all jumped from 0 to over 90 percent in a very short timespan.

* All people which are familiar with '''pig latin''' are now able to use Inkscape's user interface in that language. Isthay isway oughtbray otay usway ybay away ewnay anslatortray.

* Updated '''British English''', '''Catalan''', '''Czech''', '''Bulgarian''', '''French''', '''Danish''', '''Finnish''', '''German''', '''Brazilian Portuguese''' and '''Thai''', '''Vietnamese''' and '''Dzongkha''' translations.

* A new Esperanto translation added including default document template.

* Default Lithuanian template was not installed before, which is now fixed.

* New tutorial "Easter Eggs" by Steve Karg.

* Added Catalan default template and elements tutorial.

* Russian header and footer templates for tutorials are added.

* Several tutorial translations were updated, namely '''Catalan''', '''Brazilian Portuguese''', '''Russian''', '''German''', '''Danish''' and '''French'''.

* There are also new Russian and Japanese translations of Windows installer strings.

= Dependency changes =

* We have changed the '''GTK+''' requirement for compilation to version 2.8. However, it is highly recommended to use at least the version '''2.10.7''' because previous versions contain at least one crash bug which may cause Inkscape to crash after typing in a value into a spinbutton.

= Notable bugfixes =

* When deleting a node, neighboring smooth nodes are converted to cusp.

* Releasing the mouse button while dragging nodes using a tablet will now always release the nodes. Before this, a race condition could occur where dragging could continue after the mouse button was released.

* An object's mask and clipping path are now preserved after Simplify, Object/Stroke to path, or boolean operations.

* Ungrouping a group containing clipped/masked objects might sometime break the clip/mask (move it away); this is fixed.

* Transforming an object and its clone no longer behaves unexpectedly when they are both within a transformed group.

* User-supplied templates in ~/.inkscape/templates can now be SVGZ files in addition to SVG.

* Previously, Inkscape didn't check if there's enough free memory for its pixel buffers and could crash without warning due to insufficient memory e.g. upon zooming in. This problem became much worse after implementing Gaussian blur, because rendering blurred objects at high zooms may require a pixel buffer much bigger than the visible canvas. Now this situation is handled more gracefully: if a display operation requires more memory than available, or more than 100Mb (which corresponds to a 5000x5000 pixel buffer), it is skipped. This may result in blurred objects "disappearing" at high zooms. This is purely a display issue, however, and it never corrupts data; just zoom out (or reduce blur radius) and the disappeared object will show up OK.

* When resizing objects, scaling numbers in the statusbar are no longer overwritten by other text when pressing the modifier keys (Alt, Shift, Ctrl).

* To work around problems some users had with pressure-sensitive tablets ([http://sourceforge.net/tracker/index.php?func=detail&aid=1281512&group_id=93438&atid=604306 bug 1281512]), the pressure sensitivity can be disabled from the Misc tab of Inkscape Preferences dialog. After that, the tablet can still be used as a regular mouse.

* The layer widget in the statusbar used to lose its current layer after an effect run; this is fixed.

* When using different display resolutions or a dual screen setup, dialogs could be displayed off-screen; this is fixed: now Inkscape checks whether the saved position of the dialog is offscreen, if so it will move the dialog to the center of the screen. Note that this not solve all problems. If the dialog is still not visible, go to the [http://sourceforge.net/tracker/?func=detail&atid=604306&aid=1250236&group_id=93438 bug 1250236] where a procedure is given to make the dialog visible (by editing preferences.xml).

* Grid and guidelines no longer vanish when changing their color.

* Group transformation is now correctly re-applied when ungrouping and then undoing the ungroup operation.

* Text dialog no longer discards the style of the selected text.

* Inkscape no longer crashes when you try to unflow an empty flowed text.

* Thanks to patches submitted by users of our community, Inkscape can now be built on SGI IRIX 6.5.28, gcc 3.4.0 systems and on Tru64 systems.

= Known problems =

==== Problem with "Dialogs on Top" on Windows ====

* Although the "Dialogs on Top" option is now available on Windows (File > Inkscape Preferences > Windows), it does not work exactly as it should (yet!). When the document window is minimized, the dialogs remain visible, i.e. are not minimized together with the document window. Because of this, it is not possible to get the document window back by clicking its taskbar button. A workaround to this problem is to '''right-click the Inkscape taskbar button and select "Restore".''' We expect that future releases of GTK will solve this problem.

==== Spinbuttons may crash if you have GTK+ older than 2.10.7 ====

* You may experience crashes after typing in a value into a spinbutton if you have a version of GTK+ 2.10.6 or older. Upgrade your GTK+ to fix this. (This does not affect the Windows package as it comes with GTK+ 2.10.9.)

==== Numerical Python required for Perspective effect ====

* This effect will not work until you install a python module called '''numpy''' (Numerical Python). It can be downloaded at [http://numpy.scipy.org/ numpy.scipy.org]. The Windows package already contains this module.

==== Do not use a clone of an object as its clipping path/mask ====

* In this version, you cannot use an object's clone as its clipping path or mask. Either unlink the clone first, or clip one clone of a source object (not the source itself) by another clone of the same. Properly fixing this bug requires some deep changes in the code and therefore was postponed until after 0.45 so as not to delay the release.

==== Non-Unicode symbol fonts on Windows don't work ====

* On Windows, symbol fonts without a Unicode map do not work. This is a limitation of the Pango library that we use.

==== Problems with some Debian libgc-6.7 packages ====

* Inkscape will hang or crash when linked with the first Debian packaged version of the Boehm garbage collection library. This problem was fixed in version 1:6.7-2 of the package. If you have libgc 6.7 on your Debian-based system, make sure that you are using that version of the package or later.

==== Beware of defective 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. Update: this bug appears to be fixed in newer versions of gtk-engines. If you are affected by this problem please update to a newer version of gtk-engines. If problems persist then please inform the gtk-engines maintainers of the problem.

* A similar crash happens if the KDE Baghira theme or 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 =

* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

[[Category:Marketing]]

User:Luci

2006-09-06T08:38:35Z

Luci:

|-| (- |_ |_ () |/|/ () |^ |_ |) !

<nowiki>:.. :.: ::: :</nowiki>

Editing Inkscape's website

2006-09-06T07:50:42Z

Luci: fix of template example code display (d = d because div is blocked by the wiki spam filter)

Anyone can edit the Inkscape wiki.

Once you have developer-level access to the project, you can also help with maintenance of the non-wiki parts of the Inkscape website.

== SVN Checkout of the Website Module ==

To checkout the website cvs module:

: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

For more info, see [[WorkingWithSVN]].

== Testing your website changes locally ==

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:

:<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)

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.

Hopefully, you have apache configured properly and it is running.

== Making Your Changes Live on Inkscape.org ==

# Make your changes to your local inkscape_web module.
# Commit your changes, ensuring that you provide ample notes in your commit log message.
# ssh -l <your sf username> ssh.sourceforge.net *
# cd inkscape/inkscape_web
# ./publish_web.sh

(*)
If you haven't done this before, you need to set up a link to the inkscape_web folder in your home directory.
ln -s /home/groups/i/in/inkscape inkscape

== Adding News to the Site ==

If you have SVN access, you can add news to the site. First, you should add your signature to /includes/signatures.inc.

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:
<pre><nowiki>
<div class="item">
<h3>HEADER</h3>
MONTH DAY, YEAR
MESSAGE

<?php echo $[[SIG_YOURNAME]]; ?>
</div>
</nowiki></pre>
Add new paragraphs if needed and dont forget to change the signature.

If you want, translate the news to your language and save it in news/XX/<this-year>/<this-month>

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:



Make your changes live as described above.

== Adding Screenshots to the Site ==

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.

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.

Naming convention is:

:inkscape-<version>-<id>-<name>.png
:inkscape-<version>-<id>-<name>_thumb.png

Example:

:inkscape-0.43-01-myfeature.png
:inkscape-0.43-01-myfeature_thumb.png

<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.
(NOTE: <id> wasnt there before. but i suggest using it beginning with 0.43)

save your shot into the "screenshots/gallery" folder, the thumb into "screenshots/gallery/thumbs".

Once the graphics are in the right folder, my lovely PHP script will display them automatically on the main page of the website.
They also appear on the screenshots/index.php page, therefore you must create a description file:

:inkscape-<version>-<id>-<name>.en

You may also create translations of description files. Just replace .en with the language code. Example:

:inkscape-0.43-01-myfeature.en
:inkscape-0.43-01-myfeature.de
:inkscape-0.43-01-myfeature.es

Store them in "screenshots/gallery/info"

Then make sure that you add your new images and description files and any changes to the SVN repository. For more info, see [[WorkingWithSVN]].

== Translating the Inkscape Website ==

1. Do a CVS checkout of the website module.

IMPORTANT: all files you change MUST be UTF-8 encoded!!!
else, you will get broken output.
See UT-8 note below, please.

2. Add your language by these steps:
- update the following line includes/header.php
$LANGUAGES = array("en", "de", "es"); // available languages

- 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.

- Add a line to css/base.css, similar to the following: (place your flag 50px left of the others)
#lang-xx { left:225px; }

- Add a link for your flag in includes/header.php

- create a copy of includes/localized-en.inc for your language. (like includes/localized-fr.inc) and translate the values of the strings.

- copy and translate index.en-header.php to your language.

- 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)

- you may add a signature to includes/signatures.inc and use it for news you create.

3. Look into other pages to see what needs to be done to translate them. (in general you need to create an inclusion file)
Files you need to translate: (at least you must create a copy for your language, or those pages will fail to open)
discussion-en.inc
download-en.inc
mailing_lists-en.inc
report_bugs-en.inc
submit2webmaster-en.inc
submit2webmaster-en-form.inc
doc/index-en.inc
status/index-en.inc

You also may translate news, screenshot comments and status files.

Note: The tutorial translations in the doc/ directory are handled
separately from the website translation. These are the files in
inkscape_web/doc/*/ that have .XX.html extensions. You do not need
to do anything about these pages.

Note: The translation of doxygen, wiki, and the various SF pages
are separate from the website translation. You do not need to do
anything about these pages.

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).
You do this by adding a file like /news/en/200x/xx/0xx.inc and write your announcement.

IMPORTANT: all files you change MUST be UTF-8 encoded!!!
else, you will get broken output.
See UT-8 note below, please.

Note: Even if the announcement does not need to be translated,
you should copy it to your languages folder also.
Reason: Same news must have same file names. If your announcement
is 010.inc, and then the next news is 011.inc, if you translate
that news only, your announcement will no more be shown. This is
because if you have 11 localized news and there are 12 in /en/,
the 11th will be shown in english. Now, if the 11th file in your
folder is the translation of the 12th file in /en/, it will be
displayed wrong

6. If you have CVS access, then commit your changes to the site. See the Website Editing and Working With CVS documentation for directions.

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.

== There are no UTF-8 entities !!! ==

As different people have talked about UTF-8 entities, this should be clarified: THERE IS NO SUCH THING!

An accented letter can be stored as:

* a "HTML entity": <pre> & (& a m p ;) --- ř (& # 3 4 5 ;) --- Ä (& A u m l ;)</pre>
* "character stored as UTF-8": & ř Ä
* (and a multitude of other conflicting standards, which the above two were designed to make obsolete).

HTML entities are a (somewhat) human readable transliteration.
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.

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.

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.)

Please use UTF-8 encoding!
Please do not use HTML-entities! We should all use the same system. If you have questions about this, please ask.

Reference: HTML Entities: http://www.w3schools.com/tags/ref_entities.asp

== See also ==

* [[WebSiteTranslation]]

[[Category:Help Wanted]]

Working with SVN

2006-09-06T07:38:39Z

Luci: + by

(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 by 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''

[[Category:Developer Documentation]]

Editing Inkscape's website

2006-09-06T07:36:41Z

Luci: - See

Anyone can edit the Inkscape wiki.

Once you have developer-level access to the project, you can also help with maintenance of the non-wiki parts of the Inkscape website.

== SVN Checkout of the Website Module ==

To checkout the website cvs module:

: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

For more info, see [[WorkingWithSVN]].

== Testing your website changes locally ==

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:

:<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)

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.

Hopefully, you have apache configured properly and it is running.

== Making Your Changes Live on Inkscape.org ==

# Make your changes to your local inkscape_web module.
# Commit your changes, ensuring that you provide ample notes in your commit log message.
# ssh -l <your sf username> ssh.sourceforge.net *
# cd inkscape/inkscape_web
# ./publish_web.sh

(*)
If you haven't done this before, you need to set up a link to the inkscape_web folder in your home directory.
ln -s /home/groups/i/in/inkscape inkscape

== Adding News to the Site ==

If you have SVN access, you can add news to the site. First, you should add your signature to /includes/signatures.inc.

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:
<nowiki><pre>
<d i v class="item">
<h3>HEADER</h3>
MONTH DAY, YEAR
MESSAGE

<?php echo $[[SIG_YOURNAME]]; ?>
</d i v>
</pre></nowiki>
Add new paragraphs if needed and dont forget to change the signature.

If you want, translate the news to your language and save it in news/XX/<this-year>/<this-month>

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:



Make your changes live as described above.

== Adding Screenshots to the Site ==

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.

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.

Naming convention is:

:inkscape-<version>-<id>-<name>.png
:inkscape-<version>-<id>-<name>_thumb.png

Example:

:inkscape-0.43-01-myfeature.png
:inkscape-0.43-01-myfeature_thumb.png

<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.
(NOTE: <id> wasnt there before. but i suggest using it beginning with 0.43)

save your shot into the "screenshots/gallery" folder, the thumb into "screenshots/gallery/thumbs".

Once the graphics are in the right folder, my lovely PHP script will display them automatically on the main page of the website.
They also appear on the screenshots/index.php page, therefore you must create a description file:

:inkscape-<version>-<id>-<name>.en

You may also create translations of description files. Just replace .en with the language code. Example:

:inkscape-0.43-01-myfeature.en
:inkscape-0.43-01-myfeature.de
:inkscape-0.43-01-myfeature.es

Store them in "screenshots/gallery/info"

Then make sure that you add your new images and description files and any changes to the SVN repository. For more info, see [[WorkingWithSVN]].

== Translating the Inkscape Website ==

1. Do a CVS checkout of the website module.

IMPORTANT: all files you change MUST be UTF-8 encoded!!!
else, you will get broken output.
See UT-8 note below, please.

2. Add your language by these steps:
- update the following line includes/header.php
$LANGUAGES = array("en", "de", "es"); // available languages

- 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.

- Add a line to css/base.css, similar to the following: (place your flag 50px left of the others)
#lang-xx { left:225px; }

- Add a link for your flag in includes/header.php

- create a copy of includes/localized-en.inc for your language. (like includes/localized-fr.inc) and translate the values of the strings.

- copy and translate index.en-header.php to your language.

- 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)

- you may add a signature to includes/signatures.inc and use it for news you create.

3. Look into other pages to see what needs to be done to translate them. (in general you need to create an inclusion file)
Files you need to translate: (at least you must create a copy for your language, or those pages will fail to open)
discussion-en.inc
download-en.inc
mailing_lists-en.inc
report_bugs-en.inc
submit2webmaster-en.inc
submit2webmaster-en-form.inc
doc/index-en.inc
status/index-en.inc

You also may translate news, screenshot comments and status files.

Note: The tutorial translations in the doc/ directory are handled
separately from the website translation. These are the files in
inkscape_web/doc/*/ that have .XX.html extensions. You do not need
to do anything about these pages.

Note: The translation of doxygen, wiki, and the various SF pages
are separate from the website translation. You do not need to do
anything about these pages.

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).
You do this by adding a file like /news/en/200x/xx/0xx.inc and write your announcement.

IMPORTANT: all files you change MUST be UTF-8 encoded!!!
else, you will get broken output.
See UT-8 note below, please.

Note: Even if the announcement does not need to be translated,
you should copy it to your languages folder also.
Reason: Same news must have same file names. If your announcement
is 010.inc, and then the next news is 011.inc, if you translate
that news only, your announcement will no more be shown. This is
because if you have 11 localized news and there are 12 in /en/,
the 11th will be shown in english. Now, if the 11th file in your
folder is the translation of the 12th file in /en/, it will be
displayed wrong

6. If you have CVS access, then commit your changes to the site. See the Website Editing and Working With CVS documentation for directions.

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.

== There are no UTF-8 entities !!! ==

As different people have talked about UTF-8 entities, this should be clarified: THERE IS NO SUCH THING!

An accented letter can be stored as:

* a "HTML entity": <pre> & (& a m p ;) --- ř (& # 3 4 5 ;) --- Ä (& A u m l ;)</pre>
* "character stored as UTF-8": & ř Ä
* (and a multitude of other conflicting standards, which the above two were designed to make obsolete).

HTML entities are a (somewhat) human readable transliteration.
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.

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.

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.)

Please use UTF-8 encoding!
Please do not use HTML-entities! We should all use the same system. If you have questions about this, please ask.

Reference: HTML Entities: http://www.w3schools.com/tags/ref_entities.asp

== See also ==

* [[WebSiteTranslation]]

[[Category:Help Wanted]]

WebSiteTranslation

2006-09-05T14:10:23Z

Luci: og -> of

Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

= Translation of web site =
# There are two ways of getting files that you need to translate website:
## 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!
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
##* screenshots/*
##* showcase/*
##* docs/* (at least main page for docs)
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
== Translating news and status ==
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Wiki =

Translating the pages of the wiki is quite straightforward.

In a few steps :
- 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]].
- then, start a new page for each wiki page translation, and link translated page to the main page of your language.

Don't forget to get some information about wiki syntax before creating/modifying some wiki pages.

= Release notes =
[[http://wiki.inkscape.org/wiki/index.php/Release_Notes Release notes]] simply consist in a wiki page.
You can apply the process stated [[http://wiki.inkscape.org/wiki/index.php/WebSiteTranslation#Wiki above]] for translating this content.

= Translation information =
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

CompilingMandrake

2005-03-01T21:15:47Z

Luci: *

== Building RPM Package on Mandrakelinux 10.1 ==

I did it with the src.rpm package available at sf.net.
The RPM rebuild process is pretty similar to compiling from source but first we need to satisfy the dependencies (the fastest way is Mandrakelinux's ''urpmi''):

# download the [http://prdownloads.sourceforge.net/inkscape/inkscape-0.41-1.src.rpm?download download Inkscape's src.rpm] at sourceforge.net
# <code>urpmi gtk2-devel</code> (Inkscape 0.41 needs gtk2-devel >= 2.4.0; use [http://easyurpmi.zarb.org/ urpmi source "main"] if you haven't got a CD/DVD with devel packages)
# <code>urpmi libpng3</code> (libpng >= 1.2 is needed)
# now the '''libgc 6.4+''' is needed. I didn't found or somewhat missed the [http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/ Hans Boehm's gc] package for mdk 10.1, so i downloaded and compiled it like this: <pre>./configure --prefix=/usr
make
su
make install</pre> (in fact i used <code>checkinstall</code> instead of <code>make install</code> and then <code>urpmi /usr/src/RPM/RPMS/i586/gc-6.4-1luc.i586.rpm</code>)
# <code>urpmi libxml2-devel</code>
# <code>urpmi libxslt-devel</code>
# <code>urpmi libsigc++2.0_0-devel</code> (to be found at urpmi source "contrib")
# <code>urpmi libgtkmm2.4_1-devel</code> (also urpmi source "contrib")
# <code>urpmi popt-devel</code> (urpmi source "main")
# finally you can perform successfully: <code>rpm -rebuild inkscape-0.41-1.src.rpm</code> (the resulting RPM package will be probably stored as <code>/usr/src/RPM/RPMS/i586/inkscape-0.41-1.i586.rpm</code> according to your RPM settings)

<div align="right">''luci''</div>

Compiling Inkscape

2005-03-01T20:04:11Z

Luci: *

Hopefully, Inkscape will compile right out of the box. If it doesn't, well that's what this page is for.

Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to
make mention of what version of the code you're trying to compile, the distribution you're running,
and other such information that might be pertinent.

If legitimate bugs are found or patches developed, please move them to the tracker at Sourceforge
rather than inlining them here.

= OS & Distribution Specific =
* '''Linux'''
** [[CompilingFedora|Fedora]]
** [[CompilingGentoo|Gentoo]]
** [[CompilingDebian|Debian]]
** [[CompilingYellowDog|Yellow Dog]]
** [[CompilingSuse|Suse]]
** [[CompilingSlackware|Slackware]]
** [[CompilingYoper|Yoper]]
** [[CompilingMandrake|Mandrakelinux]]
* [[CompilingMacOsX|Mac OS X]]
* [[Win32Port|Windows]]
* [[CompilingSPARC|SPARC]]
* [[CompilingSunSolaris|Sun Solaris]]
* [[CompilingStatic|Static Compiles]]

= Package Config (pkg-config) =

If you must compile and install any of these from source, you may find an error like this when trying to
compile them or Inkscape itself:

checking for gtk+-2.0 >= 2.0.0 libxml-2.0 >= 2-2.4.24 sigc++-1.2 gtkmm-2.0... Package gtkmm-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkmm-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkmm-2.0' found

A solution is to set the PKG_CONFIG_PATH variable as so:

for bash:
export PKG_CONFIG_PATH=/usr/local/bin/pkgconfig:/usr/lib/pkgconfig
for csh:
setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig

A good place to put this line is in your .bashrc or .cshrc file

= Getting and Installing Source packages =

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

$ make install

== Boehm-GC ==

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.4.tar.gz

[Note that for old 0.40CVS development versions we used the C++ version of gc, so you need to compile it with the --enable-cplusplus; we didn't include that version in any of the official releases though.]

Also, if searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* libgc-devel
* boehm-gc (on Gentoo)

== libSigc++ ==

Source: http://sourceforge.net/project/showfiles.php?group_id=1970&package_id=76644

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

== GlibMM ==

Source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.4/

== GtkMM ==

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.4/

= Developer Compilation =

Plain vanilla compilation is done as documented in INSTALL; ./autogen.sh (optionally); ./configure; make; su && make test; make install (optional). See INSTALL for more on that.

But if you're going to be doing a lot of development, there's some tricks and techniques you should know,
to get best results.

# Turn off optimization
# Use ccache for faster compilation
# Set up a separate build directory (nice for testing both gcc and g++, or cross compiling)
# Use the -j N flag to optimize for the number of processors in your machine, with N = 1 + no. proc's

Example: Setting up both gcc and g++ build environments (in separate tree), and using ccache for faster
compilations on a dual-processor machine, with no optimization, assuming /bin/bash:

mkdir build-gcc build-g++
cvs checkout inkscape
cd inkscape
libtoolize --copy --force
./autogen.sh
cd ../build-gcc
CFLAGS='-g -O0 -Wall' CC='ccache gcc' ../inkscape/configure
cd ../build-g++
CXXFLAGS='-g -O0 -Wall' CXX='ccache g++' ../inkscape/configure
cd build-gcc && make -j 3
cd build-g++ && make -j 3

Turning off just optimization (which can produce strange results in debuggers):

export CC=g++
export CXXFLAGS='-g -O0 -Wall'
export CFLAGS='-g -O0 -Wall'
./configure