Tests - Add translation test about glossary

[Gustry]

• Ticket : #20
• Add translation test about glossary

@mdouchin you wrote

use the new version of the function SELECT pgmetadata.get_dataset_item_html_content('{schema}', '{table}', '{locale}'); with a try / catch (and use the old one if the first failed SELECT pgmetadata.get_dataset_item_html_content('{schema}', '{table}');

If the language does not exist, the query is not failing @mdouchin, only the content is empty. So it does not make it easy to know if the language is supported for now.

What would be the behavior you wanted ?

[Gustry]

I think @mdouchin We should just always default to english if

• the language doesn't exist at all in PgMetadata
• the language exist in PgMetadata, but this particular glossary term does not exist for the requested language.

So we have a single query, even on the module side.

What do you think ?