Glossary and translation memory tool

Now that this issue has been created, I'll try to recall my memories of that time to give you an overview of the topic.

1. I first published the results of my efforts in this blog post. At that time, I was mainly trying to break down the Drupal UI strings into smaller translation units (TU) by downloading filtered list pages from l.d.o and HTML parsing these pages. However, this regex-paved path is definitely not feasible.
2. Following an idea I had later, I started to manually collect the 1-word strings, so that at least one terminology could be exported from l.d.o and converted into a portable industry-standard format. This work will be done by l10n_tm → , two other sister projects include single-word and multi-word strings. While the list is far from complete, at least there are now tangible practical benefits for all Drupal compilers.

Since I am not sure how much scope the team plans to take on, I have left the description of this issue unchanged, leaving it at "TBD".

Also, I'm not fully aware of the project management taste of the team but probably would be easier to track the progress of these two different functionalities in separate issues:

• Glossary: a manually curated cross-locale canonical list of fundamental expressions and concepts (mostly but not only single words!). This feature seems more trivial to implement on l.d.o.
• Translation memory: an editorial tool where the user types in their human mind-based translation and the software corrects, suggests, and predicts the rest of the translation in real time. Considering the work efforts needed to invest into the development of such a software AND the long-time existing therefore more advanced UX solutions already available on the market implementing such a feature does not seem worth building on l.d.o (for me at least).