Translation status

10 Strings 0%
Browse Translate
246 Words 0%
1,774 Characters 0%

Strings status

Strings Words Characters
10 246 1,774
All strings Browse Translate Zen
10 246 1,774
Unfinished strings Browse Translate Zen
10 246 1,774
Untranslated strings Browse Translate Zen
10 246 1,774
Unfinished strings without suggestions Browse Translate Zen

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 aa7b6c16f
♪ I'm a bot, bot, bot ♪ authored a week ago
Last commit in Weblate Translated using Weblate (Finnish) 5ac401cb5
User avatar copperi authored a year ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/LibreOfficeExtensions.po
Translation file Download po/es/master/pages/LibreOfficeExtensions.po
Last change None
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 10 246 1,774
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 0% 0 0% 0 0% 0
Untranslated strings 100% 10 100% 246 100% 1,774
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 12 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

246
Hosted words
10
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 None

Resource updated

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
File “po/es/master/pages/LibreOfficeExtensions.po” was added. 5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
%install
install -d -m 755 $RPM_BUILD_ROOT%{_libdir}/libreoffice/share/extensions/%{extname}
unzip -q target/lib/%{extname}.oxt -d $RPM_BUILD_ROOT%{_libdir}/libreoffice/share/extensions/%{extname}
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
%global extname writer2latex
Name: libreoffice-%{extname}
Requires: libreoffice-core
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
+ An example is... +
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
Many extensions are actually architecture independent, but cannot be noarch packages due to libreoffice limitations. Such packages will generate empty debuginfo sub-packages. If this is the case, add '%global debug_package %\{nil}' to the package.
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
Extensions can be written in any language that has an uno binding, e.g. C++, python, java or StarBasic. Consider the additional packaging guidelines of the language that the extension is written in if such guidelines exists. +
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
Extensions are similar to e.g. xorg video drivers in that there exist proprietary or binary only extensions, but of course normal Fedora rules apply to what extensions can be packaged, i.e. see normal packaging licensing etc. rules. The license *Must* be acceptable, and the package *Must* be built from source. +
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
Extensions *Must* be named libreoffice-FOO. +
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
An extension should normally just be able to Require: an appropriate LibreOffice component e.g. libreoffice-core, without a specific n-v-r as extensions use the stable UNO ABI which rarely changes, and then only to add extra APIs. So unless you require a specific feature of a LibreOffice release there is no need to require a specific n-v-r and force a rebuild on every n-v-r of libreoffice. +
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
  3. Spanish
Extensions *Must* be installed unpacked under %\{_libdir}/libreoffice/share/extensions. These are termed bundled extensions. Extensions should not be installed as shared extensions i.e. via unopkg --shared +
 
5 months ago
Browse all translation changes