You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #971 (and ili2db 5.2.0), MB has support for translated models.
For an imported translated model, we'll have the original model and the translated model languages available.
We need to know whether for an already imported translated model, we should have language selection or not when building the QGIS project. If that's the case, we could select the translated model language by default.
For that, we need to get both the model language and whether the model is a translation of another model (possible after claeis/ili2db@e437949).
We also need to have somewhere available the list of models that were imported in the schema import operation. This one I'm still unsure that we have it available.
Before implementing something in this respect, let's agree on what would be needed/desirable.
The text was updated successfully, but these errors were encountered:
With this opengisch/QgisModelBakerLibrary#117 we already have a solution, but it would be preferable to have a more proper solution like suggested, because it's much more future proof.
signedav
changed the title
Clarify how to deal with available languages for translated models
Translation Models: how to deal with available languages on project generation
Nov 6, 2024
Since #971 (and ili2db 5.2.0), MB has support for translated models.
For an imported translated model, we'll have the original model and the translated model languages available.
We need to know whether for an already imported translated model, we should have language selection or not when building the QGIS project. If that's the case, we could select the translated model language by default.
For that, we need to get both the model language and whether the model is a translation of another model (possible after claeis/ili2db@e437949).
We also need to have somewhere available the list of models that were imported in the schema import operation. This one I'm still unsure that we have it available.
Before implementing something in this respect, let's agree on what would be needed/desirable.
The text was updated successfully, but these errors were encountered: