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

Util.Texts not really Multilingual #8

Open
alxdean opened this issue May 12, 2020 · 0 comments
Open

Util.Texts not really Multilingual #8

alxdean opened this issue May 12, 2020 · 0 comments

Comments

@alxdean
Copy link

alxdean commented May 12, 2020

Hi Folks,
I wanted to test a Real World Multi Lingual setup and found that the Util.Texts Table has a major design flaw. While it provides the ISOLANGUAGE field, it is not part of the key. and the unique key is only the TextID.

in the real world the data would look like this:
TEXTID;LANGUAGE;ISOLANGUAGE;TEXT
1000000001;E;en;Notebook Basic 15
1000000001;S;es;Nota libro basico 15

so the same ID has two entries, one for each language. But your Schema won't allow for it. so effectively the fields Language and ISOLanguage are useless right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant