Thanks for marking that spam. [[User:Legio noctis|Legio noctis]] 19:15, 15 March 2011 (UTC)

Layer Dialog

2010-08-24T13:24:51Z

Legio noctis: /* Suggestions for improvements */

== Using the Layers dialog ==

The Layers dialog controls all layer functions: adding new layers, renaming, deleting, arranging, toggling visibility and edit-locking and setting Blend mode and opacity.

[[File:Layer_Dialog.png|200px|thumb|left]]

The Layers dialog can be opened by going to <tt>Layer > Layers...</tt>.

Most of the Layer functions are already available in this menu, including:
*add, duplicate, rename
*view one layer up/down
*move selection to layer up/down
*changing order of layers
*delete layer

There is also a <tt>View Layers</tt> shortcut button on the Commands Bar toolbar.

== Work in progress ==

== Suggestions for improvements ==

=== Adobe Illustrator sublayers ===
It would be good to consider using sublayers like in Illustartor: http://upload.wikimedia.org/wikipedia/en/8/88/Adobe_illustrator_10.png --Host-216-229-237-115.public.southern.edu 15:27, 3 October 2005

=== drag&drop functionality with opened Layer Dialog ===
simply make a selection, open the layer dialog, drag the desired Layer on the selection and drop -> the selection is added to the desired Layer--[[User:Touringlonewulf|Touringlonewulf]] 11:28, 23 August 2010 (UTC)

=== additional item in Layers menu ===
under "move selection up/down" the point: "move selection to layer" -> a new drop down opens, which shows all layers and another point "create new". Now simply clicking in the drop down list on one layer will move the selection to that layer--[[User:Touringlonewulf|Touringlonewulf]] 11:28, 23 August 2010 (UTC)

=== additional button in Layer Dialog Box ===
"import bitmap/svg into current layer"

== See also ==

*[[DocumentLayers]]
* [http://en.flossmanuals.net/Inkscape/Layers Floss Manuals User guide article on Layers in 0.47]

Layer Dialog

2010-08-24T13:24:37Z

Legio noctis:

Inkscape Wiki talk:Community Portal

2010-08-19T17:34:46Z

Legio noctis: Reverted edits by Demver5 (Talk) to last version by Mcguerty

MicrosoftVisio

2010-08-13T20:01:36Z

Legio noctis: /* Links */

Please post links to screenshots and/or insights of this vector app. We must learn from others.

Visio is a vector graphics program for creating diagrams and technical drawings.

Many users have a need for techincal drawing tools and are not well catered for by other Open Source software.
Whether you like it or not there is a demand for features from technical drawing software in Inkscape.

When drawing a shape Visio includes a diagonal line and other hints to make it easier to draw symmetrically. Also, Visio has configurable snap-to-points on each corner and middle of lines (configurable) to aid with quickly connecting links and shapes together.

Visio has an extensive set of Stencil Sheets and when it comes to implementing Library functionality and ways to manage predefined styles and objects it may serve as a useful reference.

Seen from a regular user of Visio, the following features are missing from Inkscape:
* Powerful Connection Tool: Makes it very easy to create all sorts of diagrams with connecting lines, arrows etc. that re-route automatically.
** Connector styles: Right Angle or Straight.
** User definable Connection Points on objects
** Line Jumps may be added to crossing lines: Arc, Gap, Square.
** The auto-routed connections are easily adjusted manually.
* Text Annotation: All objects are easily annotated with a text box whose properties (position, size, rotation etc.) follows those of the annotated object.
* Drawing scale: Scaling between paper size and drawing size is necessary for CAD-like drawings with real world dimensions. Measurement Objects available as a stencil make it easy to annotate drawings with true to scale measurements.
* Multipage Drawings: A drawing may consist of multiple pages. The pages are made available with tabs below the current page.
* Stencil Sheets: Visio includes all sorts of stencil objects. Stencil sheets with user objects are easily created.

=== Screenshots ===

[http://www.netsoc.tcd.ie/~horkana/dia/visio/screenshots/ ahorkana's screenshots]

=== Links ===

* [http://www.microsoft.com/office/visio/default.asp Official site]
* [http://vdxtosvg.sourceforge.net/ VDXtoSVG]

MicrosoftVisio

2010-08-13T20:00:22Z

Legio noctis: /* Links */

Please post links to screenshots and/or insights of this vector app. We must learn from others.

Visio is a vector graphics program for creating diagrams and technical drawings.

Many users have a need for techincal drawing tools and are not well catered for by other Open Source software.
Whether you like it or not there is a demand for features from technical drawing software in Inkscape.

When drawing a shape Visio includes a diagonal line and other hints to make it easier to draw symmetrically. Also, Visio has configurable snap-to-points on each corner and middle of lines (configurable) to aid with quickly connecting links and shapes together.

Visio has an extensive set of Stencil Sheets and when it comes to implementing Library functionality and ways to manage predefined styles and objects it may serve as a useful reference.

Seen from a regular user of Visio, the following features are missing from Inkscape:
* Powerful Connection Tool: Makes it very easy to create all sorts of diagrams with connecting lines, arrows etc. that re-route automatically.
** Connector styles: Right Angle or Straight.
** User definable Connection Points on objects
** Line Jumps may be added to crossing lines: Arc, Gap, Square.
** The auto-routed connections are easily adjusted manually.
* Text Annotation: All objects are easily annotated with a text box whose properties (position, size, rotation etc.) follows those of the annotated object.
* Drawing scale: Scaling between paper size and drawing size is necessary for CAD-like drawings with real world dimensions. Measurement Objects available as a stencil make it easy to annotate drawings with true to scale measurements.
* Multipage Drawings: A drawing may consist of multiple pages. The pages are made available with tabs below the current page.
* Stencil Sheets: Visio includes all sorts of stencil objects. Stencil sheets with user objects are easily created.

=== Screenshots ===

[http://www.netsoc.tcd.ie/~horkana/dia/visio/screenshots/ ahorkana's screenshots]

=== Links ===

[http://www.microsoft.com/office/visio/default.asp Official site]
[http://vdxtosvg.sourceforge.net/ VDXtoSVG]

MicrosoftVisio

2010-08-13T19:57:30Z

Legio noctis: /* Links */ spam

Please post links to screenshots and/or insights of this vector app. We must learn from others.

Visio is a vector graphics program for creating diagrams and technical drawings.

Many users have a need for techincal drawing tools and are not well catered for by other Open Source software.
Whether you like it or not there is a demand for features from technical drawing software in Inkscape.

When drawing a shape Visio includes a diagonal line and other hints to make it easier to draw symmetrically. Also, Visio has configurable snap-to-points on each corner and middle of lines (configurable) to aid with quickly connecting links and shapes together.

Visio has an extensive set of Stencil Sheets and when it comes to implementing Library functionality and ways to manage predefined styles and objects it may serve as a useful reference.

Seen from a regular user of Visio, the following features are missing from Inkscape:
* Powerful Connection Tool: Makes it very easy to create all sorts of diagrams with connecting lines, arrows etc. that re-route automatically.
** Connector styles: Right Angle or Straight.
** User definable Connection Points on objects
** Line Jumps may be added to crossing lines: Arc, Gap, Square.
** The auto-routed connections are easily adjusted manually.
* Text Annotation: All objects are easily annotated with a text box whose properties (position, size, rotation etc.) follows those of the annotated object.
* Drawing scale: Scaling between paper size and drawing size is necessary for CAD-like drawings with real world dimensions. Measurement Objects available as a stencil make it easy to annotate drawings with true to scale measurements.
* Multipage Drawings: A drawing may consist of multiple pages. The pages are made available with tabs below the current page.
* Stencil Sheets: Visio includes all sorts of stencil objects. Stencil sheets with user objects are easily created.

=== Screenshots ===

[http://www.netsoc.tcd.ie/~horkana/dia/visio/screenshots/ ahorkana's screenshots]

=== Links ===

[http://www.microsoft.com/office/visio/default.asp Official site]

UI improvements

2010-07-26T20:00:05Z

Legio noctis: /* Improvements */

== UI Improvement Effort ==

=== Abstract ===

Inkscape provides the user with a graphically and feature rich environment for creating visual artwork. Why should we care about investing effort to UI improvement?

First of all, of course, because we like Inkscape and are passionate about the project, hence it deserves our attention and energy by definition.

But there are also a few more rational points to make about how the user could benefit from UI improvements.

In general, a user interface is crudely seperable into its ''visual'' and its ''interactive'' features.

Most modern user interfaces are comprised of several (mostly) rectangular logical elements (Widgets, Windows, Textboxes, ScrollBars, etc ...).
Those elements provide basic interactivity, while being ''styleable'' in size, color, texture and sometimes shape.

This separation of concerns at the level of development is coherent with the idea of arguing about ''interactivity'' and ''visual style'' separately.
As such, both groups deserve special attention and we will categorize our specific improvement propositions accordingly.

'''Note: Every improvement proposition on this page is required to be acompanied with a more or less elaborate, rational explanation.
'''

=== Improvements ===

==== Visual Improvements ====

=====Simplify Icons + Theme=====

======Proposal:======
Simlify both shape and color of current default icon set.
Also, make Inkscape load a custom, default gtk theme.
Make icons and theme s/w (grayscale) and low in contrast with a neutral base ( meaning the base color is 50% gray ).

======Explanation:======

Since Inkscape is a tool for creating rich visual content, its own visual appearance should not compete with that content.
The users attention should be focused on his/her own artwork, but the human eye is known to focus on high contrasts, both color and value contrasts.
Therefore, after eliminating saturation and contrast from the UI, it is reasonable to assume that a user can devote his attention more easily to the task at hand.
It is worth noting that it is technically possible for each user to implement both of these improvements on his own by modifing certain files in his specific Inkscape installation.
However, most users will probably not even be aware of such subtle and unconscious effects and, more importantly, it is unreasonable to expect the user know about such technicalities. The user's problem domain is ''visual content''. Every problem he or she has to solve that is not directly part of that domain is to be considered a waste of time.
Therefore Inkscape's default state should be one that intuitively aids in that problem domain.

A [http://farm5.static.flickr.com/4137/4828395519_5a9263c22a_b_d.jpg screenshot] of how this might look.

=====Maximize Working Area=====

======Proposal:======

Hide/group most unessential tools, buttons and panels in default state.
Automatically minimize or show panels based on mouse position or context.
User-configurable panels (drag'n'drop).

======Explanation:======

Inkscape provides many beautifully specialized features and tools for creating vector art. But in the domain of vector drawing applications its real strength lies rather in the generality of its tools, allowing the artist to explore and create what could not be anticipated by the creators of Inkscape. This approach towards general features instead of highly specific ones has its roots in the SVG specification itself and the developers of Inkscape agree with it. The benefits of this approach is nicely illustrated by Inkscape's rich filter system.

In the same spirit, a user should be able to configure his interface by means of creating custom panels, naming them and dragging and dropping tools, menu items and other buttons into and out of them.
While this approach would allow the user to create highly customized and arbitrarily complex user interfaces, Inkscapes default UI state should nonetheless adhere to the concept of most simplicity and generality.
Here is a [http://farm5.static.flickr.com/4092/4830923751_59d76a41f4_b.jpg screenshot] of how the UI could be reduced.

Also, Inkscape's working area is the most important area of the UI (compared, for example, to panels, buttons and the status bar) because the user's problem domain (his/her content) is represented mostly in that area. As a result it deserves special attention and a higher priority.

This could be achieved by automatically hiding bars and panels, thereby maximizing the working area, and only blend them in in special circumstances, such as mouse movement towards the screen edge or some other context.

This would contribute to the concept of simplicity and generality, because all of Inkscape's UI would be accessible and explorable to the user, while being as clean and simple as possible during his or her tasks.

==== Interactivity Improvements ====

=====Self-documenting UI=====

======Proposal:======

Every tool, button, panel and menu item should have an extensive tooltip popup showing the associated shortkey, links to the documentation and an optional short description.
''Note: This assumes/implicates, that every item has its own shortkey assigned.''

======Explanation:======

Exploration and experimentation are a big part of the Inkscape user experience. It's not only fun, but tremendously important to become able to use Inkscape as a creative tool.

Therefore, every feature that eases and encourages the user to gain experience can be considered very valuable.

The notion of a 'tooltip' has become very intuitive for the average PC user and it also lends itself well to the idea of simplicity and generality explained above, because it's only visible if the user wishes for it and otherwise does not complicate the UI.

UI improvements

2010-07-26T19:48:47Z

Legio noctis: /* Abstract */

== UI Improvement Effort ==

=== Abstract ===

Inkscape provides the user with a graphically and feature rich environment for creating visual artwork. Why should we care about investing effort to UI improvement?

First of all, of course, because we like Inkscape and are passionate about the project, hence it deserves our attention and energy by definition.

But there are also a few more rational points to make about how the user could benefit from UI improvements.

In general, a user interface is crudely seperable into its ''visual'' and its ''interactive'' features.

Most modern user interfaces are comprised of several (mostly) rectangular logical elements (Widgets, Windows, Textboxes, ScrollBars, etc ...).
Those elements provide basic interactivity, while being ''styleable'' in size, color, texture and sometimes shape.

This separation of concerns at the level of development is coherent with the idea of arguing about ''interactivity'' and ''visual style'' separately.
As such, both groups deserve special attention and we will categorize our specific improvement propositions accordingly.

'''Note: Every improvement proposition on this page is required to be acompanied with a more or less elaborate, rational explanation.
'''

=== Improvements ===

==== Visual Improvements ====

'''Simplify Icons + Theme'''

Proposal:
Simlify both shape and color of current default icon set.
Also, make Inkscape load a custom, default gtk theme.
Make icons and theme s/w ( grayscale ) ,low in contrast with a neutral base ( meaning the base color is 50% gray ).

Explanation:
Since Inkscape is a tool for creating rich visual content, its own visual appearance should not compete with that content.
The users attention should be focused on his/hers own artwork, but the human eye is known to focus on high contrasts, both color and value contrasts.
Therefore, by eliminating saturation and contrast from the UI, it is reasonable to assume, that a user can devote his attention more easily to the ask at hand.
It is worth noting, that both these improvements are technically possible for each user to implement on his own by modifing certain files in his specific Inkscape installation.
But, most users might not even be aware of such subtle and unconcious effects and more importantly, it is unreasonable to expect the user know about such technicalities. The users problem domain is ''visual content''. Every problem he or she has to solve, that is not directly part of that domain is to be considered a waste of time.
Therefore Inkscapes default state should be one, that intuitivly aids in that problem domain.

Here is a [http://farm5.static.flickr.com/4137/4828395519_5a9263c22a_b_d.jpg screenshot] of how this could possible look like .

''' Maximize Working Area '''

Proposal:
Hide/group most unessential tools, buttons and panels in default state.
Automatically minimize or show panels based on mouse position or context.
User-configurable panels ( drag'n'drop ).

Explanation:
Inkscape provides many beautifully specialized features and tools for creating vector art. But in the domain of vector drawing applications its real strength lies rather in the generality of its tools, allowing the artist to explore and create what could not be anticipated by the creators of Inkscape. This concept towards general features instead of highly specific ones has its roots in the SVG specification itself and infused the developers of Inkscape. The benefits of this approach is nicely illustrated by Inkscapes rich filter system.
In the same spirit, a user should be able to configure his interface by means of creating custom panels, naming them and dragging and dropping tools, menu items and other buttons into and out of them.
While this approach would allow the user to create highly customized and arbitrarily complex user interfaces, Inkscapes default UI state should nonetheless adhere to the concept of most simplicity and generality.
Here is a [http://farm5.static.flickr.com/4092/4830923751_59d76a41f4_b.jpg screenshot] of how the UI could possibly be reduced.

Also, since the working area of Inkscape compared to other parts of the UI ( panels, button bars, status bar ) is of most importance, because the users content, his/hers problem domain, is most stringly represented in that area, it should deserve special attention, higher priority.
This could be achieved by automatically hiding bars and panels, thereby maximizing the working area, and only blend them in in special circumstances, such as mouse movement towards the screen edge, or some other context.
This would contribute to the concept of simplicity and generality, because all of Inkscapes UI would be accessible and explorable to the user, while being as clean and simple as possible during his or her tasks.

==== Interactivity Improvements ====

''' Self-documenting UI '''

Proposal:

Every tool, button, panel and menu item should have an extensive tooltip popup showing the associated shortkey, links to the documentation and an optional short description.
''Note: This assumes/implicates, that every item has its own shortkey assigned.''

Explanation:

Exploration and experimentation are a big part of the Inkscape user experience. Its not only fun, but tremendously important to become able to use Inkscape as an creative tool.
Therefore, every feature, that eases and encourages these experiences can be considered very valuable to the user.
The notion of a 'tooltip' has become very intuitive for the average PC user and it also lends itself well to the idea of simplicity and generality explained above, because its only visible if the user wishes for it, and otherwise does not complicate the UI.

Talk:User manual information

2010-07-06T17:25:15Z

Legio noctis: moved Talk:User manual infromation to Talk:User manual information

== Official User Manual ==

In this article someone wrote « Why not write the manual here? ». I agree because as a beginner I find it hard to get help. The Wiki could be used as a help center to document the whole software. I found it hard to believe that there wasn't even a Help document in the software, only tutorials. Tavmjong Bah is working on [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php A Guide to Inkscape], Kevin Wixson on [http://www.angelfire.com/mi/kevincharles/inkscape/index.html Inkscape User Manual : Un-official manual]... What about working together and make that Official User Manual happen ? [[User:Goa103|goa103]] 16:36, 8 June 2006 (PDT)

User manual information

2010-07-06T17:23:14Z

Legio noctis: moved User manual infromation to User manual information

== Read ==

There exist a number of comprehensive manuals for Inkscape:
*[http://tavmjong.free.fr/INKSCAPE/MANUAL/html/ Inkscape: Guide to a Vector Drawing Program] by Tavmjong Bah
*A [http://en.flossmanuals.net/Inkscape/ FLOSS Manuals guide]

A larger list is available at [http://www.inkscape.org/doc/index.php the main Inkscape website].

== Contribute ==

# [http://lists.sourceforge.net/mailman/listinfo/inkscape-docs Subscribe] to the inkscape-docs mailing list
# Read the manual
# [http://wiki.inkscape.org/wiki/index.php/User_Manual_Work_in_Progress Read what needs to be done]
# Introduce yourself in the list and tell us what you want to do so that no work is duplicated
# Read [http://en.flossmanuals.net/bin/view/Inkscape/WritingConventions writing conventions]
# [http://en.flossmanuals.net/bin/view/Inkscape/WebHome Start contributing].

Here is is a hint: we try to use as much content from release notes as possible, since last 5-6 ones were written in a very much verbose way.

== Translate ==

We very much welcome translations of the manual. Please [http://lists.sourceforge.net/mailman/listinfo/inkscape-docs join] the inkscape-docs mailing list and tell us about yourself.

So far we have established the following translations "zones":

* [http://translate.flossmanuals.net/bin/view/Inkscape_br/WebHome Brazilian]
* [http://translate.flossmanuals.net/bin/view/Inkscape_ca/WebHome Catalan]
* [http://fr.flossmanuals.net/ French]
* [http://translate.flossmanuals.net/bin/view/Inkscape_de/WebHome German]
* [http://translate.flossmanuals.net/bin/view/Inkscape_es/WebHome Spanish]
* [http://translate.flossmanuals.net/bin/view/Inkscape_pl/WebHome Polish]
* [http://translate.flossmanuals.net/bin/view/Inkscape_pt/WebHome Portuguese]
* [http://translate.flossmanuals.net/bin/view/Inkscape_ru/WebHome Russian]

Here is how you translate:

# In your translation zone you will see contents of the book. For each chapter there are "Edit" and "Translate" links and a status combobox that reveals various options. Start with those chapters which are marked as "Untranslated".
# Click "Translate"
# In the newly opened copy'n'paste contents of the most recent revision of chapter fromthe left editing field to the right one. A sequence of Ctrl+C and Ctrl+C should do the trick
# Translate
# Choose a new status of the newly created translation. '''Untranslated''' — if you just copy'n'pasted original text in English. '''Unpublished''' — if you translated the text, but want to review and improve it before it goes live. '''Published''' — if your translation is '''really''' ready to go live and visible for everybody else.
# Click 'Save'

You can still do further revision of that chapter anytime by clicking 'Edit' from the Contents table.

Reading [http://en.flossmanuals.net/bin/view/Inkscape/WritingConventions writing conventions] is strictly recommended for better understanding of markup rules and use of styles.

You can also track revisions in the translation zone by clicking "Subscribe" link in the translation zone index page. This will enable mailing you list of changes (to the address with which you registered in the system).

It's best to team up with several people and coordinate your efforts.

German contributors might like to reuse some text from [http://wiki.inkscape-forum.de/handbuch German] translation started by [[User:FZap]] in the DocBook/XML days of the manual.

We still haven't decided how to provide source SVG files in most comfortable way to make localization of illustrations easy. Ideas are welcome.

Note that French translation is placed in a different zone, because it's mostly ready. As soon as each translation is close to completeness, it is moved to its own subdomain too.

== People ==
* '''[[User:Relsi.ramone|Relsi Ramone]]''' - Contributor for Brazilian Portuguese - ''relsi.ramone at gmail.com''
* '''[[User:Cedric|Cedric Gemy]]''' - main contributor - ''cedric at le-radar.com''
* '''[[User:Elisa-yemanja|Elisa]]''' - contributor in French - ''elisa at ec.yemanja.net''
* '''John''' - Author and French/British translation
* '''Ernesto''' - Spanish translation - ''celise at prodigy.net.mx''
* '''Antonio''' - Italian translation - ''antonio.angelo at poste.it''
* '''Bryce''' - English translation/editing - ''bryce at bryceharrington.com''
* '''Kevin''' - English translation/editing - ''inkscape.docs at wixsonit.com''
* '''[[User:Colin Marquardt|Colin Marquardt]]''' - volunteer for a German translation from English, help with xml2po if needed. Especially interested in [[Embedded_Help]].
* '''[[User:vonHalenbach|vonHalenbach-de]]''' - volunteer for a translation of pygmees manual from English to German
* '''[[User:Prokoudine|Alexandre Prokoudine]]''' - volunteer for a translation into Russian

== Misc ==
* automated screenshot taking: maybe via [http://people.redhat.com/zcerza/dogtail/ Dogtail] (see [http://www.redhat.com/magazine/020jun06/features/dogtail/] and [http://www.redhat.com/magazine/021jul06/features/dogtail/]) or [http://ldtp.freedesktop.org/ LDTP]?
* see http://live.gnome.org/autoshot, http://osdir.com/ml/gnome.documentation/2006-08/msg00045.html

* the [http://inkscape.org/doc/inkscape-man.html Inscape "man page"]

* [[VectorAndBitmap]]
* [[Inkscape for Adobe Illustrator users]]
* [[TricksAndTips]]
* [[KeyboardShortcuts]]
* [[InkscapeColor]]

[[Category:User Documentation]]
[[Category:Needs Work]]

User manual information

2010-07-06T17:18:45Z

Legio noctis: Merged User_manual_information

User manual information

2010-07-06T17:16:37Z

Legio noctis: Reverted edits by Homy (Talk) to last version by Tweenk

== Read ==

http://en.flossmanuals.net/inkscape — this is where you read the manual.

== Contribute ==

# [http://lists.sourceforge.net/mailman/listinfo/inkscape-docs Subscribe] to the inkscape-docs mailing list
# Read the manual
# [http://wiki.inkscape.org/wiki/index.php/User_Manual_Work_in_Progress Read what needs to be done]
# Introduce yourself in the list and tell us what you want to do so that no work is duplicated
# Read [http://en.flossmanuals.net/bin/view/Inkscape/WritingConventions writing conventions]
# [http://en.flossmanuals.net/bin/view/Inkscape/WebHome Start contributing].

Here is is a hint: we try to use as much content from release notes as possible, since last 5-6 ones were written in a very much verbose way.

== Translate ==

We very much welcome translations of the manual. Please [http://lists.sourceforge.net/mailman/listinfo/inkscape-docs join] the inkscape-docs mailing list and tell us about yourself.

So far we have established the following translations "zones":

* [http://translate.flossmanuals.net/bin/view/Inkscape_br/WebHome Brazilian]
* [http://translate.flossmanuals.net/bin/view/Inkscape_ca/WebHome Catalan]
* [http://fr.flossmanuals.net/ French]
* [http://translate.flossmanuals.net/bin/view/Inkscape_de/WebHome German]
* [http://translate.flossmanuals.net/bin/view/Inkscape_es/WebHome Spanish]
* [http://translate.flossmanuals.net/bin/view/Inkscape_pl/WebHome Polish]
* [http://translate.flossmanuals.net/bin/view/Inkscape_pt/WebHome Portuguese]
* [http://translate.flossmanuals.net/bin/view/Inkscape_ru/WebHome Russian]

Here is how you translate:

# In your translation zone you will see contents of the book. For each chapter there are "Edit" and "Translate" links and a status combobox that reveals various options. Start with those chapters which are marked as "Untranslated".
# Click "Translate"
# In the newly opened copy'n'paste contents of the most recent revision of chapter fromthe left editing field to the right one. A sequence of Ctrl+C and Ctrl+C should do the trick
# Translate
# Choose a new status of the newly created translation. '''Untranslated''' — if you just copy'n'pasted original text in English. '''Unpublished''' — if you translated the text, but want to review and improve it before it goes live. '''Published''' — if your translation is '''really''' ready to go live and visible for everybody else.
# Click 'Save'

You can still do further revision of that chapter anytime by clicking 'Edit' from the Contents table.

Reading [http://en.flossmanuals.net/bin/view/Inkscape/WritingConventions writing conventions] is strictly recommended for better understanding of markup rules and use of styles.

You can also track revisions in the translation zone by clicking "Subscribe" link in the translation zone index page. This will enable mailing you list of changes (to the address with which you registered in the system).

It's best to team up with several people and coordinate your efforts.

German contributors might like to reuse some text from [http://wiki.inkscape-forum.de/handbuch German] translation started by [[User:FZap]] in the DocBook/XML days of the manual.

We still haven't decided how to provide source SVG files in most comfortable way to make localization of illustrations easy. Ideas are welcome.

Note that French translation is placed in a different zone, because it's mostly ready. As soon as each translation is close to completeness, it is moved to its own subdomain too.

== People ==
* '''[[User:Relsi.ramone|Relsi Ramone]]''' - Contributor for Brazilian Portuguese - ''relsi.ramone at gmail.com''
* '''[[User:Cedric|Cedric Gemy]]''' - main contributor - ''cedric at le-radar.com''
* '''[[User:Elisa-yemanja|Elisa]]''' - contributor in French - ''elisa at ec.yemanja.net''
* '''John''' - Author and French/British translation
* '''Ernesto''' - Spanish translation - ''celise at prodigy.net.mx''
* '''Antonio''' - Italian translation - ''antonio.angelo at poste.it''
* '''Bryce''' - English translation/editing - ''bryce at bryceharrington.com''
* '''Kevin''' - English translation/editing - ''inkscape.docs at wixsonit.com''
* '''[[User:Colin Marquardt|Colin Marquardt]]''' - volunteer for a German translation from English, help with xml2po if needed. Especially interested in [[Embedded_Help]].
* '''[[User:vonHalenbach|vonHalenbach-de]]''' - volunteer for a translation of pygmees manual from English to German
* '''[[User:Prokoudine|Alexandre Prokoudine]]''' - volunteer for a translation into Russian

== Misc ==
* automated screenshot taking: maybe via [http://people.redhat.com/zcerza/dogtail/ Dogtail] (see [http://www.redhat.com/magazine/020jun06/features/dogtail/] and [http://www.redhat.com/magazine/021jul06/features/dogtail/]) or [http://ldtp.freedesktop.org/ LDTP]?
* see http://live.gnome.org/autoshot, http://osdir.com/ml/gnome.documentation/2006-08/msg00045.html

* the [http://inkscape.org/doc/inkscape-man.html Inscape "man page"]

* [[VectorAndBitmap]]
* [[Inkscape for Adobe Illustrator users]]
* [[TricksAndTips]]
* [[KeyboardShortcuts]]
* [[InkscapeColor]]

[[Category:User Documentation]]
[[Category:Needs Work]]

User talk:Ali19971987

2010-06-19T19:47:15Z

Legio noctis: Created page with 'The best place to ask about this is on the [http://www.inkscapeforum.com/ Inkscape Forum]. ~~~~'

The best place to ask about this is on the [http://www.inkscapeforum.com/ Inkscape Forum]. [[User:Legio noctis|Legio noctis]] 19:47, 19 June 2010 (UTC)

Extension repository

2010-05-23T10:19:18Z

Legio noctis: Extension repository mockups

It would be very useful to have a central Internet repository for Inkscape extensions, similarly as Firefox has. This way, Inkscape could update installed extensions from the web site, with no need for the user to know if an extension is updated.

== Extensions ==

'''What extensions are there? We can start listing them here:'''
===[http://www.ekips.org/comp/inkscape/ Inkscape Effects]===
Aaron Spikes' set of extensions is now included in Inkscape.

===[[ExtrudeEffect]]===
Extrude polygons to "3d", also make "string art".

===[http://www.colibre.com.br/bin/view/Aurium/InkscapeCalendarShellScript InkscapeCalendarShellScript]===
Creating calendars sucks or is impractical if you do not have something that automates the process of putting the days organized in blocks of months for you. To format manually is easy, but this extension can help you on this too Bash script, works for Win32 with Cygwin.

===[http://www.colibre.com.br/bin/view/Aurium/InkscapeAreaCuter InkscapeAreaCutter]===
For web designers. Slice your site design into .png images. (pt_BR)

===[http://www.julienvitard.eu/ EQTeXSVG]===
Convert an inline LATEX equation into SVG path using Python.

===[http://www.kono.cis.iwate-u.ac.jp/~arakit/inkscape/inklatex.html InkLaTeX]===
Insert LaTeX text or equations into Inkscape.

===[http://www.iki.fi/pav/software/textext/ TexText]===
Embed re-editable LaTeX objects into SVG drawings.

===[http://math.univ-lille1.fr/~barraud/Inkscape/pathdeform/ PathDeform]===
Bend a path according to another one.
N.B. This extension was added to Inkscape 0.45 as "Pattern along Path".

===[http://www.inkbar.lineaire.net/ InkBar]===
Create EAN13 bar codes.

===[http://technoargia.free.fr/swftools/ SWF output]===
Save drawings as SWF.

===[http://www.colivre.coop.br/Aurium/Puff Puff]===
Fluffs elements! :D

===[http://www.colivre.coop.br/Aurium/InkSudoku Sudoku Generator]===
Generates a Sudoku square with its solution (''in a small square if you want'').

===[[CalligraphedOutlineFill]]===
Helps to fill in the inside area of shapes drawn with the Calligraphy tool.

===[http://edlab.die.unipd.it/Site4.html SlotStar]===
Helps to draw the star of slot of a winding of an electrical machine

===[http://richard.henwood.googlepages.com/inkscapelatexextension inkscapeLatexExtension]===
Extract text in an SVG drawing to a LaTeX picture environment.

===[http://saws.googlecode.com s.a.w.s]===
Export an SVG as valid XHTML/CSS files.

===[http://www.colivre.coop.br/Aurium/InkscapeGenerator Generator]===
Replace text and data to automatically generate files (as PDF, PS, JPG, etc...), based on an SVG template and a data file.

===[http://code.google.com/p/inkscape2tikz/ TikZ exporter]===
Export SVG paths as TikZ/PGF code for use with LaTeX.

===[[FindMatch]]===
Looks for paths that match the selected path and places all matches on the same layer.

===[http://xico.freeshell.org InkSyntax]===
A source code syntax highlighter plugin for Inkscape (wrapping [http://www.pygments.org pygments] and [http://www.andre-simon.de/doku/highlight/en/highlight.html highlight]).

===[http://sites.google.com/site/placeonpath/ Place Objects on Path]===
Places objects on a curve. The curve is the object that has the lowest z-order (and which must be a path). Distances between objects remain the same as they were before placing. If objects can't be placed on the curve because of their distances they are left in place. Objects will not be modified; clones are allowed. Arrange distances between your objects manually first as curve position and direction.

===[http://code.google.com/p/jessyink/ JessyInk]===
A collection of Javascripts that can be embedded into an SVG file to produce slide shows on opening in a browser. Current releases of JessyInk include a number of inkscape extensions to assign effects, transitions and other aspects of the presentations.

===[http://svg2dxf.googlecode.com/files/svg2dxf_inkscape.zip svg2dxf]===
Updated version of [http://www.bobcookdev.com/inkscape/inkscape-dxf.html Better Better DXF output] which adds support for polylines and does not overwrite the default inkscape simpletransform.py. See README if getting lxml xpath errors.

===[http://code.google.com/p/pixelsnap/ PixelSnap]===
Tool for aligning object/paths onto the pixel grid for bitmap export.

===[http://code.google.com/p/inkscape-guides-creator/ Guide creator]===
Creates multiple guides at once, at set intervals.

===[http://code.google.com/p/inkscapescalegenerator/ Scale Generator]===
Create ruler scales / map scales.

===[http://code.google.com/p/scott-inkscape/wiki/SevenSegmentDigits Seven Segment Digits]===
Create calculator style digits.

===[http://www.cnc-club.ru/forum/viewtopic.php?f=15&t=37&p=92 Close curves]===
Closes all open paths in the selection.

===[http://www.cnc-club.ru/forum/viewtopic.php?f=15&p=101 Gcode tools]===
Generates Gcode program (used in CNC machinery) from given paths.

===[http://dp48069596.lolipop.jp/inkscape_script.html Closeoff, Scatterpath, Selection, Zigzag and Netting]===
See [http://dp48069596.lolipop.jp/inkscape_video.html] for how to use Zigzag and scater extensions.

===[http://wiki.xmoto.tuxfamily.org/index.php?title=How_to_create_smooth_levels_using_Inkscape Inksmoto]===
Level editor for the Xmoto game.

===[http://www.cnc-club.ru/forum/viewtopic.php?f=33&t=37 Close Curves]===
Extension to close the paths in the selection, useful for importing filled paths into openoffice.

===[http://kalyaev.com/2010/20100423/gcodetools.html gcodetools]===
Gcodetools is a plug-in for Inkscape. It prepares and converts paths from Inkscape to Gcode, using biarc interpolation. for use with CNC milling machines.

==Extensions for Programmers:==
===[http://www.colivre.coop.br/bin/view/Aurium/RubyInk RubyInk]===
Inkscape extension with Ruby
===[http://www.colivre.coop.br/bin/view/Aurium/InkBash Ink-Bash]===
<nowiki>ShellScript</nowiki> Forever!
===[http://www.colivre.coop.br/bin/view/Aurium/InkMoz InkMoz]===
The Bridge from Inkscape to Mozilla (Inkscape extension with Javascript and more)

== The Repository Specification ==

A website where programmers can publish their extensions, users can search by that, and an update program can access this updates.

=== The Website ===

Must Have:
* '''User Registration''': to allow upload, votes and comments
* '''Extension Validation''': when published, it is public, but the user must be notified that was not validated (the code must be viewed by an validator user). The software updater do not update non-validated versions.
** '''Validation Feedback''': the validator user must write why the extension was not validated.
** '''Extension Deletion''': the validator user can delete an extension or version when he found a malicious code. The upload user must be marked as a malicious user and the account must be blocked.
* '''Extension Search''': with filter, by any available data.
* '''User Votes and Comments for Extensions''': The user can vote and/or comment an extension version.
* '''Extension Bug-Tracker''': today, third part extensions are in simple web-pages. The site may have a Bug-Traker to help all little scripts.
* '''User Extensions Requests''': a lot of users have ideas. Here is a good place for programmers see and make that alive.
* '''Host a cool page for the extension''': allow introduction text, documenbtation, screenshots, examples, and '''i18n'''!
* '''Help the l10n of this extensions''': with a web interface, like pootle and provide the l10n file for the updater program.
* '''Provide Version Control''': A SVN account will be cool, but web uploads (by web-forms) can be transparently SVN commits.

=== The Extension Meta-Data ===

''The data in INX file and more some, like the OS and Inkscape version compatibility...''

The INX file will define the meta-data settable by that. If some extension uses multiples INX files to have more than one option in the menu, all INX files must be read to set the meta-data. The meta-data will be cached in a database to help the search. The DB only need the meta-data of the last validated version and the last non-validated (if that is newer).

=== The Update Program ===

* '''Search for New Extensions''': when the user request
* '''Update Extensions''': search for updates and install that
* '''Help the Code Validation''': for advanced users. Show the extension code and the diff if is that an update.
* '''Help the User Bug-Reporting''': that is not working! The user must say now! ''(When the Update Program be part of the Inkscape, the error window can have a button to submit a bug-report)''
* '''Must test the extension dependencies''': the user must know what is needed to install before try to use.

== Name Proposal ==

Propose a name for the Inkscape Extension Repository:

* '''The Factory'''
* '''Extension Factory'''
* '''INX Factory'''

''Why Factory? Because it is not only a repository. ;-)''

* '''The Furnace'''
''Because Fire & Coal (Passion & Knowledge) are your tools for creating the extensions''

[[Category:Developer Documentation]]
[[Category:Extensions]]

== Mockups ==

Here are some suggestions for what an extension repository might look like.

<gallery>
File:Extension_repository_-_homepage.png|The home page.
File:Extension_repository_-_extension_page.png|The page for an individual extension.
File:Extension_repository_-_request_page.png|The page for an individual request.
File:Extension_repository_-_search_page.png|The search form page.
File:Extension_repository_-_search_results.png|The search results page.
File:Extension_repository_-_submit_extension.png|The extension submission page.
File:Extension_repository_-_submit_request.png|The request submission page.
File:Extension_repository_-_requests.png|The main requests page.
</gallery>

I have no idea of the detail of this project; I don't currently have the skills necessary to try implementing it. I'm also not sure whether it's a good idea for Inkscape to offer hosted repositories (using [http://www.redmine.org/projects/redmine Redmine] or [http://trac.edgewall.org/ Trac]?) or whether it would be better to just leave it to the developer to use somewhere like [http://github.com/ GitHub] or [http://bitbucket.org/ BitBucket] and then use their APIs to pull some basic data onto the site. [[User:Legio noctis|Legio noctis]] 10:19, 23 May 2010 (UTC)

File:Extension repository - request page.png

2010-05-23T10:15:11Z

Legio noctis: A mockup of an extension repository for Inkscape.