From: "ldv at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/27450] Update Polish translation
Date: Sat, 06 Mar 2021 03:00:27 +0000 [thread overview]
Message-ID: <bug-27450-10460-ayxr6CJVjz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27450-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27450
--- Comment #8 from Dmitry V. Levin <ldv at sourceware dot org> ---
(In reply to Mark Wielaard from comment #7)
> Two questions:
>
> 1) How should we manage the POTFILES? How did you note the missing files?
> Can this be automated somehow?
I was using
$ git grep -El '\<(_|[ns]gettext) *\("'
On the current master, it says the following files should be added:
$ grep '^[^#]' po/POTFILES.in |sort -u | \
comm -13 - <(git grep -El '\<(_|[ns]gettext) *\("')
libcpu/i386_lex.l
libcpu/i386_parse.y
It also says the following listed files don't contain translations:
$ grep '^[^#]' po/POTFILES.in |sort -u | \
comm -23 - <(git grep -El '\<(_|[ns]gettext) *\("')
libdw/dwarf_error.c
libdwfl/libdwflP.h
libelf/elf_error.c
src/elfcompress.c
src/stack.c
tests/backtrace.c
tests/dwflmodtest.c
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-06 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 13:48 [Bug general/27450] New: " piotrdrag at gmail dot com
2021-02-21 13:49 ` [Bug general/27450] " piotrdrag at gmail dot com
2021-02-21 13:57 ` piotrdrag at gmail dot com
2021-02-21 14:35 ` piotrdrag at gmail dot com
2021-02-21 14:35 ` piotrdrag at gmail dot com
2021-02-21 21:01 ` ldv at sourceware dot org
2021-02-22 15:27 ` piotrdrag at gmail dot com
2021-02-22 15:28 ` piotrdrag at gmail dot com
2021-03-06 2:30 ` mark at klomp dot org
2021-03-06 3:00 ` ldv at sourceware dot org [this message]
2021-03-06 10:34 ` piotrdrag at gmail dot com
2021-03-06 10:53 ` ldv at sourceware dot org
2021-03-06 13:48 ` mark at klomp dot org
2021-03-06 13:49 ` mark at klomp dot org
2021-03-07 11:30 ` piotrdrag at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27450-10460-ayxr6CJVjz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).