Windows-itpro-docs: [LOC] Back-Translation "タイムアウト エラー" → "TIME OUT ERRORS"

[hyoshioka0128]

https://docs.microsoft.com/ja-jp/windows/deployment/update/windows-update-errors

---

ドキュメントの詳細

⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

• ID: 1cb9f2a2-76ad-8301-7d80-e33a7bb80a1b
• Version Independent ID: dd070c32-53d5-53d6-7ba2-a4361b5263bb
• Content: Windows Update の一般的なエラーと軽減策
• Content Source: windows/deployment/update/windows-update-errors.md
• Product: w10
• Technology: windows
• GitHub Login: @kaushika-msft
• Microsoft Alias: elizapo

[e0i]

@officedocsbot assign @e0i
@officedocsbot assign @dongmicro
@officedocsbot add label localization

[e0i]

@dongmicro Looks like a message handle corresponding to an error ID that is not supposed to be translated has been translated. Would you review and advise in resolution of this issue? Thanks.

[hyoshioka0128]

https://docs.microsoft.com/ja-jp/windows/deployment/update/windows-update-errors

[e0i]

@officedocsbot assign @MollyMalone

[e0i]

@officedocsbot unassign @MollyMalone
@officedocsbot assign @TinaMcN

[e0i]

@officedocsbot unassign @dongmicro

[TinaMcN]

This issue now appears to be fixed. @hyoshioka0128 can you please confirm and close?

[TinaMcN]

@e0i I think this is an issue with the English source content. I believe "TIME OUT ERRORS" should be changed to "TIME_OUT_Errors" i.e. include "_" between the words. The MT tool is over-translating the terms as a result. Can you fix the English source?

[hyoshioka0128]

Hi, @TinaMcN. (I'm poor English.)

3597 ("ERROR_INVALID_DATA") is Fixed.

3595 ("TIME OUT ERRORS") is not Fixed.

Thank you.

[TinaMcN]

Hi Hiroshi-san, thank you for confirming (ありがとうございました). We will wait for @e0i to hopefully fix the English "TIME OUT ERRORS).

[TinaMcN]

@e0i This is still not fixed in the English or Japanese content. Please change TIME OUT ERRORS to TIME_OUT_ERRORS.

[illfated]

@TinaMcN : This issue ticket was automatically closed upon merging the PR from e0i -- but I presume you find it to be a little bit too soon, given the time it takes before the change migrates from its Github source to docs.microsoft.com and the translated pages. I agree, we should wait to see the final results before closing the ticket.

[TinaMcN]

@illfated thank you, it's true that we probably shouldn't close the ticket until the fixes are verifiable on the live content.

[illfated]

Looks like the solution has migrated to the live page now, so our reflection on the workflow timing has become purely academic. 😉

[TinaMcN]

@illfated Thank you! I see that it is fixed on the Japanese page.

[illfated]

Yes, both the en-us and ja-jp pages are updated, so thank you to @e0i for the solution.

• https://docs.microsoft.com/ja-jp/windows/deployment/update/windows-update-errors
• https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-errors