- Inkscape Docs - Inkscape Mailman

Announcing an Inkscape Manual Booksprint
by Joshua Facemyer / Impressus Art 02 Jun '08

02 Jun '08

A short time ago, those of us who had been actively discussing the manual on the inkscape-docs list agreed that FLOSS Manuals (http://flossmanuals.net <http://flossmanuals.net/>) was our best option for keeping an official manual up-to-date while encouraging non-technical users to contribute. It has a simple interface, is readily available (it is a web application), and there exist translation tools which are being actively developed to provide a usable translation interface. There are many other benefits to using FLOSS Manuals (FM) as well: we would have the ability to organize different setups of manuals / how-tos by arranging existing content into new “manuals”; to generate manuals in different distributable formats (export as pdf, html, and even print online with lulu.com, et cetera). These powerful capabilities create an exciting possibility to build and maintain a dynamic manual with minimal effort. Recently, FM has received a small grant from Google to host a “book sprint”. Adam Hyde of FM has personally invited some of the members from the inkscape-docs list to join him for the book sprint in order to flesh out a basic, up-to-date manual using the FM tools. (If you have not seen how this works yet, you can go to the website and check it out. Since our manual has only some test material in it, you cannot yet view it as a manual, but if you set up user account, you can view it in the edit mode.) While FM has certain guidelines which the book sprint must follow and goals to accomplish, we will be discussing on inkscape-docs the particulars which we want the book sprint to produce in order to make it most productive for both FM and Inkscape. Adam will be active in this discussion, and help guide it so that it proceeds toward both FLOSS Manual goals and Inkscape Docs goals. Anyone who would like to participate in this discussion is welcome and encouraged to do so. Also, anyone is welcome and encouraged to take part in the actual book sprint itself, which will be taking place from July 5^th through the 12^th in Paris. Participants are welcome either in person, if you are able, or else by internet. (Details will follow on inkscape-docs as they are worked out.) The committed participants thus far are: Adam Hyde (from FLOSS Manuals) Brianna Laugher from Wikimedia (http://brianna.modernthings.org <http://brianna.modernthings.org/>) Cédric Gemy (pygmee) Elisa de Castro Guerra (yemanja) Alexandre Prokoudine and I (Joshua Facemyer) We are all looking forward to spending some time getting to know each other better, seeing Paris (those of us who don't live there ;) and, most importantly, putting together an Inkscape Manual for the betterment of the Inkscape community!

2 1

svg filters
by Alexandre Prokoudine 30 Apr '08

30 Apr '08

Hi, Felipe started a series of tutorials on SVG filters. http://fedev.blogspot.com/2008/04/filter-effects-blend.html http://fedev.blogspot.com/2008/04/filter-effects-color-matrix.html BTW, which of contents is the final one? Alexandre

3 4

German online documentation - interpolation
by Helmut Hauser 24 Apr '08

24 Apr '08

Hello, I have noted that the documentation part (HTML) about interpolation in German is not entirely translated. see: http://www.inkscape.org/doc/interpolate/tutorial-interpolate.de.html I would like to help. Where can I start to do so? thanks for this awesome piece of software. cheers, Helmut __________________________________________________________ Gesendet von Yahoo! Mail. Der Mailbox mit unbegrenztem Speicher. http://de.overview.mail.yahoo.com

2 1

docs source file format
by Alexandre Prokoudine 24 Feb '08

24 Feb '08

Hi people, A week ago I was in Zagreb on Open Translation Tools 2007 conference. One of the guys there wa Adam Hyde who created http://flossmanuals.net/. This is a website based on twiki which is multilingual by design. You can create/edit content, translate content etc. It outputs PDF, HTML and zipped HTML, maybe even more. Do we want to invest time into figuring out how it might fit our workflow? Alexandre

4 7

tutorials
by Alexandre Prokoudine 13 Feb '08

13 Feb '08

Hi, Here is the list of tutorials that we might still do for 0.46: http://wiki.inkscape.org/wiki/index.php/TutorialUpdates-0.46#New_Tutorials I can do docbookification in no time. Let's decide which ones we want for 0.46 to be really good and ready, so that translators had enough time to make their part of the work. To me it looks like "Clipping, Masking and Patterns" and "Paint Bucket Tool" have most chances, but both need some work. And |Interpolation" is in SVN already. What do you think? Alexandre

1 0

Preparing Next inkscape realease
by radar.map35＠...6... 21 Dec '07

21 Dec '07

lo everyone, We have been quiet these last weeks, but now Inskcape is nearly to reach the next release. It would be nice if we've had documented new features are proof-read existing for changes. I know we wanted to make some deep changes, but i think we won't haev time for now and keep that in mind for the next rel. Would someone have time or wishes to read or add some parts, and eventually which one ? pygmee

4 5

Translate Doc file for Inkscape
by Khoem Sokhem 13 Nov '07

13 Nov '07

Hi All, Now I am updating translations for Khmer for Inkscape, It will be finished soon. And I also would like to translate the Help for Inkscape. I want Inkscape to be fully in Khmer both applications and help. Where can start for this? Your respone is welcome! Thanks, Sokhem

3 2

defining tags
by Joshua Facemyer / Impressus Art 13 Nov '07

13 Nov '07

On #Inkscape today we were discussing the possibility of using the tag <formalpara> to replace <simplesect> so that we can have titles built into our paragraphs when necessary. From what I can tell, this works the same as a <para> tag and it takes a <title> tag as well. This would be a whole lot easier than encapsulating every <para> that needs a title with <section> or some other tag simply to give it a title. It would make more sense with the formatting scripts as well, and would keep other tags like <section> free solely for their primary uses. Does anyone know of any reasons not to do this? If not, what's the best way to test it? Finally, I've been working (following up on someone else's work) at putting all the tags we'll be using on the wiki at http://wiki.inkscape.org/wiki/index.php/DocumentationStandards along with their purpose so we're more unified in our restructuring and future writing. Please look over it and add tags or comments that are missing. JF

1 0

help and toc
by radar.map35＠...6... 09 Nov '07

09 Nov '07

Lo, I took advantage of travelling a lot by train this week to read carefully alexander mail. 1) happy to see that you follow the way i've already begun with , ie style 1 +2 ;) 2) context-sensitive help would need that the team had chosen a "help browser" and have ertainly done sone modifications in the core to allow this. For the help browser (which scribus has for example), we could use yelp that is nearly fully docbook compliant but the question many oppose to that is how would it work on other OSs. This is a big problem and until we find a solution, the only easy way would use web browser and have some "html name rewrite" from an ID that could be used as context reference. We cannot go further this way without talking aboutthis with other guys of the core-team. From that, what can we thing of grouping elements in the TOC? Grouping is a common task for any author. It tries to organize the needs to help the reader to understand. In the actual manual, you may see that in most part, it describes menus one by one, and in more thematic way some more complex tools or concepts. Why this ? Because if you think of the manual as a help sensitive system, you guess that the reader would read from the beginning to the end but will browse it in search of a specific info (for ex: what means mass in Calligraphic tool and how it is made for). Sure there could ne many ways in grouping elements, but at least we can simply do link to other parts if needed so, the place of one is less important that it can be in a book. hypertext navigation is not a space navigation so it doesn't change anything for the reader if we use in one part a page that is written in another. An example of this. In your Proposal, Alex, have a specific part for Preferences. right. But some tool need to be set in preferences quite often, for ex 3d tool) so that preferences is in this case a real part of the tool usage. HAving a complete reference to the page related to this is a must in this case, and would be a gooduse of non-linear reading. Thinking of some special elements like Color management or icon preview, I'm just wondering if it would not be usefull to have some part about specific usage of Inkscape. I'm thinking of : - Inkscape for press - Inkscape for theme design - inkscape for web design ans so on. Having fill'n'stroke in colours is also something strange especially for stroke settings which can be considered as object properties. I'm not sure if we should map all this to visualize the several relationship that can be set between pages. We also need to define a basis structure of each pages. Is the one we already have good enough (title+screenshot+Intro+Activation+Procedure+Additional infos+Links) ? Alex, i'm also wondering if it would not be better to split much than you did. I would do : One file per TOC entry. I didn't follow the new gimp's process, but that was what they had some years ago when i contributed. Roman could be open to help us in a reasonable way, he always answered my mails ;) A+

4 3

TOC on the wiki?
by Joshua Facemyer / Impressus Art 29 Oct '07

29 Oct '07

I've updated the TOC according to my understanding of what you mean, Alexandre. If it's incorrect, please fix or let me know to fix it. I'd like to be sure about what you had wanted before we continue. JF

1 0