Repository navigation
Replies: 1 comment
|
Based on the 'Community Translations & Localizations' section, you should publish the translation in your own repository ('agency-agents-it') and request to have it linked in the README document. Vedendo il paragrafo "Community Translations & Localizations" dovresti pubblicare la traduzione in un tuo repo "agency-agents-it" e chiedere che venga linkato nel documento README. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi! I've translated the whole roster into Italian and would like to know how you'd prefer to host it before opening any PR.
What exists
scripts/i18n/agent-names-it.json(Italianname/descriptionfor all 267 agents, same format asagent-names-zh.json),scripts/i18n/localize-agents-it.ps1+README-it.md,CONTRIBUTING_it.md,README_it.md, and one row in the "Community Translations" table. No agent file is touched.scripts/whose persona-section keywords (convert.sh,lint-agents.sh) also recognise Italian headings, so the OpenClaw SOUL/AGENTS split works. Checked: 267/267 convert;lint-agents.sh,check-divisions.shandcheck-tools.shpass.Question
Following your CONTRIBUTING (translations/bulk changes → discuss first) I'd suggest:
agency-agents-it) linked from the "Community Translations" table, like the other languages.Would that work for you, or would you rather have the translated agents in this repo (e.g. under
i18n/it/)? Happy to adapt.Thanks for the project!
All reactions