Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Translation issues in new property page
See original GitHub issueVisual Studio Version: 16.9 Preview 4
Summary: Some translations (in Chinese) are inappropriate. Please review it and review them in other languages too.
‘unsafe’ is a keyword and should not be translated. It’s already mentioned in the English message.
Suggestion: 确定性输出 (Deterministic output)
Nullable is not suitable for property page users. They should be at least translations of “nullable types” or “nullable reference types”.
Translating “Any CPU” is OK but not so good for me.
Language order specific for Chinese. 将追加子文件夹到此路径 is more natural.
I don’t have a fork for this repo so not opening PR. Please also remind other language translators for similar issues.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@drewnoakes Internal tracking for me. These fixes are being returned via https://github.com/dotnet/project-system/pull/7072
@cristianosuzuki77 can you explain what the number 399008 refers to?