Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329339 - Translations should be able to be part of the .rptdesign
Summary: Translations should be able to be part of the .rptdesign
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: 3.7.0   Edit
Assignee: Birt-Report-inbox@eclipse.org CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard: Obsolete
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-03 08:29 EDT by Mikkel Andersen CLA
Modified: 2011-05-26 13:32 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mikkel Andersen CLA 2010-11-03 08:29:34 EDT 
Build Identifier: 2.6.0

The .rptdesign file can contain almost everything, images, connections, datasets, layout, css... but not the translations themselves. We distribute the report by uploading the .rptdesign file to a server, but are forced to have the .properties in the shared resource folder for the report to use the translations.
It would be nice if the key /value pair together with language could be added directly to the .rptdesign - since it is an xml format it should be easy to follow other widely used translation-xml schemas

Reproducible: Always
Comment 1 Xiaoying Gu CLA 2010-11-03 22:31:53 EDT 
The separate property files enable users to localize the text in different locales without modifying the report design. It's also the convention of Eclipse does.