i18n(zh-cn): translate about module

[GuoJikun]

Description

• What does this PR change? Give us a brief description.
• Closes #

[netlify]

✅ Deploy Preview for tauri-v2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f7eae11
🔍 Latest deploy log	https://app.netlify.com/sites/tauri-v2/deploys/674d65498717180008f8ee1c
😎 Deploy Preview	https://deploy-preview-3023--tauri-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (🔴 down 1 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

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

[GuoJikun]

I don't know what should be translated here.

Maybe you can explain it in English.

[FabianLars]

I don't know what should be translated here.
Maybe you can explain it in English.

No idea either 😂 The last part of that section isn't really correct anymore either (in the english source)

[GuoJikun]

The last part of that section isn't really correct anymore either (in the english source)

here?

[FabianLars]

No this part

Today, Tauri uses Rust for the backend - but in the not too distant future, other backends like Go, Nim, Python, Csharp, etc. will be possible. This is because we are maintaining the official Rust bindings to the webview organization and plan to let you switch out the backend for your needs. Since our API can be implemented in any language with C interop, full compliance is only a PR away.

We very likely won't completely switch out rust, but have the second backend "attached" to the rust one. Also, we're not the webview bindings maintainers anymore.