Preparation of migrating Drupal UI localization into Translation Memory

This project is not a regular module or theme for Drupal. Instead, it's special purpose is to provide further contexts of UI strings helping translators working on localize.drupal.org.

---

With more grouping options available we can prepare easier for integration with/migration into a Translation Memory (TM) tool hopefully happening in the future. For more details of this initiative please read the documentation explaining all the background.

Sister modules

By some technical reasons a single project was not enough to bring multiple sorting options onto localize.drupal.org, so a couple of other "fake modules" were registered as well:

• l10n_terminology_short for the one-word long strings of terminology
• l10n_terminology_long for the multiple words long strings of terminology
• …and possible some others may come in the future.

Task #1. – Portable glossary generation

As a first endeavor the initial goal is to get Drupal's terminology in shape to be able of export, transform, convert, import, and so on. Preparing such a glossary based on multiple locales' collection found available is done by adding already existing strings to versioned releases of these modules. This way translators are able to filter to strings consisting of single and double words. Translations filtered this way become exportable .po files which can be converted into the industry-standard .tbx file format finally. For more details about this process please read this docs page.

Further plans (aka. Roadmap)

• Try to tame the chaos of UI string contexts
• Do something about reducing the very similar UI strings
• Provide all the contrib project names as a separate filtering option as well
• So many plans for such a short freetime…