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

MLCP localization problem #61

Closed
qcz opened this issue Feb 15, 2019 · 4 comments
Closed

MLCP localization problem #61

qcz opened this issue Feb 15, 2019 · 4 comments
Assignees

Comments

@qcz
Copy link
Contributor

qcz commented Feb 15, 2019

I've tried to continue to localize VS Code to Hungarian on the new MLCP site. I got over the fact that this platform is sub par in every possible aspect as a localization tool compared to Transifex: no easy way to view already localized strings, search for text and expressions in the full localized and non-localized sources, no sub groups, no information about who the translation comes from, and no information about which source file this text comes from exactly (which helped me many times when it was not clear what the expression exactly meant from the entry itself). These in themselves makes localization hard, and "community" localization more harder. It looks like that translating JSON files would be more productive than using the site itself 😞.

However the current problem I face looks like a full showstopper. It seems that I cannot add a suggestion to a text which already has a suggestion:
firefox_2019-02-15_15-17-47
When I try to add it, a suggestion the button is disabled. Only one suggestion is allowed per entry? If so, I cannot continue to localize VS Code as the Hungarian language is full of sub par and wrong suggestions. (For example the entry in the screenshot makes no sense and does not use the already established translation for Activity Bar used everywhere.) Asking to remove every suggestion via GitHub issues would be very time consuming and it would remove the joy of the translation ifself...

@qcz
Copy link
Contributor Author

qcz commented Feb 22, 2019

@janbaltus, @shawndon: The radio silence is worrying. Should I just translate JSON files and send PRs or should I forget any meaningful localization?

@janbaltus
Copy link
Contributor

Please do not translate json directly. It would be overwritten by MLCP next export.
For Tool Feedback @shawndon please.

@janbaltus
Copy link
Contributor

regarding the Suggestion to add it is possible and I tried just now to add third suggestion to string.
In some browsers submit button do not work correctly please try Ctrl+Right arrow for submit.
If you still face this issue please make a screenshot of error message from the top of the page.

@shawndon
Copy link
Contributor

@qcz Thank you very much for your feedback on the MLCP service. Some of the points you mention have already raised internally, but getting this feedback from the actual users helps to validate the usage scenarios and the asks. We will log these requests and issues, which will be prioritized by our developer/engineering team.

This migration cannot be reverted, but we hope it will not be completely blocking. While we improve MLCP (thanks to customer feedback), stay tuned for further developments on this and thank you again for your support to the Visual Studio community.

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

3 participants