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

Bug 261293

Summary: [Scripting usability] Ability to set format of a control without changing the locale of the entire report.
Product: z_Archived Reporter: Rima Kanguri <rkanguri>
Component: BIRTAssignee: Haojun Chu <hchu>
Status: VERIFIED FIXED QA Contact: Maggie Shen <lshen>
Severity: normal    
Priority: P3 CC: bluesoldier, rlu, whe, wyan, zqian
Version: unspecifiedKeywords: plan
Target Milestone: 2.5.0 M7   
Hardware: PC   
OS: Windows 2000   
Whiteboard: Autoed,G-text
Attachments:
Description Flags
Locale Setting
none
Locale Setting 02 none

Description Rima Kanguri CLA 2009-01-15 18:19:09 EST
Customer wants the ability to set the format to a control without changing the locale of the report. For example, a number like 123456.789 should be formatted as 123.456,789 while maintaining the English locale for the entire report.

We basically should be able to set the locale on the data format page
Comment 1 Rima Kanguri CLA 2009-01-15 18:20:27 EST
- We can enhance the format dialog to support optional input locale property
- If user does not set the locale then we should keep the current behavior
Comment 2 Zhiqiang Qian CLA 2009-01-21 23:15:01 EST
We need model support first.
Comment 3 Rick Lu CLA 2009-01-22 01:16:26 EST
(In reply to comment #2)
> We need model support first.
> 

Locale property on NumberFormat, StringFormat, DataTimeFormat are good enough to UI?
Comment 4 Zhiqiang Qian CLA 2009-01-22 03:31:32 EST
Yes, I think a new "Locale" property should be enough.
Comment 5 Rima Kanguri CLA 2009-01-22 16:11:32 EST
We will also need support in BIRT engine right?
Comment 6 Zhiqiang Qian CLA 2009-01-22 21:22:47 EST
Yes, it also needs BIRT Engine support.
Comment 7 Rima Kanguri CLA 2009-02-09 18:52:46 EST
Can we finish this for M6? Thanks
Comment 8 hong chen CLA 2009-02-11 23:14:01 EST
provided get/setLocale() methods on FormatValueHandle.
reassign to GUI
Comment 9 Zhiqiang Qian CLA 2009-02-12 05:28:37 EST
Please propose the UI mockup.
Comment 10 Boonboon Chanchoke CLA 2009-02-13 19:00:40 EST
Created attachment 125701 [details]
Locale Setting
Comment 11 Boonboon Chanchoke CLA 2009-02-13 19:01:12 EST
Created attachment 125702 [details]
Locale Setting 02
Comment 12 Boonboon Chanchoke CLA 2009-02-13 19:01:51 EST
Proposed UIs are attached. 
Comment 13 Zhiqiang Qian CLA 2009-02-15 20:48:32 EST
Reopen for designer change.
Comment 14 Zhiqiang Qian CLA 2009-02-15 20:52:15 EST
Note the locale list should have an "Auto" choice by default selected, which means using the default locale thus being compatible with old behavior.
Comment 15 Wei Yan CLA 2009-02-24 03:23:19 EST
should we add a new property to the report design handler to control the locale used to format the data?

such as:

design:
   locale: en_US

element:
   locale: en_US/Auto/viewTime

If the user defines the locale in the report design, it means the report is always formatted with that locale. The view time locale won't changes the format of the report. If the locale is not defined, view time locale is used to format the report.

The user can override the settings in the data item's locale setting. The data item's locale setting can be:

a. auto: the report design's locale or view time locale if the report design's locale is empty.
b. locale. The locale used to format the data. In this case, the design local or the view time local is not used.
c. view time locale. In this time,the view time locale is used.

If we accept this solution, the user can easy to create the report design as:

1. a localized report design. The DESIGNER's locale is used automatically. Such kind of reports have same output in different locales. I think most of the reports belongs to this catalog.

2. a i18n report design. The user should left the report design's locale to empty and view time locale is used.


Comment 16 Chen Chao CLA 2009-03-19 05:35:40 EDT
Fixed the GUI part.
Comment 17 Chen Chao CLA 2009-04-08 22:36:37 EDT
Reassign to the engine team.
Comment 18 Haojun Chu CLA 2009-04-17 03:16:13 EDT
Fixed. Checked in on Apr 17.
Comment 19 Maggie Shen CLA 2009-04-23 03:01:25 EDT
verified on build 2.5.0 v20090422-0630. Issue in excel is logged as #273377.