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/>

Translation status

162 Strings 100%
Browse Translate
2,955 Words 100%

Strings status

162
All strings — 2,955 words Browse Edit Zen
162
Translated strings — 2,955 words Browse Edit Zen
162
Strings waiting for review — 2,955 words Browse Edit Zen
1
Translated strings with dismissed checks — 124 words Browse Edit Zen

Other components

Component Translated Untranslated Untranslated words Untranslated characters Checks Suggestions Comments
Glossary yast-scanner GPL-2.0
Browse all components

Overview

Project website github.com/yast/yast-scanner
Project maintainers User avatar ancorgonzalezsosa
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license GNU General Public License v2.0 only
Source code repository git@github.com:yast/yast-translations.git
Repository branch master
Last remote commit Merge branch 'origin/master' into Weblate. f6307a1351
openSUSE Weblate authored 41 minutes ago
Weblate repository https://l10n.opensuse.org/git/yast-base/master/
Filemask po/scanner/*.po
Translation file Download po/scanner/ja.po
Last change Jan. 29, 2018, 5:56 a.m.
Last author Yasuhiko Kamata

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 162 2,955 18,996
Translated 100% 162 100% 2,955 100% 18,996
Needs editing 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Last year Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

2,955
Hosted words
162
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource update

yast-scanner / master — Japanese

Resource update a month ago
User avatar None

Resource update

yast-scanner / master — Japanese

Resource update 3 months ago
User avatar None

Resource update

yast-scanner / master — Japanese

Resource update 3 months ago
User avatar None

Resource update

yast-scanner / master — Japanese

Resource update 7 months ago
User avatar admin

Resource update

yast-scanner / master — Japanese

Resource update 7 months ago
User avatar admin

Resource update

yast-scanner / master — Japanese

Resource update 11 months ago
User avatar None

Committed changes

yast-scanner / master — Japanese

Committed changes 3 years ago
User avatar YasuhikoKamata

Translation changed

yast-scanner / master — Japanese

Activate the driver
ドライバをの有効にする化
3 years ago
User avatar None

Committed changes

yast-scanner / master — Japanese

Committed changes 3 years ago
User avatar YasuhikoKamata

Suggestion removed

yast-scanner / master — Japanese

The hpoj driver requires the PTAL system to be set up and running.
In particular, the ptal service must be up and running.

Before the ptal service can be started, the PTAL system must be initialized.
Additionally, the ptal service should be activated for start when booting.
The PTAL system and the hplip service exclude each other.
Therefore a running hplip service would be stopped and deactivated
before the the PTAL system is initialized, activated, and started.
An automated initialization of the PTAL system is only safe for USB.
If you have a non-USB device or if the automated initialization for USB fails,
set up the PTAL system manually.
If you have an all-in-one device (scanner+printer), note that
a running ptal service monopolizes the USB device file (e.g., /dev/usb/lp0),
so the printer can no longer be addressed via the USB device file.

Should the PTAL system for USB be initialized, activated, and started now?
hpojドライバを設定し、実行するためにはPTALシステムが必要です。
具体的には、ptalサービスが開始され、実行されている必要があります。

ptalサービスは、PTALシステムが初期化された後で、開始できるようになります。
ptalサービスは、ブート時に開始されるように、有効にする必要があります。
PTALシステムとhplipサービスを同時に使用することはできません。
したがって、hplipサービスが実行されている場合、PTALシステムを
初期化した後、有効にし開始する前に、hplipサービスは停止され無効になります。
PTALシステムは、USBを使用する場合に限り、初期化を自動化しても安全です。
USBでないデバイスを使用する場合や、USB用のUSBの自動初期化に失敗した場合には、
PTALシステムを手動で設定します。
スキャナとプリンタのオールインワンデバイスを使用している場合は、実行中のptalサービス
によってUSBデバイスファイル(例:/dev/usb/lp0)が独占されるため、
USBデバイスファイル経由でプリンタにアクセスできなくなります。

USBのPTALシステムを初期化した後、有効にして開始しますか?
3 years ago
Browse all translation changes