- Legal documents ## Application developer guide 通过国际化来开始 与 Weblate 集成 使用GNU gettext 来翻译软件 - 使用 Sphinx 翻译文档 - 使用 Weblate CDN 翻译 HTML 和 JavaScript - 翻译组件警告 - 构建翻译者社区 管理翻译 复查字符串 Weblate 基础知识 ## 项目和组件架构 在 Weblate 中，翻译组织成为项目和组件。每个项目可以包含几个组件，并且组件包含各个语言的翻译。组件相应于一个翻译文件（例如 GNU_gettext 或安卓字符串资源）。项目帮助您将组件组织为逻辑的组（例如，将一个应用中使用的所有翻译分组）。 默认情况下，每个项目内都有对跨组件传播的公共字符串的翻译。这减轻了重复和多版本翻译的负担。但假如 Customize download menu: • gettext PO • 带有 gettext 扩展的 XLIFF • XLIFF 1.1 • TermBase eXchange • 翻译记忆库交换 • gettext MO (only available when translation is using gettext PO) • CSV • Excel Open XML

translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical available, including a compiled file to use in your choice of application (for example .mo files for GNU Gettext) using the Files menu. ## Uploading translations When you have made your changes, use Upload translation 串通常会导致严重的问题，因此字符串中的格式通常应与源匹配。 Weblate 支持检查几种语言的格式字符串。仅当适当地标记了字符串时（例如，C 格式为 c-format），才会自动启用该检查。Gettext 会自动添加它，但是对于其他文件格式，或者如果您的 PO 文件不是由 xgettext 生成的，您可能必须手动添加它。 可以按单位（请参阅 Additional info on source strings）或在

They can be placed in up to 3 columns. #### 5.2.9 Translations managed by gettext Frontend translations are now managed by gettext. This means that standard tools like Pootle, Poedit or Virtaal can be used (--enable-sockets).| |mbstring||Required for user script support.| |gettext||php-mbstring (--enable-mbstring)| |ldap||php-gettext (--with-gettext)| |||php-ldap. Required only if LDAP authentication is used in English, you must generate translation files. To do so, run: locale/make_mo.sh msgfmt utility from gettext package is required. Note: Additionally, to use any other language than English, its locale should

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext MO (only available when

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext MO (only available when

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext MO (only available when

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available when translation is using gettext PO) • CSV

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available when translation is using gettext PO) • CSV

Starting with internationalization • Integrating with Weblate • Translating software using GNU gettext • Translating documentation using Sphinx • Translating HTML and JavaScript using Weblate CDN • translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext MO (only available when

monolingual formats ○ Automatic detection ○ Translation types capabilities ○ GNU Gettext ○ XLIFF ○ Java properties ○ Joomla translations ○ Qt Linguist .ts ○ other formats, including a compiled file to use within an application (for example .mo files for GNU Gettext) using the Files. ## Uploading translations You can upload translated files using the Upload translation not enabled automatically, only if a string is flagged appropriately (e.g. c-format for C format). Gettext adds this automatically, but you will probably have to add it manually for other file formats or