A quick workaround is to type a space after the NAT keyword, so that it gets transformed in the appropriate symbol. There is no need to erase that space afterward as leading and trailing spaces are already ignored by the search command.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1041912
Originator: NO
A quick workaround is to type a space after the NAT keyword, so that it gets transformed in the appropriate symbol. There is no need to erase that space afterward as leading and trailing spaces are already ignored by the search command.
Logged In: YES
user_id=1041912
Originator: NO
This bug is now fixed in CVS. The fix will be available in the next release of the platform.