feat(theme-translations): translation for Uzbek (uz)

[Zukhrik]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[facebook-github-bot]

Hi @Zukhrik!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	25a8c59
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/64d615328eae2c0008de9aac
😎 Deploy Preview	https://deploy-preview-9209--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 74	🟢 97	🟢 92	🟢 100	🟠 89	Report
/docs/installation	🟠 71	🟢 100	🟢 92	🟢 100	🟠 89	Report

[Josh-Cena]

I wonder if we should have a threshold to limit the number of languages we have. I understand that every language is potentially useful to some users, but we need to weigh between out-of-the-box usefulness and the extra install size this brings to everyone, including the 99.9% of users that don't need it. Plus there's maintenance issues, quality control, etc.

@slorber WDYT?

[slorber]

Thanks

I can't be sure the translations are good but I notice errors on the plural forms.

Please read this part to understand how to handle plurals:
#3526

Uzbek only has 2 cardinal plural forms, according to

• this page: https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html
• the browser Intl API data

Thus, your pluralized translations should only contain 2 parts and not 3.

Also the placeholders should not be translated

[slorber]

I wonder if we should have a threshold to limit the number of languages we have. I understand that every language is potentially useful to some users, but we need to weigh between out-of-the-box usefulness and the extra install size this brings to everyone, including the 99.9% of users that don't need it. Plus there's maintenance issues, quality control, etc.

@slorber WDYT?

This probably does not increase install size that much IMHO. There are lower hanging fruits to consider, like inlining our dependencies like Next.js does, which as a much more significant impact. I don't think it's time to optimize this part yet, and the maintenance remains reasonable so far.