SUSE has an in-house translations created by contracted translators in past. The work flow did not allow to merge translations between openSUSE and SLE trees up to now. It caused translation divergence. SLE Merge Robot is an output of the merge effort, and “suggests” to use SLE translation. Please review carefully, and keep standard terminology used in your language.

Initial import of yast was created from the community translations, but strings actually missing in the community translation were taken from the contracted SUSE Linux Enterprise translations. These translations are mixed in Weblate. If you are interested in the SUSE Linux Enterprise translations import review, go to ftp://ftp.suse.com/pub/people/sbrabec/yast-translations-sle-contributions/

Overview

Project website uyuni-project.org
Instructions for translators

https://github.com/uyuni-project/uyuni/wiki/Translating-Uyuni-to-your-language Mailing list for translators: <translation@lists.uyuni-project.org
Project maintainers User avatar karleichwalder User avatar PadraigDillon User avatar JulioGonzalezGil User avatar MichaelCalmer User avatar PascalArlt User avatar JuliaFaltenbacher User avatar JosephCayouette User avatar ThomasFlorio User avatar MicheleBussolotto User avatar OrnelaMaric
Translation license GNU Free Documentation License v1.2 only
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:uyuni-project/uyuni-docs.git
Repository branch manager-5.0
Last remote commit Automatic commit: update translation files c7fb1279f
Galaxy CI authored yesterday
Last commit in Weblate Automatic commit: update translation files c7fb1279f
Galaxy CI authored yesterday
Weblate repository https://l10n.opensuse.org/git/uyuni/docs-installation-and-upgrade-manager-50/
File mask l10n-weblate/client-configuration/*.po
Translation file Download l10n-weblate/client-configuration/ja.po
Last change Nov. 21, 2024, 9 p.m.
Last change made by None
Language Japanese
Language code ja
Text direction Left to right
Number of speakers 117,558,321
Number of plurals 1
Plural type None
Plurals
Plural formula 0
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 2,511 45,538 325,400
Approved 10% 260 14% 6,503 14% 45,911
Waiting for review 86% 2,176 83% 37,863 83% 270,841
Translated 97% 2,436 97% 44,366 97% 316,752
Needs editing 2% 57 1% 806 1% 6,290
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 190 3% 1,720 5% 16,802
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 18 1% 366 1% 2,358
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2,535 changes 0 changes 275 changes 0 changes 180 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

45,538
Hosted words
2,511
Hosted strings
97%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−1%
Translated
+97%
—
Contributors
+100%
User avatar None

Resource updated
The “l10n-weblate/client-configuration/ja.po” file was changed. yesterday
User avatar None

String added in the repository
The {payg} connection regular checks with the client to get the latest authentication data. It is important that the client stays running and is regular updated. If this does not happen, repository synchronization will fail with authentication errors at some point in time.
PAYG接続は、最新の認証データを取得するために、定期的にクライアントをチェックします。 クライアントが実行され続け、定期的に更新されることが重要です。 これが行われない場合、リポジトリの同期はある時点で認証エラーにより失敗します。
yesterday
User avatar None

Source string changed
The PAYG{payg} connection regular checks with the client to get the latest authentication data. It is important that the client stays running and is regular updated. If this does not happen, repository synchronization will fail with authentication errors at some point in time.
yesterday
User avatar None

Resource updated
The “l10n-weblate/client-configuration/ja.po” file was changed. yesterday
User avatar None

String added in the repository
The actions available for use in SSM are listed in table. The icons in this table indicate:
SSMで使用できるアクションを次の表に示します。 この表のアイコンの意味は次のとおりです。
yesterday
User avatar None

Source string changed
The actions available for use in SSM are listed in this table. The icons in this table indicate:
yesterday
User avatar None

String added in the repository
For more information about blackout mode in {salt}, see https://docs.saltproject.io/en/latest/topics/blackout.
{salt}の停止モードの詳細については、link:https://docs.saltstack.com/en/latest/topics/blackout/index.html[]を参照してください。
yesterday
User avatar None

Source string changed
For more information about blackout mode in {salt}, see https://docs.saltstack.comproject.io/en/latest/topics/blackout/index.html.
yesterday
User avatar None

String added in the repository
For Redfish, ensure you can establish a valid SSL connection between the client and the {productname} Server. You must have trusted the certificate authority used to sign the SSL Server Certificate of the Redfish management controller. The CA certificate must be in [literal]``.pem`` format, and stored on the {productname} Server at [path]``/etc/pki/trust/anchors/``. When you have saved the certificate, run [command]``update-ca-certificate``.
Redfishの場合、クライアントと{productname}サーバの間に有効なSSL接続を確立できることを確認してください。Redfish管理コントローラのSSLサーバ証明書を署名するために使用される認証局を信頼している必要があります。CA証明書は``.pem``フォーマットで、{productname}サーバの[path]``/etc/pki/trust/anchors/``に保存される必要があります。証明書を保存したら、[command]``update-ca-certificate``を実行します。
yesterday
User avatar None

Source string changed
For Redfish, ensure you can establish a valid SSL connection between the client and the {productname} Server. You must have trusted the certificate authority used to sign the SSL Server Certificate of the Redfish management controller. The CA certificate must be in [literal]``.pem`` format, and stored on the {productname} Server at [path]``/etc/pki/trust/anchors/``. When you have saved the certificate, run [command]``update-ca-certificate``.
yesterday
Browse all translation changes