Hi Roy and everyone,
thank you for allowing us to draw from your tutorials.
For adapting your terminology, I'd like to refer you to the Inkscape Wiki at http://wiki.inkscape.org/wiki/index.php/Inkscape_glossary.
If you like, you can also join us in editing the manual directly.
We do right now - aside from translators - have a need for people who:
- can polish the English - can take care of a more homogenous structuring of each chapter - can make screenshots of an English version, and put the image descriptions right beside the corresponding screenshots (they are currently all lumped together). - can rename + reupload + relink the good screenshots to use English file names - can check links in translated parts, and add meaningful hover texts to them, and also make them open in a new tab/window, so the user doesn't leave the manual altogether when clicking on them - can rewrite the outdated chapter about keyboard shortcuts - possibly: can write a chapter about the Align+Distribute dialog - possibly: can suggest some useful changes to the Inkscape preferences that help new users - possibly: can write a short chapter about Inkscape installation - possibly: can write a short chapter about where to get further help + learn more - can curate the proposed glossary
Anyone who reads this: You can pick a task that you feel comfortable with, and start right away :)
Kind Regards, Maren
Am 18.05.2017 um 23:40 schrieb bandura1@...114...:
Thank you, all of you, for putting in quality time, thought, and discussion on The Manual. I've been using an ad hoc terminology for some of Inkscape's functions in my tutorial and would like to bring my language into accordance with what you are designing. I invite you to use anything in the tutorial that might add to or complement your work. The tutorial is at:
https://roy-torley.github.io/Inkscape_Tutorial/Inkscape_Tutorial_Contents.ht...
I still have to Bootstrap individual lessons, but the content should be decent (good enough for government use?).
Yours with support,
Roy Torley
Hi Friends, I think Maren mentioned to Carl about terminology (in a different message) and I agree that one of the most important things we need to do, is use the same terminology throughout the manual. However, that said, I'm not sure what the best way to accomplish that would be.
Actually I was going to propose some changes to some of the
section and chapter titles, in this message. But now that I think about it, that might be putting the cart before the horse (as we say here, sometimes).
Should we create a Glossary? I mean as part of the manual? Or
should we create a glossary that we just use for our own reference, as we write? Maybe make it part of the wiki? The gitlab wiki?
Once or twice I've had a thought about making a glossary for the
website someday. But until the website contains more instructional info, it probably has no purpose yet. But what I mean is that creating a glossary, whether formally part of the manual, or just in the wiki, could also be used on the website someday.
If not glossary, what are some other ways we could keep ourselves
all on the same page regarding terminology? What about one person (or 2?) who primarily takes care of that? Other ideas?
All best, brynn
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs