Bug 132463

Comment 1 Tomer Mahlin 2006-03-19 07:29:48 EST

THis defect actualy belongs to XSD not XML editor.

Comment 2 Keith Chong 2006-03-31 13:04:36 EST

Reassign

Comment 3 Keith Chong 2006-03-31 15:36:58 EST

We'll look at this during the post M6 timeframe.

Comment 4 Keith Chong 2006-04-04 12:06:21 EDT

We cannot get a fix in place without destablizing the editor, and we do not have enough resource to fully test the fix in the 1.5 timeframe.

Comment 5 Keith Chong 2007-10-17 18:24:00 EDT

Hi Tomer,

Can you clarify what the problem is?  Upon launching the editor, are you expecting the editor to convert these characters into escape sequences?  If so, by merely launching the editor, the dirty bit will be turned on.

Or are you saying we should render the characters as escape sequences?

Note that these NL characters may fall outside the range of valid characters in a URI, the schema is invalid to start off with. And by not converting the characters, this forces the schema writer to fix the problem in the editor and use characters in the valid range.

Comment 6 Valentin Baciu 2007-10-24 10:54:53 EDT

This is a message for the bug reporter: please take a few minutes and verify the bug. If we don't hear back in a week's time we'll mark as verified and close it. Thank you.

Comment 7 Tomer Mahlin 2007-10-30 06:21:52 EDT

 It is unclear what should be verified ? The current status is RESOLVED WONTFIX.
 To address previous comment. The problem is not with display. Since you expect human beings to work with XML/XSD editors in the editor itself you would expect real glyphs to be shown. However in the stored on the disk asritfact (i.e. XSD / XML file) the namespace should not include glyphs (in other words it should not include unicode encoded characters). Instead it should include escape sequence. This is simply because the program using the generated artifact will work with a standard which in its turn prohibit using characters outside of standard English ASCII in the namspace.
  Since Source Tab reflects the content of stored on the disk artifact file you would expect to have escape sequence both on the disk file and in Source Tab. However in the graphical portion of the editor I would expect to see glyphs since they are human readable as opposed to escape sequence.
  Consequently when the artifact is stored on the file system you should convert namespace from normal (inlcuding glyphs) presentation into escape sequence form. In the opposite direction, when you show a namespace in the XSD/XML graphical editor, you should convert escape sequence into glyphs.
  I hope this clarify the problem and expectation.
  Please let me know if any additional information is required.

Comment 8 Valentin Baciu 2007-11-20 09:20:03 EST

(In reply to comment #7)
>  It is unclear what should be verified ? The current status is RESOLVED
> WONTFIX.

Hi Tomer, the comment was a bulk message I added to all bugs in the verified state to give the reporter a chance to confirm the resolution.

Thanks for the additional information in comment 7. Keith, please review.

Comment 9 Keith Chong 2008-06-10 16:40:51 EDT

(In reply to comment #7)
>   Since Source Tab reflects the content of stored on the disk artifact file you
> would expect to have escape sequence both on the disk file and in Source Tab.
> However in the graphical portion of the editor I would expect to see glyphs
> since they are human readable as opposed to escape sequence.
>   Consequently when the artifact is stored on the file system you should
> convert namespace from normal (inlcuding glyphs) presentation into escape
> sequence form. In the opposite direction, when you show a namespace in the
> XSD/XML graphical editor, you should convert escape sequence into glyphs.
>   I hope this clarify the problem and expectation.
>   Please let me know if any additional information is required.

There are no plans to do this.  Closing bug.