Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: SF_lt on August 12, 2008, 08:38:24 pm

Title: incorrect unicode support
Post by: SF_lt on August 12, 2008, 08:38:24 pm

there is a problem with national character support - some letters are saved, some not.

Names of objects, containing some local  characters aren't saved - after closing diagram they are substituted by normal latin characters as a,e,i,u

I'm expieriencing problem with the some lithuanian symbols ([ch261],[ch363],[ch371],[ch281],[ch279]), however [ch269] is handled correctly

Title: Re: incorrent unicode support
Post by: «Midnight» on August 12, 2008, 10:34:24 pm

Can you send an example project to Sparx? It would also help if you identified the environment (in terms of version, language, service pack etc. for operating system and such).

Title: Re: incorrect unicode support
Post by: Eve on August 13, 2008, 08:12:04 am

First, what database are you using?  Check for appropriate unicode support on that database.  (If using EAP files then make sure you have JET 4 support enabled, and are using the Jet 4 base model.)

Also, is the problem in all text fields, or just in the rich text fields?  We recently had a problem with the rich text fields.  That was specifically with Russian text, but it could be related.

Title: Re: incorrect unicode support
Post by: SF_lt on August 13, 2008, 03:45:55 pm

i can send project example, but this wouldn't help - characters aren't saved after diagram is closed

Title: Re: incorrect unicode support
Post by: Andrei on August 15, 2008, 09:43:54 am

I do not have a problem with russian text on Vista Home 32-bit( laptop).
On Vista Ultimate sp1 64-bit the problem exists.
Just try to put and save russian text to notes ( Properties dialog of any item).
Any idea?

Title: Re: incorrect unicode support
Post by: Eve on August 15, 2008, 12:10:32 pm

The errors with Russian text in the notes were fixed in build 831.

As for why it's happening on one computer and not another, it was dependent on a registry hack sometimes made for other tools that points registry setting for code page 1252 (windows standard) to the file for code page 1251 (russian).

If you want to look it up, in the system that has the problem you'll probably find the following in your registry.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage]
 "1252"="c_1251.nls"

If something similar gets done in Lithuania, then this was probably fixed in build 831 too.

Title: Re: incorrect unicode support
Post by: Andrei on August 19, 2008, 03:21:52 am

I have build 832 and the registry settings are correct 1252 = c_1252.nls
The problem with notes exists.

Title: Re: incorrect unicode support
Post by: Eve on August 19, 2008, 08:01:25 am

Then something else is going on.  Please send a bug report in using the bug report form (link at the bottom of this page).

Out of interest, what was your upgrade path to 832?  Did you use the patch file?