translate-po

Name: translate-po
Availability: InStock
Author: Python

Translate English PO entries into Traditional Chinese with project conventions.

282|224|Updated Jun 24, 2018

Search Tags:#documentation #localization #terminology #translate #po #zh_TW #reST

Ready to run

npx skills add https://github.com/python/python-docs-zh-tw --skill translate-po

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: translate-po
Source: https://github.com/python/python-docs-zh-tw/tree/main/.claude/skills/translate-po
Command: npx skills add https://github.com/python/python-docs-zh-tw --skill translate-po

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates PO file entries from English to Traditional Chinese (zh_TW) following project conventions. It is intended for translating new PO files or entries that are untranslated to ensure accurate and consistent localization.

Core Features & Use Cases

Terminology-driven translation: Uses references/terminology.md and glossary to maintain consistent terms across the project.
Context-aware translation: Considers msgid context, translator comments, and project-specific rules to preserve meaning.
reST and formatting preservation: Keeps reStructuredText directives intact and applies correct punctuation, spacing, and line width for PO files.
Use Case: Localize new documentation strings in a Python repository by producing zh_TW translations ready for QA and integration.

Quick Start

Translate the provided English PO file to Traditional Chinese using the required terminology references.

Frequently Asked Questions about translate-po

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I translate English PO entries to Traditional Chinese for Python documentation?▼

Translate English PO entries to Traditional Chinese (zh_TW) by applying Python project conventions. The process ensures context-aware terminology usage, proper reST handling, and enforces project rules and line-length constraints for PO tooling.

What is the best way to maintain terminology consistency when localizing PO files?▼

Maintain terminology consistency in PO files by using a terminology reference and glossary. This ensures accurate and consistent localization across the project while preserving the original meaning of the documentation strings.

How does reST formatting affect PO file translation into zh_TW?▼

reST formatting affects PO file translation by requiring directives to remain intact. Translating PO entries must preserve reStructuredText syntax while applying correct punctuation, spacing, and line width constraints specific to PO tooling.

Can I use this approach to translate new untranslated entries in a PO file?▼

Yes, you can translate new untranslated entries in a PO file. This approach is specifically intended for translating new PO files or entries that are untranslated to ensure accurate and consistent localization for Python projects.

Does translating Python documentation PO files require specific line-length constraints?▼

Yes, translating Python documentation PO files requires specific line-length constraints. The translation process enforces project rules and line-width constraints for PO tooling to ensure the localized output is ready for QA and integration.