Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
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.