Weblate Logo
weblate-4.14.2

User docs

  • Weblate basics
  • Registration and user profile
  • Translating using Weblate
  • Downloading and uploading translations
  • Glossary
  • Checks and fixups
  • Searching
  • Translation workflows
  • Frequently Asked Questions
  • Supported file formats
  • Version control integration
  • Weblate’s REST API
  • Weblate Client
  • Weblate’s Python API

Administrator docs

  • Configuration instructions
  • Weblate deployments
  • Upgrading Weblate
  • Backing up and moving Weblate
  • Authentication
  • Access control
  • Translation projects
  • Language definitions
  • Continuous localization
  • Licensing translations
  • Translation process
  • Checks and fixups
  • Configuring automatic suggestions
  • Add-ons
  • Translation Memory
  • Configuration
  • Sample configuration
  • Management commands
  • Announcements
  • Component Lists
  • Optional Weblate modules
  • Customizing Weblate
  • Management interface
  • Getting support for Weblate
  • Legal documents
    • ITAR and other export controls
    • US encryption controls

Application developer guide

  • Starting with internationalization
  • Integrating with Weblate
  • Translating software using GNU gettext
  • Translating documentation using Sphinx
  • Translating HTML and JavaScript using Weblate CDN
  • Localization libraries and packages
  • Translation component alerts
  • Building translators community
  • Managing translations
  • Reviewing strings
  • Promoting the translation
  • Translation progress reporting

Contributor docs

  • Contributing to Weblate
  • Starting contributing code to Weblate
  • Weblate source code
  • Debugging Weblate
  • Weblate internals
  • Developing add-ons
  • Weblate frontend
  • Reporting issues in Weblate
  • Weblate testsuite and continuous integration
  • Data schemas
  • Releasing Weblate
  • Security and privacy
  • Contributing to Weblate modules
  • About Weblate
  • License

Change history

  • Weblate 4.14.2
  • Weblate 4.14.1
  • Weblate 4.14
  • Weblate 4.13.1
  • Weblate 4.13
  • Weblate 4.12.2
  • Weblate 4.12.1
  • Weblate 4.12
  • Weblate 4.11.2
  • Weblate 4.11.1
  • Weblate 4.11
  • Weblate 4.10.1
  • Weblate 4.10
  • Weblate 4.9.1
  • Weblate 4.9
  • Weblate 4.8.1
  • Weblate 4.8
  • Weblate 4.7.2
  • Weblate 4.7.1
  • Weblate 4.7
  • Weblate 4.6.2
  • Weblate 4.6.1
  • Weblate 4.6
  • Weblate 4.5.3
  • Weblate 4.5.2
  • Weblate 4.5.1
  • Weblate 4.5
  • Weblate 4.4.2
  • Weblate 4.4.1
  • Weblate 4.4
  • Weblate 4.3.2
  • Weblate 4.3.1
  • Weblate 4.3
  • Weblate 4.2.2
  • Weblate 4.2.1
  • Weblate 4.2
  • Weblate 4.1.1
  • Weblate 4.1
  • Weblate 4.0.4
  • Weblate 4.0.3
  • Weblate 4.0.2
  • Weblate 4.0.1
  • Weblate 4.0
  • Weblate 3.x series
  • Weblate 2.x series
  • Weblate 1.x series
  • Weblate 0.x series
Weblate
  • Legal documents
  • Edit on GitHub

Legal documents

Note

Herein you will find various legal information you might need to operate Weblate in certain legal jurisdictions. It is provided as a means of guidance, without any warranty of accuracy or correctness. It is ultimately your responsibility to ensure that your use of Weblate complies with all applicable laws and regulations.

ITAR and other export controls

Weblate can be run within your own datacenter or virtual private cloud. As such, it can be used to store ITAR or other export-controlled information, however, end users are responsible for ensuring such compliance.

The Hosted Weblate service has not been audited for compliance with ITAR or other export controls, and does not currently offer the ability to restrict translations access by country.

US encryption controls

Weblate does not contain any cryptographic code, but might be subject export controls as it uses third party components utilizing cryptography for authentication, data-integrity and -confidentiality.

Most likely Weblate would be classified as ECCN 5D002 or 5D992 and, as publicly available libre software, it should not be subject to EAR (see Encryption items NOT Subject to the EAR).

Software components used by Weblate (listing only components related to cryptographic function):

Python

See https://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq#Is_Python_subject_to_export_laws.3F

GnuPG

Optionally used by Weblate

Git

Optionally used by Weblate

curl

Used by Git

OpenSSL

Used by Python and cURL

The strength of encryption keys depends on the configuration of Weblate and the third party components it interacts with, but in any decent setup it will include all export restricted cryptographic functions:

  • In excess of 56 bits for a symmetric algorithm

  • Factorisation of integers in excess of 512 bits for an asymmetric algorithm

  • Computation of discrete logarithms in a multiplicative group of a finite field of size greater than 512 bits for an asymmetric algorithm

  • Discrete logarithms in a group different than above in excess of 112 bits for an asymmetric algorithm

Weblate doesn’t have any cryptographic activation feature, but it can be configured in a way where no cryptography code would be involved. The cryptographic features include:

  • Accessing remote servers using secure protocols (HTTPS)

  • Generating signatures for code commits (PGP)

See also

Export Controls (EAR) on Open Source Software

Previous Next

© Copyright 2012–2022 Michal Čihař. Revision 043675e6.

Built with Sphinx using a theme provided by Read the Docs.
Read the Docs v: weblate-4.14.2
Versions
latest
weblate-4.9.1
weblate-4.9
weblate-4.8.1
weblate-4.8
weblate-4.7.2
weblate-4.7.1
weblate-4.7
weblate-4.6.2
weblate-4.6.1
weblate-4.6
weblate-4.5.3
weblate-4.5.2
weblate-4.5.1
weblate-4.5
weblate-4.4.2
weblate-4.4.1
weblate-4.4
weblate-4.3.2
weblate-4.3.1
weblate-4.3
weblate-4.2.2
weblate-4.2.1
weblate-4.2
weblate-4.14.2
weblate-4.14.1
weblate-4.14
weblate-4.13.1
weblate-4.13
weblate-4.12.2
weblate-4.12.1
weblate-4.12
weblate-4.11.2
weblate-4.11.1
weblate-4.11
weblate-4.10.1
weblate-4.10
Downloads
On Read the Docs
Project Home
Builds