Chris;
I think the
confusion point might be the difference between Unicode database support and Unicode compliance. The difference being that with 6.3, Unicode Database support,
you get the ability to have your ARServer(s) pointing to a single database instead
of multiple. With Unicode Compliance
you get a much different picture…. This essentially means that your code is
written in a Unicode format and that you are able to interpret Unicode
characters at the application (ARServer) level much like the Java programming
language does, therefore you end up with a server that allows you to run
multiple languages, in other words not a language-centric server.
Let me know if
you have questions…
Thanks
Kirk
From: Action Request
System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]
On Behalf Of VanAartsen,
Christopher
Sent: Friday, September 08, 2006
6:39 AM
To: arslist@ARSLIST.ORG
Subject: Re: Chinese Characters on
a US
database
Heard back from Remedy
Support and they confirmed.
"To change the character set, you
would have to reinstall SQL Server, then you would need to migrate the ARServer
data and defs to the new database. With ARS 6.3, this would require two servers
to handle the two character sets. With ARS 7.0, you may be able to use one
server, but you cannot get Chinese characters into a LATIN1 database."
Can anyone speak to the issue of 2 servers
for 6.3 and 1 server for 7.0? I was under the understanding that with ARS
6.3, using a SQL database (Unicode), could handle multiple Character
sets. Does anyone else use this configuration, if so, which Character
sets?
From: Action
Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]
On Behalf Of Michiel Beijen
Sent: Tuesday, August 29, 2006
8:34 AM
To: arslist@ARSLIST.ORG
Subject: Re: Chinese Characters on
a US
database
Yup, it seems to me that
the collation is the problem.
This is tricky on a SQL 2000 database as you might have to alter the collation
on Master and Tempdb as well.
Check the KB article for more information:
http://support.microsoft.com/?kbid=325335
Kind regards,
Michiel
On 8/28/06, VanAartsen,
Christopher <
[EMAIL PROTECTED]> wrote:
**
Michiel, thanks for the response.
The Database is Unicode, (from the ar.cfg
file) Db-Character-Set: UTF-16.
Looks to me like the character set is the
issue, we only have SQL_Latin1_General_CP1_CI_AS collated. Can we add
additional character sets at this point?
Ö ñ ê ë è are in the Latin1 character set
and show up fine.
Thanks
Chris
From: Action Request
System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On
Behalf Of Michiel Beijen
Sent: Monday, August 28, 2006 9:10
AM
Chris,
You said: Setup is unicode. Are you referring to the DATABASE or
to the AR Server? What is the character set for your database? You can view
this by right-clicking on the database in SQL Server Enterprise Manager.
Kind regards,
Michiel
On 8/28/06, VanAartsen,
Christopher <[EMAIL PROTECTED]
> wrote:
**
This is regardless of the WUT, both
Chinese and English. Also with the user preference set as Chinese.
I notice that with the User Preference set as Chinese, menus like
File/View/Tools, etc show as Chinese characters.
When using Mid-Tier 补救规则 does not change to ???? until after the ticket is saved.
When using the desktop clients it changes right away. I have the Chinese
.dll's installed on the desktop client.
Anyone have any other ideas or
suggestions?
From: Action
Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of danish khoya
Sent: Sunday, August 27, 2006 9:55
AM
To: arslist@ARSLIST.ORG
Subject: Re: Chinese Characters on
a US
database
Whether your WUT on Windows Chinese machine or English machine?
What is the language set for the user in preference server option when
you try to enter chinese characters?
On 8/26/06, VanAartsen,
Christopher <[EMAIL PROTECTED]>
wrote:
I have an issue when adding Chinese characters in our US based
system. I
can type the Chinese characters in word (well, I can't, but my computer
can), see them in any other application, but when they are copied/pasted or
typed into Remedy, it changes the characters into question
marks. I'm just
attempting to localize the simple requester form, which worked fine for
English and Portuguese. I've opened a ticket with support, but I'm
not
getting too far. They want me to run a user tool log that I just
can't seem
to get to pull the correct errors.
Environment: ARS 6.3 , patch 14 (tried on patch 17 too), running on Windows
2003. Database is SQL 2000 advanced, and is setup UNICODE.
Anyone have any ideas? Anyone willing to go to
http://babelfish.altavista.com
<
http://babelfish.altavista.com> , translate
from English to Chinese and see if they can reproduce this error?
补救规则 (aka,
remedy rules) If you can't read this and you are using
windows os you probably don't have the east Asian language files installed.
There is a KM article that explains the exact problem I am having, but the
example is for Oracle&HP/UX, I'm trying to find out what to look for, for
SQL.
KM-000000024118
Thanks,
Dazed and confused…
Chris
This e-mail message and any attachments may contain legally privileged,
confidential or proprietary Information, or information otherwise protected by
law of ArvinMeritor, Inc., its affiliates, or third parties. This notice serves
as marking of its 揅onfidential�status
as defined in any confidentiality agreements concerning the sender and
recipient. If you are not the intended recipient(s), or the employee or agent
responsible for delivery of this message to the intended recipient(s), you are
hereby notified that any dissemination, distribution or copying of this e-mail
message is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete this e-mail message from your
computer.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
This e-mail message and any attachments may contain legally privileged,
confidential or proprietary Information, or information otherwise protected by
law of ArvinMeritor, Inc., its affiliates, or third parties. This notice serves
as marking of its �Confidential� status as defined in any confidentiality
agreements concerning the sender and recipient. If you are not the intended
recipient(s), or the employee or agent responsible for delivery of this message
to the intended recipient(s), you are hereby notified that any dissemination,
distribution or copying of this e-mail message is strictly prohibited. If you
have received this message in error, please immediately notify the sender and
delete this e-mail message from your computer.
__20060125_______________________This posting was submitted with HTML
in it___
This e-mail message and any attachments may contain legally
privileged, confidential or proprietary Information, or information otherwise
protected by law of ArvinMeritor, Inc., its affiliates, or third parties. This
notice serves as marking of its �Confidential� status as defined in any
confidentiality agreements concerning the sender and recipient. If you are not
the intended recipient(s), or the employee or agent responsible for delivery of
this message to the intended recipient(s), you are hereby notified that any
dissemination, distribution or copying of this e-mail message is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and delete this e-mail message from your computer.
__20060125_______________________This posting was
submitted with HTML in it___
This e-mail message and any attachments may contain legally privileged,
confidential or proprietary Information, or information otherwise protected by
law of ArvinMeritor, Inc., its affiliates, or third parties. This notice serves
as marking of its Confidential status as defined in any confidentiality
agreements concerning the sender and recipient. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of this message to the
intended recipient(s), you are hereby notified that any dissemination,
distribution or copying of this e-mail message is strictly prohibited. If you
have received this message in error, please immediately notify the sender and
delete this e-mail message from your computer.
__20060125_______________________This posting was submitted with HTML in it___ |