This is not the case. Only '&' and '<' *have* to be escaped (I'm not sure about the latter when it is in quotes). The other common ones (>, ', ") only *have* to be escaped if they would affect the context (for example, " is required when the quote is within "" but can be avoided by writing an attribute as name='"quoted"').
Pete Edoardo Comar wrote: > David Mankin wrote: > >> (| = cursor, [] = selection) >> >> Before: >> <target name=">|" > > > > If I don't misunderstand your notation, > you should have escaped your attribute value .... > > <target name=">" > > Edo > >> >> Press Ctrl-W (wrong!): >> <target name=">["] >> Press Ctrl-W again (correct): >> <target name=[">"] >> Press Ctrl-W again (correct): >> <target [name=">"] >> >> The first Control-W press selects the closing quote instead of the >> contents of the string that the cursor is in. If the character inside >> the string is alphanumeric instead of punctuation, all is well. If the >> character is "." instead of ">", the same problem exists. >> >> More examples: >> name=".|" -- bad >> name="x|" -- ok >> name=".x|" -- ok >> name="x.|" -- bad >> name="x.x|" -- ok >> >> -David Mankin >> >> > > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
