import or export no support chinese code

[GINO]

hello,

When I to import or export Reference data, for example:when I inputed the tranditional chinese ,if i export glossary data to xml
I can get the tranditional chinese front.
when I prepare a xml include tranditional chinese front. it's still have problem when I import to EA.
does anybody can help me to process this problem

only generate glossary report can setup the language...

[suki]

Hello,
I'm not sure which type of database do you use. I had also some problem with it. If you use local EAP database you can try these steps:

1. You'll need another EAP template for EA. It is different than original template which is installed with EA.
You can download it for example here:
http:// http://www.siteadvisor.nl/sites/sparxsystems.com.au/downloads/652987/
This EAP supports the JET4 databases. If you decide to use it in future for all your new projects then replace with it the original file "EABase.eap" in program folder of EA.

2. Then change settings of your EA:
    - Options-> tab General -> check the box "Use JET 4.0"
    - Options-> tab XML Specifications -> Fill value 'utf-8' into filed Code Page

With this EAP database I'm able to export each package to XMI keeping right codepage.
Unfortunately I can't help you with export from current EAP.
Maybe it would be helpful if you set yours computer to the Chinese enviroment before export.

[skiwi]

If you decide to use it in future for all your new projects then replace with it the original file "EABase.eap" in program folder of EA.

[highlight]Bug warning[/highlight]: Every time you install EA it will splat all over your file and revert to the prehistoric (non unicode) version.
Sparx really need to up the ante on this one

[KP]

Every time you install EA it will splat all over your file

So move it or rename it.

It's not a bug. Every version of EA installs the latest version of EABase.eap, and so it should.

[skiwi]

It's not a bug. Every version of EA installs the latest version of EABase.eap, and so it should.

Well we differ on that. EA should not be defaulting to such an old version of an MS Access Database in the first place - we have to have a unicode capable repository.
Really what EA needs is an option that says always use (2007, 2007, 2010, SQ-Lite, .. whatever) to create new repositories.

Its not reasonable that when we update our EA install on the dozen machine or so that we are using it we have to then go around and rename the EA base file.

Surely you can see this.

Its a bug.

[KP]

Its not reasonable that when we update our EA install on the dozen machine or so that we are using it we have to then go around and rename the EA base file.

In that case, put your version of the base model in a shared network location that all machines have access to, and use the "Copy a Base Project" command to create new models, not the "Create a New Project" command. That is, put one file in one location, once, and never worry about it being overwritten ever again.