 The Weblate Manual 2.9formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 265 页 | 1.10 MB | 1 年前3 The Weblate Manual 2.9formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 265 页 | 1.10 MB | 1 年前3
 The Weblate Manual 2.8formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 251 页 | 1.07 MB | 1 年前3 The Weblate Manual 2.8formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 251 页 | 1.07 MB | 1 年前3
 The Weblate Manual 2.12formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 287 页 | 1.18 MB | 1 年前3 The Weblate Manual 2.12formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 287 页 | 1.18 MB | 1 年前3
 The Weblate Manual 2.6formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 235 页 | 1009.42 KB | 1 年前3 The Weblate Manual 2.6formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 235 页 | 1009.42 KB | 1 年前3
 The Weblate Manual 4.17instructions for translators, or a directory or link to the string in the version control system repository the project uses. If you want direct links, the translation format has to support it. Translation Files menu. The first option is to download the file in the original format as it is stored in the repository. In this case, any pending changes in the translation are getting committed and the up-to-date translation components and you can use all Weblate features on them — commenting, storing in a remote repository, or adding explanations. Use any component as a glossary by turning on Use as a glossary. You0 码力 | 794 页 | 18.87 MB | 1 年前3 The Weblate Manual 4.17instructions for translators, or a directory or link to the string in the version control system repository the project uses. If you want direct links, the translation format has to support it. Translation Files menu. The first option is to download the file in the original format as it is stored in the repository. In this case, any pending changes in the translation are getting committed and the up-to-date translation components and you can use all Weblate features on them — commenting, storing in a remote repository, or adding explanations. Use any component as a glossary by turning on Use as a glossary. You0 码力 | 794 页 | 18.87 MB | 1 年前3
 Weblate 2.9 Documentationformats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 214 页 | 1.61 MB | 1 年前3 Weblate 2.9 Documentationformats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 214 页 | 1.61 MB | 1 年前3
 The Weblate Manual 2.7formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 242 页 | 1014.46 KB | 1 年前3 The Weblate Manual 2.7formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 242 页 | 1014.46 KB | 1 年前3
 The Weblate Manual 2.8formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 205 页 | 1.54 MB | 1 年前3 The Weblate Manual 2.8formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 205 页 | 1.54 MB | 1 年前3
 The Weblate Manual 2.11formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 280 页 | 1.12 MB | 1 年前3 The Weblate Manual 2.11formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 280 页 | 1.12 MB | 1 年前3
 The Weblate Manual 2.10.1formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 276 页 | 1.12 MB | 1 年前3 The Weblate Manual 2.10.1formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot0 码力 | 276 页 | 1.12 MB | 1 年前3
共 302 条
- 1
- 2
- 3
- 4
- 5
- 6
- 31














