This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
I want to generate a script to automate the translations, but won't do it until I have practical answers to all these questions.
- how you want overrides to behave
the Folders are split into two levels....
en - the natural language.
en-GB - the regional language.
The design is that the natural langage has a full set of keys for all namespaces. the regional language will have overrides for that specific area.
For example "en-US" will have "Authorization" where "en" will have "Authorisation".
- how you want fallback chains to be enforced
Fallback chains are always xx-XX -> XX -> en
- whether you want machine‑generated placeholders
the en versions of the files should be considered as the master list and will always have a match, any machine generated values will be created based on that
- whether you want to preserve human edits
I would love for the human edits to be preserved. Or to put another way, for the en version of the files to be used as a source, then only the keys that are missing from the other files to have the detla changes in their language.
This way the whole file does not need to be regenerated every time.
- whether you want to detect missing keys, extra keys, or drift
I would want the code to do a pass of the en versions of the files and compare it to the rest of the source code, this will provide the master list of "keys"
If there are any values missing, these will need to be filled in before proceeding on to other languages.
For now, extra keys will be kept, but I may decide to change this in future, and archive them, so that they do not clutter up the production build.
The script will drop an empty .gitkeep file in to every folder (if not already present), so ensure that git will rentain the whole directory structure. The files are not used for anything else.
