[Gimp-docs] more changes to help
I have an idea for the Fire up the GIMP section; please tell me if you agree wihtthis and I'll implement it. First, the section title: I tried to rephrase the title since fire up the GIMP is an awful one that doesn't belong in a help file, but it just means running GIMP which is already the name of the first sub-section. So I intend to combine both sections into one (the second one is very small anyway), and furthermore I'd like to add a small section explaining how to change the menurc file to the one that comes with GIMP (and is located in the easy to find etc/gimp/2.0) and has Photoshop keyboard shortcuts. The result should change the section from this: 2. Fire up the GIMP 1. Running GIMP 1.1. Known Platforms 1.2. Language 1.3. Command Line Arguments 2. Starting GIMP the first time 2.1. Finally . . . to this: 2. Running GIMP 1. Running GIMP 1.1. Known Platforms 1.2. Language 1.3. Command Line Arguments 1.4. For Photoshop Users 1.5. Starting GIMP for the first time1.6. Before you proceed It looks weird that there's a single running GIMP section inside another running GIMP section; but it's already the case with Getting Unstuck. If there is a way to get around it I'd like to hear about it. If there is no objection I will implement these changes. P.S. Why is the straight lines tutorial placed separately from all the other quick tutorials? ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] Starting help for gimp-2.8
I can rewrite that section for 2.6 - it's not much of a change - and keep this version for when, gnu willing, the new version comes out. 2011/3/29 Julien Hardelin jm.h...@wanadoo.fr Hi Roman, On Thu, Mar 03, 2011 at 07:07:00AM +0100, Julien Hardelin wrote: For that, we need: - a separated git module for gimp-help-2.8, containing a copy of the present gimp-help-2 at first. - a gimp-doc-wiki(like the old we had) with the list of features that must be updated, and the possibility of knowing who works on what. Perhaps for this, the developers wouldn't mind if the documentation team could use the wiki as well? I could perhaps ask on the developer mailing list for this opportunity... The wiki is not the most important as long as contributors are few. But what about a separated module for gimp-help-pre-2.8? Michael sent a re-written quickie.xml file. This tutorial is much better than the present one, but it refers to the Export command, which is a gimp-2.7 feature. I can't push it to the gimp-help-2 repository. Michael is a valuable recruit for gimp-help. I'm afraid he will turn discouraged if its work is not validated. Cheers, Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] building documentation?
2011/3/26 Ulf-D. Ehlert ud...@web.de I wonder if we won't get a copyright problem if the images are replaced... And even if not, shouldn't we show respect for the original author? Obviously not - the entire thing is under the GNU Free documentation License. The original images were taken from Astronomy picture of the Day, and checking the About page, I see they were not released under any kind of free license; some of them may be copyrighted. If anything, replacing the images will make the doc more free. As for my own pictures, I figure if I add them to the documentation they fall under the GNU FDL. Anther reason for taking the time to replace all of them was that I wanted all the screenshots to have a similar theme (clearlooks, which I believe is the Gnome 2.x default) and I had to replace at least some because the interface has changed. As for respect, I have all respect to Carol Spears who invested her time and effort to write the original tutorials, and I kept the credit in the introduction. But while it is natural for tutorials on personal website to maintain a casual tone and have tangential interests such as astronomy feature in the tutorials, I believe official documentation should be more professional. These are, after all, quick tutorials for those who don't want to read the entire manual to get some small task done; I tried to make it as short and to the point as possible. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] building documentation?
2011/3/24 Owen rc...@pcug.org.au Could I suggest that you run autogen.sh again, and read the last 20 or so lines. Just see what programs weren't found and install them. Now if you have the style sheets on your computer, it shouldn't have to go to the net to get them. Install all the stylesheets you can find (I think you were using Ubuntu so just search synaptic for stylesheets ) Owen Thanks! It's working now. And with a launcher to a small script that generates a draft of a single file, I can preview with the click of a button, like God intended :) I see you've already changed the wiki, so add the following: docbook-xsl (this is the one with the stylesheets) docbook-utils (solved a number of dependencies) There might be more packages necessary; I added a bunch of other packages, don't remember which, I just ticked anything that seemed like it was related to docbook. Also, I still get one line of missing dependencies: checking for dot... no I couldn't find something called dot in synaptic and it seems to be working without it anyway. Now, some more questions: 1. There are two folders, both with XML files: XML and SRC. I understand XML is the one files are built from, and SRC is the one GIT uses to fetch files. But how do the two interact? do I copy files manually or is there some tool or script to update one or the other? In other words what is the work process here? 2. UI screenshots: Do you have a preference for the theme used in the screenshots? The wiki says screenshots should use the default theme but is it the Gnome's or Ubuntu's default theme I should be using? Gnome's default is Clearlooks, right? 3. I intend to replace the astronomy images used in the quickies with images more representative of something a normal user would use, everyday objects such as cars, animals, plants, tourist attractions and if I find the right subjects, people. These are good looking images I took myself, but I want to know if I need to do anything rights-wise, you know, do I need to explicitly release them under the GPL or CC or what have you, and if I do, how do I do it. 4. it's a long shot, but does anyone here use Notepad++ and has the correct HTMLtidy settings file to correctly reflow and indent docbook XML? ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
[Gimp-docs] building documentation?
IT's taken some time (I had a rather optimistic estimate of tmy free time) but I'm finally making some headway with rewriting parts of the documentation. My current aim is to rewrite Gimplite Quickies. Problem is, I still don't know how to build the html. I was told here on the mailing list that Ubuntu has all the needed tools but I wasn't told what they are... Validating is not a problem, I have XML validation tools, but editing XML blindly can only go so far: I really need to see what I'm doing. Can anyone help me with this? BTW, I'm targeting 2.8, i.e., changing references from save as to Export, etc. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
2011/2/23 Julien Hardelin jm.h...@wanadoo.fr Hi Michael, OK for substance. Some remarks about form: - TAB are set to 2 spaces. - Lines are less than 80 characters and spaces. OK, figured out how to do those with Notepad++. - When explaining a term, please add an indexterm indexterm primaryResolution/primary /indexterm This will automatcally appear in the index chapter: last line in the html summary. I've been meaning to ask about this: There were 7 terms in concepts.xml but only one of them, channels, had an indexterm. So if I understand correctly, the reason is that those other terms are explained at length elsewhere, and THOSE places are linked to in the index, while there is no other reference to resolution in the help? - I noticed 2 typos: reslution and noticable. You probably have a spelling command in your editor. Yup. I guess I'm so used to check-as-you-type spellcheckers I haven't thought of runing a spell check. what is the significance of adding acronym and quote tags? what are they for? they seem to have no influence on the final output. For acronym, I don't know. But quote is important for internationalization. With quoteHello/quote, I automatically get the French quotes in French html (« Hello ») with indivisible spaces! I made these changes in your xml file. Do you want I push your changes? Sure. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
[Gimp-docs] concepts
So, in the last couple of weeks I tried to look up material about Docbook. I'm still not sure about how you people edit the help files, and I'd obviously prefer a more wysiwg way of doing things, but for now I'll settle for XML-aware editors. I downloaded the repository to my Linux volume but I'm more comfortable working on Windows so I'm using Notepad++ for editing and XMLnotepad to validate the XML. Docbook seems straightforward enough but I do have some questions: what is the significance of adding acronym and quote tags? what are they for? they seem to have no influence on the final output. Anyway here is my first change: I took the concepts page and added a much-needed Resolution section. I know from experience this is a term that many beginners find difficult to understand, especially when it comes to understanding the resolution property of files coming from digital cameras. I also removed the comparison of a multi-layer image to a book: it is a confusing metaphor as it is nothing like a book in reality, so I changed it to a stack of transparent sheets of paper. Lastly, how important is the way these files are indented? I always use tabs, and any editor I'm familiar with uses tabs to indent lines, while these files seem to use spaces. Is is important to indent the XML in this way? regards Michael ?xml version=1.0 encoding=UTF-8? !DOCTYPE sect1 PUBLIC -//OASIS//DTD DocBook XML V4.3//EN http://www.docbook.org/xml/4.3/docbookx.dtd; !-- section history: 2009-03-20 j.h: fixed bug #557343 2008-06-03 prokoudine: yet another shot at Russian content 2007-02-27 prokoudine: fixes to Russian translation 2007-02-27 lexa: reorganized concepts 2006-05-02 Dust: added Korean translation 2006-02-27 kolbjørn: added norwegian 2006-01-07 HdJ: Added quote and acronym tags, added english and dutch version of layers explanation 2005-12-18 Lexa: reviewed and added de translation -- sect1 xmlns:xi=http://www.w3.org/2001/XInclude; id=gimp-concepts-basic titleBasic Concepts/title indexterm primaryConcepts/primary /indexterm figure titleWilber, the GIMP mascot/title mediaobject imageobject imagedata format=PNG fileref=images/using/wilber.png / /imageobject caption para The Wilber_Construction_Kit (in src/images/) allows you to give the mascot a different appearance. It is the work of Tuomas Kuosmanen (tigertATgimp.org). /para /caption /mediaobject /figure para This section provides a brief introduction to the basic concepts and terminology used in acronymGIMP/acronym. The concepts presented here are explained in much greater depth elsewhere. With a few exceptions, we have avoided cluttering this section with a lot of links and cross-references: everything mentioned here is so high-level that you can easily locate it in the index. /para variablelist varlistentry termImages/term listitem para Images are the basic entities used by acronymGIMP/acronym. Roughly speaking, an quoteimage/quote corresponds to a single file, such as a TIFF or JPEG file. You can also think of an image as corresponding to a single display window (although in truth it is possible to have multiple windows all displaying the same image). It is not possible to have a single window display more than one image, though, or for an image to have no window displaying it. /para para A acronymGIMP/acronym image may be quite a complicated thing. Instead of thinking of it as a sheet of paper with a picture on it, think of it as more like a stack of sheets, called quotelayers/quote. In addition to a stack of layers, a acronymGIMP/acronym image may contain a selection mask, a set of channels, and a set of paths. In fact, acronymGIMP/acronym provides a mechanism for attaching arbitrary pieces of data, called quoteparasites/quote, to an image. /para para In acronymGIMP/acronym, it is possible to have many images open at the same time. Although large images may use many megabytes of memory, acronymGIMP/acronym uses a sophisticated tile-based memory management system that allows acronymGIMP/acronym to handle very large images gracefully. There are limits, however, and having more memory available may improve system performance. /para /listitem /varlistentry varlistentry termLayers/term listitem para If a simple image can be compared to a single sheet of paper, an image with layers is likened to a sheaf of transparent papers stacked one on top of the other. You can draw on each paper, but still see the contant of the other sheets through the transparent areas. You can also move one sheet in relation to the others. Sophisticated
