Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365562

Summary: Localization issue with selection choices created in a rptlibrary
Product: z_Archived Reporter: donino donino <dpardon>
Component: BIRTAssignee: Birt-ReportEngine-inbox <Birt-ReportEngine-inbox>
Status: VERIFIED FIXED QA Contact: Hao Zhou <hao.zhou>
Severity: normal    
Priority: P3 CC: bluesoldier, yChen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Simple example to highlight this issue none

Description donino donino CLA 2011-12-05 05:09:01 EST 
Build Identifier: 3.7.1

When a parameter with selection choices is created in a library, and therefore the related localization resource properties file is added to this rptlibrary, the selection choices localization keys are not found by Birt Engine. 

It appears that for selection choices, Birt is looking for localization keys only in the report resource files, library resources are just ignored whereas  whereas for prompts and helptext properties, it seems working fine. 

A workaround is to  manually add libraries properties file to every related reports, bit it doesnt appear to be a very maintainable option.

Reproducible: Always

Steps to Reproduce:
1.Add a localization properties file to a rptlibrary resources
2.Create a radio button parameter in this rptlibrary, add static selection choices with localization keys.
3.Update manually the parameter display text, to distinguish if birt retrieves it from properties file or rptdesign: for instance add "static" at the beginning of every selection choice display text.
4.Use this parameter in a report, without any localization resource properties attached => the "static" texts will be used every time
Comment 1 donino donino CLA 2011-12-05 05:11:48 EST 
Created attachment 207906 [details]
Simple example to highlight this issue

Copy the rptlibrary and the properies files in your resource_path root and run the report in a designer / webviewer.
Comment 2 Yu Chen CLA 2012-06-18 06:24:40 EDT 
Fixed.
Comment 3 Hao Zhou CLA 2012-06-26 23:41:51 EDT 
Verified in 4_2_0-20120614