Fixed Japanese translations for messages 1259, 2556, 2620, 2621, 2706, and 18046#62120
Conversation
|
These files are maintained by our localization team and can't really be updated externally (they push them here). I don't think we can accept this PR. |
|
I'm disappointed to hear that, as I submitted this PR because issue #53337 has a "Help Wanted" label. I understand you can't accept this PR, but I hope the incorrect translations can still be fixed. Messages 2620, 2621, and 2706 have meanings that are opposite to what they should be. How can I help get these corrected? |
|
Sorry for the incorrect tag on that one, I missed something there. I'll try to track down who is in charge of the loc files these days. |
|
@RyanCavanaugh |
|
With 6.0 out as the final release vehicle for this codebase, we're closing all PRs that don't fit the merge criteria for post-6.0 patches. If you think this was a mistake and this PR fits the post-6.0 patch criteria, please post to the 6.0 iteration issue with details (specifically, which PR and which patch criteria it satisfies). Next steps for PRs:
|
Fixes #53337
Testing
I did not add unit tests for this change because:
/path/to/TypeScript/built/local/tsc.js --locale jalocally and confirmed that the expected error messages are displayed correctlyThe change is a straightforward localization fix that aligns the Japanese error message with the English version, and manual testing confirms the expected behavior.