Book a Demo

Author Topic: problem with encoding in Model Issues  (Read 7483 times)

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
problem with encoding in Model Issues
« on: July 11, 2006, 03:11:31 am »
Hi,

I have a problem with some czech characters in editing model issue. In Maintenance window I can add a model issue with czech characters, but when I save the issue and reopen the dialog the Name field contains some wrong characters.

I tried these characters

and after saving and reopening the dialog I got this


Will you help me?
I have EA 6.1.791
Thanks

ernest
-ernest

thomaskilian

  • Guest
Re: problem with encoding in Model Issues
« Reply #1 on: July 12, 2006, 05:41:53 am »
There have been posts regarding Czech chars here. Have you searched for them (can't actually help you)?

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #2 on: July 13, 2006, 02:48:13 am »
yes, I tried searching for string "czech" during last year at the forum and I found only "Problem with RTF report for Model Issues". I think, this is another problem.

Does anybody have the same problem?
-ernest

Jan ´Bary´ Glas

  • EA User
  • **
  • Posts: 408
  • Karma: +0/-0
  • Bary
    • View Profile
Re: problem with encoding in Model Issues
« Reply #3 on: July 14, 2006, 12:15:59 am »
Quote
Does anybody have the same problem?

It works well for me, build 6.1.792.
Cannot replicate.
Problems with Czech I suffered before:
when Czech (localized) MS Windows w/EN keyboard - problems with RTF generation (already fixed)
not described problem w/ RTF generation (from time to time it behaves strange w/custom templates, still no idea why, working on it)

Conclusion: I have problem with nothing inside the EA (considering Czech).
Jan 'Bary' Glas

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #4 on: July 18, 2006, 04:34:13 am »
In EA version 6.1.792 the problem still persists. I tried another computer in our company (with the same version), and they have the problem too. We have Unicode version installed.

I don't have another problem with czech characters except this and the behavior which Bary described.

Could you remove the unpleasant behavior? Has anybody some idea, what to do/test?
-ernest

Jan ´Bary´ Glas

  • EA User
  • **
  • Posts: 408
  • Karma: +0/-0
  • Bary
    • View Profile
Re: problem with encoding in Model Issues
« Reply #5 on: July 19, 2006, 10:48:14 am »
 ernest, still cannot repeat.
what system do you have? (I have MS Windows XP English version.)
Jan 'Bary' Glas

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: problem with encoding in Model Issues
« Reply #6 on: July 19, 2006, 03:06:37 pm »
I'm not completely sure of your problem, but if you're using EAP files make sure that you're using JET 4.  (Tools | Options| General)  You may also need to get a JET4 base model.

If you're using a repository, make sure that the repository is set up to handle unicode characters.

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #7 on: July 20, 2006, 05:45:49 am »
I'm running WinXP Pro Cze SP2 and as a repository we have MS SQL 2000 Standard Edition SP3, Server collation SQL_Czech_CP1250_CI_AS. Database collation is the same.

ooops, I was looking into the database, into the table t_objectproblem and I noticed that the column Problem has varchar datatype whilst the column ProblemNotes and other has ntext and nvarchar. It's possible that this could cause the problem?
-ernest

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: problem with encoding in Model Issues
« Reply #8 on: July 21, 2006, 11:10:09 am »
That sounds entirely likely.
No, you can't have it!

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #9 on: July 24, 2006, 12:10:00 am »
Yes, it works! Changing the datatype of the column from VARCHAR to NVARCHAR, solved my problem.
Thank you everybody
-ernest

Jan ´Bary´ Glas

  • EA User
  • **
  • Posts: 408
  • Karma: +0/-0
  • Bary
    • View Profile
Re: problem with encoding in Model Issues
« Reply #10 on: July 24, 2006, 12:51:34 am »
Superb, helps for the future in similar cases. Thanks a lot.
Jan 'Bary' Glas

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #11 on: July 24, 2006, 01:49:28 am »
Quote
Yes, it works! Changing the datatype of the column from VARCHAR to NVARCHAR, solved my problem.
Thank you everybody
As you can see, the Sparxians do monitor this forum, but it may be best to let them know formally...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

ernest

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: problem with encoding in Model Issues
« Reply #12 on: July 24, 2006, 02:07:26 am »
Quote
As you can see, the Sparxians do monitor this forum, but it may be best to let them know formally...

Paolo


I wanted to discuss the problem first.

And now, is it necessary to report a bug or will you solve the problem without the report?
-ernest

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: problem with encoding in Model Issues
« Reply #13 on: July 24, 2006, 04:58:41 am »
BTW, remember that this (changing from 8-bit to extended character types) will work - with appropriate adjustments - for Oracle, SQL Server, and Sybase repositories. I suspect similar adjustments will also work with the other repository types.
No, you can't have it!