Weblate Logo
weblate-4.6.2

ユーザー ドキュメント

  • Weblate の基本
  • 登録とユーザー情報
  • Weblate を使用した翻訳
  • 翻訳のダウンロードとアップロード
  • 用語集
  • 検査と修正
  • 検索
  • 翻訳ワークフロー
  • よくある質問
  • 対応するファイル形式
  • バージョン管理の統合
  • Weblate's REST API
  • Weblate クライアント
  • Weblate の Python API

管理者ドキュメント

  • 導入方法
  • Weblate の設置
  • Weblate のアップグレード
  • Weblate のバックアップと移動
  • 認証
  • アクセス制御
  • 翻訳プロジェクト
  • 言語の定義
  • Web サービスを連携した翻訳
  • 翻訳のライセンス
  • 翻訳の処理
  • 検査と修正
  • 機械翻訳
  • アドオン
  • 翻訳メモリ
  • 設定
  • 設定例
  • Management commands
  • お知らせ
  • コンポーネント リスト
  • Optional Weblate modules
  • Customizing Weblate
  • 管理画面
  • Weblate からのサポートを受ける
  • Legal documents
    • ITAR and other export controls
    • US encryption controls

アプリケーション開発者ガイド

  • Starting with internationalization
  • Integrating with Weblate
  • GNU gettext を使用するソフトウェアによる翻訳
  • Translating documentation using Sphinx
  • Translating HTML and JavaScript using Weblate CDN
  • Translation component alerts
  • Building translators community
  • Managing translations
  • Reviewing strings
  • Promoting the translation
  • 翻訳の進捗状況レポート

貢献者ドキュメント

  • Weblate に貢献
  • Weblate にコードの提供開始
  • Weblate のソース コード
  • Debugging Weblate
  • Weblate の内部
  • アドオンの開発
  • Weblate フロントエンド
  • Weblate の問題の報告
  • Weblate testsuite and continuous integration
  • データ スキーマ
  • Weblate のリリース
  • セキュリティとプライバシー条項
  • Weblate について
  • ライセンス

変更履歴

  • 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¶

注釈

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)

参考

Export Controls (EAR) on Open Source Software

Next Previous

© Copyright 2012 - 2021 Michal Čihař. Revision 0344ddb4.

Built with Sphinx using a theme provided by Read the Docs.
Read the Docs v: weblate-4.6.2
Versions
latest
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
Downloads
On Read the Docs
Project Home
Builds