Just reviewing the patch:
[...]
> + check in order not to lose unsaved data. It is worth remembering
> + that a fresh canvas is white, and that it is surrounded by greyish
> + borders in case the canvas is smaller than the available window area.
> + A simple dialogue is also launched for selecting the size of any new,
> + blank image.
Depending on dialect/register, the phrase "in case" is annoyingly
ambiguous: it can mean either "conditionally, to handle the case
where..." or "unconditionally, to avoid the case where". I'd
recommend avoiding it in favour of plain "if".
[...]
> + Some of the icons have the property of becoming dimmed at select times.
> + This is an indication that the action is not accessible at a particular
> + moment: Inapproriate program mode; No editing steps could be
> + undone or redone; No in-memory content exists.
I presume "at select times" means "at particular times", not "at the
time they're selected"? The adjective has unwanted associations
("fastidiously chosen, exclusive").
Does the wording echo particular user-visible diagnostics? If so:
Some of the icons have the property of becoming dimmed if the action is
not accessible at a particular moment, indicating "Inapproriate
program mode", "No editing steps could be undone or
redone", or "No in-memory content exists".
Otherwise, if we are free to rephrase them:
[...], indicating that &software; is in
an inapproriate mode, that no editing steps can be undone/redone, or
that no in-memory content exists.
[...]
> + The manipulation of more or less large chunks of the canvas deserves
> + an expressed description, to avoid initial mistakes. When a rectangular
Abbreviating the metadescription. "More or less large"... does that
mean "(vaguely) big" or "larger or smaller"? Either way, we can
probably drop it:
<para>
To make it easier to get started, here's an introduction to how to
manipulate chunks of the canvas.
</para>
<para>
When a rectangular [...]
(Or maybe we could even swallow the whole thing up in a change of
title to "Copying, cutting, and pasting - a beginner's guide"?)
[...]
> + When doing a <emphasis>Cut</emphasis>, the marked area is emptied of
> + its content, so it will appear as a black rectangle, but the removed
> + portion will be remembered as in-memory content which remains available
> + for pasting back. Observe that copying and cutting can only be made in
s/made/performed/, and from here on it's fine.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- rgbpaint.xml.mea 2010-12-11 17:21:59.000000000 +0000 +++ rgbpaint.xml.jbr 2010-12-11 21:14:12.000000000 +0000 @@ -261,7 +261,7 @@ from or writing to image files. Each action conducts its own safety check in order not to lose unsaved data. It is worth remembering that a fresh canvas is white, and that it is surrounded by greyish - borders in case the canvas is smaller than the available window area. + borders if the canvas is smaller than the available window area. A simple dialogue is also launched for selecting the size of any new, blank image. </para> @@ -293,10 +293,10 @@ of the canvas. </para> <para> - Some of the icons have the property of becoming dimmed at select times. - This is an indication that the action is not accessible at a particular - moment: Inapproriate program mode; No editing steps could be - undone or redone; No in-memory content exists. + Some of the icons have the property of becoming dimmed if the action is + not accessible at a particular moment, indicating that &software; is in + an inapproriate mode, that no editing steps can be undone/redone, or + that no in-memory content exists. </para> </refsect1> @@ -404,18 +404,20 @@ <refsect1 id="copy.cut.paste.en"> <title>Copying, cutting, and pasting</title> <para> - The manipulation of more or less large chunks of the canvas deserves - an expressed description, to avoid initial mistakes. When a rectangular - portion of the canvas has been selected, it is possible to perform the - action <emphasis>Copy</emphasis>. It will take the content of the marked - area and save it in-memory for later access. + To make it easier to get started, here's an introduction to how to + manipulate chunks of the canvas. + </para> + <para> + When a rectangular portion of the canvas has been selected, it is + possible to perform the action <emphasis>Copy</emphasis>. It will take + the content of the marked area and save it in-memory for later access. </para> <para> When doing a <emphasis>Cut</emphasis>, the marked area is emptied of its content, so it will appear as a black rectangle, but the removed portion will be remembered as in-memory content which remains available - for pasting back. Observe that copying and cutting can only be made in - <emphasis>Selection</emphasis> mode, since a selected area must exist + for pasting back. Observe that copying and cutting can only be performed + in <emphasis>Selection</emphasis> mode, since a selected area must exist for either action to be sensible. </para> <para>
Attachment:
rgbpaint.xml
Description: XML document