| On Fri, Apr 28, 2006 at 03:39:40PM +0300, Jari Aalto wrote: | > Package: bash | > Version: 3.1-4 | > Severity: minor | > | > Basch manual reads: | > | > QUOTING | > Quoting is used to remove the special meaning of certain characters or | > ... | > | > Enclosing characters in double quotes preserves the literal value of | > all characters within the quotes, with the exception of $, `, \, and, | > when history expansion is enabled, !. The characters $ and ` retain | > their special meaning within double quotes. The backslash retains its | > special meaning only when followed by one of the following characters: | > $, `, ", \, or <newline>. A double quote may be quoted within double | ^^^^^^ | escaped? | | > quotes by preceding it with a backslash. If enabled, history expansion | > will be performed unless an ! appearing in double quotes is escaped | > using a backslash. The backslash preceding the ! is not removed. | > | > This chapter is packed with information and very, very difficult to | > read or understand properly. | | I didn't find it to be that bad. Well, the language is actually quite | good, even if posix sh is quirky.. | | > Furthermore the case of (!) is really not ironed out well, because | > it is also used for history mechanism. | | Isn't that the whole problem? There are an entire 2 sentences devoted | to this :) | | > which demonstrates just how difficult it is to treat ! character | > properly. This should be better documented. | | Perhaps by a boldface in the existing phrase? | | The backslash preceding the ! is \fBnot\fP removed. | | > Add clarifying examples to demonstrate the quoting rules for these special | > characters mentioned ($ ` " \ !) | | I think it is clear how, at least, the first 4 work. | I would suggest the 2 changes: s/quoted/escaped/, and boldfacing of | "not".
This is not sufficient. For anyone else than native, tech savvy programmer, the chapter may be "clear enough", but please provide clarifying examples. This really calls for them, need them as described in the bug report mentioned earlier. Those visual examples make it clear, whereas the text stays obscured after reading and reading when one has to "translate" meaningg of those word into one's own native language. Pictures do not suffer from language barries that much. Exmaples even less. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
