Bugzilla – Bug 536
Double byte characters in policy set names and rule names causes Arg Null exceptions.
Last modified: 2011-06-03 22:53:32 UTC
If you create a policy set or rule with double byte characters, after saving and re-entering the edit policy page, the set or rule name will not show up and you will get the exception when clicking on the item. The initial exception is coming from the EMF getting invalid XML Character (Unicode x 19).
madean ( 12/6/2004 11:12:07 AM Fixing - Approved for Investigation ) May be a candidate for future release of designer. Bill is it true that we are not supporting any double byte or extended characters for initial designer release?
Should be fixed as soon as possible.
Marv, I've added utf-8 encoding to the model. Could you please retest? Thanks.
Based on Will's comment we're marking this "resolved, fixed"... If it is still an issue, please reopen it.
Regressed 20050613. Arg Null exception are no longer occurring.
I wasn't suppose to close this out. Arg Null exceptions are no longer occuring, however, when you save the project and reopen double-byte characters are not displayed properly. Steps to duplicate: 1.) Designer Build 20050613 2.) Launch Designer, open a policy in Policy Builder 3.) Add a rule and give it a name with double-byte characters 4.) Save the project and close Designer 5.) Re-open Designer and look at the new rule you created. Double-byte characters are not displayed properly. See attachment for details...
Created attachment 39071 [details] Screenshot
Marking fixed/built
Regressed 20050629.
Marking closed/resolved fixed bugs public view.