specify and design a localisation ui / process for multilingual sea-map

[wu-lee]

No description provided.

[ColmDC]

Is there any reason for this not be for LX too?

[ColmDC]

Lynne recommends https://www.transifex.com/ - used by Open Food Network

[wu-lee]

Lynne recommends https://www.transifex.com/ - used by Open Food Network

That seems to be a service? Might be useful - hard to get a handle on exactly what it does from a quick skim. @lin-d-hop

This issue is pretty old, and totally under-specced but I it might be more intended for supporting a multilingual UI better. Currently the UI supports more than one language but it's entirely hardwired. It should be able to be referred to external translation tables.

One idea I was thinking that would work with existing code is to use the same Vocab tables we use for taxonomies. These support multiple and arbitrary languages.

I'm not sure how LX does multilingual text, if at all. Even if it did, the phrases needed for the UI would likely be entirely different. Possibly it would use the same vocabs we do in MykoMap - but AIUI it doesn't use vocabs at all.

[wu-lee]

For recent maps I've actually used vocabs for multilingual UI support - but it can currently only be done in the pop-ups, which allow (mandate!) custom code.

To support this I created a script to convert a spreadsheet with UI term IDs and the translations in an arbitrary number of languages back into a vocab file that MM can use.

What needs to be done is to make the whole UI use a vocab table instead of the hard-wired table it currently uses. then the MM UI will be fully multilingual, allowing custom languages to be added per-site.