Dependent upon: #71, #72, #73, #74, #75, #76, #77, #78, #79, #80, #81, #82, #83, #84, #85, #86, #87
Pulling language/script combinations from the PloneLanguageTool for use in, e.g., GeographicNameLite has proved problematic. It now seems best not to entangle these two functions. So, we need a separate tool for managing this, preferably with scope for realizations of the language/script names in multiple modern languages for locale-specific presentation via, e.g., LinguaPlone. Moreover, ATVocabularyManager (which we were considering using for, e.g., GeographicEntityTypeThesaurus), has alot of overhead related to its support for VDEX. Though we intend to use VDEX for our core vocabularies, the way ATVM handles them is clunky. Given these factors, we're building our own portal tool: PleiadesThesauri
