October 2007 - Inkscape Docs - Inkscape Mailman

by radar.map35＠...6...

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+

15 years, 10 months

4
3
0 / 0

TOC on the wiki?

by Joshua Facemyer / Impressus Art

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

15 years, 11 months

1
0
0 / 0

Tag fixing in inkscapeUTFfr.xml

by Colin Marquardt

Hi, I just changed inkscapeUTFfr.xml so that xml2po is happy with it. I had to change a lot of <para></para> or <para /> to <para>some text</para> (I used FIXME instead of "some text"), since xml2po doesn't seem to like such empty tags. (Not just paras, also terms and titles etc.) Doing xmllint --valid --noout inkscapeUTFfr.xml still complains about some issues though. Oh, and I also changed "<para >" to "<para>" for cosmetic reasons. If you want to try creating a pot file youself, do: xml2po --output=inkscape_user_manual_orig_fr.pot inkscapeUTFfr.xml Cheers Colin

15 years, 11 months

5
15
0 / 0

Automated screenshotting

by Colin Marquardt

Hi, I think we very much want something like this: http://www.gnome.org/~dscorgie/autoshot.html Doc is http://live.gnome.org/autoshot http://osdir.com/ml/gnome.documentation/2006-08/msg00044.html Cheers Colin

15 years, 11 months

1
0
0 / 0

english file

by radar.map35＠...6...

I've been looking at the english splitted file and applied the same strategy on fr. For info, interested people may find a "translation" of the curriculum.xml file at http://www.le-radar.com/articles/drawinginkscape/html.en/index.html but in HTML. But if the file is kept, it might be a good start for improvments. regards pygmee

15 years, 11 months

1
0
0 / 0

couple of questions

by Joshua Facemyer / Impressus Art

I'm working on a few minor translations to get started. A couple of questions: "Nom d'outil ou partie" I'm translating to "name of utility or function" - is "function" appropriate? I'm not sure what the comment signifies exactly, so need some help. The English version of the xml file is not really a translation of the French, as there is a lot of extra stuff in the English (for example, in the "SVG Goals" section). Should I attempt to reconcile the differences and cut everything extra out of the English version (most of it is not really useful, in my opinion), or is the extra stuff in the English version getting put into the French version eventually. Sorry if I'm a bit confused by this. I really want to get my hands dirty, but keep coming upon roadblocks :) JF

15 years, 11 months

5
15
0 / 0

Re: [Inkscape-docs] couple of questions

by Joshua Facemyer / Impressus Art

Elisa-yemanja wrote: > Le Friday 12 October 2007 18:01:32, vous avez écrit : > >> Elisa-yemanja wrote: >> >>> What is your new structure ? You are, actually, only on the english >>> version, so you're free. >>> >> It's not a huge difference, but the first two sections of the Intro.xml >> file are modified ("Inkscape" and "SVG") - paragraph structure. I also >> put a screenshot of the main Inkscape window in the interface section. >> >> > > Puis-je t'écrire en français ? > > Je viens de voir ce que tu as écrit. Oui c'est différent, l'esprit reste le > même. Je trouve cela très bien. > But, from what I understand, the problem is that we have to have the same paragraph structure (meaning for each section, the same amount of paragraphs - or more generally, all the elements need to be the same for each localization, just the actual content being different). So we'd have to sync the two documents together in that way (xml elements), n'est ce pas? > >> Apart from that, mostly minor things, so not a big deal. If you want to >> compare the new work in En to the Fr, I think what I changed is much >> better. However, I don't know how it compares to the Fr, since I just >> wanted to adapt what was already there in English. >> > > Si tu préfère faire ainsi, ok aucun soucis. > Well, I was just doing it for that part, since those sections needed a lot of help and I didn't have time to translate the French yet. I will work on straight translations for most parts that exist in the Fr manual, unless I think they need to be reworked even after translation. >> The changes were commited yesterday, I believe. >> >> >>> Are you on irc ? >>> >> I can be, but I'm not usually available at the times you are on, since I >> work evenings (3:00pm to 10:00pm Central time). Some days, (Lundi et >> Mardi, usually) I can be available. Is there a docs room, or just the >> regular inkscape dev room? >> > > Yes i think about #inkscape. But i connect in Inkscape just at night. > I'm not sure what the time difference is - I think we might actually be able to work together - I'll look at it. Feel free to jab me any time on jabber to find out if I'm around :) > >> By the way, if anyone uses jabber, you can >> page me at faceman@...1... >> > > done. > > >> I'll go ahead and work, then, and follow the French structure as much as >> I can. Any structure I change will be noted on this list, so you can >> review it and approve it. How's that sound? >> > > Very cool for me. > > What do you think about my proposal of the new content ? > I'm not sure what you mean - can you restate your proposal? JF

15 years, 11 months

1
0
0 / 0

separating docs

by Alexandre Prokoudine

Hi, With revision 16217 docs in English are separated into smaller files (one chapter - one file) and moved to xml/en/ directory. Wenow need the Makefle to be adjusted and XSL styles to handle XInclude. Colin? :) Alexandre

15 years, 11 months

3
2
0 / 0

Re: [Inkscape-docs] separating docs

by Alexandre Prokoudine

On 10/10/07, Joshua Facemyer / Impressus Art wrote: > I've done a bit of work on the EN xml file (monolithic). Is it possible > to send a diff to get put into the separated files? I'm guessing not. > If not, then can I just separate my version of the monolithic file the > same way you did, or is it more complicated than that? Send it to me offlist -- I'll apply changes Alexandre

15 years, 11 months

2
1
0 / 0

on SVG filters

by Alexandre Prokoudine

Hi, Here is what I've found useful for our missing docs on SVG filters so far http://www.w3.org/TR/SVG11/filters.html http://www.adobe.com/svg/basics/filtereffects.html http://www.adobe.com/svg/basics/filtereffects2.html http://docs.gimp.org/en/plug-in-convmatrix.html (feConvolveMatrix') http://docs.gimp.org/en/plug-in-dilate.html (feMorphology) http://docs.gimp.org/en/plug-in-erode.html (feMorphology) And I hope that Niko will help us :) Alexandre

15 years, 11 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Inkscape Docs October 2007