sveltia / sveltia-cms

Alternative to Netlify/Decap CMS. Fast, lightweight, Git-based headless CMS. Modern UX, first-class i18n support, open source & free. Made with Svelte.
MIT License
863 stars 43 forks source link

WIP: Add italian localization #71

Closed zanhk closed 10 months ago

zanhk commented 10 months ago

@kyoshino I will work on this tomorrow, if in the future you need to add more localization keys just put the english one and ping me.

zanhk commented 10 months ago

@kyoshino Can you connect the issue https://github.com/sveltia/sveltia-cms/issues/70? thanks

kyoshino commented 10 months ago

I really appreciate this, but it’s too early to start l10n. (The Japanese l10n exists because I’ve developed this CMS for my clients, who are mostly in Japan.)

Since many features are still missing, many strings will be added before 1.0, including many invisible labels for accessibility. I’ll keep #70 open and ping you early next year when the strings are better organized, polished, and more stable.

Actually, the string format may also change. The current library is svelte-i18n, but I’ll evaluate other options since it doesn’t even support singular/plural switches. Some locales are complicated — Fluent (created for Mozilla Firefox, svelte-fluent) might be a better choice.

Let me know if you have an opinion on Italian 🙂 (Japanese is too simple, there is mostly no plural form, gender, or whatever)

Edit: I’ve realized that the Fluent homepage has an Italian example, which shows a lowercase variant.

Edit: I think I’ll create my own Svelte wrapper for Fluent.js.

kyoshino commented 10 months ago

Tip: When you write “Fix #70”, “Close #70”, etc. in the pull request description, the PR and issue will be automatically linked, and the issue will be automatically closed when the PR is merged. 😺 See:

zanhk commented 10 months ago

I really appreciate this, but it’s too early to start l10n. (The Japanese l10n exists because I’ve developed this CMS for my clients, who are mostly in Japan.)

Since many features are still missing, many strings will be added before 1.0, including many invisible labels for accessibility. I’ll keep #70 open and ping you early next year when the strings are better organized, polished, and more stable.

Actually, the string format may also change. The current library is svelte-i18n, but I’ll evaluate other options since it doesn’t even support singular/plural switches. Some locales are complicated — Fluent (created for Mozilla Firefox, svelte-fluent) might be a better choice.

Let me know if you have an opinion on Italian 🙂 (Japanese is too simple, there is mostly no plural form, gender, or whatever)

Edit: I’ve realized that the Fluent homepage has an Italian example, which shows a lowercase variant.

Edit: I think I’ll create my own Svelte wrapper for Fluent.js.

Ok

kyoshino commented 10 months ago

I’ve added README for localizers 😅 You’re good as you’ve filed an issue!