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

MLGT-General: Inconsistent behavior for "Entry Status" and "Term Classification" #1

Open
ronaldtse opened this issue Dec 17, 2018 · 5 comments
Labels
translated content Related to content issues in the MLGT

Comments

@ronaldtse
Copy link
Contributor

In these languages, the operational language is used for these two fields:

  • Spanish
  • Russian
  • Finnish
  • Chinese

In all other languages, English is used for the representation of these values.

e.g.
"Entry Status [OPERATING LANGUAGE]
Data Type:
Must be one of 'notválido' 'válido' 'superseded' 'retired'."

"Term Clasification [OPERATING LANGUAGE]

Data Type: Character String
Must be one of the following: 'preferente', 'admitido', 'deprecated'"
"

(And there's a typo for "Clasification" for all sheets).

Strongly suggest we only use English for these status values.

@ronaldtse ronaldtse added the bug label Dec 17, 2018
@ronaldtse
Copy link
Contributor Author

The consequence of this is that the "Entry Status" and "Term Classification" fields are wrong for these 4 languages. We could fix the parsing, but the Excel sheet will still be inconsistent.

@ReesePlews
Copy link
Contributor

ReesePlews commented Dec 18, 2018 via email

@ronaldtse
Copy link
Contributor Author

Agree, will wait for the outcome of the MLGT discussions!

@ronaldtse
Copy link
Contributor Author

@ReesePlews is it possible to change the localized values (e.g. Spanish 'notválido' 'válido' 'superseded' 'retired') to English for these entries in the next issue of the MLGT?

Thanks!

@ronaldtse
Copy link
Contributor Author

I've found the following inconsistencies in the MLGT, and have updated the code to reflect to the best of my knowledge.

————
Entry Status
Data Type must be one of
‘notValid’, ‘valid’, ‘superseded’, 'retired’.

Russian

действующий => valid
информация отсутствует => Google Translate says it means “information absent”. What state is this?
(more information: https://context.reverso.net/translation/russian-english/информация+отсутствует)

—————
Term Classification
Data Type must be one of the following
‘preferred’, ‘admitted’, 'deprecated'

Finnish
suositettava => Recommended
suositeltava => Recommended

There’s no superseded or retired? Are these two terms equivalent?

Spanish

adminitido => “Administered”? What does this mean?
admitido => “Admitted"

@ronaldtse ronaldtse changed the title Inconsistent behavior for "Entry Status" and "Term Classification" MLGT: Inconsistent behavior for "Entry Status" and "Term Classification" Aug 11, 2019
@ronaldtse ronaldtse added the translated content Related to content issues in the MLGT label Aug 11, 2019
@ReesePlews ReesePlews removed the bug label Aug 11, 2019
@ReesePlews ReesePlews changed the title MLGT: Inconsistent behavior for "Entry Status" and "Term Classification" MLGT-General: Inconsistent behavior for "Entry Status" and "Term Classification" Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
translated content Related to content issues in the MLGT
Projects
None yet
Development

No branches or pull requests

2 participants