https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&user=Faceman&feedformat=atomInkscape Wiki - User contributions [en]2024-03-29T12:08:01ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=Roadmap_revised&diff=53775Roadmap revised2009-09-15T15:02:07Z<p>Faceman: Created page with '=== Milestone 14 - Inkscape 0.48 - Infrastructure and Bugfixing (Short Cycle, Point Releases) === Infrastructure * Change DVCS * Complete lib2geom integration * Continue Cairoif...'</p>
<hr />
<div>=== Milestone 14 - Inkscape 0.48 - Infrastructure and Bugfixing (Short Cycle, Point Releases) ===<br />
<br />
Infrastructure<br />
* Change DVCS<br />
* Complete lib2geom integration<br />
* Continue Cairoification (in new branch)<br />
<br />
Tools:<br />
* Text tool<br />
** [https://bugs.launchpad.net/inkscape/+bug/sf904962 correct handling of multiple font faces] by Text tool<br />
** Ability of setting other units than pixels<br />
** Better inline style editing<br />
** Hyphenation<br />
* [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/16938/ Filters tool]<br />
Finish autoswatches<br />
Finish Maximilian's patch for guides selection<br />
* Aligning objects to a selected guideline<br />
* Distribution of guides<br />
Update LPEs that can take advantage of the new node tool (e.g. envelope)<br />
<br />
<br />
Merge GSoC work<br />
* Spray tool<br />
<br />
Image links management<br />
* Better management of image links (manage absolute and relative links properly)<br />
* Simple UI to fix broken links or relink images<br />
* Proper interpretation of the resolution of the imported images (i.e.: if the document's default units are cm or inches, read the resolution value of the image and scale it to fit the proper size))<br />
<br />
Color Management<br />
* Support for icc profiles<br />
* Color managed view<br />
* Use recently added color management in poppler based PDF/AI import plug-in<br />
Guides<br />
<br />
Desktop Integration Effort:<br />
* [PARTIALLY DONE] Inter-application cut-and-paste<br />
* Inter-application drag-and-drop<br />
<br />
Extension Effort:<br />
* Unification of the way to display help on extensions<br />
* Localizable help of bundled extensions<br />
* Effect extensions browser<br />
<br />
File Import/Export:<br />
* File dialogues<br />
** Put all the non svg formats into export/import<br />
* Uniconvertor that can handle text<br />
* PDF Import/Export<br />
** Choice of PDF spec. (PDF/X-1a, PDF/X-3)<br />
** Add file info/comments<br />
** Generate multipage PDF documents<br />
** Define bleed and slug areas for offset printing<br />
** Add crop, bleed and registration marks<br />
** Add color bars<br />
* [[MicrosoftVisio|Visio]] support<br />
** Add extension for use of [[VDX2SVG]] (http://vdxtosvg.sourceforge.net/)<br />
<br />
=== Milestone 15 - Inkscape 0.49 - Code Refactoring (Long Cycle) ===<br />
<br />
Libraries<br />
* GDL - submit patches upstream, switch to dependency on upstream library<br />
* Finish Cairoification<br />
* Extract lib2geom, libavoid and libcoroco - switch to dependency as separate libraries<br />
<br />
Extensions<br />
* Make extensions more modular (groundwork for 3rd party extensions)<br />
<br />
Switch to the usual coordinates system<br />
<br />
Change build system<br />
<br />
GUI<br />
* Support for creating dock items with named icons<br />
<br />
SP tree<br />
<br />
Improve quality and speed of rendering</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=Save_as_vs_export&diff=25454Save as vs export2008-03-18T21:20:25Z<p>Faceman: </p>
<hr />
<div>= Sort out ''Save as'' vs ''Export'' formats =<br />
<br />
This blueprint stems from several discussions on the mailing list about which format should be available in ''Save as'' or in ''Export'' and whether some should be exclusively available in only one of those. <br />
<br />
==Current status==<br />
There are different opinions on the current status of this functionality in Inkscape which is:<br />
<br />
; Save<br />
: contains all possible file formats (except PNG) and saves with the same name. If a format other than Inkscape SVG (or SVGZ) is used, a nag screen is displayed at close time, to warn the user about possible data loss.<br />
; Save as<br />
: idem but saves with a new name and this new document is used inside Inkscape. Same nag screen.<br />
; Save a copy<br />
: idem but the new document is not used inside Inkscape. It is just written on the disk and work continues in the current document. Hence saving as a format different from SVG does not cause the nag screen to appear (the working document is still SVG)<br />
; Export<br />
: saves the drawing or part of it as a PNG raster file, with a new name, and keep the working image as SVG. The ''Export'' dialog can stay open at all times.<br />
<br />
As a reminder, current save formats are (at least): Inkscape SVG(Z), Plain SVG(Z), PS, EPS, Cairo PDF, Cairo PS, POV, ODG, TEX, AI (8.0), DXF, AutoCAD DXF, EPSI, GPL, XCF, XAML, Inkscape svg with media ZIP, EMF.<br />
<br />
Some people are just fine with this, some other think it is a mess, some other think a middle ground should be found between this and changing everything.<br />
<br />
==Proposal==<br />
<br />
The new behavior is based on the principles that<br />
# The user should not be able to shoot him/herself in the foot by saving only to a lossy format<br />
# The number of items in the file menu should be reduced<br />
# Functionality (or UI at least) should be consistent for all save/export format<br />
<br />
Principle 1 means that ''Save'' and ''Save as'' should only save as Inkscape SVG(Z) (and possibly plain SVG for people that only work in plain SVG?).<br />
<br />
Principle 2 means that one of ''Save a copy'' and ''Export'' has to go since they are kind of redundant.<br />
<br />
Principle 3 means that, when it is possible, saving in vector formats should offer the option to save only one object or a specific part of the canvas to the saved image, as export to PNG does. Furthermore, the UI should be consistent for this functionality.<br />
<br />
The proposed behavior is therefore<br />
<br />
; Save<br />
: saves only as Inkscape SVG(Z) (Plain SVG(Z)? People, please give opinions on this. I don't personally work with SVG as the end format so can't tell what the workflow is in this case. Plain SVG is lossy from the editing point of view but maybe that is a major pain to have two copies of the same document when working with what is supposed to be Inkscape's native format)<br />
; Save as<br />
: idem, with a new name and setting the working document to be the new file<br />
; Save a copy (incremental)<br />
: saves current file in its current working format (Inkscape SVG(Z) (Plain SVG(Z)) with the specified increment appended. The increment expression would be on a panel of the Document Preferences dialog, but should default to just a simple incremental number based on the existence of other files with the same name and an appended number.<br />
; Export<br />
: saves to all vector and bitmap (and other e.g. GPL) formats, comprising Inkscape SVG(Z) and Plain SVG(Z), with a new name, keeping the working document in place. The export dialog should present a similar set of options for all file types, disable those not available for the particular file type selected, in a dialog as compact as possible (since it is meant to stay open at all time)<br />
<br />
===Description of the export dialog===<br />
* a file chooser at the top, and file type defaulting to "Guess from extension". The chosen filename should be shown relative to the current document and use and ellipsis to always show the extension (so that it is immediately obvious which file type is exported)<br />
* batch export all selected object check box*<br />
* four tabs underneath (Page, Drawing, Objects, Custom)**<br />
* depending on the file type, enable or disable batch export<br />
* when batch export is unchecked/unavailable, enable or disable each tab depending on the file type<br />
** PNG: enable all<br />
** PDF/PS/EPS: enable page, drawing, objects<br />
** other graphic formats: enable page or drawing depending on the behaviour of the file type<br />
** other formats (GPL): disable all<br />
<br />
(*) To simplify matters, if batch export is restricted to PNG, it could be made a separate menu entry in the file menu Indeed, there is very little user interaction left in the dialog when it is checked (basically one can only click "Export") so it may be more efficiently done in one action (File > Batch export to bitmap) instead of three (File > Export bitmap, tick batch export, Click export). With SHIFT+ALT+CTRL+E as keyboard shortcut and a discardable nag screen (no they are not always evil) about the fact that it overwrites previous files it seems like a good solution to me.<br />
If batch export is implemented in other formats, then this menu-item could mean "batch-export in the last used format".<br />
<br />
(**) Selection becomes Objects and exports only selected objects (as with "hide all except selected objects" now). Custom behaves by default as "Selection" does now: the coordinates are the one of current selection and, when only one object is selected, the filename to which it is saved is saved in the SVG. When coordinates are changed manually and it reverts to how custom works currently. Does that make sense? Another solution would be to have Page, Drawing, Object, Selection/Selected area, Custom but it would make the dialog bigger.<br />
<br />
===Correspondance between bitmap and vector functionality===<br />
<table border="0" cellspacing="5" cellpadding="5"><br />
<tr><th>Bitmap</th><th>Cairo PDF/PS</th></tr><br />
<tr><td>page</td><td>page</td></tr><br />
<tr><td>drawing</td><td>drawing</td></tr><br />
<tr><td>selection+hide</td><td>by ID</td></tr><br />
<tr><td>selection-hide</td><td>no equivalent (could be achieved by clipping though, or setting a crop box in the pdf)</td></tr><br />
<tr><td>custom</td><td>no equivalent (idem)</td></tr><br />
</table><br />
(see http://jo.irisson.free.fr/dropbox/test-export.zip for an illustrated version)</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=User:JoshuaFacemyer&diff=17724User:JoshuaFacemyer2007-12-28T23:36:36Z<p>Faceman: New page: email and jabber: faceman <at> impressusart <dot> com</p>
<hr />
<div>email and jabber: faceman <at> impressusart <dot> com</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=UserManualOutline&diff=17004UserManualOutline2007-11-27T23:37:28Z<p>Faceman: </p>
<hr />
<div>== Future manual outline ==<br />
<br />
'''Introduction to Inkscape'''<br />
* About SVG<br />
* State of available SVG software<br />
* Inkscape Goals<br />
<br />
'''Basics''' (already outlined, needs some refinement)<br />
* Interface ''(no real depth here - just a basic overview of how these things work, where they are, what they look like...)''<br />
** Menus<br />
** Command Bar<br />
** Toolbars<br />
** Tool Options<br />
** Working with the Canvas<br />
** Rulers, Guides and Grids<br />
** Palette<br />
** Information Bar<br />
** Dialogs (at least the difference between floating/docked)<br />
<br />
'''Documents'''<br />
* Document properties<br />
* Creating templates<br />
* Metadata<br />
<br />
'''Toolbox'''<br />
* Selector<br />
* Navigation tools<br />
* Drawing tools<br />
* Transformation tools<br />
* Color tools<br />
* Text<br />
* Connector<br />
<br />
'''Objects'''<br />
* copying and pasting (+ styles)<br />
* transformations<br />
* grouping<br />
* cloning<br />
* whatever else<br />
<br />
'''Layers'''<br />
* you know what we need here<br />
<br />
'''Paths'''<br />
<br />
'''Colors'''<br />
* fill'n'stroke<br />
* swatches<br />
* color management<br />
* link to gradient tool<br />
* probably "clean up defs"<br />
<br />
'''Patterns'''<br />
<br />
'''Effects'''<br />
* modification effects<br />
* raster effects<br />
* Live Path Effects<br />
* SVG filters<br />
* creating new effects (i.e. Python scripts tutorial)<br />
<br />
'''Setting up Inkscape (Preferences)'''<br />
<br />
'''Additional help resources'''<br />
* everything from Help menu<br />
* copy of the page that links to international sites<br />
* mailing lists</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=UserManualOutline&diff=16999UserManualOutline2007-11-27T23:36:31Z<p>Faceman: </p>
<hr />
<div>== Future manual outline ==<br />
<br />
'''(Introduction to Inkscape)'''<br />
* About SVG<br />
* State of available SVG software<br />
* Inkscape Goals<br />
<br />
'''Basics''' (already outlined, needs some refinement)<br />
* Interface ''(no real depth here - just a basic overview of how these things work, where they are, what they look like...)''<br />
** Menus<br />
** Command Bar<br />
** Toolbars<br />
** Tool Options<br />
** Working with the Canvas<br />
** Rulers, Guides and Grids<br />
** Palette<br />
** Information Bar<br />
** Dialogs (at least the difference between floating/docked)<br />
<br />
'''Documents'''<br />
* Document properties<br />
* Creating templates<br />
* Metadata<br />
<br />
'''Toolbox'''<br />
* Selector<br />
* Navigation tools<br />
* Drawing tools<br />
* Transformation tools<br />
* Color tools<br />
* Text<br />
* Connector<br />
<br />
'''Objects'''<br />
* copying and pasting (+ styles)<br />
* transformations<br />
* grouping<br />
* cloning<br />
* whatever else<br />
<br />
'''Layers'''<br />
* you know what we need here<br />
<br />
'''Paths'''<br />
<br />
'''Colors'''<br />
* fill'n'stroke<br />
* swatches<br />
* color management<br />
* link to gradient tool<br />
* probably "clean up defs"<br />
<br />
'''Patterns'''<br />
<br />
'''Effects'''<br />
* modification effects<br />
* raster effects<br />
* Live Path Effects<br />
* SVG filters<br />
* creating new effects (i.e. Python scripts tutorial)<br />
<br />
'''Setting up Inkscape (Preferences)'''<br />
<br />
'''Additional help resources'''<br />
* everything from Help menu<br />
* copy of the page that links to international sites<br />
* mailing lists<br />
<br />
----<br />
<br />
<br />
Here's a more detailed outline proposal. I know it's missing some stuff. If you have any suggestions, feel free to add and/or comment on them. -JF<br />
<br />
*'''Introduction to Inkscape'''<br />
** About SVG<br />
** State of available SVG software<br />
** Inkscape Goals<br />
** Interface ''(no real depth here - just a basic overview of how these things work, where they are, what they look like...)''<br />
*** Menus<br />
*** Command Bar<br />
*** Toolbars<br />
*** Tool Options<br />
*** Working with the Canvas<br />
*** Rulers, Guides and Grids<br />
*** Palette<br />
*** Information Bar<br />
*** Dialogs (at least the difference between floating/docked)<br />
<br />
For me, dialogs, how to work with canvas, how to work with tool, it's after.<br />
(/elisa)<br />
Hum, i'm not sure : it depends if you think of the manual as a tutorial or as a help system. In the first case you're right, in the second, one usually first explain the environnment before going further because the reader simply don't read it from A to Z. So the TOC is not thought as a learning path but a logical. (/pygmee)<br />
<br />
(elisa) ok JF and you are ok to put working with canvas here. 2 yes and 1 no. Then it's ok :-) So, we are near our definitively TOC (just wait proposition of Alexandre).<br />
(/elisa)<br />
<br />
I like your layout. I moved a few things (Tool Options after toolbars, since it makes more sense to have the subordinate come second). I think we still need to make mention of the Dialogs here, but just general mention of how they work. The specifics of each dialog will come in following sections. You still have Working with the Canvas above, though you said you thought it should come later. I think it should be briefly described above, more specifically later. -JF<br />
<br />
*'''Toolbox''' ''(In depth, but limited to what you can do simply by clicking on the tool and using its toolbar controls)''<br />
** Selector<br />
** Node Tool<br />
** Tweak Tool<br />
** Magnification Tool<br />
** Object Tools<br />
*** Box Tool<br />
*** Elipse Tool<br />
*** Shape Tool<br />
*** Spiral Tool<br />
** 3D Tool<br />
** Drawing Tools<br />
*** Freehand Tool<br />
*** Bezier Tool<br />
*** Calligraphy Tool<br />
**** Engraving Tool<br />
** Paint Bucket / Fill Tool<br />
** Text Tool<br />
** Diagram Tool<br />
** Color Tools<br />
*** Gradient Tool<br />
*** Color Picker / Dropper<br />
<br />
(elisa) for me color bar not here, but at the begining in presentation of interface. (/elisa)<br />
<br />
I took it out - since there's not much to talk about anyway it will be taken care of in the interface section. -JF<br />
<br />
*'''Advanced Topics''' ''(Stuff in menus and dialogs)''<br />
** Fill / Stroke<br />
** Display<br />
*** Display modes<br />
*** Icon preview<br />
** Effects<br />
*** Filter ''(Different from path effects?)''<br />
*** Path<br />
*** Raster<br />
** Arrangement of Objects<br />
*** Coordinates (?)<br />
*** Layers<br />
*** Aligning / Distributing<br />
*** Grids, Guides & Snapping<br />
** Object Operations<br />
*** Path Operations<br />
*** Selecting / Copying / Pasting<br />
*** Grouping<br />
*** Duplicating / Cloning / Tile Cloning<br />
*** Transforming<br />
*** Clip / Mask<br />
*** Bitmap Functions ''(any operation particular to bitmaps not covered elsewhere)''<br />
**** Make Bitmap Copy<br />
**** Tracing Bitmap<br />
** Text ''(Detailed)''<br />
** Input ''(Mouse, Keyboard, Pen Tablet, Telekinesis :)''<br />
** Document Properties<br />
** (Vacuum Defs)<br />
** Import / Export / Saving As ''(detailed)''<br />
*** Openclipart Import / Export Script<br />
*** File Format spec and inkscape conformity<br />
** Printing<br />
** Inkscape Preferences<br />
<br />
(elisa) For me, all ok,all the dialogs and the effects here.(/elisa)<br />
<br />
<br />
*'''Super Advanced Topics''' ''("Power User" stuff, hidden options, etc)''<br />
** XML Editor<br />
** Color Profiling ''(Color Management)''<br />
** Whiteboard<br />
** Hidden Options<br />
** Command Line<br />
** Scripting<br />
** Using Inkview ''(Can it do anything besides display a file?)''<br />
<br />
*'''Resources'''<br />
** Tutorials ''(Either included or linked to online version)''<br />
** Website / Wiki<br />
** Forums / Mailing Lists<br />
** SVG Spec Reference<br />
** Other Pertinent Links</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16779DocumentationStandards2007-11-16T20:32:10Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
(official definitions can be found [http://www.docbook.org/tdg5/en/html/ here])<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasizing text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
=Usages=<br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".<br />
<br />
=References=<br />
Simplified DockBook - http://www.docbook.org/schemas/sdocbook/elements.html<br />
<br />
Gnome project standards project - not much there yet as it's developing - http://live.gnome.org/ProjectMallard</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16774DocumentationStandards2007-11-16T20:30:11Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
(official definitions can be found [http://www.docbook.org/tdg5/en/html/ here])<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasizing text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
=Usages=<br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16769DocumentationStandards2007-11-16T20:28:58Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
(official definitions can be found [http://www.docbook.org/tdg5/en/html/ here])<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasizing text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16764DocumentationStandards2007-11-16T20:09:00Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
(official definitions can be found [http://www.docbook.org/tdg5/en/html/ here])<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16748DocumentationStandards2007-11-15T15:56:00Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16747DocumentationStandards2007-11-15T15:54:56Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*<caption> - brief but specific description of an image<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16746DocumentationStandards2007-11-15T15:53:41Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*<guiicon> - points to an application icon image file (see below)<br />
*<inlinegraphic> - is this a valid docbook tag? Seems like it should be <inlinemediaobject><br />
*<itemizedlist><br />
*<listitem><br />
*<procedure><br />
*<step><br />
*<variablelist><br />
*<varilistentry><br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16745DocumentationStandards2007-11-15T15:48:45Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
*<mediaobject> - a wrapper for media (if multiples media objects are included in the same tag, only one is shown, depending on the displaying system) (see below)<br />
*<imageobject> - a wrapper for an image file (see below)<br />
*<imagedata> - pointer to the image file (used with "fileref" attribute, see below)<br />
*<guiicon> - points to an application icon image file (see below)<br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16744DocumentationStandards2007-11-15T15:38:50Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> (to replace <simplesect>) - paragraphs with titles (uses <title> tag)<br />
*<guimenu> - a top-level menu (such as "File")<br />
*<guisubmenu> - any sub-menu of another menu<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for a terminal item on a menu (for example "save as" in the "File" menu)<br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - a key used with a meta key for key commands (e.g. "s" when you hit "ctrl+s" to do a quick save)<br />
*<emphasis> used for emphasising text - WHEN SHOULD THIS BE USED?<br />
*<keycap> - the actual label of a key on the keyboard (usage: probably used within <keycombo> tags most often)<br />
*<keycombo> - standard key combination for a command (e.g. "ctrl+s" would be marked up as <keycombo><keycap>Ctrl</keycap><keycap>S</keycap></keycombo>)<br />
<br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16741DocumentationStandards2007-11-14T21:13:56Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
*<formalpara> to replace <simplesect> - paragraphs with titles<br />
*<guimenuitem> (guimenuitem accel accel guimenuitem) - is for final menu, for example "save as" in the "file <guimenu><br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*<accel> - ?<br />
*<emphasis> inline tag<br />
*<keycap> - (keycombo keycap keycombo)<br />
*<keycombo> - standard key combination for a command (keycombo is to define a key combination for ex Ctrl+S where Ctrl is a keycap and S another one) <br />
*tag-tree for pictures especially screenshots and icons (for tools and cursors) <br />
**mediaobject imageobject imagedata fileref="" imageobject mediaobject<br />
*** caption - légende<br />
**guiicon inlinegraphic fileref="" guiicon<br />
*indexeterm primary secondary indexterm - tag for index<br />
*itemizedlist listitem para listitem itemizedlist<br />
*procedure step step procedure<br />
*variablelist varilistentry => ?????????? what's that ?<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<indexterm> <primary></primary><secondary></secondary></indexterm> (here or after ?)<br />
<formalpara> <title></title><br />
<mediaobject> <imageobject><imagedata firelef="url/"></imageoject><br />
<caption></caption><br />
</mediaobject><br />
<para></para><br />
<itemizedlist><listitem><para></para></listitem></itemizedlist><br />
<emphasis></emphasis><br />
<br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16731DocumentationStandards2007-11-13T02:59:52Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
<br />
(are we keeping these?)<br />
*<formalpara> to replace <simplesect> - paragraphs with titles<br />
*<guimenuitem> - is for final menu, for example "save as" in the "file <guimenu><br />
*<guilabel> - stands for any label at any places : Fill at the bottom or X property ...<br />
*(keeping them is interesting : at export it is easier to applie specific formatting if they are tagged.)<br />
*<emphasis> - ?<br />
*<accel> - ?<br />
*<keycap> - ?<br />
*<keycombo> - standard key combination for a command (keycombo is to define a key combination for ex Ctrl+S where Ctrl is a keycap and S another one)<br />
* i would also keep accel, keycap, and keycombo which are different ways of reaching a command, and having them it is also easy to build a accel list, keycombo list.<br />
<br />
*add the tag-tree for pictures especially screenshots and icons (for tools and cursors)<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<para></para><br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationStandards&diff=16727DocumentationStandards2007-11-12T21:49:49Z<p>Faceman: </p>
<hr />
<div>Here is a list of proposals for documentation standards for the User Manual (most important for DocBook xml and content)<br />
<br />
=DocBook tags we should use=<br />
*<book> - main tag encapsulating the whole book<br />
*<part> - For larger sections (e.g. "Menus", etc; should only be a few of these in the book)<br />
*<chapter> - subsections of a part (e.g."File" menu)<br />
*<section> - subsections of a chapter (e.g. "Save" menu item)<br />
*<para> - encapsulating any subsection of a chapter that needs a distinction from the preceeding and proceeding text (textual paragraphs, text content withing each list item or procedural item, etc)<br />
<br />
(are we keeping these?)<br />
<br />
*<guimenuitem> - ?<br />
*<guilabel> - ?<br />
*<emphasis> - ?<br />
*<accel> - ?<br />
*<keycap> - ?<br />
*<keycombo> - standard key combination for a command<br />
<br />
maybe http://www.docbook.org/schemas/sdocbook/elements.html?<br />
<br />
http://live.gnome.org/ProjectMallard - not much there<br />
<br />
=Basic Structure of a Part=<br />
*title+Intro+screenshot+Activation+Procedure+Additional infos+Links<br />
<br />
<part> <title></title><br />
<chapter> <title></title><br />
<section> <title></title><br />
<para></para><br />
</section><br />
<chapter><br />
</part><br />
<br />
=Miscellany=<br />
* Links to sections should be named the same as the section title, except don't use caps and replace all spaces with dashes, e.g., the link for section "Menu Bar" would be "menu-bar".</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_object_tocurve.png&diff=16634File:Orig object tocurve.png2007-10-29T17:56:34Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_stroke_tocurve.png&diff=16633File:Orig stroke tocurve.png2007-10-29T17:56:19Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_symmetric.png&diff=16632File:Orig node symmetric.png2007-10-29T17:56:09Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_smooth.png&diff=16631File:Orig node smooth.png2007-10-29T17:55:53Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_line.png&diff=16630File:Orig node line.png2007-10-29T17:55:44Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_join_segment.png&diff=16629File:Orig node join segment.png2007-10-29T17:55:42Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_join.png&diff=16628File:Orig node join.png2007-10-29T17:55:27Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_insert.png&diff=16627File:Orig node insert.png2007-10-29T17:55:20Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_delete_segment.png&diff=16626File:Orig node delete segment.png2007-10-29T17:55:11Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_delete.png&diff=16625File:Orig node delete.png2007-10-29T17:54:19Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_cusp.png&diff=16624File:Orig node cusp.png2007-10-29T17:54:02Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_curve.png&diff=16623File:Orig node curve.png2007-10-29T17:53:52Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_node_break.png&diff=16622File:Orig node break.png2007-10-29T17:53:39Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_nodes_show_handles.png&diff=16621File:Orig nodes show handles.png2007-10-29T17:52:59Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_transform_stroke.png&diff=16620File:Orig transform stroke.png2007-10-29T17:46:57Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_transform_pattern.png&diff=16619File:Orig transform pattern.png2007-10-29T17:46:43Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_transform_gradient.png&diff=16618File:Orig transform gradient.png2007-10-29T17:46:34Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_transform_corners.png&diff=16617File:Orig transform corners.png2007-10-29T17:46:21Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_select_all_in_all_layers.png&diff=16616File:Orig selection select all in all layers.png2007-10-29T17:46:12Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_select_all.png&diff=16615File:Orig selection select all.png2007-10-29T17:46:02Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_deselect.png&diff=16614File:Orig selection deselect.png2007-10-29T17:45:50Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_top.png&diff=16613File:Orig selection top.png2007-10-29T17:45:39Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_down.png&diff=16612File:Orig selection down.png2007-10-29T17:45:29Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_bot.png&diff=16611File:Orig selection bot.png2007-10-29T17:45:18Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_selection_up.png&diff=16610File:Orig selection up.png2007-10-29T17:45:07Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_object_rotate_90_CW.png&diff=16609File:Orig object rotate 90 CW.png2007-10-29T17:44:58Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_object_rotate_90_CCW.png&diff=16608File:Orig object rotate 90 CCW.png2007-10-29T17:41:58Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_object_flip_ver.png&diff=16607File:Orig object flip ver.png2007-10-29T17:35:42Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=File:Orig_object_flip_hor.png&diff=16606File:Orig object flip hor.png2007-10-29T17:32:20Z<p>Faceman: </p>
<hr />
<div></div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=UserManualOutline&diff=16602UserManualOutline2007-10-29T04:43:02Z<p>Faceman: </p>
<hr />
<div>== Future manual outline ==<br />
<br />
Proposition of Alexandre :<br />
<br />
'''Basics'''<br />
* (already outlined, needs some refinement) Do you mean what is below? -JF<br />
<br />
'''(Introduction to Inkscape)'''<br />
* About SVG<br />
* State of available SVG software<br />
* Inkscape Goals<br />
* Interface ''(no real depth here - just a basic overview of how these things work, where they are, what they look like...)''<br />
** Menus<br />
** Command Bar<br />
** Toolbars<br />
** Tool Options<br />
** Working with the Canvas<br />
** Rulers, Guides and Grids<br />
** Palette<br />
** Information Bar<br />
** Dialogs (at least the difference between floating/docked)<br />
<br />
'''Documents'''<br />
* Document properties<br />
* Creating templates<br />
* Metadata<br />
<br />
'''Toolbox'''<br />
* Selector<br />
* Navigation tools<br />
* Drawing tools<br />
* Transformation tools<br />
* Color tools<br />
* Text<br />
* Connector<br />
<br />
'''Objects'''<br />
* copying and pasting (+ styles)<br />
* transformations<br />
* grouping<br />
* cloning<br />
* whatever else<br />
<br />
'''Layers'''<br />
* you know what we need here<br />
<br />
'''Paths'''<br />
<br />
'''Colors'''<br />
* fill'n'stroke<br />
* swatches<br />
* color management<br />
* link to gradient tool<br />
* probably "clean up defs"<br />
<br />
'''Patterns'''<br />
<br />
'''Effects'''<br />
* modification effects<br />
* raster effects<br />
* Live Path Effects<br />
* SVG filters<br />
* creating new effects (i.e. Python scripts tutorial)<br />
<br />
'''Setting up Inkscape (Preferences)'''<br />
<br />
'''Additional help resources'''<br />
* everything from Help menu<br />
* copy of the page that links to international sites<br />
* mailing lists<br />
<br />
----<br />
<br />
<br />
Here's a more detailed outline proposal. I know it's missing some stuff. If you have any suggestions, feel free to add and/or comment on them. -JF<br />
<br />
*'''Introduction to Inkscape'''<br />
** About SVG<br />
** State of available SVG software<br />
** Inkscape Goals<br />
** Interface ''(no real depth here - just a basic overview of how these things work, where they are, what they look like...)''<br />
*** Menus<br />
*** Command Bar<br />
*** Toolbars<br />
*** Tool Options<br />
*** Working with the Canvas<br />
*** Rulers, Guides and Grids<br />
*** Palette<br />
*** Information Bar<br />
*** Dialogs (at least the difference between floating/docked)<br />
<br />
For me, dialogs, how to work with canvas, how to work with tool, it's after.<br />
(/elisa)<br />
Hum, i'm not sure : it depends if you think of the manual as a tutorial or as a help system. In the first case you're right, in the second, one usually first explain the environnment before going further because the reader simply don't read it from A to Z. So the TOC is not thought as a learning path but a logical. (/pygmee)<br />
<br />
(elisa) ok JF and you are ok to put working with canvas here. 2 yes and 1 no. Then it's ok :-) So, we are near our definitively TOC (just wait proposition of Alexandre).<br />
(/elisa)<br />
<br />
I like your layout. I moved a few things (Tool Options after toolbars, since it makes more sense to have the subordinate come second). I think we still need to make mention of the Dialogs here, but just general mention of how they work. The specifics of each dialog will come in following sections. You still have Working with the Canvas above, though you said you thought it should come later. I think it should be briefly described above, more specifically later. -JF<br />
<br />
*'''Toolbox''' ''(In depth, but limited to what you can do simply by clicking on the tool and using its toolbar controls)''<br />
** Selector<br />
** Node Tool<br />
** Tweak Tool<br />
** Magnification Tool<br />
** Object Tools<br />
*** Box Tool<br />
*** Elipse Tool<br />
*** Shape Tool<br />
*** Spiral Tool<br />
** 3D Tool<br />
** Drawing Tools<br />
*** Freehand Tool<br />
*** Bezier Tool<br />
*** Calligraphy Tool<br />
**** Engraving Tool<br />
** Paint Bucket / Fill Tool<br />
** Text Tool<br />
** Diagram Tool<br />
** Color Tools<br />
*** Gradient Tool<br />
*** Color Picker / Dropper<br />
<br />
(elisa) for me color bar not here, but at the begining in presentation of interface. (/elisa)<br />
<br />
I took it out - since there's not much to talk about anyway it will be taken care of in the interface section. -JF<br />
<br />
*'''Advanced Topics''' ''(Stuff in menus and dialogs)''<br />
** Fill / Stroke<br />
** Display<br />
*** Display modes<br />
*** Icon preview<br />
** Effects<br />
*** Filter ''(Different from path effects?)''<br />
*** Path<br />
*** Raster<br />
** Arrangement of Objects<br />
*** Coordinates (?)<br />
*** Layers<br />
*** Aligning / Distributing<br />
*** Grids, Guides & Snapping<br />
** Object Operations<br />
*** Path Operations<br />
*** Selecting / Copying / Pasting<br />
*** Grouping<br />
*** Duplicating / Cloning / Tile Cloning<br />
*** Transforming<br />
*** Clip / Mask<br />
*** Bitmap Functions ''(any operation particular to bitmaps not covered elsewhere)''<br />
**** Make Bitmap Copy<br />
**** Tracing Bitmap<br />
** Text ''(Detailed)''<br />
** Input ''(Mouse, Keyboard, Pen Tablet, Telekinesis :)''<br />
** Document Properties<br />
** (Vacuum Defs)<br />
** Import / Export / Saving As ''(detailed)''<br />
*** Openclipart Import / Export Script<br />
*** File Format spec and inkscape conformity<br />
** Printing<br />
** Inkscape Preferences<br />
<br />
(elisa) For me, all ok,all the dialogs and the effects here.(/elisa)<br />
<br />
<br />
*'''Super Advanced Topics''' ''("Power User" stuff, hidden options, etc)''<br />
** XML Editor<br />
** Color Profiling ''(Color Management)''<br />
** Whiteboard<br />
** Hidden Options<br />
** Command Line<br />
** Scripting<br />
** Using Inkview ''(Can it do anything besides display a file?)''<br />
<br />
*'''Resources'''<br />
** Tutorials ''(Either included or linked to online version)''<br />
** Website / Wiki<br />
** Forums / Mailing Lists<br />
** SVG Spec Reference<br />
** Other Pertinent Links</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=TangoifiedIcons&diff=16505TangoifiedIcons2007-10-24T04:09:41Z<p>Faceman: New page: It would be nice to have a complete Tangoified Inkscape Icon Set for a future release (hopefully sooner rather than later). The current set [http://gnomelook.org/content/show.php/Tangofi...</p>
<hr />
<div>It would be nice to have a complete Tangoified Inkscape Icon Set for a future release (hopefully sooner rather than later).<br />
<br />
<br />
The current set [http://gnomelook.org/content/show.php/Tangofied+inkscape+icons+set?content=48140 here] is lacking many icons. It is based on the [http://tango.freedesktop.org/ArtLibreSet Tango ArtLibre Icon Set], which also Gimp is using.<br />
<br />
<br />
Maybe this would be a good place to list all the icons Inkscape needs and the corresponding icon places (whether filled or not) in the [http://tango.freedesktop.org/ArtLibreSet ArtLibre Set].</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=Application_icons&diff=16504Application icons2007-10-24T04:02:25Z<p>Faceman: </p>
<hr />
<div>This is the development discussion of ICONS for Inkscape.<br />
<br />
David Horsley, please rsend your SVG file type icon for windows to the development list for inkscape (inkscape_bayo_screeshot.jpg) <br />
<br />
DEFENDGUIN and others have been asking about ICON development. We need to figure out where we stand on this? Do we want to develop ALL new icons, or replace some existing ones, or fill-in the ones we don't have completed?<br />
<br />
Is anyone familiar with the procedure on how to design and implement new icons in the Inkscape Interface? It would be helpful if someone (bulia? ahem... :) ) could take the time to lay-out how to do this for some newbies to the project (DEFENDGUIN, myself, etc).<br />
<br />
Inkscape Icon suitable for GNOME menu use is included with Inkscape. By default it is installed to /usr/share/pixmaps/inkscape.png.<br />
<br />
==Stock Icons==<br />
This list is here to provide a guide of what gnome stock icon names match functions, tools and dialogs in inkscape. <br />
By referencing to these icons it allows inkscapes icon set to be modified by the global gnome theme.<br />
<br />
I'll be creating gnome style icons for the functions not yet included and submit them to the gnome icon theme to be distributed with the rest of the stock gnome icons<br />
- [[AndyFitz]]<br />
<br />
===Main Menu===<br />
<br />
====FILE====<br />
'''new document''' <br />
/stock/document/stock_new<br />
<br />
'''print'''<br />
/stock/io/stock_print<br />
<br />
'''open'''<br />
/stock/io/stock_open<br />
<br />
'''save'''<br />
/stock/io/stock_save<br />
<br />
'''save as'''<br />
/stock/io/stock_save-as<br />
<br />
'''revert'''<br />
/stock/io/stock_reload<br />
<br />
'''export bitmap'''<br />
/stock/io/stock_export<br />
<br />
<br />
====EDIT====<br />
'''cut'''<br />
/stock/generic/stock_cut<br />
<br />
'''copy'''<br />
/stock/generic/stock_copy<br />
<br />
'''paste'''<br />
/stock/generic/stock_paste<br />
<br />
'''delete'''<br />
/stock/generic/stock_delete<br />
<br />
'''undo'''<br />
/stock/generic/stock_undo<br />
<br />
'''redo'''<br />
/stock/generic/stock_redo<br />
<br />
====HELP====<br />
<br />
'''About'''<br />
/stock/generic/stock_about<br />
<br />
'''Tutorials'''<br />
/stock/generic/stock_book-open<br />
<br />
'''keys and mouse'''<br />
!TBD-[[AndyFitz]]!<br />
<br />
<br />
===Main Toolbar===<br />
'''new document'''<br />
/stock/object/stock_inster_graphic<br />
<br />
'''insert image'''<br />
/stock/image/stock_insert_image<br />
<br />
<br />
===functions===<br />
<br />
'''cut'''<br />
/stock/generic/stock_cut<br />
<br />
'''copy'''<br />
/stock/generic/stock_copy<br />
<br />
'''paste'''<br />
/stock/generic/stock_paste<br />
<br />
'''delete'''<br />
/stock/generic/stock_delete<br />
<br />
'''undo'''<br />
/stock/generic/stock_undo<br />
<br />
'''redo'''<br />
/stock/generic/stock_redo<br />
<br />
'''print'''<br />
/stock/io/stock_print<br />
<br />
'''open'''<br />
/stock/io/stock_open<br />
<br />
'''save'''<br />
/stock/io/stock_save<br />
<br />
'''save as'''<br />
/stock/io/stock_save-as<br />
<br />
'''revert'''<br />
/stock/io/stock_reload<br />
<br />
'''export bitmap'''<br />
/stock/io/stock_export<br />
<br />
===TOOLS===<br />
<br />
'''Pencil ( Freehand tool )'''<br />
/stock/image/stock_draw-freeform-line<br />
<br />
'''pen / bezier'''<br />
/stock/image/stock_linepen<br />
<br />
'''text'''<br />
/stock/text/stock_draw-text<br />
<br />
'''zoom'''<br />
/stock/navigation/stock_zoom<br />
<br />
'''color picker'''<br />
/stock/image/stock_3d-color-picker<br />
<br />
===Dialogs===<br />
<br />
'''Fill and Stroke'''<br />
<br />
'''Inkscape Properties'''<br />
/stock/generic/stock_properties<br />
<br />
'''document Properties'''<br />
/stock/generic/stock_file-properties<br />
<br />
'''grid'''<br />
/stock/image/stock_display-grid<br />
<br />
'''Align and Distribute'''<br />
/stock/image/stock_graphics-align-left<br />
<br />
/stock/image/stock_graphics-align-right<br />
<br />
/stock/image/stock_graphics-align-top<br />
<br />
/stock/image/stock_graphics-align-bottom<br />
<br />
/stock/image/stock_graphics-align-center<br />
<br />
/stock/image/stock_graphics-align-centered<br />
<br />
'''circle, elipse, arc'''<br />
/stock/image/stock_draw-circle-pie <br />
<br />
'''open arc'''<br />
/stock/image/stock_draw-circle-segment<br />
<br />
'''rectangle, square '''<br />
/stock/image/stock_draw-rounded-rectangle<br />
<br />
==See Also==<br />
<br />
*[[TangoifiedIcons|Tangoified Inkscape Icon Set]]<br />
*[[HowToEditIcons|How to Edit Icons]]<br />
*[[IconsStyle|Icon Style]]<br />
*[http://www.out-of-order.ca/inkscape-icon-tutorial/ A Beginner's tutorial on making icons in Inkscape]<br />
*[http://developer.gnome.org/projects/gup/hig/2.0/icons.html Gnome HIG about icons]<br />
*[http://developer.gnome.org/projects/gup/hig/2.0/design.html#Palette Colors for Gnome icons]<br />
*[http://mmmaybe.gimp.org/tutorials/Creating_Icons/ "Creating Icons" tutorial from Jacub Steiner for GIMP]<br />
*[http://jimmac.musichall.cz/ikony.php3 Jacub Steiners icons]<br />
*[http://placide.home.sapo.pt/inkscape.html Plácido Sousa's crispy icon theme]<br />
*[http://www.freeiconsweb.com Free Icons Library]<br />
<br />
[[Category:Developer Discussion]]<br />
[[Category:Needs Work]]</div>Facemanhttps://wiki.inkscape.org/wiki/index.php?title=DocumentationReferences&diff=16450DocumentationReferences2007-10-17T02:01:56Z<p>Faceman: New page: [http://wiki.docbook.org DocBook Wiki] [http://www.oasis-open.org/docbook/documentation/reference/html/docbook.html DocBook: the Definitive Guide] [http://l10n.kde.org/docs/markup/markup...</p>
<hr />
<div>[http://wiki.docbook.org DocBook Wiki]<br />
<br />
[http://www.oasis-open.org/docbook/documentation/reference/html/docbook.html DocBook: the Definitive Guide]<br />
<br />
[http://l10n.kde.org/docs/markup/markup-guide.html KDE's guide to DocBook authoring]<br />
<br />
[http://opensource.bureau-cornavin.com/crash-course/en/index.html Writing Documentation Using DockBook - a tutorial]<br />
<br />
[http://www.sagehill.net/docbookxsl/index.html DocBook XSL]<br />
<br />
[http://docbook.sourceforge.net/release/xsl/current/doc/ DocBook XSL Stylesheets]<br />
<br />
[http://nwalsh.com/docs/articles/dbdesign/ Another one on XSL Stylesheets]<br />
<br />
[http://www.garshol.priv.no/download/xmltools/ Free XML Tools] - might have something handy for editing</div>Faceman