readthedocs.org/docs/locale/zh_CN/LC_MESSAGES/localization.po

125 lines
3.8 KiB
Plaintext

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2010-2018, Read the Docs, Inc & contributors
# This file is distributed under the same license as the Read the Docs package.
#
# Translators:
msgid ""
msgstr ""
"Project-Id-Version: readthedocs-docs\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-17 19:05-0500\n"
"PO-Revision-Date: 2018-09-18 00:14+0000\n"
"Last-Translator: Anthony <aj@ohess.org>\n"
"Language-Team: Chinese (China) (http://www.transifex.com/readthedocs/readthedocs-docs/language/zh_CN/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: zh_CN\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../localization.rst:2
msgid "Localization of Documentation"
msgstr ""
#: ../../localization.rst:4
msgid ""
"This feature only applies to Sphinx documentation. We are working to bring "
"it to our other documentation backends."
msgstr ""
#: ../../localization.rst:6
msgid ""
"Read the Docs supports hosting your docs in multiple languages. There are "
"two different things that we support:"
msgstr ""
#: ../../localization.rst:9
msgid "A single project written in another language"
msgstr ""
#: ../../localization.rst:10
msgid "A project with translations into multiple languages"
msgstr ""
#: ../../localization.rst:14
msgid "Single project in another language"
msgstr ""
#: ../../localization.rst:16
msgid ""
"It is easy to set the *Language* of your project. On the project *Admin* "
"page (or *Import* page), simply select your desired *Language* from the "
"dropdown. This will tell Read the Docs that your project is in the language."
" The language will be represented in the URL for your project."
msgstr ""
#: ../../localization.rst:22
msgid ""
"For example, a project that is in Spanish will have a default URL of "
"``/es/latest/`` instead of ``/en/latest/``."
msgstr ""
#: ../../localization.rst:25
msgid ""
"You must commit the ``.po`` files for Read the Docs to translate your "
"documentation."
msgstr ""
#: ../../localization.rst:28
msgid "Project with multiple translations"
msgstr ""
#: ../../localization.rst:30
msgid ""
"This situation is a bit more complicated. To support this, you will have one"
" parent project and a number of projects marked as translations of that "
"parent. Let's use ``phpmyadmin`` as an example."
msgstr ""
#: ../../localization.rst:35
msgid ""
"The main ``phpmyadmin`` project is the parent for all translations. Then you"
" must create a project for each translation, for example ``phpmyadmin-"
"spanish``. You will set the *Language* for ``phpmyadmin-spanish`` to "
"``Spanish``. In the parent projects *Translations* page, you will say that "
"``phpmyadmin-spanish`` is a translation for your project."
msgstr ""
#: ../../localization.rst:42
msgid "This has the results of serving:"
msgstr ""
#: ../../localization.rst:44
msgid "``phpmyadmin`` at ``http://phpmyadmin.readthedocs.io/en/latest/``"
msgstr ""
#: ../../localization.rst:45
msgid ""
"``phpmyadmin-spanish`` at ``http://phpmyadmin.readthedocs.io/es/latest/``"
msgstr ""
#: ../../localization.rst:47
msgid "It also gets included in the Read the Docs flyout:"
msgstr ""
#: ../../localization.rst:52
msgid ""
"The default language of a custom domain is determined by the language of the"
" parent project that the domain was configured on. See "
":doc:`alternate_domains` for more information."
msgstr ""
#: ../../localization.rst:56
msgid ""
"You can include multiple translations in the same repository, with same "
"``conf.py`` and ``.rst`` files, but each project must specify the language "
"to build for those docs."
msgstr ""
#: ../../localization.rst:60
msgid ""
"You can read :doc:`guides/manage-translations` to understand the whole "
"process for a documentation with multiples languages in the same repository "
"and how to keep the translations updated on time."
msgstr ""