We have already discussed the paragraph that I am proposing to insert right after the note at the beginning of the section.  I think that David T's wording is better than my original proposal.

The next paragraph is presently worded as follows:

“To open the Find Transactions dialog in the Account Tree Window go to the Tools menu and select Find Transactions or type menu shortcut Ctrl-F. To open the Find Transactions dialog in the Account Register Window go to the Edit menu and select Find... or type menu shortcut F6. “

I am proposing to simplify that to:

“To open the Find Transactions dialog  go to the Edit menu and select Find... or type menu shortcut  Ctrl-F.”

I am not sure whether the F6 shortcut still works.  I think not, at least in the Windows implementation.

Just before Table 7.1 the last sentence presently reads as follows:

“The criteria row is used to combine different criteria buttons. The following table describes the possible button combinations (regex means regular expression search); “

I am from the old school of computer users that are used to the kind of searches that we do in Microsoft Word, etc. where wildcards like *, ?, and a few other tricks work, but not at all like regex.  Since we old timers and Microsoft Word/Open Office users haven't all died yet, I want some clue that regex is not the same, and that we need to take a class to figure this new stuff out.  Since I have not taken that class yet, this is a little over my head.

I propose to add something along this line:

“The criteria row is used to combine different criteria buttons. The following table describes the possible button combinations (regex means regular expression text search as used in various computer programs such as Perl);”

Continuing on to Table 7.1, I want to make it abundantly clear that the fields that are named “Description”, Memo”, and “Number” in the English language edition of GnuCash are common to all lines of a transaction.  As such any transaction in the starting set with a match to these criteria will appear in the result set.  In the case of the other fields, only one item in one line of a transaction is required to match.  There are always at least two and often more than two lines having fields that are evaluated for those other matches.  As noted previously, the result register has no way to identify exactly which parts match and which parts came along for the ride.  

To accomplish this identification I would propose to add footnotes to the table for the “Description”, Memo”, and “Number” items.  It could be worded like this:

“The Description, Memo, Number are common to all lines in a transaction.”

The section of the table covering the possible values that can appear in the “Reconcile” field is not defined anywhere that I can find in all the help documents.  I believe that a table needs to be added, probably in the Tutorial and Concepts Guide to define the meaning of each of those values and there should be a footnote or comment after this table directing the reader to that table.

The footnote or comment could be worded like this:

“The Reconcile button applies the selected criteria to each line of a transaction individually.  Each transaction line may have only one of the indicated values, but there is often a mix of values within a complete transaction, so companion lines may not meet the selected criteria.   See separate note defining status values.”

Then I propose to add the following table to the Tutorial and Concepts guide section Transactions:The Account Register:Features of the Account Register  and reference it in the list of tables:


N
New
Default status when a transaction is created
C
Cleared
Status may be assigned either manually or by an import process.
R
Reconciled
Status assigned solely by the reconciliation process.  Places limits optionally requiring confirmation on editing fields in that line of a transaction 
F
Frozen
Not implemented at this time.
V
Voided
Status is assigned or released manually through the transaction menu to a transaction and applies to every line in the transaction.  It hides most of the transaction details but does not delete them. When a transaction is voided a reason entry is required that appears to the right of the description.  

The menu action  items Void and Unvoid arecurrently described in the Help Manual Table 4.14. Account Register - Transaction Menu - access to transaction tools.  but without a description of how they work



