Suggestion：More Chinese documents.

[NMSAzulX]

A lot of the first-hand information is in English. Can the official translation team internationalize these documents?
e.g: https://github.com/dotnet/coreclr/blob/master/Documentation/design-docs/

There are many developers in China who like. Net Core. The common problem is that they can't understand the meaning of English documents. Suppressed by the JAVA market, we were forced to make a living. We can put up with everything, but we need more information about. Net Core, which is an important source of spiritual power. This topic is not initiated by me alone, in China,. Net ecological construction is a common topic for developers.

We have Microsoft China here, but we don't know what they're doing.
If there are political reasons, please let us know.

[NMSAzulX]

Is anyone here? Who can give me an answer or a plan? 🙁

[janvorli]

@richlander do you have any comment on this?

[MeiChin-Tsai]

@NMSAzulX, can you be more specific on which documents are of your interests? We don't internationalize our design documents as there are so many different languages to target.

We certainly can help answer questions.

[NMSAzulX]

@MeiChin-Tsai e.g: https://github.com/dotnet/coreclr/blob/master/Documentation/design-docs/unloadability.md#assemblyloadcontext-unloading-process
I don't know much about the unmanaged layer, even how the whole ALC works. It would be even better to add some nouns to the document.
This is just one of the things that puzzles me. In addition, I can be sure that there is no official plan to translate the design documents and not the lack of our suggestions.

[danmoseley]

cc @mairaw for thoughts (although this concerns in repo docs)

[huoyaoyuan]

I've submitted several changes to Chinese documentation/string resources, but the experience is not good for several reasons:

• The Microsoft localization team doesn't work on GitHub. There's no discussion on the docs.zh-cn repo. They just discuss at somewhere unavailable to me, then add a commit for final decision.
• The localization team is not familiar enough to the technology/context itself. There's often mis-translations for polysemous words.

I'd expect localizations of open source products are also done at open source locations.

[mairaw]

Sorry I missed the ping earlier.

Adding @JasonCard and @SonjaSaltzman to comment on the docs localization process and how decisions are made since it's not transparent to our users.
However, I do see issues enabled at https://github.com/dotnet/docs.zh-cn/issues.

Re. in repo docs:
I've seen those from time to time, and I think it's a bad habit we have.
I think that design docs are ok to be in English only. But once a feature is finalized and has customer value, we should consider adding docs to docs.microsoft.com and not here in the repo.

[danmoseley]

@JasonCard and @SonjaSaltzman for question above?

[JasonCard]

@danmosemsft We only localize content which is published to Microsoft Docs from https://github.com/dotnet/docs.
I agree with @mairaw that content valuable for customers should be moved to Microsoft Docs, so we can localize it for our international customers.
cc @SonjaSaltzman

[danmoseley]

@JasonCard do you have thoughts about this comment above:

The Microsoft localization team doesn't work on GitHub. There's no discussion on the docs.zh-cn repo. They just discuss at somewhere unavailable to me, then add a commit for final decision.

Perhaps this was a point in time problem?

[JasonCard]

@danmosemsft @huoyaoyuan Each suggestions on localized repos (e.g. docs.zh-cn) are reviewed by our localization vendor who work with their linguistic moderators to review the suggestions. Although we cannot share their internal communication on GitHub, if you have further feedback on the final decision (commit), then you are welcome to add comments and make further suggestions.

For feedback on mis-translation, please provide examples and link to the localized document, so we can look into it case-by-case. Please understand that we use Machine Translation (MT) on some content and there are limitations to MT quality, but we are actively working to improve our MT engine. Thank you and we always appreciate your feedback and suggestions.

Kind regards,
Microsoft DOCS International Team

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.