Ukrainian localisation

🔍 Search Terms

"Ukrainian" "localization"

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

To everyone's shame there is no Ukrainian localization of TypeScript.

I am willing to contribute the bulk of work, and adhere to any specific standard and practice to make it happen. Hope to help Microsoft not to spend much effort, and gain the good will.

If your internal tooling has some funky format that's OK, just give me a template for English or even say Spanish and I'll get Ukrainian back to you.

We can also arrange for a linguist professional to look over any concerns, questions and such.

📃 Motivating Example

There is a large body and community of Ukrainian software developers using TypeScript every day.

You'll gain tons of goodwill, and a positive branding from this.

💻 Use Cases

1. What do you want to use this for? -- Reduce friction of mental translation for the newcomers to TypeScript.
2. What shortcomings exist with current approaches? -- great approaches, just no Ukrainian locale.
3. What workarounds are you using in the meantime? -- English locale.

The issue names no files, tests, or entry points. Start by locating TypeScript's existing localization workflow and English or other locale templates, then determine the required translation format and validation process; done means a Ukrainian locale is integrated and its checks pass.