Enhancement
For some time now, the translation service DeepL has made it possible to define your own translation tables (glossaries) in order to achieve consistent naming for a subject area.
In the context of TopLogic, for example, "map" never means "map", but always "mapping".
Improvement
- A glossary can now be defined for generating I18N from code documentation.
- Glossaries stored at DeepL can be created and updated via the TopLogic Maven plugin.
- The in-app translation (for entering multilingual texts) can also use stored glossaries.
The example of the glossary for TopLogic:
- Entries are stored in /bos-deepl/glossaries/tl-en-en.tsv
- The glossary stored at DeepL is updated with mvn tl:upload-glossary@glossary
- For this, the plugin must be configured in the project (here bos-deepl) as follows:
#!xml <plugin> <groupId>com.top-logic</groupId> <artifactId>tl-maven-plugin</artifactId> <executions> <execution> <id>glossary</id> <goals> <goal>upload-glossary</goal> </goals> <configuration> <file>${project.basedir}/glossaries</file> </configuration> </execution> </executions> </plugin>
Test
- Make glossary entry
- Update glossary.
- Use term in I18N.
- Generate I18N.
- Check that glossary entry was used.