Package Import fails with Unicode names

[Paolo F Cantoni]

If you import a package that has a name containing Unicode characters (such as [ch949] (small epsilon) ) the t_package will contain the correct [ch949] character but t_object will contain an e (small letter E).  This is because the import has an intermediate process where the name is not Unicode (that is - although in both t_package and t_object Name is nvarchar(255); however as EA is storing the t_object Name it's being passed through a varchar(255) variable (converting the [ch949] to an e) - which needs to be changed to nvarchar(255)).

As far as I can tell the exported XMI is correct and contains "#949;" (the correct representation for [ch949] (small epsilon).

NOTE: Project transfer doesn't have this problem because it uses a more direct mechanism to populate the tables.

Steps:
Create an EAP project containing a package name with [ch949] (small epsilon)
Transfer to an SQL Server instance using Project transfer
Run Integrity Check [Shift+F9]
Observe no problems
Export the same package to XMI from .EAP
Import into SQL'
Run Integrity Check [Shift+F9]
Observe inconsistent name issues
Reported,
Paolo

[skiwi]

I can only hope that 9 will report the many Unicode problems we have encountered, including spelling and unavailability is various places in the model.
I'll be trying this soon.

856 RTF editor input methods
Unicode support in EA