Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminoralways2006-11-23 16:502009-05-22 19:34
Reporteruser11View Statuspublic 
Assigned Toiciordia 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0003093: User level locale

DescriptionCurrently 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.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
2006-11-24 15:20
edited on: 2008-06-12 09:26

Logged In: YES
Originator: YES

See also people having problems with data formats: [^]

2005-06-01 00:00
edited on: 2008-06-12 09:43

This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in: [^]
pjuvara (reporter)
2008-06-16 16:33

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

- 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

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker