report data with different char-set other than english

In my report i have to display data from sql db which has this data string in
Russian language. The report object and the text box object have a very
promising property
called: language but setting this property to the required language is not
helping.
How can i make my report to display this data. We changed the language
seeting and IE encoding settging to view the data in the report to the
correct format but its not working. So far what we found is either the report
or reporting services is escaping the high (over 128) characters in the HTML
page.
Any input is appreciated.
--
TIA
-PSHello PS,
I would like to know this issue clearly.
Did you mean that you want to show the text which is in Russian and stored
in SQL Server database?
If so, I don't think you need to do any configuration in the reporting
service and the textbox will show what you stored in the SQL server
database.
Could you please let me know more clearly about which data you stored in
SQL Server and what you want to show up?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for the reply!
Yes i want to just display the text (Russian language data) in the report so
that user can read the data in Russian language without any problem. The data
is stored in the sql server by another application and we just use sql query
in report to select the data and display it in the report. We are able to
see the same data that is stored in the sql server in the report but the data
is not readable. It is like this "Iiia? aa. AAeeoae." in report. when we
select the data from query analyser it shows the same data("Iiia? aa.
AAeeoae.") which is not readble in russian lang.
When we put this data in a sample html page and set the enocding to
"Cyrillic (Windows) it is readable by russian user. But when we open the
report in report manager and set the encoding in the browser to "Cyrillic
(Windows) it is not readable. what we have to do in reports to make it
readable? we tired the report object and the text box language property to
the russian lang setting but we still get the same junk data. I hope this
--
TIA
-PS
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hello PS,
> I would like to know this issue clearly.
> Did you mean that you want to show the text which is in Russian and stored
> in SQL Server database?
> If so, I don't think you need to do any configuration in the reporting
> service and the textbox will show what you stored in the SQL server
> database.
> Could you please let me know more clearly about which data you stored in
> SQL Server and what you want to show up?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello PS<
I would like to know the data type of your problem column and you could
send me the sample HTML file to get the data and show up correct.
I guess you are using the varchar data type for the data and varchar data
type did not support the unicode. If you insert the Unicode char into it,
it will convert into some unreadable format and you may not conver it back
directly.
I would like to suggest you modify the application which insert the data
into your sql server.
Here is a sample to insert and retrieve the unicode data for varchar data
type. Or you may consider to use the Nvarchar data type.
drop table Russia
create table Russia (id int, mytext varchar(100))
insert Russia values (3, cast(cast (N''as varbinary(100)) as varchar(100)))
select id, cast (convert(varbinary(100), mytext)as nvarchar(100)) from
Russia
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for the reply.
I changed the varchar data type column to Nvarchar data type as you said but
still getting the same issue. will my old data will be converted to nvarchar
type after changing just the column data type to nvarchar?
Regarding the html output here is the sample html snip from reporting
service. see the russian char are displayed as "#238;ì.." (reporting services
is escaping the high characters) when i view source from the IE.
In the browser output it is displayed as something like this .."�ëèòåë"..
when i applied the correct enocding in the IE and i still cannot view
correctly
<html>
<head>
</head><body>
Snip from Reporting Services <br>
/*+ RULE ORDERED INDEX(C IDX_TDC_PS_COST) */
N.CALLING_PARTY_NUMBER_RID as "�îìåð à á. �",
N.CALLED_PARTY_NUMBER as "�îìåð à á. �",
C.call_start as "�à òà ",
N.CALL_DURATION as "�ëèòåë.",
decode (CALL_DIRECTION, 'O',
</html>
Below is the sample html that i consturted manually with russian data from
db directly. When i use the correct encoding i'm able to view the russioan
data
<html>
<br><br>
Non escaped high characters will convert properly with the browsers View |
Encoding | Cyrllic (Windows) <br>
/*+ RULE ORDERED INDEX(C IDX_TDC_PS_COST) */
N.CALLING_PARTY_NUMBER_RID as "�îìåð à á. �",
N.CALLED_PARTY_NUMBER as "�îìåð à á. �",
C.call_start as "�à òà ",
N.CALL_DURATION as "�ëèòåë.", decode
(CALL_DIRECTION, 'O',
</body>
</html>
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello PS,
Changing the data type from Varchar to char will not convert it to right.
Since when you insert the Unicode characetors into a Varchar type column,
the information have corrupted yet. And changing the data type will not fix
those old data.
You may need to contact your application vendor to re input the data.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for that info.
ok then i will input fresh data and test it and will let you know.
Thanks
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hello PS,
> Changing the data type from Varchar to char will not convert it to right.
> Since when you insert the Unicode characetors into a Varchar type column,
> the information have corrupted yet. And changing the data type will not fix
> those old data.
> You may need to contact your application vendor to re input the data.
> Hope this helps.
>
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Wei,
we tested the nvarchar changes with new set of data and it did not work.
The issue we have is not Unicode related because the original russian
characters are ISO-1251. ISO-1251 is just using single byte characters not
Unicode double byte characters.
--
TIA
-PS
"PS" wrote:
> Hi Wei,
> Thanks for that info.
> ok then i will input fresh data and test it and will let you know.
> Thanks
> --
> TIA
> -PS
>
> "Wei Lu [MSFT]" wrote:
> > Hello PS,
> >
> > Changing the data type from Varchar to char will not convert it to right.
> > Since when you insert the Unicode characetors into a Varchar type column,
> > the information have corrupted yet. And changing the data type will not fix
> > those old data.
> >
> > You may need to contact your application vendor to re input the data.
> >
> > Hope this helps.
> >
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >|||Hello PS,
I would like to get the sample database data and your collation settings
for the table and database so that I can reproduce this issue.
Could you please get a simple database backup with only on issue table?
You could zip and send it to me.
To reach my real email, please remove the ONLINE in my display email.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello PS,
Did you send your database yet? If anything I can help, please feel free to
let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.