My involvement with the database design portion of this is limited, but I
will give you as much as I know.
Our database is SQL Server. We have a table called 'dt_column_headers'.
This is where we stored all of the data labels that get displayed on our
reports (and within our app). This table includes the column names and a
dt_id. We also have a table called 'language' which stores culture codes and
language_ids. 'language_translation' contains columns for culture_name, the
dt_id, the english_text, the language_id and the translated_text.
My reports contain two stored procedures. One procedure pulls my data, the
other one pulls my data labels from the translated_text in the
language_translation table.
Hope this helps.
Lisa
Anyone out there have the answer to my original question??
[quoted text, click to view] "Chiara" wrote:
> Hi Lisa
>
> I am also working on creating a report in Chinese. Could you share with me
> how you do multilingual? What is language_translation table?
>
> I stored my data in MSSQL in UTF-8 format eg ä½ å¥½&x3002, which is some chinese
> characters. But when retrieved from database and displayed on the report, the
> report designer and report server seem to recognise "&" as "&" straight
> away, so instead of showing the chinese characters, the report shows
> "ä½ å¥½。"
>
> Would be good if you could share with me how you did it step by step.
> Any coding? How did you store your data? Where to get language_translation
> table? what stored procedure?
>
> "Lisa" wrote:
>
> > I am doing multilingual reporting and have just about worked it all out. The
> > method I am using is to pass the culture code into the report and it brings
> > back my dataset from a language_translation table via stored procedure.
> > Everything is working great, but I have one caveat.
> >
> > I am using a page header that displays on all pages except page 1. Page 1
> > comes from my body. It contains the Globals!ReportName. This field must
> > also be translated as those labels in the body, so I changed the report_name
> > textbox to reference a field in the body that contains the translated report
> > name.
> >
> > It only seems to work when the referenced field is contained within the
> > table footer. Which would be fine if that were displayed on every page, but
> > it isn't. When I move the text up into the detail or page header, it won't
> > display in my header. Why is this? Is there a solution?
> >
> > I also already tried eliminating the page header and placing my report
> > header in my table header, but the problem with that is that I can't use the
> > Globals!PageNumber in my body. (I have a different report name for
Hi Lisa
Maybe you can show me a sample of your data for the different tables?
Probably show me how the translated_text is stored, is it in the utf-8
unicode format? How does it appear in the report? Did you need to do any
setting in the report itself to make the translated_text appear alright?
I stored my data (say the word "Hello") in the format like "xf" etc, but
the chinese characters does not show because of the ampersand "&", it gets
converted to "&#4xf", what some people call escape characters.
Does the report server automatically knows how to translate the english word
"Hello" to Chinese or any other language?
Your help is greatly appreciated and needed. Maybe you can email me at
llbog@yahoo.com
[quoted text, click to view] "Lisa" wrote:
> My involvement with the database design portion of this is limited, but I
> will give you as much as I know.
>
> Our database is SQL Server. We have a table called 'dt_column_headers'.
> This is where we stored all of the data labels that get displayed on our
> reports (and within our app). This table includes the column names and a
> dt_id. We also have a table called 'language' which stores culture codes and
> language_ids. 'language_translation' contains columns for culture_name, the
> dt_id, the english_text, the language_id and the translated_text.
>
> My reports contain two stored procedures. One procedure pulls my data, the
> other one pulls my data labels from the translated_text in the
> language_translation table.
>
> Hope this helps.
>
> Lisa
>
> Anyone out there have the answer to my original question??
>
> "Chiara" wrote:
>
> > Hi Lisa
> >
> > I am also working on creating a report in Chinese. Could you share with me
> > how you do multilingual? What is language_translation table?
> >
> > I stored my data in MSSQL in UTF-8 format eg ä½ å¥½&x3002, which is some chinese
> > characters. But when retrieved from database and displayed on the report, the
> > report designer and report server seem to recognise "&" as "&" straight
> > away, so instead of showing the chinese characters, the report shows
> > "ä½ å¥½。"
> >
> > Would be good if you could share with me how you did it step by step.
> > Any coding? How did you store your data? Where to get language_translation
> > table? what stored procedure?
> >
> > "Lisa" wrote:
> >
> > > I am doing multilingual reporting and have just about worked it all out. The
> > > method I am using is to pass the culture code into the report and it brings
> > > back my dataset from a language_translation table via stored procedure.
> > > Everything is working great, but I have one caveat.
> > >
> > > I am using a page header that displays on all pages except page 1. Page 1
> > > comes from my body. It contains the Globals!ReportName. This field must
> > > also be translated as those labels in the body, so I changed the report_name
> > > textbox to reference a field in the body that contains the translated report
> > > name.
> > >
> > > It only seems to work when the referenced field is contained within the
> > > table footer. Which would be fine if that were displayed on every page, but
> > > it isn't. When I move the text up into the detail or page header, it won't
> > > display in my header. Why is this? Is there a solution?
> > >
> > > I also already tried eliminating the page header and placing my report
> > > header in my table header, but the problem with that is that I can't use the
> > > Globals!PageNumber in my body. (I have a different report name for
Don't see what you're looking for? Try a search.