Translation template file needs to be updated
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- perl
- Domain
- internationalization, localization
Research direction
The translation template is po/debbuild.pot, and the strings come from the Perl sources under the debbuild directory. Run the xgettext command from the issue at the repository root, then diff the output against po/debbuild.pot to find the roughly 10 missing strings. Check that the --package-version value matches the current release. Done when the regenerated POT contains the missing strings and the diff is committed.
Written by the indexing model from the issue text.
Description
po/debbuild.pot last update happened 4 years ago, and a local update test showed me that 10 strings should be available for translation and are not.
Please notice that the Fedora Weblate needs the POT file to be up-to-date in order to provide these translation strings for translations.
So please consider updating it and also making it a step of the release workflow, in order to assure translations can contribute.
Now, how to generate the POT? I didn't find a script, Makefile target or documentation, so for my local tests I used the following command (from the repository root directory):
xgettext \
--language=Perl \
--keyword=_ \
--output=po/debbuild.pot \
--copyright-holder="Andreas Scherer" \
--package-name=DEBBUILD \
--package-version=23.12.0 \
--msgid-bugs-address=https://github.com/debbuild/debbuild/issues \
debbuild
- Dominant language
- Perl
- Stars
- 66
- Forks
- 26
- Avg merge
- 26m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from debbuild/debbuild
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Pick up flags from dpkg-buildflagsMay be free again @Conan-Kudo claimed this 1044 days ago, and no pull request is open. Open
All issues in debbuild/debbuild
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day