Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation Models: how to deal with available languages on project generation #973

Open
gacarrillor opened this issue Oct 31, 2024 · 1 comment

Comments

@gacarrillor
Copy link
Collaborator

Since #971 (and ili2db 5.2.0), MB has support for translated models.

image

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.

@signedav
Copy link
Member

signedav commented Nov 6, 2024

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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants