Translation status

56 Strings 0%
Browse Translate
2,292 Words 0%
17,277 Characters 0%

Strings status

Strings Words Characters
56 2,292 17,277
All strings Browse Translate Zen
56 2,292 17,277
Unfinished strings Browse Translate Zen
56 2,292 17,277
Untranslated strings Browse Translate Zen
19 969 7,297
Strings with suggestions Browse Translate Zen
37 1,323 9,980
Unfinished strings without suggestions Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/quick-docs
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/quick-docs.git
Repository branch master
Last remote commit automatic update of pot/po files 07a1b530fd
♪ I'm a bot, bot, bot ♪ authored 10 days ago
Last commit in Weblate Translated using Weblate (Spanish) 5c144eb3d9
User avatar vareli authored 5 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-quick-docs/nav/
File mask po/*/master/pages/fedora-repositories.po
Translation file Download po/ja/master/pages/fedora-repositories.po
Last change None
Last author None
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 56 2,292 17,277
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 33% 19 42% 969 42% 7,297
Untranslated strings 100% 56 100% 2,292 100% 17,277
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 78 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
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

2,292
Hosted words
56
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
Why is _updates-testing_ enabled by default in pre-releases?
なぜ、プレリリース版では _updates-testing_ が標準で有効化されてるのか？
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
Before a stable release occurs, this mechanism is not necessary. Before the release is declared to be done, there is no _frozen_ state of the release: effectively, the whole Branched development process is _working towards_ what will become the _frozen_ state of the release, so of course package builds for the Branched release land directly in the _fedora_ repository.
安定リリースが発生する前なら、このメカニズムは必要ありません。 リリースが行われたと宣言される前には、リリースの_frozen_ 状態はありません。effectively, the whole Branched development process is _working towards_ what will become the _frozen_ state of the release, so of course package builds for the Branched release land directly in the _fedora_ repository.
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
Since we wish to maintain this _frozen_ state for the _fedora_ repository, we cannot place updates directly into it. The necessity for the _updates_ repository therefore becomes obvious - we need a place to put updates to stable releases that is outside the _frozen_ state of the release.
_fedora_ リポジトリの _frozen_ 状態を私たちは維持したいので、アップデートを直接そこに配置することは不可能なのです。 したがって、 _updates_ リポジトリの必要性が明らかになります。リリースの _frozen_ 状態の外側にて安定リリースの更新を配置する場所が私たちには必要です。
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
The reason for the difference is that we want to have a record of the exact 'state' of a given Fedora stable release. That is, at the time a Fedora release is declared to be done at a https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go Meeting], we consider the state of the release at that time to be the canonical definition of that release, and we wish to preserve a record of that state. For a stable release, the tree containing the _fedora_ repository *is* that record, and the _fedora_ repository it contains is the canonical record of the precise _frozen_ package set that formed the main part of that stable release.
違いの理由は、特定のFedora安定版リリースの正確な 'state' のレコードを私たちが所持したいからです。 つまり、Fedoraのリリースが https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go Meeting] で行われると宣言された時点で、その時点でのリリースの状態をそのリリースの正統な定義であると私たちは見なし、その状態のレコードを保存することを私たちは望みます。 安定版リリースの場合、_fedora_リポジトリを含むツリー *は* そのレコードであり、それに含まれる _fedora_ リポジトリは、その安定版リリースの主要部分を形成した正確な _frozen_ パッケージセットの正統なレコードです。
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
As described above, updates for both Branched pre-releases and final, _stable_ releases go through the _updates-testing_ process before being moved to a _stable_ repository. Before the final release, they are placed in the _fedora_ repository. After release, they are placed in _updates_.
上記で説明したように、 アップデートは、ブランチ のプレリリースにしろ、最終リリースにしろ、_stable_ リリースでは、アップデートは事前に _updates-testing_ プロセスで検証・淘汰されてから、合格したものが _stable_ な状態のリポジトリに移動します。 最終リリースより前では、これらのアップデートは _fedora_ リポジトリに置かれます。リリース後は、 アップデートは _updates_ のみに置かれます。
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
Why is _updates_ only used after the stable release?
なぜ、安定リリースでは _updates_ だけが使われるのか?
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
For Branched releases, the _stable_ state is represented solely by the current contents of the _fedora_ repository (and, arguably, the _bleed_ repository, but that is a small case).
ブランチリリースにおいて、 _stable_ 状態とは、もっぱら _fedora_ リポジトリの現行のコンテンツによる状態のことです (and, arguably, the bleed repository, but that is a small case).
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
It is not unusual to see references to the 'stable repository', but this is something of a misnomer. _stable_ is more of a state that can be considered to exist for both Branched releases post https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling[Bodhi enabling] and for stable releases. It consists of package builds that were part of Rawhide at the time they Branched, package builds sent directly to the Branched _fedora_ repository between the branch point and the _Bodhi enabling point_, and package builds that passed the https://fedoraproject.org/wiki/Updates_Policy[Updates Policy] and moved from _updates-testing_ after the _Bodhi enabling point_.
'stable repository'（安定リポジトリ）といった名称をときどき見かけるかもしれませんが、しかし Fedora においては、それは誤った名称の何かです。 _stable_ is more of a state that can be considered to exist for both Branched releases post https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling[Bodhi enabling] and for stable releases. It consists of package builds that were part of Rawhide at the time they Branched, package builds sent directly to the Branched _fedora_ repository between the branch point and the _Bodhi enabling point_, and package builds that passed the https://fedoraproject.org/wiki/Updates_Policy[Updates Policy] and moved from _updates-testing_ after the _Bodhi enabling point_.
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
The _rawhide_ repositories for the various primary https://fedoraproject.org/wiki/Architectures[architectures] can be found in the directory on the mirrors, and can also be queried from https://fedoraproject.org/wiki/MirrorManager[MirrorManager]. For instance, https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-rawhide&arch=x86_64 will return mirrors for the x86_64 _fedora_ repository for Rawhide.
多くの主要な https://fedoraproject.org/wiki/Architectures[アーキテクチャ] 用の _rawhide_ リポジトリは、ミラーで直接的に見つかるか、あるいはクエリを https://fedoraproject.org/wiki/MirrorManager[MirrorManager] とやりとりしても見つけられます。たとえば https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-rawhide&arch=x86_64 でミラーは x86_64 のための Rawhide 用の _fedora_ リポジトリを返します。
8 months ago
User avatar anonymous

Suggestion added

  1. fedora-docs-l10n/quick-docs
  2. master/pages/fedora-repositories
  3. Japanese
In Rawhide - Fedora's rolling release repository, from which release are Branched before finally going stable - _rawhide_ is the only repository. All package builds are sent there. It is represented for xref:dnf.adoc[DNF] in the `fedora-rawhide.repo` file in the repository path. For any system running Rawhide, it should be enabled. For any other system, it should not.
Rawhide - これは Fedora のローリングリリースのリポジトリであり、まだ安定してないリポジトリを枝分かれ(Branched)させた物です。そういったリポジトリは _rawhide_ だけしかありません。そのようなパッケージが Rawhide に送られます。 ファイル `fedora-rawhide.repo` にあるリポジトリパス(repository path) に従い、 xref:dnf.adoc[DNF] がソフトウェアを取りに行きます。 Rawhide を有効化しているシステムでのみ、ローリングリリースが有効です。Rawhide を有効化してない他のシステムでは一切、ローリングリリースを使えません。
8 months ago
Browse all translation changes