Translation: Simplified Chinese (partial)

[djyde]

The goal of this PR is to try to translate 100% into Chinese. I speparate different part to track the progress:

• Settings

  • General panel
  • Appearance panel
  • Actions panel
  • Integrations panel
  • Profile panel
  • Shortcusts panel
  • Wallet panel
  • Invitations panel
  • About panel

• Sidebar

  • words
  • context menu
  • Edit feed

• Articles list

  • words
  • context menu

• Entry content

• Discover

[vercel]

@djyde is attempting to deploy a commit to the RSS3 Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
follow	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 13, 2024 7:54am

[Innei]

@djyde

Thanks for the contribution.

One thing though, we need to split multiple namespaces to make the i18n module more maintainable.

For example

namespace - common is used to store common nouns verbs etc.
namespace - lang can be used to store language nouns.
Other things like setting can also be split into one namespace.

We don't want to manage all the i18n modules in a single file, as the file will be bloated and difficult to maintain.

[djyde]

@djyde

Thanks for the contribution.

One thing though, we need to split multiple namespaces to make the i18n module more maintainable.

For example

namespace - common is used to store common nouns verbs etc. namespace - lang can be used to store language nouns. Other things like setting can also be split into one namespace.

We don't want to manage all the i18n modules in a single file, as the file will be bloated and difficult to maintain.

I recommend maintain in one single file. Do you have some open source project example that I can learn how to maintain in seperate namespace?

[Innei]

@djyde
Thanks for the contribution.
One thing though, we need to split multiple namespaces to make the i18n module more maintainable.
For example
namespace - common is used to store common nouns verbs etc. namespace - lang can be used to store language nouns. Other things like setting can also be split into one namespace.
We don't want to manage all the i18n modules in a single file, as the file will be bloated and difficult to maintain.

I recommend maintain in one single file. Do you have some open source project example that I can learn how to maintain in seperate namespace?

Maybe vscode-loc?

https://github.com/microsoft/vscode-loc/blob/main/i18n/vscode-language-pack-cs/translations/extensions/ms-vscode.js-debug.i18n.json

[djyde]

@djyde
Thanks for the contribution.
One thing though, we need to split multiple namespaces to make the i18n module more maintainable.
For example
namespace - common is used to store common nouns verbs etc. namespace - lang can be used to store language nouns. Other things like setting can also be split into one namespace.
We don't want to manage all the i18n modules in a single file, as the file will be bloated and difficult to maintain.

I recommend maintain in one single file. Do you have some open source project example that I can learn how to maintain in seperate namespace?

Maybe vscode-loc?

https://github.com/microsoft/vscode-loc/blob/main/i18n/vscode-language-pack-cs/translations/extensions/ms-vscode.js-debug.i18n.json

Well. I still don't think it's a good practice. Separating to different files only increases maintainance cost. For example, I just need to translate one single file to get 100% trasnlation for the whole app to another language.

And if translations locate on different namespace, you always need to consider which namespace you should use with useTranslation(). Maybe sometime you need to even use more than one useTranslation() in a single component.

[Innei]

@djyde

For translation contributors or maintainers, it is indeed better to write all translations in the same file.

But imagine if a json has thousands of lines and there are many nested modules, and each developer maintains a different module. In the subsequent development, it is easy to have redundancy and code conflicts.

Or, the subsequent module deletion also becomes difficult.

Though I do agree with you very much.

But we need to break down into at least the following necessary namespaces:

• common - common translation resource
• app - used only in app
• external - only used in external pages
• lang provides translations for languages, e.g. original Name and names in the current language.

[Innei]

If you agree with this, I would move the root resource to namespaces/app

[Innei]

Also, for the sake of app loading speed, we don't load all the language resources. But by splitting the namespaces, we load the common resource for all languages, but not the others.

We only load the language-specific resource when necessary.

[djyde]

If you agree with this, I would move the root resource to namespaces/app

Sure. I will finish the rest of translation after your refactoring

[Innei]

@djyde I've refactored it and resolved the code conflicts

[djyde]

@dorival @Innei I've made the i18n key flat

[djyde]

@Innei Now all the translation is done except the "Wallet" setting panel (I don't have dev api server to test this page).

When the Wallet panel is done, I think we can rollout this PR

[Innei]

@djyde Can you provide the current cursor ai chat prompt? Thank you very much.

[djyde]

@djyde Can you provide the current cursor ai chat prompt? Thank you very much.

Open the component you want to translate, then cmd+l:

Notice that you need to at(@) the correct locale file

[Innei]

I've merged it first, I'll continue translating it later

[stuchilde]

Have all the content been translated?