Re: [Gimp-docs] concepts
> - When explaining a term, please add an > > Resolution > >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? > That is docbook rules: there is no varlistentry parent for indexterm but there is title. In varlistentry you must include indexterm within tags. Please see > http://docbook.org/tdg/en/html/indexterm.html There are some inconsistencies in the index. It has to be reviewed. > I made these changes in your xml file. Do you want I push your changes? > > > Sure. Done http://git.gnome.org/browse/gimp-help-2/ ___ 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 > 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 > > Resolution > > 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 Hello, 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
Re: [Gimp-docs] concepts
The main reason for using things like and is to separate function from appearance. With tags that describe the function of an entity, even if the appearance is currently just plain text, it can be changed at any time by altering the rules for rendering entities, without having to rewrite the xml code for the whole document. The principle is to use a different tag for any entity that the manual *might sometime* want to render in a special way. Regarding tabs, the reason for using spaces instead is that there is no fixed rule for converting tabs to spaces, so when tabs are used, the appearance of the document will vary depending of which editor is used to work on it. -- Bill ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
Den 23.02.2011 13:32, skreiv Ulf-D. Ehlert: > Kolbjørn Stuestøl (Wednesday, 23. February 2011) >> BTW: For some reasons the tag does not work in Norwegian. >> Hello is written as "Hello" instead of «Hello». (We >> are using the same quotes as in French). > This is a DocBook bug, IMHO. Try to change the quote chars manually > (in /usr/share/xml/docbook/stylesheet/nwalsh/1.75.2/common/nn.xml or > wherever your language file is) to be sure. > > Bye, > Ulf The Windows keyboard do not has the «» quote signs by default. Linux has. I'll give your suggestion a try. Until now I have deleted the tag and entered the signs by hand in my translated po files. (Not in the original xml files). Thank you, Ulf. Kolbjoern ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
Michael Grosberg (Tuesday, 22. February 2011) > what is the significance of adding "acronym" and "quote" tags? > what are they for? they seem to have no influence on the final > output. tags are important to set the correct quotation chars. tags are used to convert the enclosed text to capital letters, AFAIK (I never did any tests), and add ... to the HTML output, which may be used in CSS stylesheets. So right now they are not really important -- it's good style and correct if you use them, but nothing happens if you forget it. > 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? By convention we use two spaces. Mixing tabs and spaces will make the XML files less readable, especially if someone uses a different editor. Bye, Ulf -- Religionen sind falsche Mittel zur Befriedigung echter Bedürfnisse. -- Karlheinz Deschner signature.asc Description: This is a digitally signed message part. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
Kolbjørn Stuestøl (Wednesday, 23. February 2011) > BTW: For some reasons the tag does not work in Norwegian. > Hello is written as "Hello" instead of «Hello». (We > are using the same quotes as in French). This is a DocBook bug, IMHO. Try to change the quote chars manually (in /usr/share/xml/docbook/stylesheet/nwalsh/1.75.2/common/nn.xml or wherever your language file is) to be sure. Bye, Ulf -- Erstaunlich, wie vieles sich verständigt, ohne Verstand zu haben, und wie viele Verstand haben, ohne sich verständigen zu können. -- Karlheinz Deschner signature.asc Description: This is a digitally signed message part. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
Den 23.02.2011 08:34, skreiv Julien Hardelin: > Hi Michael, > > … >> 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. The tag capitalize the contents of the tag. gimp outputs GIMP. BTW: For some reasons the tag does not work in Norwegian. Hello is written as "Hello" instead of «Hello». (We are using the same quotes as in French). Kolbjoern > But "quote" is important for > internationalization. WithHello, 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? > > Regards, > > Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] concepts
Hi Michael, OK for substance. Some remarks about form: > 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? - TAB are set to 2 spaces. - Lines are less than 80 characters and spaces. - When explaining a term, please add an Resolution This will automatcally appear in the "index" chapter: last line in the html summary. - I noticed 2 typos: "reslution" and "noticable". You probably have a spelling command in your editor. > 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 Hello, 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? Regards, Julien ___ 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 http://www.docbook.org/xml/4.3/docbookx.dtd";> http://www.w3.org/2001/XInclude"; id="gimp-concepts-basic"> Basic Concepts Concepts Wilber, the GIMP mascot 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). This section provides a brief introduction to the basic concepts and terminology used in GIMP. 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. Images Images are the basic entities used by GIMP. Roughly speaking, an image 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. A GIMP 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 layers. In addition to a stack of layers, a GIMP image may contain a selection mask, a set of channels, and a set of paths. In fact, GIMP provides a mechanism for attaching arbitrary pieces of data, called parasites, to an image. In GIMP, it is possible to have many images open at the same time. Although large images may use many megabytes of memory, GIMP uses a sophisticated tile-based memory management system that allows GIMP to handle very large images gracefully. There are limits, however, and having more memory available may improve system performance. Layers 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 GIMP users often deal with images containing many layers, even dozens of them. Layers need not be opaque, and they need not cover the entire extent of an image, so when you look at an image's display, you may see more than just the top layer: you may see elements of many layers. Resolution Digital images comprise of a grid of square elements of varying colors, called pixels. Each image has a pixel size, such as 900 pixels wide by 600 pixels high. But pixels don't have a set size in physical space. To set up an image for printing, we use a value called resolution, defined as the ratio between an image's size in pixels and its physical size (usualy in inches) when it is printed on paper. Most file formats (but not all) can save this value, which is expressed as ppi - pixels per inch. When printing a file, the resolution value determines the size the image will have on paper, and as a result, the physucal size of the pixels. The same 900X600 pixel image may be printed a
