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) CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 0
Finnish CC-BY-SA-3.0 0 0 0 0 0 0 0
French CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 0
Japanese CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 0
Portuguese (Brazil) CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 0
Spanish CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 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 ea88fe2ed
♪ I'm a bot, bot, bot ♪ authored a month 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
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 70 1,722 12,418
Source 10 246 1,774
Translated 28% 20 28% 492 28% 3,548
Needs editing 0% 0 0% 0 0% 0
Read-only 14% 10 14% 246 14% 1,774
Failing checks 1% 1 1% 5 1% 20
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 71% 50 71% 1,230 71% 8,870
Last 12 months Previous

Activity in last 12 months

3 changes 0 changes 17 changes 0 changes 0 changes 0 changes 10 changes 0 changes 19 changes 0 changes 3 changes 0 changes 2 changes 0 changes 0 changes 12 changes 0 changes 0 changes 21 changes 0 changes 2 changes 1 change 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

1,722
Hosted words
70
Hosted strings
28%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Alert triggered

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/LibreOfficeExtensions
Component seems unused. 2 months ago
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
Browse all component changes