From Mahara Wiki

< Mahara日本語ドキュメント‎ | 言語パック
Revision as of 21:01, 12 December 2017 by Mits (talk | contribs) (言語リリースポリシー案 Proposed Language Release Policy)

作成中です - mits (talk)

背景 Background



ある程度の一般的なエラーを発見して通知すると共に壊れた言語パックのダウンロードを防ぐため、Mahara開発者はツール ( を導入しました。このページの言語パックは処理および確認された後、 からダウンロードできるようになります。

言語リリースポリシー案 Proposed Language Release Policy


同時に常に公式ダウンロードページを使用して、代替ダウンロードサイトの使用を止めさせてください。このようにしてMahara開発者はあなたの言語パックをチェックして、ユーザは常にセキュリティホールを塞がれた言語パックのコピーを取得することができます。This way Mahara developers can run the checks on your language pack and users will always download a working copy of it (with most blatant security holes plugged).

Rationale: When people start translating new languages, they sometimes don't use Launchpad, because they are probably not familiar with Launchpad and its associated tools. So they set up a shared space (a view in, a dropbox account, etc.) and they use it to do the initial translation work (e.g., this is how the Spanish translation for Mahara 1.3 was done).

It's only after they have something more or less complete that they get in contact with Mahara core developers to ask for a place in the official language repository.

In the first phase (shared place outside the official language repository) no quality control is done (in the sense of errors that may break Mahara). So that's why we propose that translators clearly tell other people they shouldn't use that 'work-in-progress' version from the shared space. Unless they are going to collaborate on translation, of course.

The rest of the people should wait until that work-in-progress version is put into the official language repository, where those additional checks are run. That way they would use a non-broken version of the language pack.

Please see " How to start a translation" for more information on getting started.

Technical Details

  • All files must be in the UTF-8 encoding without BOM (byte-order mark)
  • All files must be valid PHP files (i.e. no syntax errors). Run "php -l myfile.php" to check.