mirror of
https://gh.wpcy.net/https://github.com/WeblateOrg/weblate.git
synced 2026-05-02 21:40:04 +08:00
71 lines
2.8 KiB
ReStructuredText
71 lines
2.8 KiB
ReStructuredText
Integrating with Weblate
|
|
========================
|
|
|
|
.. include:: /snippets/basics.rst
|
|
|
|
Importing localization project into Weblate
|
|
+++++++++++++++++++++++++++++++++++++++++++
|
|
|
|
Weblate was developed with VCS integration in mind. The easiest approach to
|
|
integrate with it is to grant access to your VCS repository. The import process
|
|
will guide you through configuring components with your translations.
|
|
|
|
In case you do not use VCS or do not want to grant access to your VCS at all,
|
|
you can use Weblate without a remote VCS repository - it will create local
|
|
repository with all the translations.
|
|
|
|
.. seealso::
|
|
|
|
:ref:`adding-projects`,
|
|
:ref:`faq-submodule`
|
|
|
|
Getting translations updates from Weblate
|
|
+++++++++++++++++++++++++++++++++++++++++
|
|
|
|
To fetch updated strings from Weblate you can simply fetch the underlying
|
|
repository (either from filesystem or it can be made available through
|
|
:ref:`git-exporter`). Prior to this, you might want to commit any pending
|
|
changes (see :ref:`lazy-commit`). This can be achieved in the user interface
|
|
(in the :guilabel:`Repository maintenance`) or from command line using :ref:`wlc`.
|
|
|
|
This can be automated if you grant Weblate push access to your repository and
|
|
configure :ref:`component-push` in the :ref:`component`.
|
|
|
|
.. seealso::
|
|
|
|
:ref:`continuous-translation`
|
|
|
|
Pushing string changes to Weblate
|
|
+++++++++++++++++++++++++++++++++
|
|
|
|
To push newly updated strings to Weblate, just let it pull from the upstream
|
|
repository. This can be achieved in the user interface (in the :guilabel:`Repository
|
|
maintenance`) or from command line using :ref:`wlc`.
|
|
|
|
This can be automated by installing a webhook on your repository to trigger
|
|
Weblate whenever there is a new commit, see :ref:`update-vcs` for more details.
|
|
|
|
When not using a VCS integration, you can use UI or :doc:`/api` to update
|
|
translations to match your code base.
|
|
|
|
.. seealso::
|
|
|
|
:ref:`continuous-translation`
|
|
|
|
Adding new strings
|
|
++++++++++++++++++
|
|
|
|
In case your translation files are stored in VCS together with the code, you most
|
|
likely have existing workflow for developers to introduce new strings. You
|
|
might extend it by using :ref:`source-quality-gateway`.
|
|
|
|
When the translation files are separate, there needs to be a way to introduce
|
|
new strings. Weblate can add new strings on monolingual translations only (see
|
|
:ref:`bimono`). You have three options to do that:
|
|
|
|
* Manually, using :guilabel:`Add new translation string` from :guilabel:`Tools`
|
|
menu on source language translation.
|
|
* Programatically, using API :http:post:`/api/translations/(string:project)/(string:component)/(string:language)/units/`.
|
|
* By uploading source file as :guilabel:`Replace existing translation file`
|
|
(this overwrites existing strings, so please make sure the file includes both
|
|
old and new ones, see :ref:`upload-method`).
|
