Hi Brynn, Am 06.06.2017 um 13:50 schrieb brynn: >> I'm a bit disappointed about everyone being so engaged and vocal about > helping/liking the action, and now me working on it alone for > 2 weeks > already. > But that's normal, I guess - it was the reason why I haven't started > this earlier, and I felt ready to take it on now, no matter what. > > Don't worry, Maren. I'm still on top of helping with the manual. It's > just life offline keeps pulling me away from computer lately.
- Mine is busy, too. > I will start proofing as soon as I can get this moderation stuff settled. - Yes, if you could help with fixing language errors, that would be helpful. > For working on the graphics, as you have outlined, I have some blockers > on that. Somewhere I've mentioned them, but I don't think they were > answered. (I think I put comments in the Notes tab, below the line of > *. But I see now that that line of * is gone, and so are the comments I > made.) - Yes, that tab has been wiped. > Starting on Interface chapter: > > 1 -- graphics are not proportional, they're stretched long and squeezed > side to side > 2 -- the interface that's being used, uses a non-default display mode > (with command bar on the right) - Yes, this is described in the book. It's the standard display mode new users get when they are using a wide screen (please someone correct me if I'm wrong, my screen is 4:3). Widescreens are standard now, so most users should get that display. > 3 -- the interface is using some custom icon set - It uses the standard icons. All the icons that look different to you are provided by the operating system and look different from your Windows setup, yes (they look the same for me, btw.). > Before we start working on the graphics issues, these things need to be > addressed, in my opinion (otherwise we might have to eventually > duplicate some work). - You can leave the picture layouting to someone experienced with web page styling. This also requires coordination with the style person or persons, and some understanding of how the different output formats influence the layout. It would be helpful if you could continue with renaming the images that do not need to be changed - i.e. the tool icons, or drawings without any text or menus shown. And then, as a native speaker, language fixes would help us, and perhaps compiling that list of frequent issues for the chapter that we would like to add. Also, I seem to remember there was a glossary chapter that needed to be added. > I think we need to be using the most default interface screenshots as > possible. And of course, the graphics should be displayed in proper > proportions. > > The most important thing to decide, is where the new graphics will come > from. Should be someone with not such an ugly theme (color) as mine. > Should be someone who is committed to providing the graphics and won't > disappear. Should be using a default display mode and icon set. - CR volunteered for this in another email :D > I wonder if it's possible in Windows, if I make a new user account, that > account could use a different theme? I'll investigate. If I can, I'll > provide the graphics. - Let's take one step after the other, Brynn. It's better to finish one thing, then take on the next. This is also easier for me, because I don't need to be all over the place when I know that a task is being tackled and finished. Can you go through the images, and rename all the files that will not be deleted, so they will be understandable when others look at them at Hackfest time? Can you get back to us when you are done with that, so we can then find a new task? (Probably one of: proofreading for language errors, compiling list of frequent basic issues and helpful tricks). Kind Regards, Maren > I'm changing the title of this message to start a separate thread on the > graphics issues. (I see a long string of replies to making a News item, > and I suspect there may be a few different issues. I'm off to read more > now :-) (Also switching to only Docs list) > > All best, > brynn > > -----Original Message----- From: Maren Hachmann > Sent: Sunday, June 04, 2017 6:46 AM > To: inkscape-de...@lists.sourceforge.net ; Inkscape-Docs > Subject: Re: [Inkscape-docs] [Inkscape-devel] News item about the new > manual work? > > CR, I have been translating (and fixing contents as I go) 1-2 chapters > each day for the last 2.5 weeks and am more than halfway through (35 > chapters done, 24 left to do). There wasn't anyone else to be seen > around, after the first week, when one person translated a chapter > (unfortunately they picked the only one that needs to be rewritten from > scratch, because Inkscape changed), and two people proofread a couple of > chapters (thank you!!!). Well, and a couple of days ago, someone seems > to have accidentally wiped all the notes on the book, that were supposed > to help get people started (or maybe it was a platform bug). > > I'd be glad to see some proofreading and styling/screenshooting people > get on board, so we can continue seamlessly after I'm through with > translating. > > I'm a bit disappointed about everyone being so engaged and vocal about > helping/liking the action, and now me working on it alone for > 2 weeks > already. > But that's normal, I guess - it was the reason why I haven't started > this earlier, and I felt ready to take it on now, no matter what. > > Anyway, I'm going to continue to plow through, then translations will be > ready before the hackfest. In parallel, I'm going to be plowing through > my new garden, and to help fix up someone else's house, so I expect to > not have time for much else. > > I'd be glad if someone could try and reengage people to help with the > manual (preferably people who are able to work independently and know > Inkscape inside out, or who concentrate on something they really do > well, like fixing up language or styling). > > There are more than enough open tasks: > from CSS to cover design, to screenshooting, to consistency checking and > layouting, to improving on my more or less weird English, to adding > missing content (or perhaps, translating, of course). > > And yet, when we do this, I think it's important to take care to honor > the underlying 'Keep it simple and as short as possible' concept of the > book, which would make it possible for young teenagers to use it to get > started, without much theoretical ballast. > Elisa seems to have invested a *lot* of thought into how she built up > the chapters and when to start teaching which concept. I suspect her > concept stems from experience in teaching live Inkscape courses. > > Maren > > Am 04.06.2017 um 13:32 schrieb C R: >> I'd say let's wait and do a progress report, so we can say that we're >> making progress on it, rather than just that we've decided to do it. I >> plan on helping this area of the project much more after I handle the >> hackfest swag. It would be better to have a more or less complete >> manual before we announce it to the public, unless it's a call for >> help with it. >> >> If it's a call for help with that area of the project, then go ahead, >> though. :) >> >> Thanks for the amazing amount of work you're doing for the project, >> brynn. It's definitely helping drive my own motivation for Inkscape >> project work. :) >> >> -C >> >> On Sun, Jun 4, 2017 at 12:17 PM, brynn <br...@frii.com> wrote: >>> Hi Friends, >>> As I'm writing up a quick draft to announce the upcoming >>> hackfest, I >>> suddenly wondered if it might be a good idea to write a short item >>> about the >>> recent new work on the new manual? >>> >>> I could do that, after I finish the hackfest article. I'm >>> thinking >>> Maren might be able to get all the details correct, the first time >>> around? >>> Although I don't mean to volunteer her. As I said, I could do it >>> myself, if >>> we decide to do it. >>> >>> I think it would help in community-building, to keep the wider >>> community up to date about these things. What do other manual >>> workers and >>> Docs list subscribers think? >>> >>> 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-devel mailing list >>> inkscape-de...@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >> ------------------------------------------------------------------------------ >> >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Inkscape-devel mailing list >> inkscape-de...@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> > > > ------------------------------------------------------------------------------ > > 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
