Inkscape Wiki - User contributions [en]

Tracking Dependencies

2012-03-15T08:14:09Z

Kaeso: /* Distros */ opensuse

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.47
! v 0.48.x
! trunk
|-
| Boehm-GC
| ?
| 6.4
| 6.4
|-
| Cairo
| ?
| ?
| 1.10
|-
| GDK
| ?
| ?
| ?
|-
| GDL1
| N/A
| N/A
| (3.4)2
|-
| Glib
| ''2.16*''
| ''2.16*''
| 2.24
|-
| glibmm
| ?
| ?
| ?
|-
| GTK+
| ''2.12*'' < 3.0
| ''2.12*'' < 3.0
| 2.20 < 3.0
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency'' 
1Inkscape has an internal fork of GDL that we will eventually remove. GDL 3.4 will contain all the new functionality that was introduced in our fork. However, this will also introduce a dependency upon GTK+ 3. 
2We can't actually build against GDL 3.4 until we are able to support GTK+ 3.

== Functions used ==

{| class="wikitable"
|-
! Function
! Lib
! Since
! Required
|-
| g_timeout_add_seconds
| Glib
| 2.14
| ?
|}

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! glib
! glibmm
! gtk+
! gtkmm
! pango
! gdl
! lcms
! libsigc++
! libgc
|-
|Windows Devlibs
| 1.10.2
| 2.28.8
| 2.26.0
| 2.24.8
| 2.22.0
| 1.28.3
| (none)
| 1.17
| 2.2.4.2
| 7.1
|-
| style="background:Orange;"| Debian 6.0 (Squeeze, stable) EOL ~2014?
| style="background:Orange;"| 1.8.10
| 2.24.2
| 2.24.2
| 2.20.1
| 2.20.3
| 1.28.3
| 2.30.1
| 1.18
| 2.2.4.2
| 6.8
|-
| Fedora 15 EOL 2012-06
| 1.10.2
| 2.28.6
| 2.28.6
| 2.24.4 3.0.9
| 2.24.0
| 1.28.4
| 3.0.0
| 1.19 2.2
| 2.2.9
| 7.2~alpha
|-
| Fedora 16
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.8 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.3
| 2.2.10
| 7.2~alpha
|-
| Open SuSE 11.4 EOL 2012-09-15
| 1.10.2
| 2.28.0
| 2.25.5
| 2.22.1
| 2.22.0
| 1.28.3
| 2.30.1
| 1.19 2.1
| 2.2.8
| 7.1
|-
| Open SuSE 12.1 EOL 2013-05-15
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.7 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.2
| 2.2.10
| 7.1
|-
| style="background:Orange;"| Ubuntu 10.04 LTS (Lucid) EOL 2013-04 (Desktop)
| style="background:Orange;"| 1.8.10
| 2.24.0
| 2.24.1
| 2.20.0
| 2.20.2
| 1.28.0
| 2.30.0
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 10.10 (Maverick) EOL 2012-04-10
| 1.10.0
| 2.26.1
| 2.25.2
| 2.22.0
| 2.20.3
| 1.28.2
| 2.30.0
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 11.04 (Natty) EOL 2012-10
| 1.10.2
| 2.28.6
| 2.28.0
| 2.24.4 3.0.8
| 2.24.0
| 1.28.4
| 2.30.1
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 11.10 (Oneiric) EOL 2013-04
| 1.10.2
| 2.30.0
| 2.30.0
| 2.24.6 3.2.0
| 2.24.2 3.2.0
| 1.29.3
| 3.1.5
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 12.04 (Precise) EOL 2017-04 (as of 2012-03-08)
| 1.10.2
| 2.31.20
| 2.31.20
| 2.24.10 3.3.18
| 2.24.2 3.3.18
| 1.29.5
| 3.3.4
| 1.19 2.2
| 2.2.10
| 7.1
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape 0.48 unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|}

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2012-03-15T08:08:28Z

Kaeso: /* Distros */ fedora

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.47
! v 0.48.x
! trunk
|-
| Boehm-GC
| ?
| 6.4
| 6.4
|-
| Cairo
| ?
| ?
| 1.10
|-
| GDK
| ?
| ?
| ?
|-
| GDL1
| N/A
| N/A
| (3.4)2
|-
| Glib
| ''2.16*''
| ''2.16*''
| 2.24
|-
| glibmm
| ?
| ?
| ?
|-
| GTK+
| ''2.12*'' < 3.0
| ''2.12*'' < 3.0
| 2.20 < 3.0
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency'' 
1Inkscape has an internal fork of GDL that we will eventually remove. GDL 3.4 will contain all the new functionality that was introduced in our fork. However, this will also introduce a dependency upon GTK+ 3. 
2We can't actually build against GDL 3.4 until we are able to support GTK+ 3.

== Functions used ==

{| class="wikitable"
|-
! Function
! Lib
! Since
! Required
|-
| g_timeout_add_seconds
| Glib
| 2.14
| ?
|}

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! glib
! glibmm
! gtk+
! gtkmm
! pango
! gdl
! lcms
! libsigc++
! libgc
|-
|Windows Devlibs
| 1.10.2
| 2.28.8
| 2.26.0
| 2.24.8
| 2.22.0
| 1.28.3
| (none)
| 1.17
| 2.2.4.2
| 7.1
|-
| style="background:Orange;"| Debian 6.0 (Squeeze, stable) EOL ~2014?
| style="background:Orange;"| 1.8.10
| 2.24.2
| 2.24.2
| 2.20.1
| 2.20.3
| 1.28.3
| 2.30.1
| 1.18
| 2.2.4.2
| 6.8
|-
| Fedora 15 EOL 2012-06
| 1.10.2
| 2.28.6
| 2.28.6
| 2.24.4 3.0.9
| 2.24.0
| 1.28.4
| 3.0.0
| 1.19 2.2
| 2.2.9
| 7.2~alpha
|-
| Fedora 16
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.8 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.3
| 2.2.10
| 7.2~alpha
|-
| Open SuSE 11.4 EOL 2012-09-15
| 1.10.2
| 2.28.0
| 2.25.5
| 2.22.1
| 2.22.0
| 1.28.3
| 2.30.1
| 1.19 2.1
| 2.2.8
|
|-
| Open SuSE 12.1 EOL 2013-05-15
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.7 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.2
| 2.2.10
|
|-
| style="background:Orange;"| Ubuntu 10.04 LTS (Lucid) EOL 2013-04 (Desktop)
| style="background:Orange;"| 1.8.10
| 2.24.0
| 2.24.1
| 2.20.0
| 2.20.2
| 1.28.0
| 2.30.0
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 10.10 (Maverick) EOL 2012-04-10
| 1.10.0
| 2.26.1
| 2.25.2
| 2.22.0
| 2.20.3
| 1.28.2
| 2.30.0
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 11.04 (Natty) EOL 2012-10
| 1.10.2
| 2.28.6
| 2.28.0
| 2.24.4 3.0.8
| 2.24.0
| 1.28.4
| 2.30.1
| 1.18
| 2.2.4.2
| 6.8
|-
| Ubuntu 11.10 (Oneiric) EOL 2013-04
| 1.10.2
| 2.30.0
| 2.30.0
| 2.24.6 3.2.0
| 2.24.2 3.2.0
| 1.29.3
| 3.1.5
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 12.04 (Precise) EOL 2017-04 (as of 2012-03-08)
| 1.10.2
| 2.31.20
| 2.31.20
| 2.24.10 3.3.18
| 2.24.2 3.3.18
| 1.29.5
| 3.3.4
| 1.19 2.2
| 2.2.10
| 7.1
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape 0.48 unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|}

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2012-03-14T10:29:41Z

Kaeso: /* Distros */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.47
! v 0.48.x
! trunk
|-
| Boehm-GC
| ?
| 6.4
| 6.4
|-
| Cairo
| ?
| ?
| 1.10
|-
| GDK
| ?
| ?
| ?
|-
| GDL1
| N/A
| N/A
| (3.4)2
|-
| Glib
| ''2.16*''
| ''2.16*''
| 2.24
|-
| glibmm
| ?
| ?
| ?
|-
| GTK+
| ''2.12*'' < 3.0
| ''2.12*'' < 3.0
| 2.20 < 3.0
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency'' 
1Inkscape has an internal fork of GDL that we will eventually remove. GDL 3.4 will contain all the new functionality that was introduced in our fork. However, this will also introduce a dependency upon GTK+ 3. 
2We can't actually build against GDL 3.4 until we are able to support GTK+ 3.

== Functions used ==

{| class="wikitable"
|-
! Function
! Lib
! Since
! Required
|-
| g_timeout_add_seconds
| Glib
| 2.14
| ?
|}

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! glib
! glibmm
! gtk+
! gtkmm
! pango
! gdl
! lcms
! libsigc++
! libgc
|-
|Windows Devlibs
| 1.10.2
| 2.28.8
| 2.26.0
| 2.24.8
| 2.22.0
| 1.28.3
| (none)
| 1.17
| 2.2.4.2
| 7.1
|-
| style="background:Orange;"| Debian 6.0 (Squeeze, stable) EOL ~2014?
| style="background:Orange;"| 1.8.10
| 2.24.2
| 2.24.2
| 2.20.1
| 2.20.3
| 1.28.3
| 2.30.1
| 1.18
| 2.2.4.2
| 6.4
|-
| Fedora 15 EOL 2012-06
| 1.10.2
| 2.28.6
| 2.28.6
| 2.24.4 3.0.9
| 2.24.0
| 1.28.4
| 3.0.0
| 1.19 2.2
| 2.2.9
|-
| Fedora 16
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.8 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.3
| 2.2.10
|-
| Open SuSE 11.4 EOL 2012-09-15
| 1.10.2
| 2.28.0
| 2.25.5
| 2.22.1
| 2.22.0
| 1.28.3
| 2.30.1
| 1.19 2.1
| 2.2.8
|-
| Open SuSE 12.1 EOL 2013-05-15
| 1.10.2
| 2.30.1
| 2.30.0
| 2.24.7 3.2.1
| 2.24.2 3.2.0
| 1.29.4
| 3.2.0
| 1.19 2.2
| 2.2.10
|-
| style="background:Orange;"| Ubuntu 10.04 LTS (Lucid) EOL 2013-04 (Desktop)
| style="background:Orange;"| 1.8.10
| 2.24.0
| 2.24.1
| 2.20.0
| 2.20.2
| 1.28.0
| 2.30.0
| 1.18
| 2.2.4.2
|-
| Ubuntu 10.10 (Maverick) EOL 2012-04-10
| 1.10.0
| 2.26.1
| 2.25.2
| 2.22.0
| 2.20.3
| 1.28.2
| 2.30.0
| 1.18
| 2.2.4.2
|-
| Ubuntu 11.04 (Natty) EOL 2012-10
| 1.10.2
| 2.28.6
| 2.28.0
| 2.24.4 3.0.8
| 2.24.0
| 1.28.4
| 2.30.1
| 1.18
| 2.2.4.2
|-
| Ubuntu 11.10 (Oneiric) EOL 2013-04
| 1.10.2
| 2.30.0
| 2.30.0
| 2.24.6 3.2.0
| 2.24.2 3.2.0
| 1.29.3
| 3.1.5
| 1.19 2.2
| 2.2.10
|-
| Ubuntu 12.04 (Precise) EOL 2017-04 (as of 2012-03-08)
| 1.10.2
| 2.31.20
| 2.31.20
| 2.24.10 3.3.18
| 2.24.2 3.3.18
| 1.29.5
| 3.3.4
| 1.19 2.2
| 2.2.10
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape 0.48 unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|}

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

AnnouncePlanning046

2008-03-10T20:15:17Z

Kaeso: (...everywhere...)

Planning the PR for the 0.46 release is done here...

=Tasks=
{| class="wikitable" style="text-align:center"
|-
! Task
! Performer
! Projected Date of completion
! Status
|-
| Informal PR text
| Collaborated on this wiki page
| 18th Feb 2008
| 50%
|-
| Formal PR text
| Collaborated on this wiki page
| 18th Feb 2008
| 50%
|-
| Interview
| [[user:Prokoudine|Prokoudine]]
| progressing
| 90%
|}

=Announcement Process=
# Create new news posts (using the small overview below) on all the relevant social bookmarking sites: digg, slashdot etc.
# Create a new Page on the Inkscape website that has the Formal Announcement on it (for linking purposes) have links back to the socal bookmarking stories for the release.
# Post the official announcement to the Inkscape News on the website, the and the relevant inkscape lists (announce, user, deleveloper)
# Send out the informal announcement (include a link to the webpage with the formal announcement)
# Send out the formal announcement. (include a link to the webpage with the formal announcement)

=Press Release Translations=
Once the English Press Release text has been finalised, translation can start into other languages.

The current goal for this PR text is to have the english version finished by 18th Feb 2008.

Please Create a new Wiki page for planning / translating the 0.46 PR in your language here:

=Press Release Text=
==Small Overview==
Inkscape, the open source vector graphics editor has released version 0.46. Major updates include native PDF support, a paint bucket tool, color profiles, dockable dialogs, SVG Filters, Live Path Effects, and many more features and updates.

==Informal==
===Inkscape Announces 0.46 Release :: http://www.inkscape.org :: Draw Freely.===
The Inkscape community today is announcing the release of the newest version of its open source vector graphics editor. Inkscape 0.46 is a major update that introduces native PDF support. The implementation of PDF support in Inkscape provides an easy, open source solution to editing PDF documents.

A ton of new features and performance improvements are included in this release. Dialogs boxes now have the ability to be docked to the side. Gradients can be edited completely on-canvas now. The new Paint Bucket Tool fills bounded areas with colors and allows quick recoloring of existing objects. A new 3D Box tool helps with creating perspective-correct drawings. A new Tweak tool gives a intuitive method for modifying node paths. The new Live Path Effects feature creates "brushes" and attaches organic effects to paths. Improvements to color management includes support for color spaces other than just sRGB. Most SVG Filters are now implemented, and now have a dedicated UI.

===Download Inkscape 0.46 for Linux, Windows or Mac OS X===
http://sourceforge.net/project/showfiles.php?group_id=93438

===For More Information===
Complete Release Notes for 0.46, http://wiki.inkscape.org/wiki/index.php/ReleaseNotes046 
Community Contributed Screenshots, http://inkscape.org/screenshots/

===About Inkscape===
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

==Formal==
===The Inkscape Community Releases Inkscape 0.46===

New York, NY, '''INSERT DATE OF RELEASE HERE****yyyy/mm/dd****''' -- The Inkscape community today announced the
release of Inkscape 0.46, the newest stable version of their
multi-platform, open-source vector graphics editor.

This newest Inkscape release includes a plethora of new tools and
improvements, beginning with native PDF support. Developed with the
assistance of the 2007 Google Summer of Code, and utilising the open
source Cairo and Poppler libraries, Inkscape 0.46 provides an easy, open
source tool for editing and creating PDF documents.

The 2007 Google Summer of Code also produced the new 3D Box tool and Live Path Effects.

As its name suggests, the 3D Box tool makes it possible to create and
edit the perspective of three-dimensional boxes.

Live Path Effects can be used to create "brushes" and organic effects
while keeping the original paths editable. [This needs to be more
concrete as well.]

The new Tweak Tool allows you to modify objects similar to molding clay.

As well, gradient editing is now done visually and on-canvas. Gradient
stops are depicted as nodes, and multiple nodes can be selected and
moved simultaneously.

Colour management has also been improved, with initial support for
colour spaces other than sRGB, including Adobe RGB and calibrated CMYK.
This makes it possible to use calibrated colour values, including CMYK
values, that are preserved across applications.

The new Paint Bucket Tool allows bounded areas to be filled with colour
at the click of a mouse button. This new tool creates a closed-path
based on the visible canvas and is useful for quickly colouring line
drawings.

The Gaussian Blur filter, introduced in Inkscape 0.45, was the first SVG
Filter. Inkscape 0.46 expands on this with Offset, Blend, Diffuse
Lighting, Specular Lighting and Turbulence primitives. There is also a
new, dedicated user interface for creating and altering filters based on
these new primitives.

Finally, Inkscape 0.46 introduces workflow and user interface
improvements. Dialogue boxes can now be docked and minimised to a
side-panel, reducing visual clutter and making the relationship between
documents and interaction choices clearer, especially when working on
multiple documents in separate Inkscape instances.

With 0.46 out, the Inkscape community is already working on future
releases, including the upcoming 0.47. Full compatibility with SVG
Mobile/Tiny is slated for version 0.50 and version 1.0 will include
complete W3C SVG 1.1 compliance.

Inkscape users have contributed many features and ideas to the project
and the community invites anyone to contribute to the project. The more
help Inkscape gets, the sooner we reach these goals.

<strike>
The Inkscape community today announced the release of the newest version of their multi platform, open source vector graphics editor, Inkscape 0.46. The latest installment of Inkscape is a feature filled release that introduces a large number of new tools and improvements, including native PDF support. Utilizing the open source libraries of Cairo and Poppler, and developed with the assistance of the Google Summer of Code, Inkscape's PDF support provides an easy, open source solution to editing PDF documents.

Inkscape 0.46 introduces improvements that provides enhanced work flow that complements creativity. Dialogs boxes now have the ability to be docked and minimized to a side panel, enhancing the user experience when editing multiple documents in separate inkscape instances. Gradient editing can now be done visually on-canvas, with gradient stops being depicted as nodes and the abilty to select and move multiple stops simultaneously. Color management has also been improved, with initial support for color definitions that use a colorspace other than sRGB (for example Adobe RGB, or calibrated CMYK colors). This allows for the use of calibrated color spaces, including using CMYK values that are preserved across applications.

The new Paint Bucket Tool allows bounded areas to be quickly filled in with color. It creates a closed path based on the visible canvas and is useful for quickly coloring line drawings. Additional functionality produced by the Google Summer of Code 2007 include the new 3D Box tool, the Tweak tool and Live Path Effects. The Tweak Tool allows smooth and natural change of the shape or style of objects directly on canvas. Live Path Effects can be used to create "brushes" and all kinds of organic effects, while keeping the original paths editable.

Inkscape 0.45 introduced SVG Filters with the Gussian Blur filter primitive; Inkscape 0.46 greatly expands on this by adding the Offset, Blend, Diffuse Lighting, Specular Lighting and Turbulence primitives. As well, there is a new dedicated user interface for creation and alteration of complex filters based on these primitives.

The Inkscape community is now working on the upcoming 0.47 release and invites you to contribute to the project. Beyond that, Inkscape is pushing for full compatibility with SVG Mobile/Tiny by version 0.50, and full W3C SVG 1.1 compliance by Inkscape 1.0. Users have also contributed many great feature ideas in addition to this; the more help the project receives, the faster these goals and ideas can be achieved.
</strike>

===Download Inkscape 0.46 for Linux, Windows or Mac OS X===
http://sourceforge.net/project/showfiles.php?group_id=93438

===For More Information===

Complete Release Notes for 0.46, http://wiki.inkscape.org/wiki/index.php/ReleaseNotes046 
Community Contributed Screenshots, http://inkscape.org/screenshots/

===About Inkscape===
Inkscape is a multi platform, open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

=Places to Announce=

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

== Receive small overview ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Digg
|ryanlerch
|digg.com someone needs to post a short excerpt anouncing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|slashdot.org
|ryanlerch
|submit a new news item.
|-
|-style="border-bottom:white 2px solid;"
|newsvine.com/
|ryanlerch
|submit a new news item.
|-
|}

== Receive Informal PR ==
=== Open Source Community ===
{| style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|- style="border-bottom:white 2px solid;"
|gnome office list
|
|gnome-office-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|svg developers yahoo group
|
|svg-developers at yahoo dot com must join the list to send (rejon is on)
|-style="border-bottom:white 2px solid;"
|SVG.org
|ryanlerch
|antoine at graougraou dot com, svg at steltenpower dot com
|-style="border-bottom:white 2px solid;"
|svgfaq.org
|ryanlerch
|maxdunn at siliconpublishing dot com
|-style="border-bottom:white 2px solid;"
|svgfoundation.org
|ryanlerch
|michael (at) svgfoundation.org
|-style="border-bottom:white 2px solid;"
|cairo list
|ryanlerch
|cairo at cairographics dot org
|-style="border-bottom:white 2px solid;"
|gnome-list
|ryanlerch
|gnome-announce-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|Scribus List (mrdocs)
|ryanlerch
|scribus at nashi dot altmuehlnet dot de
|-style="border-bottom:white 2px solid;"
|osnews.com
|ryanlerch
|http://osnews.com/submit.php
|-style="border-bottom:white 2px solid;"
|desktoplinux.com
|ryanlerch
|http://desktoplinux.com/contactus.html
|-style="border-bottom:white 2px solid;"
|SVG Cafe.com
|ryanlerch
|http://www.svg-cafe.com/ join and post to news section
|-style="border-bottom:white 2px solid;"
|Freshmeat.net
|
|a new release has to be added to inkscape's freshmeat profile
|-style="border-bottom:white 2px solid;"
|gnome footnotes
|
|http://gnomedesktop.org/node/add/story
|-style="border-bottom:white 2px solid;"
|scale-a-vector
|ryanlerch
|kukofka at scale-a-vector dot de http://www.scale-a-vector.de/cont.htm
|-style="border-bottom:white 2px solid;"
|http://dot.kde.org
|ryanlerch
|http://dot.kde.org/addPostingForm
|-style="border-bottom:white 2px solid;"
|revelinux.com
|ryanlerch
|theobroma at revelinux dot com
|-style="border-bottom:white 2px solid;"
|}

=== Broader Inkscape & Art Community ===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Inkscape deviantart group
|ScislaC
|http://inkscape.deviantart.com/
|
|-style="border-bottom:white 2px solid;"
|the inkscape forum
| ryanlerch
|http://www.inkscapeforum.com/ run by microUgly
|-style="border-bottom:white 2px solid;"
|inkscape tutorials blog
|ryanlerch
|http://inkscapetutorials.wordpress.com/
|-
|-style="border-bottom:white 2px solid;"
|open clip art library list
|ryanlerch
|clipart@freedesktop.org
|-style="border-bottom:white 2px solid;"
|open clip art library news
|ryanlerch
|
|-style="border-bottom:white 2px solid;"
|artdc.org forum
|johncoswell
|http://www.artdc.org/
|-style="border-bottom:white 2px solid;"
|bittbox.com - vector art blog
|ryanlerch
|contact(at)bittbox.com
|-style="border-bottom:white 2px solid;"
|The Daily Ubuntu - Daily Ubuntu Applications
|ryanlerch
|http://www.contactify.com/35b54
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

== Receive Formal PR ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://linuxformat.co.uk/
|
|login and submit news via top of page link
|-style="border-bottom:white 2px solid;"
|http://linux-magazine.com/
|
|pr(at)linux - magazine (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxjournal.com/
|
|newproducts (at) ssc (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxmagazine.com/
|
|jbrockmeier at linux hyphen mag DOT com.
|-style="border-bottom:white 2px solid;"
|http://linuxuser.co.uk
|
|terry at linuxuser dot co dot uk http://linuxuser.co.uk/index.php?option=com_content&task=view&id=48&Itemid=40
|-style="border-bottom:white 2px solid;"
|http://www.tuxmagazine.com/
|
|editor at tuxmagazine dot com
|-style="border-bottom:white 2px solid;"
|http://www.linuxworld.com/
|
|mrhinkle at linuxworld dot com tim at linuxworld dot com
|-style="border-bottom:white 2px solid;"
|http://cmykmag.com/
|
|
|-style="border-bottom:white 2px solid;"
|http://www.computerarts.co.uk/
|
|dom dot hall at futurenet dot co dot uk http://www.computerarts.co.uk/contacts
|-style="border-bottom:white 2px solid;"
|http://www.theopensourcereport.com/
|ryanlerch
|contact at theopensourcereport dot com
|-style="border-bottom:white 2px solid;"
|http://www.builderau.com.au/
|ryanlerch
|Chris Duckett, editor at builderau dot com dot au
|-style="border-bottom:white 2px solid;"
|http://www.zdnet.com.au
|ryanlerch
|edit at zdnet dot com dot au
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other ===

* [http://openpr.com openpr] - http://openpr.com/news/submit.html
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* http://graphicdesign.about.com
* http://graphicssoft.about.com
* http://desktoppublishing.about.com

AnnouncePlanning046

2008-03-10T20:13:59Z

Kaeso: Point to sourceforge in the announce, as file will be first available there (and then donwloads.html sync'ed)

Planning the PR for the 0.46 release is done here...

=Tasks=
{| class="wikitable" style="text-align:center"
|-
! Task
! Performer
! Projected Date of completion
! Status
|-
| Informal PR text
| Collaborated on this wiki page
| 18th Feb 2008
| 50%
|-
| Formal PR text
| Collaborated on this wiki page
| 18th Feb 2008
| 50%
|-
| Interview
| [[user:Prokoudine|Prokoudine]]
| progressing
| 90%
|}

=Announcement Process=
# Create new news posts (using the small overview below) on all the relevant social bookmarking sites: digg, slashdot etc.
# Create a new Page on the Inkscape website that has the Formal Announcement on it (for linking purposes) have links back to the socal bookmarking stories for the release.
# Post the official announcement to the Inkscape News on the website, the and the relevant inkscape lists (announce, user, deleveloper)
# Send out the informal announcement (include a link to the webpage with the formal announcement)
# Send out the formal announcement. (include a link to the webpage with the formal announcement)

=Press Release Translations=
Once the English Press Release text has been finalised, translation can start into other languages.

The current goal for this PR text is to have the english version finished by 18th Feb 2008.

Please Create a new Wiki page for planning / translating the 0.46 PR in your language here:

=Press Release Text=
==Small Overview==
Inkscape, the open source vector graphics editor has released version 0.46. Major updates include native PDF support, a paint bucket tool, color profiles, dockable dialogs, SVG Filters, Live Path Effects, and many more features and updates.

==Informal==
===Inkscape Announces 0.46 Release :: http://www.inkscape.org :: Draw Freely.===
The Inkscape community today is announcing the release of the newest version of its open source vector graphics editor. Inkscape 0.46 is a major update that introduces native PDF support. The implementation of PDF support in Inkscape provides an easy, open source solution to editing PDF documents.

A ton of new features and performance improvements are included in this release. Dialogs boxes now have the ability to be docked to the side. Gradients can be edited completely on-canvas now. The new Paint Bucket Tool fills bounded areas with colors and allows quick recoloring of existing objects. A new 3D Box tool helps with creating perspective-correct drawings. A new Tweak tool gives a intuitive method for modifying node paths. The new Live Path Effects feature creates "brushes" and attaches organic effects to paths. Improvements to color management includes support for color spaces other than just sRGB. Most SVG Filters are now implemented, and now have a dedicated UI.

===Download Inkscape 0.46 for Linux, Windows or Mac OS X===
http://inkscape.org/download/

===For More Information===
Complete Release Notes for 0.46, http://wiki.inkscape.org/wiki/index.php/ReleaseNotes046 
Community Contributed Screenshots, http://inkscape.org/screenshots/

===About Inkscape===
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

==Formal==
===The Inkscape Community Releases Inkscape 0.46===

New York, NY, '''INSERT DATE OF RELEASE HERE****yyyy/mm/dd****''' -- The Inkscape community today announced the
release of Inkscape 0.46, the newest stable version of their
multi-platform, open-source vector graphics editor.

This newest Inkscape release includes a plethora of new tools and
improvements, beginning with native PDF support. Developed with the
assistance of the 2007 Google Summer of Code, and utilising the open
source Cairo and Poppler libraries, Inkscape 0.46 provides an easy, open
source tool for editing and creating PDF documents.

The 2007 Google Summer of Code also produced the new 3D Box tool and Live Path Effects.

As its name suggests, the 3D Box tool makes it possible to create and
edit the perspective of three-dimensional boxes.

Live Path Effects can be used to create "brushes" and organic effects
while keeping the original paths editable. [This needs to be more
concrete as well.]

The new Tweak Tool allows you to modify objects similar to molding clay.

As well, gradient editing is now done visually and on-canvas. Gradient
stops are depicted as nodes, and multiple nodes can be selected and
moved simultaneously.

Colour management has also been improved, with initial support for
colour spaces other than sRGB, including Adobe RGB and calibrated CMYK.
This makes it possible to use calibrated colour values, including CMYK
values, that are preserved across applications.

The new Paint Bucket Tool allows bounded areas to be filled with colour
at the click of a mouse button. This new tool creates a closed-path
based on the visible canvas and is useful for quickly colouring line
drawings.

The Gaussian Blur filter, introduced in Inkscape 0.45, was the first SVG
Filter. Inkscape 0.46 expands on this with Offset, Blend, Diffuse
Lighting, Specular Lighting and Turbulence primitives. There is also a
new, dedicated user interface for creating and altering filters based on
these new primitives.

Finally, Inkscape 0.46 introduces workflow and user interface
improvements. Dialogue boxes can now be docked and minimised to a
side-panel, reducing visual clutter and making the relationship between
documents and interaction choices clearer, especially when working on
multiple documents in separate Inkscape instances.

With 0.46 out, the Inkscape community is already working on future
releases, including the upcoming 0.47. Full compatibility with SVG
Mobile/Tiny is slated for version 0.50 and version 1.0 will include
complete W3C SVG 1.1 compliance.

Inkscape users have contributed many features and ideas to the project
and the community invites anyone to contribute to the project. The more
help Inkscape gets, the sooner we reach these goals.

<strike>
The Inkscape community today announced the release of the newest version of their multi platform, open source vector graphics editor, Inkscape 0.46. The latest installment of Inkscape is a feature filled release that introduces a large number of new tools and improvements, including native PDF support. Utilizing the open source libraries of Cairo and Poppler, and developed with the assistance of the Google Summer of Code, Inkscape's PDF support provides an easy, open source solution to editing PDF documents.

Inkscape 0.46 introduces improvements that provides enhanced work flow that complements creativity. Dialogs boxes now have the ability to be docked and minimized to a side panel, enhancing the user experience when editing multiple documents in separate inkscape instances. Gradient editing can now be done visually on-canvas, with gradient stops being depicted as nodes and the abilty to select and move multiple stops simultaneously. Color management has also been improved, with initial support for color definitions that use a colorspace other than sRGB (for example Adobe RGB, or calibrated CMYK colors). This allows for the use of calibrated color spaces, including using CMYK values that are preserved across applications.

The new Paint Bucket Tool allows bounded areas to be quickly filled in with color. It creates a closed path based on the visible canvas and is useful for quickly coloring line drawings. Additional functionality produced by the Google Summer of Code 2007 include the new 3D Box tool, the Tweak tool and Live Path Effects. The Tweak Tool allows smooth and natural change of the shape or style of objects directly on canvas. Live Path Effects can be used to create "brushes" and all kinds of organic effects, while keeping the original paths editable.

Inkscape 0.45 introduced SVG Filters with the Gussian Blur filter primitive; Inkscape 0.46 greatly expands on this by adding the Offset, Blend, Diffuse Lighting, Specular Lighting and Turbulence primitives. As well, there is a new dedicated user interface for creation and alteration of complex filters based on these primitives.

The Inkscape community is now working on the upcoming 0.47 release and invites you to contribute to the project. Beyond that, Inkscape is pushing for full compatibility with SVG Mobile/Tiny by version 0.50, and full W3C SVG 1.1 compliance by Inkscape 1.0. Users have also contributed many great feature ideas in addition to this; the more help the project receives, the faster these goals and ideas can be achieved.
</strike>

===Download Inkscape 0.46 for Linux, Windows or Mac OS X===
http://sourceforge.net/project/showfiles.php?group_id=93438

===For More Information===

Complete Release Notes for 0.46, http://wiki.inkscape.org/wiki/index.php/ReleaseNotes046 
Community Contributed Screenshots, http://inkscape.org/screenshots/

===About Inkscape===
Inkscape is a multi platform, open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

=Places to Announce=

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

== Receive small overview ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Digg
|ryanlerch
|digg.com someone needs to post a short excerpt anouncing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|slashdot.org
|ryanlerch
|submit a new news item.
|-
|-style="border-bottom:white 2px solid;"
|newsvine.com/
|ryanlerch
|submit a new news item.
|-
|}

== Receive Informal PR ==
=== Open Source Community ===
{| style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|- style="border-bottom:white 2px solid;"
|gnome office list
|
|gnome-office-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|svg developers yahoo group
|
|svg-developers at yahoo dot com must join the list to send (rejon is on)
|-style="border-bottom:white 2px solid;"
|SVG.org
|ryanlerch
|antoine at graougraou dot com, svg at steltenpower dot com
|-style="border-bottom:white 2px solid;"
|svgfaq.org
|ryanlerch
|maxdunn at siliconpublishing dot com
|-style="border-bottom:white 2px solid;"
|svgfoundation.org
|ryanlerch
|michael (at) svgfoundation.org
|-style="border-bottom:white 2px solid;"
|cairo list
|ryanlerch
|cairo at cairographics dot org
|-style="border-bottom:white 2px solid;"
|gnome-list
|ryanlerch
|gnome-announce-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|Scribus List (mrdocs)
|ryanlerch
|scribus at nashi dot altmuehlnet dot de
|-style="border-bottom:white 2px solid;"
|osnews.com
|ryanlerch
|http://osnews.com/submit.php
|-style="border-bottom:white 2px solid;"
|desktoplinux.com
|ryanlerch
|http://desktoplinux.com/contactus.html
|-style="border-bottom:white 2px solid;"
|SVG Cafe.com
|ryanlerch
|http://www.svg-cafe.com/ join and post to news section
|-style="border-bottom:white 2px solid;"
|Freshmeat.net
|
|a new release has to be added to inkscape's freshmeat profile
|-style="border-bottom:white 2px solid;"
|gnome footnotes
|
|http://gnomedesktop.org/node/add/story
|-style="border-bottom:white 2px solid;"
|scale-a-vector
|ryanlerch
|kukofka at scale-a-vector dot de http://www.scale-a-vector.de/cont.htm
|-style="border-bottom:white 2px solid;"
|http://dot.kde.org
|ryanlerch
|http://dot.kde.org/addPostingForm
|-style="border-bottom:white 2px solid;"
|revelinux.com
|ryanlerch
|theobroma at revelinux dot com
|-style="border-bottom:white 2px solid;"
|}

=== Broader Inkscape & Art Community ===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Inkscape deviantart group
|ScislaC
|http://inkscape.deviantart.com/
|
|-style="border-bottom:white 2px solid;"
|the inkscape forum
| ryanlerch
|http://www.inkscapeforum.com/ run by microUgly
|-style="border-bottom:white 2px solid;"
|inkscape tutorials blog
|ryanlerch
|http://inkscapetutorials.wordpress.com/
|-
|-style="border-bottom:white 2px solid;"
|open clip art library list
|ryanlerch
|clipart@freedesktop.org
|-style="border-bottom:white 2px solid;"
|open clip art library news
|ryanlerch
|
|-style="border-bottom:white 2px solid;"
|artdc.org forum
|johncoswell
|http://www.artdc.org/
|-style="border-bottom:white 2px solid;"
|bittbox.com - vector art blog
|ryanlerch
|contact(at)bittbox.com
|-style="border-bottom:white 2px solid;"
|The Daily Ubuntu - Daily Ubuntu Applications
|ryanlerch
|http://www.contactify.com/35b54
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

== Receive Formal PR ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://linuxformat.co.uk/
|
|login and submit news via top of page link
|-style="border-bottom:white 2px solid;"
|http://linux-magazine.com/
|
|pr(at)linux - magazine (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxjournal.com/
|
|newproducts (at) ssc (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxmagazine.com/
|
|jbrockmeier at linux hyphen mag DOT com.
|-style="border-bottom:white 2px solid;"
|http://linuxuser.co.uk
|
|terry at linuxuser dot co dot uk http://linuxuser.co.uk/index.php?option=com_content&task=view&id=48&Itemid=40
|-style="border-bottom:white 2px solid;"
|http://www.tuxmagazine.com/
|
|editor at tuxmagazine dot com
|-style="border-bottom:white 2px solid;"
|http://www.linuxworld.com/
|
|mrhinkle at linuxworld dot com tim at linuxworld dot com
|-style="border-bottom:white 2px solid;"
|http://cmykmag.com/
|
|
|-style="border-bottom:white 2px solid;"
|http://www.computerarts.co.uk/
|
|dom dot hall at futurenet dot co dot uk http://www.computerarts.co.uk/contacts
|-style="border-bottom:white 2px solid;"
|http://www.theopensourcereport.com/
|ryanlerch
|contact at theopensourcereport dot com
|-style="border-bottom:white 2px solid;"
|http://www.builderau.com.au/
|ryanlerch
|Chris Duckett, editor at builderau dot com dot au
|-style="border-bottom:white 2px solid;"
|http://www.zdnet.com.au
|ryanlerch
|edit at zdnet dot com dot au
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other ===

* [http://openpr.com openpr] - http://openpr.com/news/submit.html
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* http://graphicdesign.about.com
* http://graphicssoft.about.com
* http://desktoppublishing.about.com

WhiteBoard

2008-01-10T08:45:04Z

Kaeso: /* Status */

Pedro is the name of the whiteboard on inkscape, it allow to share the canvas, and work at several people on a same picture.

==Status==
===(16/01/06)===
Can connect to both gristle.org and jabber.org using pedro, on establishing a whiteboard connection the reciever crashes

===(10/01/08)===
Can connect to im.apinc.org. I tried to google.com xmpp server few month ago it worked (but I lost my login informations).
Tried with jabber.linux.it, it establishes rightly a connection and can see my buddy list; it works for chatting, but I have no-one to try sharing a draw (In parallel I've had a pidgin session, with didn't experience any trouble).
CANT connect to jabber.org:5222, SASL error.

== How to have whiteboard enable ==
You must compile inkscape with the configure option --enable-whiteboard

./configure --prefix=/my/installed/inkscape/path/ --enable-whiteboard &&
make &&
make install
# (or 'make install-strip' to remove debug symbols, but we could need it here).

then launch Inkscape.

=== launching Pedro whiteboard ===
there is a menu '''Whiteboard''' between Effects and Help menues.

Choose '''Whiteboard=>Instant Messaging...'''

A new window pop up called '''Pedro XMPP Client'''.

=== connecting to the server ===
Use menu '''File=>Connect''' to connect to the server.
Enter commons jabber parameters (if you have no jabber account you can test the creation of a new one), then connect.
* If you already have contact with your account, they will be displayed in the Buddies window.
* If your evereyday jabber IM client is launched, you will see yourself with this client. resource.

Then start the conversation with your friend, or start to share your canvas...

=== Sharing the canvas ===
'''Click'' on your friend or contact '''buddy''' with '''right mouse button''' and choose from '''contextual menu''': '''share whiteboard'''

A new window will popup requesting you to choose which document to share :
* The current document (the name of the actual document in the list).
* A new document (Blank Document on the list).

select it and click on Open. A new window will popup with 'Inkboard session (youruser@server/resource to otheruser@server/resource).

This is the working whiteboard....

WhiteBoard

2008-01-10T08:43:42Z

Kaeso: /* Status */

Pedro is the name of the whiteboard on inkscape, it allow to share the canvas, and work at several people on a same picture.

==Status==
===16/01/06)===
Can connect to both gristle.org and jabber.org using pedro, on establishing a whiteboard connection the reciever crashes

===(10/01/08)===
Can connect to im.apinc.org. I tried to google.com xmpp server few month ago it worked (but I lost my login informations).
Tried with jabber.linux.it, it establishes rightly a connection and can see my buddy list; it works for chatting, but I have no-one to try sharing a draw (In parallel I've had a pidgin session, with didn't experience any trouble).
CANT connect to jabber.org:5222, SASL error.

== How to have whiteboard enable ==
You must compile inkscape with the configure option --enable-whiteboard

./configure --prefix=/my/installed/inkscape/path/ --enable-whiteboard &&
make &&
make install
# (or 'make install-strip' to remove debug symbols, but we could need it here).

then launch Inkscape.

=== launching Pedro whiteboard ===
there is a menu '''Whiteboard''' between Effects and Help menues.

Choose '''Whiteboard=>Instant Messaging...'''

A new window pop up called '''Pedro XMPP Client'''.

=== connecting to the server ===
Use menu '''File=>Connect''' to connect to the server.
Enter commons jabber parameters (if you have no jabber account you can test the creation of a new one), then connect.
* If you already have contact with your account, they will be displayed in the Buddies window.
* If your evereyday jabber IM client is launched, you will see yourself with this client. resource.

Then start the conversation with your friend, or start to share your canvas...

=== Sharing the canvas ===
'''Click'' on your friend or contact '''buddy''' with '''right mouse button''' and choose from '''contextual menu''': '''share whiteboard'''

A new window will popup requesting you to choose which document to share :
* The current document (the name of the actual document in the list).
* A new document (Blank Document on the list).

select it and click on Open. A new window will popup with 'Inkboard session (youruser@server/resource to otheruser@server/resource).

This is the working whiteboard....

Editing Inkscape's website

2008-01-03T14:01:28Z

Kaeso: how to publish svn change

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 SVN module:

:Type <pre>svn co https://inkscape.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.
# If you have ssh access to inkscape.org, just launch ./publish_web.sh from your local checkout; otherwise ask a developer to do it for you (they usually hang on #inkscape channel on Freenode).

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

Note: all news entries which weren't translated yet will show up in english.

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 an SVN checkout of the website module.

'''IMPORTANT: all files you change MUST be UTF-8 encoded! Otherwise, you will get broken output. See the UTF-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! Otherwise, you will get broken output. See the UTF-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 SVN access, then commit your changes to the site. See the Website Editing and Working With SVN documentation for directions.
:If you do ''not'' have SVN access, then show your translation to one of the Inkscape administrators for review. They will then give you access to SVN 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]]

Editing Inkscape's website

2008-01-03T13:57:26Z

Kaeso: Reverting to previous revision... please keep this page in English

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 SVN module:

:Type <pre>svn co https://inkscape.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>

Note: all news entries which weren't translated yet will show up in english.

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 an SVN checkout of the website module.

'''IMPORTANT: all files you change MUST be UTF-8 encoded! Otherwise, you will get broken output. See the UTF-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! Otherwise, you will get broken output. See the UTF-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 SVN access, then commit your changes to the site. See the Website Editing and Working With SVN documentation for directions.
:If you do ''not'' have SVN access, then show your translation to one of the Inkscape administrators for review. They will then give you access to SVN 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]]

Translation information

2008-01-03T13:49:49Z

Kaeso: Reverting to revision 17089... this page has to be in English, please create a localized new one if you want to translate it content

== Introduction ==
=== Community based, user oriented ===
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented project, which implies that software developers/contributors are generally users. It also implies that the translation efforts are user oriented, with a strong focus on interface, user documentation and website.

=== Guidelines/workflow ===

# '''Contact to a local translation group, to get support and help on your language'''. Rather than working alone, you should work with an experienced translation team for your language. Thus you will benefit from their knowledge, as well as being able to communicate with them on your own mother tongue. Moreover, translation teams use to have style guidelines and a standarized vocabulary for technical terms that you should be aware of. There may be many communities working on translations for your own language, but a good starting point is subscribing to your local [http://developer.gnome.org/projects/gtp/teams.html GNOME translation team] or [http://l10n.kde.org/teams/ KDE translation team].
# '''Subscribe to''' [https://lists.sourceforge.net/lists/listinfo/inkscape-translator Inkscape translator mailing list]. By subscribing on Inkscape's translator list you will be able to ask for help on some questions more related to Inkscape issues to other Inkscape translators, as well as the mantainers.
# '''Get files for your language'''. If you only want to translate the interface messages, you can get the files from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/ Inkscape's svn repository web interface]. Besides getting files from web interface, you can obtain the full repository; instructions on how to do this are found [http://inkscape.org/svn.php here]. See section [[#Translatable_content]] for which files you have to modify to translate each part of Inkscape.
# '''Submit finished work to patch tracker'''. Finished translations must be sent to patch tracker and/or mailing list in order to be integrated into the trunk. You will need a Launchpad account to commit patches to [http://bugs.launchpad.net/inkscape Inkscape's patch tracker]. Before sending a file, remember to check that the file(s) you are submitting doesn't have syntax errors that would break the building process.
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.

=== Best practices ===

* Best case for a good translation: translate from English to your mother tongue.
* Test the behavior of the interface before starting translation.
* Several small updates are more efficient than only a big one.
* If you're new to Inkscape, or to vector software, taking a look at [http://wiki.inkscape.org/wiki/index.php/InkscapeTerminology Inkscape Terminology page] can be a good idea. It is a work in progress, but can give some clues on basic vocabulary of Inkscape.
* Some good explanations of the behavior of Inkscape, also using some reference terminology can be found here: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php A Guide to Inkscape] and [http://wiki.inkscape.org/wiki/index.php/UserManual User manual].
* Always keep in mind consistency of terminology; a simple, precise & explicit vocabulary/style will result in an efficient and thus good translation.
* Don't hesitate to ask others (developers/translators/users) if you don't understand a word/sentence or if you think an original string is not good (too complex, not precise enough, etc.).

=== Polishing Translations - Microtypography ===
Here are some things to note in order to achieve good microtypography (typography at the word or character level).
* use the proper quotes (e.g. »foo« or «foo» or “foo”, depending on your local rules)
* use the proper kind of dashes (with the proper amount of whitespace around them) - EN DASH (U+2013): "–", MINUS (U+2212): "−"
* use non-breakable space where appropriate (e.g. before units; some countries use a halfspace here) - NO-BREAK SPACE (U+00A0): " "
* use halfspace where appropriate (example: "z. B.") NARROW No-BREAK SPACE U+202F: " "
* use "24×24", not "24x24"
* use "90°", not "90 degrees" where appropriate
* use the proper Unicode codepoint for "..." - "…". In German at least, a space comes before this ellipsis.
* see http://www.cs.tut.fi/~jkorpela/chars/si.html for information on the use of SI units in Unicode
* write numbers correctly - either with a decimal comma or a decimal point (see http://en.wikipedia.org/wiki/Decimal_separator#Dot_countries)
* see http://translate.sourceforge.net/wiki/toolkit/pofilter

==== Links ====
* http://de.wikipedia.org/wiki/Typografie (German)
* [http://www.dante.de/dante/DTK/dtk96_4/Text/dtk96_4_neubauer_feinheiten.pdf Marion Neubauer: ''Feinheiten bei wissenschaftlichen Publikationen – Mikrotypographie-Regeln, Teil I''] (PDF, German)
* [http://www.dante.de/dante/DTK/dtk97_1/Text/dtk97_1_neubauer_feinheiten.pdf Marion Neubauer: ''Feinheiten bei wissenschaftlichen Publikationen – Mikrotypographie-Regeln, Teil II''] (PDF, German)
* [http://www.zvisionwelt.de/typokurz.pdf Christoph Bier: ''typokurz – Einige wichtige typograﬁsche Regeln''] (PDF, German)
* http://www.cs.tut.fi/~jkorpela/html/french.html (in English, for French)

== Translatable content ==

Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, sorted by priority.

These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or were just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for you to do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications were existing to make these tasks much easier.

=== User interface ===

PO files contain the strings for the Inkscape user interface (main software and extentions). A PO file is a text file which contains the original English message and its translation. That's why it is obviously the translation to start with.

See [[InterfaceTranslation#Interface_Translation|InterfaceTranslation]] page for detailed information on the PO files.

=== Tutorials ===

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.
It is even a good opportunity for '''you''' to become more acquainted with Inkscape.

See [[DocumentationTranslation#Tutorial_Translation|Documentation Translation]] page for detailed information on tutorial translation.

=== Keyboard and mouse shortcuts ===

Inkscape is proud for having keyboard and mouse shortcuts for almost all of its functionality. Those shortcuts can help you increase your drawing productivity/efficiency. The map of the default shortcuts is embedded in the interface (help menu) next to the tutorials, and can also be accessed from the web site.

See [[DocumentationTranslation#Keyboard_and_mouse_translation|Documentation Translation]] page for detailed information on translating shortcuts.

=== Windows installer ===

High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps potential users a lot to get a good feeling when they use Inkscape.

See [[InterfaceTranslation#Windows_installer_translation|Interface Translation]] page for detailed information for Windows installer translation.

=== Templates ===

The default template of the Inkscape document can be localized to make the localization consistent. Localized can be the (size?) of the default document and also the name of the default layer.

See [[InterfaceTranslation#Default_template_translation|Interface Translation]] page for detailed information on default document's template.

=== Man pages ===
The man pages consist of a standard user documentation, available from the command line. On Unixbased systems simply type "man inkscape" from the prompt of a command window.

Some distributions also generate a browsable (html) man page, accessible from a dedicated help shortcut.

The man page of Inkscape provides some insightful information about the software, especially focused on operations that do not require GUI (example: export to png from the command line, or extract one object from a svg file).

See [[DocumentationTranslation#Man_pages|Documentation Translation]] page for detailed information for man page translation.

=== Release notes ===
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps the "normal user" to get a lot of insight into the capabilities of Inkscape.

* gives a general overview of the possibilities of the software to potential users
* can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

See [[WebSiteTranslation#Release_notes|WebSite Translation]] page for detailed information on translating release notes.

=== User manual ===
Some members of the Inkscape community are also focusing on an [[UserManual]]. This document can be read as a reference document for advanced users and as a good introduction to the functionalities of Inkscape by everyone.

See [[DocumentationTranslation#User_Manual|Documentation Translation]] page for detailed information on translating the user manual.

=== Web pages, News and Wiki ===
English is generaly the exchange-tongue of developers, and developer/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

You can take a look at the [[WebSiteTranslation|WebSite Translation]] page for detailed information about how to translate the web content of Inkscape

See the [[Main_Page|main wiki page of Inkscape]] to get some examples (Spanish and German) of the translation of this wiki.

=== Others ===
Text files found in the inkscape directory
...

== Status ==
See this [[TranslationStatus|dedicated page]].

Creating Inkscape distributions

2007-03-16T17:16:40Z

Kaeso: /* Creating a distribution source tarball package */

== Creating Dists of Inkscape ==

Those who wish to produce packaged releases of inkscape are welcome to do so.
If it is packages changes that you've made to the official release, please select a
version name that distinguishes it from the official version, to avoid confusion. For
example, “inkscape-0.35-johndoe.tar.gz”. Please consider distributing your changes
as a patch rather than as a full distribution, as patches tend to be easier to
maintain.

Inkscape's release process works like this:

# Start of release process - Finish up work on features.
# Feature Freeze Mode - Shift focus from feature implementation to bug fixing
# Hard Freeze - Two freeze wardens are named. All development must be done as patches submitted to the freeze wardens for review and integration.
# Branch - The codebase is tagged and branched. Final release tarball is posted. The codebase is returned to regular open development.
# Packaging - Three days are allowed for creating release dists (rpm's, deb's, exe's, and autopackages).
# Release Announcement - A Release Announcement and a Press Release are written and circulated to relevant online news sites. Our Freshmeat record is updated.

=== Feature Freeze Mode ===

In the run-up to [[CreatingDists]], for a short time preceding the tagging of the release it's a good idea to hold off on adding new features or doing other major changes like architectural changes to the code that might decrease its stability. Whether a change is minor enough to be “ok” is left to the developer's judgement, and they're trusted to be conservative and careful.

The most useful activity to do during a feature freeze is to locate and/or fix bugs that produce crashes, and to do so with the smallest amount of change to the codebase possible. If a “proper” fix requires architectural changes or redesign of the code, consider writing that up as a post-release task.

-----

It might be useful to branch off a release branch a week before making the release. Hopefully most people using CVS would switch to this branch at this time. Then only bug fixes can go into that branch. --[[Ted]]

=== Branching the release candidate ===

Before release, a branch should have been be created for that release in the form RELEASE_<major>_<minor>_BRANCH. For example, 0.38 should have a branch called RELEASE_0_38_BRANCH.

Minor fixes and code review can then be performed on that branch before the final release; it also permits making future point releases easily (if necessary).

To create the release branch, do the following:

<pre>svn copy https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/trunk https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH</pre>

To check out this branch:

<pre>svn checkout https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/RELEASE_0_38_BRANCH inkscape-0.38-branch</pre>

Once the release is deemed ready a distribution tarball should be created as below.

=== Creating a distribution source tarball package ===

On the release branch (NOT ON HEAD):

* Set the version name via the file configure.ac in the AC_INIT() macro, Makefile.mingw.common, packaging/win32/inkscape.nsi, src/inkscape_version.h.mingw, debian/changelog, build.xml, and in build28.xml
* Run `perl packaging/mkNEWS 0.45 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and lynx. Don't forget to replace 0.45 with the correct version number.
* Run ./autogen.sh && ./configure (with any flags, e.g. CXXFLAGS=).
* Run “cd src && make helper/sp-marshal.h helper/sp-marshal.cpp inkscape_version.h && perl mkfiles.pl && perl mkdep.pl”, then do “cvs -q diff -du make.*|less” to check for anything strange (e.g. source files accidentally added or removed), and finally “cvs commit -m '' make.*”.
* Run "cd po && make update-po" to update the translation files. This especially must be done before declaring string freeze.
* Make sure the code passes a “make distcheck”
* This should produce inkscape-VERSION.tar.gz
* Commit the changed configure.ac and other files to the branch
* Tag the release in CVS

Release tags should be in the form RELEASE_<major>_<minor>_<point>. A non-point-release like 0.38 would get the tag RELEASE_0_38_0, 0.38.1 would get the tag RELEASE_0_38_1, and so on.

On HEAD:

* Add the release notes into the NEWS file in the release branch
* Change configure.ac and inkscape_version.h.mingw to reflect the new future version

=== GPG signing Tarballs ===

Downstream packagers are asking for and may soon demand gpg signed tarballs. For Fedora, this is not a requirement, but does ease acceptance of packages. It also shows we are doing “The Right Thing”. md5sums are not foolproof.

* To create a gpg signed tarball:

<pre>$gpg -u packager@foo.net --armor --output tarball.sig --detach-sig tarball.tar.gz</pre>

* To verify :

<pre>$gpg --verify ./tarball.asc ./tarball.tar.gz</pre>

Of course, this step doesn't mean much in practice unless people have a trust path to your key. Packagers are encouraged to attend key signing parties and take other measures to establish important trust paths to their keys (particularly with downstream packagers).

:Where are the public keys matching these sig's posted?

=== Creating a Windows Distro ===
Inkscape/sodipodi has always been
buildable on Win32. The problem with the sodipodi and original inkscape build, though,
was that the Win32 builder had to download and configure
a lot of things to make it to work. Mingw, MSYS, automake,
autoconf, pkg-config, the codepages, etc. He would spend more
time on THAT than the actual code.

What a pain for the average developer/user who merely wants
to make Inkscape do what he wants it to do. Why waste
days and days getting it to compile, when the developer
would rather be working on the program itself?

So we spent several weeks collecting libraries, building others,
installing the codepages into the source (which we can delete soon
because of Pango) and creating a set of clean makefiles
that work on Win9x, NT, XP, and the cross-compiler.
It is a bit more work for people like me, but hopefully it
attains its goal of saving a lot of work for other people.

Also, remember that on Unix/Linux, $PREFIX is commonly
/usr/local or /usr or something like that. On M$, all of
a program's files are typically located in their own directory. So all
of the files are located relative to “.”. Actually, relative to
the .exe that is currently running.

.....anyway, just wanted to explain that there is a reason
for the Win32 build to be constructed in such a manner,
and that we haven't just been arbitrary.

Once the tree is built (“make -f Makefile.mingw” and “make -f Makefile.mingw dist-strip”) into the “inkscape” directory, the [http://nsis.sourceforge.net/ NSIS] installer script “inkscape.nsi” can be run to create the self-extracting win32 installer.

The Windows download package should be named according to the following scheme:

inkscape-$RELEASE-$PKG.$WINVER.exe

Where $WINVER is the required Windows version, e.g. “win32”. For example:

inkscape-0.37-1.win32.exe

=== Creating a Debian .deb ===

The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.

=== Creating a distribution RPM ===

Method A:
# do as above for tarball, or download the release tarball
# login as root
# rpmbuild -tb inkscape-x.x.tar.gz
# Your RPMs will be in /usr/src/rpm[[/RPMS]] (/usr/src/redhat on RH systems)
# RPMs should be GPG signed

Method B:
# do as above for tarball, or download the release tarball
# mkdir ~/rpm
# Copy the tarball to ~/rpm/SOURCES/
# Copy the inkscape.spec from the tarball to ~/rpm/SPECS/inkscape.spec
# rpmbuild -ba ~/rpm/SPECS/inkscape.spec
# Your RPMs will be in ~/rpm/RPMS and ~/rpm/SRPMS
# RPMs should be GPG signed

The rpm should be named according to the following pattern:

inkscape-$RELEASE-$PKG.$DISTRO.$ARCH.rpm

Where:

$RELEASE: the Inkscape release number, such as “0.37”, “0.36.2”, etc.
The third number should be omitted if it is 0. (I.e., 0.37 instead of 0.37.0)

$PKG: A version number for your package. Use a value of 1 for your package, and increment it if you
need to update the released package for some reason.

$DISTRO: The name and an indicator of the version number for the distro. E.g.,
rh71, rh90, mdk91, suse90, fc1, etc. No need to be too exhaustive with the distro versions;
for a given brand of distro it's probably enough to have a reasonably “modern” release
and an older one for legacy support. For instance, rh71 and rh90.

$ARCH: The architecture that the package was built on. E.g., i686, i386, athlon, ppc, etc.
Don't bother with i586 - either i386 or i686 is preferred. The i386 packages will run on Cyrix
and K-6.

Examples:

inkscape-0.37-1.mdk80.i386.rpm
inkscape-0.37-1.mdk80.i686.rpm
inkscape-0.37-1.mdk91.i386.rpm
inkscape-0.37-1.mdk91.i686.rpm

inkscape-0.37-1.fc1.i386.rpm
inkscape-0.37-1.fc1.i686.rpm
inkscape-0.37-1.fc1.athlon.rpm
inkscape-0.37-1.fc1.ppc.rpm

For creating spec files, feel free to list yourself as the packager, but please use
inkscape-devel@lists.sourceforge.net as the contact email address, to ensure that
questions/complaints about the RPM go to the official support channel.

==== Patching RPMs ====

Occasionally, the RPM will not build without some modifications. If the problem is serious enough that it affects every packaging format, this could signal a need to do a point release, but usually you can just add a patch specifically for the RPM. This is what RPM is for, after all. :-)

Here's how to do it:

1. Create a copy of the source tree, with the modifications needed to correct the issue.
2. Generate a patch like this:

$ diff -uNr package-1.0/ package-1.0p/ > ../SOURCES/package-1.0-my.patch

3. Next add the patch to the RPM. In the specfile at %_topdir/SPECS/package.spec, add a line like this at the top of the file:

Patch0: package-1.0-my.patch

Then further down add a line after the %setup section, like this:

%prep
%setup ...
%patch0 -p1

It's a very good idea to split up changes into discrete patches, giving each a different number (they don't have to be consecutively numbered). Also, be sure to upload the patch(es) to the patch tracker so they'll get into the codebase for the next release.

Then rebuild the package like this:

rpmbuild -ba SPECS/package.spec

=== Signing your package ===

First, you need to have a public/private keypair. This can be generated with gpg using 'gpg --gen-key'.

To add a signature to an extisting package, use the command rpm --addsign /path/to/package.rpm To sign in the process of building a package, use rpmbuild -bb --sign

To check the signature on a package, use rpm --checksig.

=== Releasing Dists on the [[SourceForge]] File Release Tool ===

To release a file: (You need Release Tech permission for your Inkscape account)

* ftp upload.sf.net (anonymous/anonymous)
* cd incoming
* mput filename
* go to Admin -> File Releases
* scroll to the bottom and click [Add Release] to the inkscape item
* Enter 0.35 in the box & click “Create this Release”
* Fill in the form, checkbox the file you uploaded in (c)
* It won't give you a clear “success” message, but you can check it got in right by going to the Files list. You can then edit any of the info you entered, to make it more correct.

Also see [[CVSNamingConventions]] if you are making a release.

=== Announcing Releases ===

When you cut a release, send a copy of the release notes as an announcement to inkscape-announce@lists.sourceforge.net.
If you find other mailing lists or websites that should receive the announcements, add their email address to the inkscape-announce list. This is done by a list admin such as Bryce Harrington.

'''[[AnnouncingReleases]]''' - Keep an eye out for other places we could announce such as distros or graphics-related sites (not only Linux-centric!).

=== Updating Website Collateral ===

When a new release is cut, there are several pieces of info that need to be added to the website:

* Add a news item on front page
* Review/revise FAQ
* Review/revise Roadmap
* Add or revise Screenshots (if appropriate)
* doc directory: Add the manpage for the release, update doc/keys.html file, and change the corresponding version number(s) in doc/index.php.
** From the shell on inkscape.org, cd to /home/inkscape/inkscape_web and run the command “(cd ../inkscape; svn update; chmod g+w -R * 2>/dev/null); pod2html --cachedir=/tmp --infile=../inkscape/inkscape.pod --outfile=doc/inkscape-man.html”.

[[Category:Help Wanted]]

ReleaseAnnounce045-it

2007-02-04T20:16:07Z

Kaeso: /* Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. */

This is concept Italian translation of Release Announcement for 0.45 version

== Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape è lieta di annunciare l'ultima versione del proprio software di disegno vettoriale.
Inkscape 0.45 supporta ora il filtro SVG per la sfocatura gaussiana. Questo filtro, sviluppato grazie al programma di sponsorizzazione del Google Summer of Code, permette di sfuocare in maniera naturale e omogenea qualsiasi oggetto in Inkscape, sia esso un testo, una forma, un'immagine o quant'altro. In questa maniera è possibile raggiungere un livello fotorealistico strabiliante per un'ampia gamma di effetti.

Sono presenti anche altre nuove caratteristiche, numerose migliorie e varie correzioni di bug. I nuovi effetti sono molti, tra cui tutte le estensioni che manipolano i colori o che decorano i tracciati con motivi a scelta.
Per una più gradevole esperienza di disegno è stata riveduta la manipolazione dei gradienti e sono state migliorate le performance generali ottenendo un guadagno in velocità globale del 2-3%, con punte di 5-10% per disegni che fanno largo uso di trasparenze e gradienti radiali.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.45:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

===Informazioni su Inkscape===

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la manipolazione dei nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati vettoriali.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open Source uno strumento di disegno che rispetti pienamente gli standard W3C XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza all'aggiunta di funzioni tramite il meccanismo delle estensioni e la creazione di un processo di sviluppo aperto, collaborativo e orientato alla comunità.

ReleaseAnnounce045-it

2007-02-04T20:03:27Z

Kaeso: /* Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. */

This is concept Italian translation of Release Announcement for 0.45 version

== Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape è lieta di annunciare l'ultima versione del proprio software di disegno vettoriale. Inkscape 0.45 supporta ora il filtro SVG per la sfocatura gaussiana. Sviluppato grazie al programma di sponsorizzazione del Google Summer of Code, il filtro gaussiano permette di sfuocare in maniera naturale e omogenea qualsiasi oggetto in Inkscape, sia esso un testo, una forma, un'immagine o quant'altro. In questa maniera è possibile raggiungere un livello fotorealistico strabiliante per un'ampia gamma di effetti.

Sono presenti anche altre nuove caratteristiche, numerose migliorie e varie correzioni di bug. I nuovi effetti sono molti, tra cui tutte le estensioni che manipolano i colori o che decorano i tracciati con motivi a scelta.
Per una più gradevole esperienza di disegno è stata riveduta la manipolazione dei gradienti e sono state migliorate le performance generali ottenendo un guadagno in velocità globale del 2-3%, con punte di 5-10% per disegni che fanno largo uso di trasparenze e gradienti radiali.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.45:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

===Informazioni su Inkscape===

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la manipolazione dei nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati vettoriali.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open Source uno strumento di disegno che rispetti pienamente gli standard W3C XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza all'aggiunta di funzioni tramite il meccanismo delle estensioni e la creazione di un processo di sviluppo aperto, collaborativo e orientato alla comunità.

ReleaseAnnounce045-it

2007-02-04T19:56:29Z

Kaeso:

This is concept Italian translation of Release Announcement for 0.45 version

== Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape è lieta di annunciare l'ultima versione del proprio software di disegno vettoriale. Inkscape 0.45 supporta ora il filtro SVG per la sfocatura gaussiana. Sviluppato grazie al programma di sponsorizzazione del Google Summer of Code, il filtro gaussiano permette di sfuocare in maniera naturale e omogenea qualsiasi oggetto in Inkscape, sia esso uno testo, una forma, un'immagine o quant'altro. In questa maniera è possibile raggiungere un livello fotorealistico strabiliante per un'ampia gamma di effetti.

Sono presenti anche altre nuove caratteristiche, numerose migliorie e varie correzioni di bug. I nuovi effetti sono molti, tra cui tutte le estensioni che manipolano i colori o che decorano i tracciati con motivi a scelta.
Per una più gradevole esperienza di disegno è stata riveduta la manipolazione dei gradienti e sono state migliorate le performance generali ottenendo un guadagno in velocità globale del 2-3%, con punte di 5-10% per disegni che fanno largo uso di trasparenze e gradienti radiali.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.45:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

===Informazioni su Inkscape===

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la manipolazione dei nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati vettoriali.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open Source uno strumento di disegno che rispetti pienamente gli standard W3C XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza all'aggiunta di funzioni tramite il meccanismo delle estensioni e la creazione di un processo di sviluppo aperto, collaborativo e orientato alla comunità.

ReleaseAnnounce045-it

2007-02-04T19:55:58Z

Kaeso:

This is concept Italian translation of Release Announcement for 0.45 version

== Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape è lieta di annunciare l'ultima versione del proprio software di disegno vettoriale. Inkscape 0.45 supporta ora il filtro SVG per la sfocatura gaussiana. Sviluppato grazie al programma di sponsorizzazione del Google Summer of Code, il filtro gaussiano permette di sfuocare in maniera naturale e omogenea qualsiasi oggetto in Inkscape, sia esso uno testo, una forma, un'immagine o quant'altro. In questa maniera è possibile raggiungere un livello fotorealistico strabiliante per un'ampia gamma di effetti.

Sono presenti anche altre nuove caratteristiche, numerose migliorie e varie correzioni di bug. I nuovi effetti sono molti, tra cui tutte le estensioni che manipolano i colori o che decorano i tracciati con motivi a scelta.
Per una più gradevole esperienza di disegno è stata riveduta la manipolazione dei gradienti e sono state migliorate le performance generali ottenendo un guadagno in velocità globale del 2-3%, con punte di 5-10% per disegni che fanno largo uso di trasparenze e gradienti radiali.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.44:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes044

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

===Informazioni su Inkscape===

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la manipolazione dei nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati vettoriali.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open Source uno strumento di disegno che rispetti pienamente gli standard W3C XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza all'aggiunta di funzioni tramite il meccanismo delle estensioni e la creazione di un processo di sviluppo aperto, collaborativo e orientato alla comunità.

ReleaseAnnounce045-it

2007-02-04T19:50:07Z

Kaeso:

This is concept Italian translation of Release Announcement for 0.45 version

== Annuncio del rilascio di Inkscape 0.45 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape è lieta di annunciare l'ultima versione del proprio software di disegno vettoriale. Inkscape 0.45 supporta ora il filtro SVG per la sfocatura gaussiana. Sviluppato grazie al programma di sponsorizzazione del Google Summer of Code, il filtro gaussiano permette di sfuocare in maniera naturale e omogenea qualsiasi oggetto in Inkscape, sia esso uno testo, una forma o un'immagine. In questa maniera è possibile raggiungere un livello strabiliante per un'ampia gamma di effetti fotorealistici.

Sono presenti anche altre nuove caratteristiche, numerose migliorie e correzioni di bug. I nuovi effetti sono molti, tra cui tutte le estensioni che manipolano i colori o che decorano i tracciati con motivi a scelta.
Per una migliore esperienza di disegno sono state migliorate le performance generali ottenendo un guadagno in velocità globale del 2-3%, con punte di 5-10% per disegni che usano pesantemente le trasparenze e i gradienti circolari, nonchè una migliore usabilità per la manipolazione dei gradienti.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.44:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes044

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

===Informazioni su Inkscape===

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la manipolazione dei nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati vettoriali.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open Source uno strumento di disegno che rispetti pienamente gli standard W3C XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza all'aggiunta di funzioni tramite il meccanismo delle estensioni e la creazione di un processo di sviluppo aperto, collaborativo e orientato alla comunità.

ReleaseAnnounce045-it

2007-02-04T19:24:48Z

Kaeso:

== Inkscape Announces 0.45 Release :: http://www.inkscape.org :: Draw Freely. ==

The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This 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.

Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.

Download Linux, Windows, and Mac OS X packages:

http://sourceforge.net/project/showfiles.php?group_id=93438

For many more details, see the complete Release Notes for 0.45:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Community submitted screenshots:

http://www.inkscape.org/screenshots/

===About Inkscape===

Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.

Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

User:Luci

2006-09-06T08:13:57Z

Kaeso:

luci
foo-it

User:Luci

2006-09-06T08:08:01Z

Kaeso: test

luci

ReleaseAnnounce044-it

2006-06-25T08:49:39Z

Kaeso: /* Annuncio del rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. */

This is concept Italian translation of Release Announcement for 0.44 version

== Annuncio del rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape ha rilasciato oggi l'ultima versione del proprio programma di garfica vettoriale. Inkscape 0.44 soddisfa un grande numero delle richieste degli utenti, supporta più caratteristiche di SVG, è tradotto in più lingue e contiene molti miglioramenti.

Alcune notevoli modifiche all'interfaccia grafica comprendono una sottofinestra per i livelli, l'integrazione dei campioni, una nuova finestra di preferenze, la barra del testo e nuove icone. Cambiamenti più profondi riguardano la persistenza del centro di rotazione, indicazioni interattive per la barre, acceleratori configurabili, miglioramenti al pennino calligrafico e la nuova funzionalità di scultura dei nodi. Ora l'esportazione in PDF supporta anche le trasparenze.

Ormai da diverse versioni era stato sviluppato un sistema sperimentale di plugin per gli Effetti, che era però disabilitato per precauzione. Con questo rilascio gli sviluppatori credono che il sistema sia abbastanza affidabile, per cui questa funzionalità è attiva in maniera predefinita

Inkscape ora fornisce una nuova modalità coi soli contorni, per migliorare le performance nei disegni molto complessi. L'adesione allo standard SVG ha visto un balzo in avanti con l'implementazione del tag <switch>. I profili di colore ICC sono stati implementati per le immagini, e apportate centinaia di correzioni e miglioramenti.

Ringraziamo anche Google per aver sponsorizzato cinque studenti e i loro progetti di sviluppo per Inkscape riguardanti i FIltri SVG, le specifiche del protocollo di Inkboard, l'esportazione PDF con Cairo e l'ottimizzazione della memoria.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.44:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes044

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

Informazioni su Inkscape

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la modifica sui nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati basati su vettori multipli.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open
Source uno strumento di disegno che rispetti pienamente gli standard
[[W3C]] XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una
conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza
all'aggiunta di funzioni tramite il meccanismo delle estensioni e la
creazione di un processo di sviluppo aperto, collaborativo e orientato
alla comunità.

ReleaseAnnounce044-it

2006-06-25T08:43:08Z

Kaeso: /* Annuncio del rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. */

This is concept Italian translation of Release Announcement for 0.44 version

== Annuncio del rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape ha rilasciato oggi l'ultima versione del proprio programma di garfica vettoriale. Inkscape 0.44 soddisfa un grande numero delle richieste degli utenti, supporta più caratteristiche di SVG, è tradotto in più lingue e contiene molti miglioramenti.

Alcune notevoli modifiche all'interfaccia grafica comprendono una sottofinestra per i livelli, l'integrazione dei campioni, una nuova finestra di preferenze, la barra del testo e nuove icone. Cambiamenti più profondi riguardano la persistenza del centro di rotazione, indicazioni interattive per la barre, acceleratori configurabili, miglioramenti al pennino calligrafico e la nuova funzionalità di scultura dei nodi. Ora l'esportazione in PDF supporta anche le trasparenze.

Ormai da diverse versioni era stato sviluppato un sistema sperimentale di plugin per gli Effetti, che era però disabilitato per precauzione. Con questo rilascio gli sviluppatori credono che il sistema sia abbastanza affidabile, per cui questa funzionalità è attiva in maniera predefinita

Inkscape ora fornisce una nuova modalità coi soli contorni, per migliorare le performance nei disegni molto complessi. L'adesione allo standard SVG ha visto un balzo in avanti con l'implementazione del tag <switch>. I profili di colore ICC sono stati implementati per le immagini, e apportate centinaia di correzioni e miglioramenti.

Ringraziamo anche Google per aver sponsorizzato cinque studenti e i loro progetti di sviluppo per Inkscape riguardanti i FIltri SVG, le specifiche del protocollo di Inkboard, l'esportazione PDF con Cairo e l'ottimizzazione della memoria.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.44:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

Informazioni su Inkscape

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la modifica sui nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati basati su vettori multipli.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open
Source uno strumento di disegno che rispetti pienamente gli standard
[[W3C]] XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una
conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza
all'aggiunta di funzioni tramite il meccanismo delle estensioni e la
creazione di un processo di sviluppo aperto, collaborativo e orientato
alla comunità.

ReleaseAnnounce044-it

2006-06-06T16:29:16Z

Kaeso:

This is concept Italian translation of Release Announcement for 0.44 version

== Annuncio del rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape ha rilasciato oggi l'ultima versione del proprio programma di garfica vettoriale. Inkscape 0.44 soddisfa un grande numero delle richieste degli utenti, supporta più caratteristiche di SVG, è tradotto in più lingue e contiene molti miglioramenti.

Alcune notevoli modifiche all'interfaccia grafica comprendono una sottofinestra per i livelli, l'integrazione dei campioni, una nuova finestra di preferenze, la barra del testo e nuove icone. Cambiamenti più profondi riguardano la persistenza del centro di rotazione, indicazioni interattive per la barre, acceleratori configurabili, miglioramenti al pennino calligrafico e la nuova funzionalità di scultura dei nodi. Ora l'esportazione in PDF supporta anche le trasparenze.

Ormai da diverse versioni era stato sviluppato un sistema sperimentale di plugin per gli Effetti, che era però disabilitato per precauzione. Con questo rilascio gli sviluppatori credono che il sistema sia abbastanza affidabile, per cui questa funzionalità è attiva in maniera predefinita

Inkscape ora fornisce una nuova modalità coi soli contorni, per migliorare le performance nei disegni molto complessi. L'adesione allo standard SVG ha visto un balzo in avanti con l'implementazione del tag <switch>. I profili di colore ICC sono stati implementati per le immagini, e apportate centinaia di correzioni e miglioramenti.

Ringraziamo anche Google per aver sponsorizzato cinque studenti e i loro progetti di sviluppo per Inkscape riguardanti i FIltri SVG, le specifiche del protocollo di Inkboard, l'esportazione PDF con Cairo e l'ottimizzazione della memoria.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.43:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

Informazioni su Inkscape

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la modifica sui nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati basati su vettori multipli.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open
Source uno strumento di disegno che rispetti pienamente gli standard
[[W3C]] XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una
conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza
all'aggiunta di funzioni tramite il meccanismo delle estensioni e la
creazione di un processo di sviluppo aperto, collaborativo e orientato
alla comunità.

ReleaseAnnounce044-it

2006-06-06T16:26:50Z

Kaeso: It translation

This is concept Italian translation of Release Announcement for 0.44 version

== Annuncio rilascio di Inkscape 0.44 :: http://www.inkscape.org :: Disegna in Libertà. ==

La comunità di Inkscape ha rilasciato oggi l'ultima versione del proprio programma di garfica vettoriale. Inkscape 0.44 soddisfa un grande numero delle richieste degli utenti, supporta più caratteristiche di SVG, è tradotto in più lingue e contiene molti miglioramenti.

Alcune notevoli modifiche all'interfaccia grafica comprendono una sottofinestra per i livelli, l'integrazione dei campioni, una nuova finestra di preferenze, la barra del testo e nuove icone. Cambiamenti più profondi riguardano la persistenza del centro di rotazione, indicazioni interattive per la barre, acceleratori configurabili, miglioramenti al pennino calligrafico e la nuova funzionalità di scultura dei nodi. Ora l'esportazione in PDF supporta anche le trasparenze.

Ormai da diverse versioni era stato sviluppato un sistema sperimentale di plugin per gli Effetti, che era però disabilitato per precauzione. Con questo rilascio gli sviluppatori credono che il sistema sia abbastanza affidabile, per cui questa funzionalità è attiva in maniera predefinita

Inkscape ora fornisce una nuova modalità coi soli contorni, per migliorare le performance nei disegni molto complessi. L'adesione allo standard SVG ha visto un balzo in avanti con l'implementazione del tag <switch>. I profili di colore ICC sono stati implementati per le immagini, e apportate centinaia di correzioni e miglioramenti.

Ringraziamo anche Google per aver sponsorizzato cinque studenti e i loro progetti di sviluppo per Inkscape riguardanti i FIltri SVG, le specifiche del protocollo di Inkboard, l'esportazione PDF con Cairo e l'ottimizzazione della memoria.

Download dei pacchetti per Linux, Windows e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per maggiori dettagli, fare riferimento alle note di rilascio per 0.43:

http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes

Alcuni screenshot inviati dalla comunità di utenti:

http://www.inkscape.org/screenshots/

Informazioni su Inkscape

Inkscape è un programma open source per il disegno, simile a
Illustrator, Freehand e CorelDraw, che si basa sul formato standard [[W3C]]
"scalable vector graphics" (SVG). Tra le caratteristiche supportate da
SVG vi sono le forme base, i tracciati, i testi, i segnali, i cloni, le
trasparenze, le trasformazioni, i gradienti e i gruppi. Inkscape
supporta inoltre i meta-dati Creative Commons, la modifica sui nodi, i
livelli, le operazioni complesse sui livelli, i testi su tracciato e la
modifica dell'XML SVG. Può importare da diversi formati come EPS,
<nowiki>PostScript</nowiki>, JPEG, PNG, BMP e TIFF e esportare in PNG ed in altri
formati basati su vettori multipli.

Lo scopo principale di Inkscape è quello di fornire alla comunità Open
Source uno strumento di disegno che rispetti pienamente gli standard
[[W3C]] XML, SVG e CSS2. Inoltre il piano di sviluppo prevede una
conversione del codice da <nowiki>C/Gtk</nowiki> a <nowiki>C++/Gtkmm</nowiki>, maggiore importanza
all'aggiunta di funzioni tramite il meccanismo delle estensioni e la
creazione di un processo di sviluppo aperto, collaborativo e orientato
alla comunità.

Editing Inkscape's website

2006-01-22T19:52:48Z

Kaeso: /* Adding Screenshots to the Site */

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

== CVS Checkout of the Website Module ==

To checkout the website cvs module:

:Type <pre>svn co inkscape_web</pre> after you have logged in with your username/password

For more info, see 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 cvs 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 CVS 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>
<div class="item">
<h3>HEADER</h3>
MONTH DAY, YEAR
MESSAGE

<?php echo $[[SIG_YOURNAME]]; ?>
</div>
</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 break 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 i heared different people talking about UTF-8 entities, i thought this should be clarified: THERE IS NO SUCH THING!

There are HTML entities. (that's what you think of) This is not an encoding, it is a (somewhat) human readable transliteration. They look like
<pre> & (& a m p ;) --- ř (& # 3 4 5 ;) --- Ä (& A u m l ;)</pre>
The cool thing about them 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 or whatever, at least they are system dependant.

Now, if we talk about UTF-8, this is an encoding! And it's one for UNIcode. The 8 means, that the most important chars need 8bit to store. (i think these are the same chars as the lower 128 in ASCII) All the other UNIcode chars 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 chars like äüößéńí etc.

So, if you edit existing pages, you need to have an UTF-8 capable editor. (Kate for example is capable, but you might need to check the encoding in the extras menu.)

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

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

Editing Inkscape's website

2006-01-22T19:51:49Z

Kaeso: /* CVS Checkout of the Website Module */

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

== CVS Checkout of the Website Module ==

To checkout the website cvs module:

:Type <pre>svn co inkscape_web</pre> after you have logged in with your username/password

For more info, see 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 cvs 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 CVS 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>
<div class="item">
<h3>HEADER</h3>
MONTH DAY, YEAR
MESSAGE

<?php echo $[[SIG_YOURNAME]]; ?>
</div>
</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 descriptivename.

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 CVS repository. For more info, see [[WorkingWithCVS]].

== 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 break 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 i heared different people talking about UTF-8 entities, i thought this should be clarified: THERE IS NO SUCH THING!

There are HTML entities. (that's what you think of) This is not an encoding, it is a (somewhat) human readable transliteration. They look like
<pre> & (& a m p ;) --- ř (& # 3 4 5 ;) --- Ä (& A u m l ;)</pre>
The cool thing about them 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 or whatever, at least they are system dependant.

Now, if we talk about UTF-8, this is an encoding! And it's one for UNIcode. The 8 means, that the most important chars need 8bit to store. (i think these are the same chars as the lower 128 in ASCII) All the other UNIcode chars 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 chars like äüößéńí etc.

So, if you edit existing pages, you need to have an UTF-8 capable editor. (Kate for example is capable, but you might need to check the encoding in the extras menu.)

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

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