admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Locale -> Translation

Browse Source
This commit is contained in:
John Cardinal
2020-03-06 19:36:36 +00:00
parent 884c834b3d
commit a234b3531d
58 changed files with 540 additions and 569 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
devdocs/coding-standards.txt
View File

@@ -12,7 +12,7 @@ Error messages / Numbers
- Look for English text in all the messages so far and see if can be localized even crudely by google translate and do so
- Make sure error numbers have a consistent system and don't conflict, I think there are two sets of error numbers, there should only be one
- Make sure Every error has a number and that is documented in the manual
- Locale keys for error numbers?? i.e. E1000, "blah blah error 1000"
- Translation keys for error numbers?? i.e. E1000, "blah blah error 1000"
C# code convention:
All names are PascalCaseOnly with the following two exceptions:
@@ -24,8 +24,8 @@ C# code convention:
DATES, TIMES, TIMESTAMPS - All dates and times sent or retrieved from the REST interface must be in UTC / GMT time zone.
It is the client's responsibility to display and accept dates in local format but interaction with the server is in UTC only.
Localized text - All text prsented by the server will be a locale key only and it is the clients responsibility to display in local text format with the exception of:
- Ops logs, Metrics, event logs: these items and any other future pre-generated text items will be localized at the server according to the logged in users' locale
Localized text - All text prsented by the server will be a translation key only and it is the clients responsibility to display in local text format with the exception of:
- Ops logs, Metrics, event logs: these items and any other future pre-generated text items will be localized at the server according to the logged in users' translation
JAVASCRIPT