Skip to content

[WiP] Init Vanilla'ish Tatar Translation.#898

Draft
Amirhan-Taipovjan-Greatest-I wants to merge 5 commits intoPlayPro:masterfrom
Amirhan-Taipovjan-Greatest-I:patch-1
Draft

[WiP] Init Vanilla'ish Tatar Translation.#898
Amirhan-Taipovjan-Greatest-I wants to merge 5 commits intoPlayPro:masterfrom
Amirhan-Taipovjan-Greatest-I:patch-1

Conversation

@Amirhan-Taipovjan-Greatest-I
Copy link
Copy Markdown

@Amirhan-Taipovjan-Greatest-I Amirhan-Taipovjan-Greatest-I commented May 5, 2026

@netlify
Copy link
Copy Markdown

netlify Bot commented May 5, 2026

Deploy Preview for coreprotect ready!

Name Link
🔨 Latest commit 20d2e96
🔍 Latest deploy log https://app.netlify.com/projects/coreprotect/deploys/69fa4e0f704e770008778947
😎 Deploy Preview https://deploy-preview-898--coreprotect.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Intelli Intelli added the invalid label May 5, 2026
@Intelli
Copy link
Copy Markdown
Contributor

Intelli commented May 5, 2026

Tatar can be specified in config.yml per https://docs.coreprotect.net/languages/

If changes are needed, you should make them on top of that existing translation.

@Amirhan-Taipovjan-Greatest-I
Copy link
Copy Markdown
Author

Amirhan-Taipovjan-Greatest-I commented May 5, 2026

Tatar can be specified in config.yml per https://docs.coreprotect.net/languages/

If changes are needed, you should make them on top of that existing translation.

I don't actually like the Machine Translation because of its poor Quality*, so I wanted to suggest My Translations.
Will it become a Valid?

*:

  1. Ok... it uses "Unwitnessed" Past while Vanilla Translations use "Witnessed" for such Cases. Probably not a big Deal in My Language, but still is not good.
  2. Ok... it uses not a good Sentence Ordering... or at least for Keeping that Ordering it should be with the additional Punctuation. Not nice looking, but in some Cases (where Variables are not being involved by the Way) it gets too ridiculous!!!
  3. Ok... Every Word Gets Capitalized. Not a nice Thing for My Language, but practically it doesn't matter too much.
  4. Also not a practical Issue, but an Aesthetic One: Consistency with the Vanilla Game Translations.

Thank Google that the Quality is not too poor, but it is still poor enough to make Me "stand up" and translate it better.

@Intelli
Copy link
Copy Markdown
Contributor

Intelli commented May 6, 2026

You can improve the default translation, but you presently have your tt.yml file as using the English base translations, rather than the Tatar translations, which means we can’t easily see the actual changes you’re making.

So you first need to set the tt.yml file to use the current actual Tatar translations, and then start making improvements to that file.

@Amirhan-Taipovjan-Greatest-I
Copy link
Copy Markdown
Author

Amirhan-Taipovjan-Greatest-I commented May 6, 2026

You can improve the default translation, but you presently have your tt.yml file as using the English base translations, rather than the Tatar translations, which means we can’t easily see the actual changes you’re making.

So you first need to set the tt.yml file to use the current actual Tatar translations, and then start making improvements to that file.

Yeah, I see. But I preferred and after looking up the Auto-Translated File I still prefer to start from Scratch because it seems easier than using Machine Translated File as a Base.

@Intelli Intelli removed the invalid label May 6, 2026
@Intelli
Copy link
Copy Markdown
Contributor

Intelli commented May 6, 2026

Fixed your base file. You can now re-implement your changes.

I.e.
20d2e96
51499eb
42cbfa2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[INIT] CoreProtect (a Minecraft Plugin).

2 participants