ayanova/devdocs/test protocol.txt

@@ -22,7 +22,7 @@ Test protocol for latest build:
 		- RESULTS: I would say leave all in as they each will display somethign useful on different platforms.
 
 	-  TIME INPUT UTC HONOURED? Date time input fucked: 
-		- Selected 420 in the widget edit form but it shows as 11:20 on the main list, localization time issue
+		- Selected 420 in the widget edit form but it shows as 11:20 on the main list, translation time issue
 		- Retest on desktop, probably a general date time conversion bug	
 		
 	- 404 WORKS ON ALL DEVICES DISPLAYS PROPERLY
@@ -43,7 +43,7 @@ EDGE desktop
 
 =-=-=-=-=- OLD STUFF =-=-=-=-
 - does it update automatically
-- No localization bugs
+- No translation bugs
 	- Login as different translation users and confirm no ?? showing
 - Menu
 	- surfaces properly given size changes
@@ -64,7 +64,7 @@ EDGE desktop
 - Navigate via menu then press back goes back to last form properly?
 	- About then back to form or main inventory home etc
 - Widget form
-	- Localization showing properly on form
+	- translation showing properly on form
 	- Numeric inputs show numeric keyboard on mobile
 	- Calendar selects date and time or is that still fucky on some platforms?
 	- Rights work properly

ayanova/devdocs/todo.txt

@@ -100,7 +100,7 @@ todo: TIME ZONE MISMATCH MESSAGE
 		- This way user knows it's happened and does it on purpose when appropriate
 		- Or user can ignore it and just keep working in their chosen time zone but will be aware it's an issue
 		- It may need a logout and back in unless it can just set the local setting which I guess it can, be aware of that anyway
-	- Time zone mismatch message sb localized and far shorter
+	- Time zone mismatch message sb translated and far shorter
 
 todo: Workorder/quote/pm templates (MENU ITEM)
 	- Put the link to access them into their own type, i.e. Workorder templates are accessed from either the grid listing workorders or inside an individual or perhaps BEST IDEA in the NEW menu where you pick a template !!!!!
@@ -143,7 +143,7 @@ todo: REPORT LIST
 		- One idea I just had is maybe the last report used for that form is surfaced on the context menu in addition to the regular reporting option
 		- If take last report used then it directly opens a preview
 		- If take generic Report option then it opens to another form for choosing the report and whether to print or not etc
-	- SB localized in form as "Report" not "Print" because it's going to be likely that people will want to work with pdf (email, download) instead or just the view of it, print is maybe not a common option.
+	- SB translated in form as "Report" not "Print" because it's going to be likely that people will want to work with pdf (email, download) instead or just the view of it, print is maybe not a common option.
 
 todo: WIDGET EDIT FORM SAVE AND NEW BUTTON LIKE V7?
 	- NO, just keeping this until I get here in case I think I need it again, don't need it.
@@ -267,9 +267,9 @@ todo: INVESTIGATE - Dark mode / theming (dark with a half moon icon)
 
 #translation stuff
 
-todo: LOCALIZATION form
-	- Dedicated area for localization adjustments
-	- Going to be a central form for all localization not form by form
+todo: translation form
+	- Dedicated area for translation adjustments
+	- Going to be a central form for all translation not form by form
 	- Review the spec doc and the cases regarding this as there are some little touches that were requested and make sense related to search and replace and other things.
 
 
@@ -348,7 +348,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
 
 - API get code is incorrectly dealing with expired bearer cert, a 401 is returned and it tries to parse the result as if it succeeded when it really should trigger a login process
 - Time zone offset mismatch warning needs expansion, it should only prompt a few times (maybe or find a way to deal with this) and it should offer to change it at the server automatically
-- Localize time zone mismatch warning
+- Translate time zone mismatch warning (PROBABLY NOT NOW)
 - Don't like popup messages, would rather see a notification icon and be part of that unless it's super critical
 	- Implement a toaster or some similar notification 
 
@@ -367,7 +367,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
     
 	    - Don't want to solve any problems that should have been solved with this form later as I will inevitably be full on copy and pasting once I get it down and so it needs to be as solid as possible First
 		- TEST SMALL and LARGE device layout regularly, don't get too far ahead of the testing
-        - Every type of entry field fully localized properly including numeric, date, time, tags etc			
+        - Every type of entry field fully translated properly including numeric, date, time, tags etc			
 			- Client: initialize after login sets translation formats for everything.
 				- Best to do this useroptions stuff after a form is in place that I can play with at the client and experiment to see what is possible
 				- How much flexibility do we have to set things like numeric / currency input / display format?		
@@ -381,10 +381,10 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
         - Error and validation properly implemented
 			- broken rule display 
         - Error reporting overall properly implemented
-			- ensure error messages that come back from API that start with LT: will be localized correctly before display / logging (may need string interpolation too for some in future, consider that)	
+			- ensure error messages that come back from API that start with LT: will be translated correctly before display / logging (may need string interpolation too for some in future, consider that)	
         - Validation / validation rules
 			- Vee validate and vuedelate both work tightly with vuetify and v-form
-			- Vee-validate can be localized
+			- Vee-validate can be translated
 			- https://baianat.github.io/vee-validate/guide/rules.html#after
 		- Dirty check and warning if navigate away.
 			- Dirty form check and prevent route leave: https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards
@@ -423,7 +423,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
 				- Override browser datetime with these settings instead (see below)
 					- One single date format string?  Or one for time, one for date and one for date/time? (see v7)
 						- Take from day.js (https://github.com/iamkun/dayjs/blob/master/docs/en/API-reference.md#list-of-all-available-formats)
-						- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid localization issues
+						- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid translation issues
 
 
 ......
@@ -455,8 +455,8 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
 	
 
 TESTING TODO
-Localized input and parsing and validation
-	- Going to need to handle localized numeric entry formats
+translated input and parsing and validation
+	- Going to need to handle translated numeric entry formats
 	- Deal with this once form is in good shape and worth testing with different translations
 -----------------
 
@@ -482,7 +482,7 @@ ABOUT form - add the  user settings such as timezone offset, translation formatt
 	- Look into: should each component do it's own ajax calls?	
 	- Make a widget component / form to view/list/enter/edit	
 	- Graph / Readonly UI component
-	- Widget: List, search, edit, localized WIDGET UI components
+	- Widget: List, search, edit, translated WIDGET UI components
 	- Post up another build with the entry form and re-round of testing
 		
 - Stage 2.5 TESTING