Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0003093 | Openbravo ERP | A. Platform | public | 2006-11-23 16:50 | 2009-05-22 19:34 |
|
Reporter | user11 | |
Assigned To | iciordia | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0003093: User level locale |
Description | Currently the local is set for the system and all users have the same locale (numbering and date formats). For SaaS this is not a valid option. |
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | ReleaseCandidate |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2008-06-16 16:33 | pjuvara | Note Added: 0007742 | |
2008-06-16 16:33 | pjuvara | Status | new => acknowledged |
2008-06-16 16:33 | pjuvara | Summary | Locale information should be configurable for every user => User level locale |
2008-06-16 16:33 | pjuvara | Description Updated | |
2008-06-16 16:33 | pjuvara | Tag Attached: ReleaseCandidate | |
2008-06-23 17:31 | pjuvara | Category | C. Security => A. Platform (WAD, XmlEngine, SQLC) |
2008-11-16 07:44 | pjuvara | Assigned To | iciordia => pjuvara |
2009-05-22 19:34 | pjuvara | Assigned To | pjuvara => iciordia |
Notes |
|
(0006682)
|
user71
|
2005-06-01 00:00
(edited on: 2008-06-12 09:43) |
|
|
|
(0003760)
|
user11
|
2006-11-24 15:20
(edited on: 2008-06-12 09:26) |
|
|
|
|
Hi folks,
Right now the decimal and hundred separators are hardcoded in XmlEngine.
In complex systems like operating systems we usually have:
- Locale information (also called regional settings).
- Language translations of the user interface.
Think of the following scenarios:
a) You have a central OB server with users operating from different countries (international offices). A user from the American office expects the "." as decimal separator and a user from the French office expects the ",".
b) A user may be based in Spain works with a Spanish locale but using the English translation.
There are a few approaches to fix this:
a) We use the locale settings for a region when a user logs in with its language (locale settings and translations work as a single unit).
b) We set the locale settings per server
c) We allow users to set their language and the locale that they want to work with.
I'm in favour of option C.
We should take into account the number formatting, date formatting and probably currency.
Jordi Mas
jmas@openbravo.com
|
|