Files
meeting-room/frontend/node_modules/axe-core/locales
flying-hero 96f6318101 📦 添加虚拟环境和启动脚本
新增:
- backend/venv/ - Python 虚拟环境
- backend/start.sh - 启动脚本(使用虚拟环境)
- backend/requirements.txt - 依赖列表
- .gitignore - 忽略虚拟环境和缓存文件

说明:
- 每个项目使用独立虚拟环境
- 避免依赖冲突
- 启动脚本自动创建和激活虚拟环境
2026-04-04 18:29:02 +08:00
..
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00
2026-04-04 18:29:02 +08:00

Localizations

We welcome any localization for axe-core. For details on how to contribute, see the Contributing section of the main README. For details on the message syntax, see Check Message Template.

To create a new translation for axe, start by running grunt translate --lang=<langcode>. This will create a JSON file with the default English text in it for you to translate. Alternatively, you could copy _template.json.

To update an existing translation file, re-run grunt translate --lang=<langcode>. This will add new messages used in English and remove messages that are no longer used in English.

_template.json is a generated file which is created every time axe is built. It's compiled using each rule's description and help properties, as well as each check's metadata.messages property. To update the _template.json file you'll need to update the corresponding rule or check metadata file and rebuild.