-
Notifications
You must be signed in to change notification settings - Fork 41
About i18n #14
Comments
I found that this is not compatible with google's Specifically, Its #: src/SUMMARY.md:3
msgid "README"
msgstr "README"
#: src/SUMMARY.md:7
msgid "ZKP 新手村入门攻略"
msgstr "ZKP Newbie Village Getting Started Guide"
#: src/SUMMARY.md:11 src/zkp-intro/toc.md:3
msgid "探索零知识证明系列"
msgstr "Explore the zero-knowledge proof series"
#: src/SUMMARY.md:12
msgid "(一)初识「零知识」与「证明」"
msgstr "(1) First introduction to \"zero knowledge\" and \"proof\""
#: src/SUMMARY.md:13
msgid "(二)理解「模拟」"
msgstr "(2) Understanding “simulation”"
#: src/SUMMARY.md:14
msgid "(三)寻找「知识」"
msgstr "(3) Looking for “knowledge”"
#: src/SUMMARY.md:15
msgid "(四)随机「挑战」"
msgstr "(4) Random \"Challenge\""
#: src/SUMMARY.md:16
msgid "(五)埋藏「秘密」"
msgstr "(5) Burying “secrets”"
#: src/SUMMARY.md:20
msgid "理解Plonk系列"
msgstr "Understanding the Plonk Series" You can see that the gettext and .po file design pattern eliminates the need for additional Each time we perform a Build & Deploy, the system automatically searches for matches and generates the corresponding content in the /en directory based on the |
I'm thinking that in the coming week (perhaps by the weekend), it would be best to first experiment with auxiliary translation repositories using the gettext and .po file design pattern: If these repositories don't work as expected or if the results aren't satisfactory, then we can consider making adjustments based on the 'About i18' approach. It might require some additional frontend hackings. 🤣 r12f/potr#7 Translation speed is too slow.... |
The issue-based communication pattern is excellent !!
|
WeChat is all the exact opposite, that's why I hate it. |
使用 GitHub Actions 和 ChatGPT,将仓库里面的 Markdown 文件翻译成其他语言,适合制作网站的国际化版本。
@Demian101
The text was updated successfully, but these errors were encountered: