The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation status

4 Strings
25%
Browse Translate
113 Words
25%
748 Characters
24%

Strings status

Strings Words Characters
4 113 748
All strings Browse Translate Zen
1 29 183
Translated strings Browse Translate Zen
3 84 565
Unfinished strings Browse Translate Zen
3 84 565
Strings marked for edit Browse Translate Zen
1 3 30
Strings with any failing checks Browse Translate Zen
1 3 30
Failing check: Placeholders Browse Translate Zen

Summary

Project website tuist.dev
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository https://github.com/tuist/tuist
Repository branch main
Last remote commit feat(kura): declare the analytics-outbox RocksDB column family (#13467) 706c0d9811
Pedro Piñera Buendía authored 09/22/2026
Last commit in Weblate Translated using Weblate (Chinese (Traditional Han script)) 00c4608470
DeepL authored 09/21/2026
Weblate repository https://translate.tuist.dev/git/tuist/documentation-pages/
File mask docs/docs/*/guides/features/registry/swift-package.md
Monolingual base language file docs/docs/en/guides/features/registry/swift-package.md
Translation file Download docs/docs/ko/guides/features/registry/swift-package.md
Last change Sept. 21, 2026, 4:07 p.m.
Last change made by Background commit
Language Korean
Language code ko
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 79,278,717
Number of plurals 1
Plural type None
Plurals
Plural formula 0
09/21/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 4 113 748
Translated 25% 1 25% 29 24% 183
Needs editing 75% 3 74% 84 75% 565
Read-only 0% 0 0% 0 0% 0
Failing checks 25% 1 2% 3 4% 30
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 13 changes 0 changes 5 changes 0 changes 21 changes 0 changes 14 changes 0 changes 2 changes 0 changes 2 changes 0 changes 3 changes 0 changes 0 changes 0 changes 3 changes 0 changes 2 changes 0 changes 3 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

113
Hosted words
4
Hosted strings
25%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar weblate:commit

Changes committed
Changes committed 09/21/2026
User avatar mt:deepl

Automatically translated
If you want to ensure that the registry is used every time you resolve dependencies, you will need to update `dependencies` in your `Package.swift` file to use the registry identifier instead of a URL. The registry identifier is always in the form of `{organization}.{repository}`. For example, to use the registry for the `swift-composable-architecture` package, do the following:
의존성을 해결할 때마다 레지스트리가 사용되도록 하려면, `Package.swift` 파일 내의 `의존성dependencies` 부분을 수정하여 URL 대신 레지스트리 식별자를 사용하도록 해야 합니다. 레지스트리 식별자는 항상 `{organization}.{repository}` 형식을 따릅니다. 예를 들어, `swift-composable-architecture` 패키지의 레지스트리를 사용하려면 다음을 수행과 같이 하십시오:
09/21/2026
User avatar mt:deepl

Automatically translated
If you are working on a Swift package, you can use the `--replace-scm-with-registry` flag to resolve dependencies from the registry if they are available:
Swift 패키지를 작업 중이라면인 경우, `--replace-scm-with-registry` 플래그를 사용하여 레지스트리에서 의존성을 해결할 수 있습니다(해당 의존성이 레지스트리에 있는사용 가능한 경우):
09/21/2026
User avatar weblate:commit

Changes committed
Changes committed 08/21/2026
User avatar mt:deepl

Automatically translated
If you want to ensure that the registry is used every time you resolve dependencies, you will need to update `dependencies` in your `Package.swift` file to use the registry identifier instead of a URL. The registry identifier is always in the form of `{organization}.{repository}`. For example, to use the registry for the `swift-composable-architecture` package, do the following:
의존성을 해결할 때마다 레지스트리가 사용되도록 하려면, `Package.swift` 파일 내의 `의존성` 부분을 수정하여 URL 대신 레지스트리 식별자를 사용하도록 업데이트해야 합니다. 레지스트리 식별자는 항상 `{organization}.{repository}` 형식을 따릅니다. 예를 들어, `swift-composable-architecture` 패키지의 레지스트리를 사용하려면 다음과 같이 을 수행하십시오:
08/21/2026
User avatar mt:deepl

Automatically translated
If you are working on a Swift package, you can use the `--replace-scm-with-registry` flag to resolve dependencies from the registry if they are available:
Swift 패키지를 작업 중인 경우이라면, `--replace-scm-with-registry` 플래그를 사용하여 레지스트리에서 의존성을 해결할 수 있습니다(사용 가능한해당 의존성이 레지스트리에 있는 경우):
08/21/2026
User avatar webhook:github

Changes committed
Changes committed 07/21/2026
User avatar mt:weblate

Automatically translated
Swift package {#swift-package}
Swift 패키지 {#swift-packages}
07/21/2026
User avatar weblate:commit

Changes committed
Changes committed 06/21/2026
User avatar mt:deepl

Automatically translated
If you want to ensure that the registry is used every time you resolve dependencies, you will need to update `dependencies` in your `Package.swift` file to use the registry identifier instead of a URL. The registry identifier is always in the form of `{organization}.{repository}`. For example, to use the registry for the `swift-composable-architecture` package, do the following:
의존성을 해결할 때마다 레지스트리가 사용되도록 하려면, `Package.swift` 파일 내의 `의존성` 부분을 URL 대신 레지스트리 식별자를 사용하도록 업데이트해야 합니다. 레지스트리 식별자는 항상 `{organization}.{repository}` 형식입을 따릅니다. 예를 들어, `swift-composable-architecture` 패키지의 레지스트리를 사용하려면 다음을 수행과 같이 하십시오:
06/21/2026
Browse all translation changes