Develop a Report for Users in Portuguese

[Vick]

I have a requirement to do some reporting for users in Portuguese language. The data in the database is in Portuguese so I am not worried about converting that.

My question is when users will encounter errors, etc. while using prompts, it will display in English. Is there any way I can have prompts error/page numbers/error messages/ etcs be displayed in Portuguese.

Thanks,
Vic

[MFGF]

I have a requirement to do some reporting for users in Portuguese language. The data in the database is in Portuguese so I am not worried about converting that.

My question is when users will encounter errors, etc. while using prompts, it will display in English. Is there any way I can have prompts error/page numbers/error messages/ etcs be displayed in Portuguese.

Thanks,
Vic

Hi,

Portugese is a supported locale - so you shouldn't have any issues. If you look in "My Preferences", there are two configurable language settings for each user - Product Language and Content Language. Portugese is there automatically in the Product Language list, and as long as you add Portugese as a language in your FM model and specify Portugese names before publishing your package, then selecting Portugese from the Content Language setting will affect the names of data objects in the packages. Take a look at Chapter 5 in the Framework Manager User Guide (Multilingual metadata):

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1/ug_fm.pdf

Then take a look at Chapter 10 in the Architecture and Deployment Guide:

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1/crn_arch.pdf

Also see Chapter 8 (Installing Translated product documentation) and Chapter 9 (Changing Global Settings) in the Installation and Configuration Guide:

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1.1/inst_cr_winux.pdf

Cheers!

MF.

[Vick]

Thanks a lot MF, but I am not using a package to develop these reports. I am using tabular SQL directly against the database.

Will it still work?

-Vic

[MFGF]

Thanks a lot MF, but I am not using a package to develop these reports. I am using tabular SQL directly against the database.

Will it still work?

-Vic

Hand-coded SQL? Really? I'm not even sure I want to ask why you would want to make life so difficult for yourself :) It's like buying a top-quality torque-sensitive electric screwdriver with every option on it, then using it to hammer your screws in like nails. ;)

Are the table names and column names in the database held Portugese? If not, you're going to have to add aliases to every item in the SQL query to specify the Portugese name to be displayed - for every report.

Cheers!

MF.

[Lynn]

Thanks a lot MF, but I am not using a package to develop these reports. I am using tabular SQL directly against the database.

Will it still work?

-Vic

[MFGF]

lol :D

[Vick]

These are 20 yr old  COBOL reports to be converted to Cognos, so there is no star schema but bunch on tables interconnected to each other. Hence we decided to go for Direct SQL vs FM Model.


To answer ur question, yes tables and data is in Portuguese.


-Vic

[MFGF]

These are 20 yr old  COBOL reports to be converted to Cognos, so there is no star schema but bunch on tables interconnected to each other. Hence we decided to go for Direct SQL vs FM Model.


To answer ur question, yes tables and data is in Portuguese.


-Vic

You can still produce an effective metadata model when the underlying tables are not star schemas. It means a little more work in creating the model and building model query subjects that appear like star schemas, but I'd do that every single time rather than taking the decision to create every report using hand-cranked SQL. Coding SQL in reports might seem like a quick and easy solution initially, but it is horrendous to maintain and it makes adding even a simple feature like a calculation or a sort impossible for a non-guru-SQL-type-person to do. One of the main benefits of reporting in Cognos is that it allows drag-and-drop capabilities for items and builds appropriate queries to answer the questions asked by non-technical users. Bi creating reports based on manual SQL you throw all of this goodness away. What you are left with is inflexible reports which are massively difficult to maintain or modify.

Anyway - enough preaching :)

If your table and column names are already in portugese then you are ok to go. Just set the Product Language and the Content Language to Portugese. Oh, and follow the steps I detailed earlier in the thread if you want to have Portugese documentation available.

Cheers!

MF.