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(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

On Thu, May 18, 2017 at 11:55 AM, brynn <brynn@...78...> wrote: > 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. This is an excellent suggestion for high level consistency as well. > > 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? Yes, a Glossary would be helpful in the manual. It would be useful as the manual is written; almost essential when beginners are using Inkscape. Probably good in a wiki, perhaps after the manual is complete to maintain consistency. > > 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. Yes. > > 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? It's likely that the people writing have some idea of what any terms mean. So it would work for people to write using their own terms (for example, I don't plan to write technical stuff about anything that I don't understand. So in situations where the material is too advanced for me, I'll only edit grammar, spelling and clarity, depending on others who are more knowledgeable to provide the technical details). Some smart person can come back and make terminology consistent throughout the manual. I think that would be better than for people to try to learn proper terminology first. This also applies to the style of writing throughout the document. Several people will be writing--and they should be writing in a way that is comfortable to them. A final editing task will be to revisit the document as a whole and make the style consistent. Carl > > 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(a)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(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

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(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs