Crystal v8.5 pro and Unicode

[Jacque]

Does CRv8.5 support unicode characters?

Thanks for your help in advance,
Jacque

 

[kenhamady]

Unicode was introduced in the VisualStudio.NET version of CR, but won't hit regular CR until v9. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[Jacque]

I need to translate reports into a language which uses unicode characters and I'm using v8.5, do you have any idea of how that will effect my efforts?

 

[kenhamady]

Sorry, I don't. Ken Hamady, On-site Custom Crystal Reports Training & Consulting
Public classes and individual training.
Guide to using Crystal in VB

http://www.kenhamady.com/

tek@kenhamady.com

 

[Jacque]

Well, very soon I'll be finding out and will let you know what I find.
Thanks, Ken.

 

[Jacque]

Hi,
My setup is as follows: WIN2K O/S, CR v8.5 pro, locale, language and input settings are set to the language of my reports. My pc is dedicated to only these reports. I'm using working reports and copying over translated text strings which may be field labels, column headers, sql queries, text contained within suppression formulas and formula contents.

Upon opening CR v8.5 English, you get an error message that translates as: impossible to find the rows necessary in order to (? - unable to translate the word used here) "Crystal Reports" in the applicable language. To continue in English language? Click Ok and CR can be used as normal. I've gotten this same error message in non-unicode, non-English languages as well with no ill results.

So far the only issues have involved formatting:

Translated characters which don't copy over correctly, for example dashes translate as an ? but if you select the question mark and replace with a dash - no problem.

When changing the font and/or font size, it sometimes(?) resizes automatically but not necessarily correctly.

When the text field size is not long enough to display the entire text string, you can't easily tell that it isn't long enough unless you know the characters of the word or you resize larger to verify. It's not as obvious as it is in English. I'm using an English db, so I haven't been able to test to see if Can Grow works correctly for db fields in this language - I have my suspicions that it might not work but I currently don't have any way of verifying this as of yet.

Fields which are left justified and 'attached' to a vertical guideline, when font type/size is changed, react normally although you may have to realign to the horizontal grid. Those that are right justified, become 'unattached' from the vertical guideline and have to be realigned both vertically and horizontally.

So far, it hasn't been as bad as I expected.