Closed martindholmes closed 6 years ago
Currently this is done by creating string variables in the hol.Utils namespace. But a better approach would be to create a single object with child objects whose keys are language designations (per BCP47), which then contain string members. The startup code could then find the first applicable [xml:]lang attribute from the map upwards, and assign the appropriate member to a property of the hol.VectorLayer instance, which would then use it. When ES6 modules are fully supported, the object could be spun off into a module for easier editing.
Created an object indexed by language in commit 08ee692.
Closing this for now; we're pretty far along with it, until we have someone who can actually do a translation for us.
This obviously needs to be done; all sorts of captions etc. are embedded in the JS directly. Options are:
These captions will have to be properties of the holMap object in the JSON.