-
-
Notifications
You must be signed in to change notification settings - Fork 62
Use fake language in our translation unit tests. #749
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
Comments
Translatewiki uses « qqq » for comments abour strings. Maybe you can reuse that code? |
qqq.json contains only descriptions of messages without placeholders for parameters that must be replaced in the real message. Thus using qqq pseudolanguage in the unit tests will not verify that parameters are properly set in the code. |
|
Or |
@mgautierfr @veloman-yunkan Can we go forward with |
@mgautierfr @veloman-yunkan please use artificial |
@veloman-yunkan Woukd be good if that one could be implemented. Seems straight forward. |
We need a fake language for tests that won't be affected by modifications made by 3rd party translators (see #749). - static/skin/i18n/hy.json was cloned as static/skin/i18n/test.json - usage of "hy" in unit-tests was replaced with "test"
We need a fake language for tests that won't be affected by modifications made by 3rd party translators (see #749). - static/i18n/hy.json was cloned as static/i18n/test.json - usage of "hy" in unit-tests was replaced with "test"
Following #679
The current tests on translation are based on Armenian language. But it is subject to translation made on translatewiki.
We should use a fake language we could use on test to be sure that translator will not break our tests.
The text was updated successfully, but these errors were encountered: