-
Notifications
You must be signed in to change notification settings - Fork 290
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
[zh-CN/policies/security] Security reporting description not translated #1959
Comments
I think there are currently no trusted people available to review translations, which is why many translation issues are not addressed at the moment. |
I can understand to a certain extent. Returning to the current issue, as a newcomer to translation, I plan to cross use translation tools and manually polish them before create a PR. Do you think this is acceptable. |
Without somebody to review the PR, it won't be merged unfortunately. |
For potential PR, may fall into a dead cycle, if no "break". |
I don't understand this sentence, can you rephrase it? |
What I roughly mean is that for pull request,, no reviewer, more backlog, more issue, similar to the situation you mentioned earlier. Even so, I will create a PR and try to find somebody to review it. Because before create issue, i want to direct create PR, but i see
from I began to gradually understand the meaning of this sentence. |
It would have to be someone that already has some trust among project members, which might be difficult to find if we don't know someone like that ourselves.
Yeah, the translations are just gonna remain the way they are right now, imperfections included. It's not optimal, but I don't see anything that can be done about it. |
Got it, thank you very much for your time. |
…e some wording Fixes rust-lang#1959
Page(s) Affected
What needs to be fixed?
[zh-CN/policies/security] Security reporting description not translated.
Suggested Improvement
Add translation for security reporting description in zh-CN/policies/security.
The text was updated successfully, but these errors were encountered: