Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 0 0 0 0 1 0 0
Chinese (Simplified Han script) CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 0 0
Finnish CC-BY-SA-3.0 9% 38 1,146 7,939 38 0 0 0
French CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 3 0
Japanese CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 3 0
Portuguese (Brazil) CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 3 0
Spanish CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 3 0
Please sign in to see the alerts.

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
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/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files ba94dc2aa
♪ I'm a bot, bot, bot ♪ authored yesterday
Last commit in Weblate Update translation files 1947f9f0e
Weblate authored yesterday
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Tcl.po
10 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 294 8,064 55,930
Source 42 1,152 7,990
Translated 15% 46 14% 1,158 14% 8,041
Needs editing 0% 0 0% 0 0% 0
Read-only 14% 42 14% 1,152 14% 7,990
Failing checks 1% 1 1% 73 1% 467
Strings with suggestions 4% 12 1% 12 1% 108
Untranslated strings 84% 248 85% 6,906 85% 47,889
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

8,064
Hosted words
294
Hosted strings
15%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+15%
—
Contributors
—
User avatar mt:weblate-translation-memory

Suggestion added
Extensions
extensions
11 months ago
User avatar mt:weblate-translation-memory

Suggestion added
Good:
Buena
11 months ago
User avatar mt:weblate-translation-memory

Suggestion added
Applications
Aplicaciones
11 months ago
User avatar None

Resource updated
File “po/es/master/pages/Tcl.po” was added. 11 months ago
User avatar None

String updated in the repository
*Stubs are ok if put in -devel subpackage:*
Some Tcl extensions provide a static 'stub' library. Stub libraries are a Tcl-ism to provide version-independent dynamic linking on a variety of platforms. These are not normal static libraries that provide the library's actual functionality, but instead provide a level of indirection pointing to the shared library. These stub libraries do not have the same static linking issues that are generally frowned upon in Fedora, and thus are acceptable. If a package provides such a stub library, it must be placed in a -devel subpackage. More information on stubs can be found on the Tcl wiki: https://wiki.tcl-lang.org/page/Stubs
 
11 months ago
User avatar None

String updated in the repository
*No dlopen()'d libraries in %\{_libdir}:*
If the extension does *not* provide a `+fooConfig.sh+` file, then the shared library *must not* be installed directly in `+%{_libdir}+`, but in the package-specific installation directory in `+%{tcl_sitearch}+` instead. This may require a patch to update the extension's `+pkgIndex.tcl+` file to look for the shared library in the correct location.
 
11 months ago
User avatar None

String updated in the repository
`+fooConfig.sh+` files must be placed in a -devel subpackage. This may require some sed magic to modify `+fooConfig.sh+` so that the paths to the libraries and headers are still correct.
 
11 months ago
User avatar None

String updated in the repository
*-devel subpackage for fooConfig.sh:*
Some arch-specific Tcl extensions provide a shared library and a corresponding `+fooConfig.sh+` file with instructions for linking against the library. The shared library for such packages *must* be installed into %\{_libdir} so that it can be found at runtime by applications that link against it. Unfortunately, the pkgIndex.tcl file in the package directory often references the shared library with a relative path. There are two ways to fix this. First, the maintainer can choose to keep the installation directory as %\{_libdir}, and make a symlink to %\{tcl_sitearch}. Second, the maintainer can choose to patch the pkgIndex.tcl file to contain an appropriate path to the shared library. Either solution is acceptible.
 
11 months ago
User avatar None

String updated in the repository
*No shells:*
Very few Tcl extension packages provide a shell. Providing a shell for an extension is frowned upon. The extension's shared library can be dynamically loaded into a Tcl interpreter through the standard `+package require ...+` mechanism without providing a shell that automatically loads the shared library. The exceptions to this rule are the shells that are commonly expected to be present on a system, including Tk (wish) and Expect (expect, expectk).
 
11 months ago
User avatar None

String updated in the repository
Arch-specific packages can be generally grouped into three categories: those that provide a shell, those that provide a fooConfig.sh file and a shared library for linking, and those that only provide a shared library for dlopen().
 
11 months ago
Browse all component changes