This commit is contained in:
2020-02-05 19:43:41 +00:00
parent da4ed1da88
commit f42be58c85
3 changed files with 13 additions and 2 deletions

View File

@@ -6,4 +6,7 @@ REQUIREMENTS
- Client does *ALL* internationalization display locally, only exception is the server ops logs
- This saves bandwidth and hassle and leaves presentation to the client where it belongs (was a source of trouble in v7)
- User options contain the date, timezone and currency format for presentation purposes
- API data is in as neutral a format as possible, i.e. ISO whatever it is for dates and times, currency is just a number? (not going multicurrency?)
- API data is in as neutral a format as possible, i.e. ISO whatever it is for dates and times, currency is just a number? (not going multicurrency?)
CALENDARS
- Only the Gregorian calendar is supported

View File

@@ -24,10 +24,12 @@ The issue comes into play when you write your .NET Core code specifically using
*/
LOCALE has defaults for currency, date, time handling
CLIENT RESPONSIBILITIES FOR DATES AND TIME ZONES
- Send all datetime fields on records to the server in UTC
- Displayed dates and times are adjusted to user timezoneoffset
- Month, day of week name and am / pm designators come from localized text
CURRENCY
@@ -35,6 +37,6 @@ CURRENCY
- Displayed and accepted based on UserOption currency symbol
NUMBER
- Displayed and accepted based on userOptions numeric format (needs work)
- Displayed and accepted based on userOptions numeric format
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat

View File

@@ -18,6 +18,12 @@ namespace AyaNova.Models
public bool? Stock { get; set; }
public bool CjkIndex { get; set; }
//TODO: Defaults for user options locale settings:
// short date, short time formats
// currency symbol
//digit grouping separator symbol
//decimal symbol
//Relationship
//was this but..