Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

French local

4 posts in General Discussion Last posting was on 2009-05-12 15:47:21.0Z
wndr Posted on 2009-05-11 21:12:58.0Z
From: "wndr" <wndr@hotmail.com>
Newsgroups: ianywhere.public.general
Subject: French local
Lines: 9
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a0894da$1@forums-1-dub>
Date: 11 May 2009 14:12:58 -0700
X-Trace: forums-1-dub 1242076378 10.22.241.152 (11 May 2009 14:12:58 -0700)
X-Original-Trace: 11 May 2009 14:12:58 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7548
Article PK: 5955

Hi guys
We support multy language application. The translation and the original
records are saved in the db file as storeprocedure. So sometimes when i run
the sql script which includes this st_p, and this st_p is added to the db
the French caracters with an accent, at the top, got replaced to some other
characters. Any idea on why it happens and how to fix that?
Thanks in advance.


John Smirnios [Sybase] Posted on 2009-05-12 13:37:48.0Z
From: "John Smirnios [Sybase]" <smirnios_at_sybase.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: French local
References: <4a0894da$1@forums-1-dub>
In-Reply-To: <4a0894da$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a097bac$1@forums-1-dub>
Date: 12 May 2009 06:37:48 -0700
X-Trace: forums-1-dub 1242135468 10.22.241.152 (12 May 2009 06:37:48 -0700)
X-Original-Trace: 12 May 2009 06:37:48 -0700, vip152.sybase.com
Lines: 35
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7549
Article PK: 5957

Without software version numbers, database collation/charset
information, and client app & charset information for where you are
creating & viewing the procedure definition, there are just too many
possibilities for where something may have gone wrong.

If you are using recent software, using a database that can properly
store the French character you are interested in, defining the procedure
from client that can properly represent the character and viewing the
procedure (or its output -- if that is where the French character is
located) from a client that can properly represent the character, you
should have no problems.

If you give more details about your environment and when it fails, I may
be able to help you.

-john.

--
John Smirnios
Senior Software Developer
iAnywhere Solutions Engineering

Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer

wndr wrote:
> Hi guys
> We support multy language application. The translation and the original
> records are saved in the db file as storeprocedure. So sometimes when i run
> the sql script which includes this st_p, and this st_p is added to the db
> the French caracters with an accent, at the top, got replaced to some other
> characters. Any idea on why it happens and how to fix that?
> Thanks in advance.
>
>


wndr Posted on 2009-05-12 14:29:45.0Z
From: "wndr" <wndr@hotmail.com>
Newsgroups: ianywhere.public.general
References: <4a0894da$1@forums-1-dub> <4a097bac$1@forums-1-dub>
Subject: Re: French local
Lines: 54
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a0987d9@forums-1-dub>
Date: 12 May 2009 07:29:45 -0700
X-Trace: forums-1-dub 1242138585 10.22.241.152 (12 May 2009 07:29:45 -0700)
X-Original-Trace: 12 May 2009 07:29:45 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7550
Article PK: 5956

Hi John
Thank you so much for replay. I am using SQL Anywhere version 9. On Windows
2003 R2 SP2.
The issue is like that. We have GUI application, that supports multiple
languages. We keep the English frases in db Table "Res" EnglishColimn1,
French translation of these phrases we keep in FrenchColumn2. We update the
FrenchColumn2 using storeprocedure:
CREATE PROCEDURE "DBA"."sp_GetRes"()
begin
update Res set EnglishColimn1 = 'EnglishPhrase,FrenchColumn2 =
'FrenchPhrase'
end
So After we run this sql scrip, when I open db file -> sp_GetRes, if the
French phrase has é, it gets replaced to some weird characters.
Appreciate any help.

"John Smirnios [Sybase]" <smirnios_at_sybase.com> wrote in message
news:4a097bac$1@forums-1-dub...
> Without software version numbers, database collation/charset information,
> and client app & charset information for where you are creating & viewing
> the procedure definition, there are just too many possibilities for where
> something may have gone wrong.
>
> If you are using recent software, using a database that can properly store
> the French character you are interested in, defining the procedure from
> client that can properly represent the character and viewing the procedure
> (or its output -- if that is where the French character is located) from a
> client that can properly represent the character, you should have no
> problems.
>
> If you give more details about your environment and when it fails, I may
> be able to help you.
>
> -john.
>
> --
> John Smirnios
> Senior Software Developer
> iAnywhere Solutions Engineering
>
> Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
> Developer Community at http://www.ianywhere.com/developer
>
> wndr wrote:
>> Hi guys
>> We support multy language application. The translation and the original
>> records are saved in the db file as storeprocedure. So sometimes when i
>> run the sql script which includes this st_p, and this st_p is added to
>> the db the French caracters with an accent, at the top, got replaced to
>> some other characters. Any idea on why it happens and how to fix that?
>> Thanks in advance.


John Smirnios [Sybase] Posted on 2009-05-12 15:47:21.0Z
From: "John Smirnios [Sybase]" <smirnios_at_sybase.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: French local
References: <4a0894da$1@forums-1-dub> <4a097bac$1@forums-1-dub> <4a0987d9@forums-1-dub>
In-Reply-To: <4a0987d9@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a099a09$1@forums-1-dub>
Date: 12 May 2009 08:47:21 -0700
X-Trace: forums-1-dub 1242143241 10.22.241.152 (12 May 2009 08:47:21 -0700)
X-Original-Trace: 12 May 2009 08:47:21 -0700, vip152.sybase.com
Lines: 113
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7551
Article PK: 5954

It's may not be relevant but that stored procedure doesn't make much
sense to me. The stored procedure "sp_GetRes" has hard-coded constant
strings in it and it updates the Res table. I'm guessing the statement
is more like:
UPDATE Res
SET EnglishColumn1='EnglishPhrase',
FrenchColumn2='FrenchPhrase'
WHERE Res.ResID = [some integer]

sp_GetRes doesn't seem to return any strings either.

Anyways, it seems strange to define a stored procedure to do a bunch of
updates that only need to be done once rather than just having a bunch
of INSERT and/or UPDATE statements in your SQL script.

For now, I'll just go with the assumption that "constant strings in a
stored procedure are not being handled correctly".

Now, what collation is the database using? If you are unsure, run dbinfo
or SELECT db_property( 'COLLATION' ).

What command line options are used to start the engine?

What application was used to define the stored procedure (dbisql,
dbisqlc, your own)? If it was your own, what interface does it use
(ODBC, ESQL, etc) and if it was ODBC, was it a Unicode app or ANSI? What
connection string was used? If the character set was not explicitly set
in the connection string, what is the character set of the OS where the
application is running? What character set was the original CREATE
PROCEDURE statement (ie the SQL script file) in? If you were using
dbisql (the Java version), how did you run the SQL script: from the
command line (eg dbisql READ stuff.sql) or by typing "read stuff.sql"
into the GUI after it was started via an icon or sybase central?

Similarly, for the application that is viewing the error messages, what
interface does it use, what was its connection string, and what is the
character set of the OS where the application is running?

Try the following:
UNLOAD SELECT * FROM SYS.SYSPROCEDURE WHERE proc_name='sp_GetRes' TO
'getres.txt';

UNLOAD SELECT * FROM Res TO 'res.txt';

Look at getres.txt and res.txt using Notepad on your French machine. Do
the e-acute letters look correct?

Sorry for the long list of questions but character set translation can
occur in so many places...


-john.

--
John Smirnios
Senior Software Developer
iAnywhere Solutions Engineering

Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer

> 2003 R2 SP2.
> The issue is like that. We have GUI application, that supports multiple
> languages. We keep the English frases in db Table "Res" EnglishColimn1,
> French translation of these phrases we keep in FrenchColumn2. We update the
> FrenchColumn2 using storeprocedure:
> CREATE PROCEDURE "DBA"."sp_GetRes"()
> begin
> update Res set EnglishColimn1 = 'EnglishPhrase,FrenchColumn2 =
> 'FrenchPhrase'
> end
> So After we run this sql scrip, when I open db file -> sp_GetRes, if the
> French phrase has é, it gets replaced to some weird characters.
> Appreciate any help.
>
>
> "John Smirnios [Sybase]" <smirnios_at_sybase.com> wrote in message
> news:4a097bac$1@forums-1-dub...
>> Without software version numbers, database collation/charset information,
>> and client app & charset information for where you are creating & viewing
>> the procedure definition, there are just too many possibilities for where
>> something may have gone wrong.
>>
>> If you are using recent software, using a database that can properly store
>> the French character you are interested in, defining the procedure from
>> client that can properly represent the character and viewing the procedure
>> (or its output -- if that is where the French character is located) from a
>> client that can properly represent the character, you should have no
>> problems.
>>
>> If you give more details about your environment and when it fails, I may
>> be able to help you.
>>
>> -john.
>>
>> --
>> John Smirnios
>> Senior Software Developer
>> iAnywhere Solutions Engineering
>>
>> Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
>> Developer Community at http://www.ianywhere.com/developer
>>
>> wndr wrote:
>>> Hi guys
>>> We support multy language application. The translation and the original
>>> records are saved in the db file as storeprocedure. So sometimes when i
>>> run the sql script which includes this st_p, and this st_p is added to
>>> the db the French caracters with an accent, at the top, got replaced to
>>> some other characters. Any idea on why it happens and how to fix that?
>>> Thanks in advance.
>
>