| Localization issue with selection choices [message #760553] |
Fri, 02 December 2011 15:03  |
Eclipse User |
|
|
|
Hi,
I create cross-report parameters in a common rptlibrary. So far so good, everything works fine except localization: i have an issue with selection choices, for instance a radio buttons static list, localization keys are ignored. It only wants to display "display text" field. Prompts and helptext localization work correctly in a library, it only relates to selection choices, and it works fine if parameters are created in reports.
This problem happens both in WebViewer and a custom application.
So did anyone succeed to make parameters' localization work in a rptlibrary? Is it a known issue or should i log a bugzilla case?
thanks!
[Updated on: Fri, 02 December 2011 15:04] by Moderator |
|
|
|
| Re: Localization issue with selection choices [message #760603 is a reply to message #760577] |
Sat, 03 December 2011 06:56  |
| Eclipse User |
|
|
|
Jason,
I use 3.7.1, i think i found why it doesn't work in my context: since parameter is created in a library, the related resource properties file is only added to rptlibrary, not to rptdesign. During the report running, it seems Birt is looking for localization keys only in the report resource files, whereas library resources are just ignored. I suppose resources should be merged when a report uses a rptlibrary? Of course we could manually add libraries properties file to every related reports, bit it doesnt appear to be a very maintainable option.
Since i dont know what is the expected behavior in this kind of context, i didn't still log a bugzilla entry.
I join a simple example wich highlights this case.
Thanks
[Updated on: Sat, 03 December 2011 07:03] by Moderator |
|
|
| Re: Localization issue with selection choices [message #760751 is a reply to message #760603] |
Mon, 05 December 2011 00:34 |
| Eclipse User |
|
|
|
Go ahead and open a bugzilla entry for this.
Jason
On 12/3/2011 6:56 AM, dpardon wrote:
> Jason,
>
> I use 3.7.1, i think i found why it doesn't work in my context: since parameter is created in a library, the related resource properties is only added to rptlibrary, not to rptdesign. During the report running, it seems Birt is looking for localization keys only in the report resource files, whereas library resources are just ignored. I suppose resources should be merged when a report uses a rptlibrary? Of course we could manually add libraries properties file to every related reports, bit it doesnt appear to be a very maintainable option.
>
> Since i dont know what is the expected behavior, i didn't still log a bugzilla entry.
>
> I join a simple example wich highlights this case.
>
> Thanks
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05076 seconds
Home