From: Massimo Maiurana <maiurana@gmail.com>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: kconfig: update-po-config broken in 2.6.29
Date: Tue, 07 Apr 2009 20:56:36 +0200 [thread overview]
Message-ID: <49DBA1E4.8000502@gmail.com> (raw)
hi,
in latest 2.6.29 "make update-po-config" fails at msguniq invocation
with an "invalid control sequence" error.
the offending string is the following, and it's located in
drivers/staging/panel/Kconfig:72:
"'\e[L' which are specific to the LCD, and a few ANSI codes. The"
looks to me like gettext expects strings in printf format, so in
this case it thinks "\e" is a control sequence but doesn't recognise
it as a valid one.
I can still obtain a suitable linux.pot file escaping the backslash,
and the resulting linux.mo file works even if the string is again
unescaped, but of course if I leave the escaped string it will be
displayed as-is (with a double backslash) if i run a configurator in
english, so it is not a valid solution for a patch.
Maybe a valid solution would be to tell kxgettext to automatically
escape this kind of strings in the */config.pot he produces, so that
msguniq would not complain?... I don't really know, and I don't even
know how to do it. I see there is an escape function right at the
top of kxgettext.c, but as I'm not a coder I don't really know how
to hack it, so it's up to you... sorry.
--
Massimo Maiurana massimo<at>ragusa.linux.it
http://massimo.solira.org GPG keyID #7044D601
Articolo 33 - [...]Enti e privati hanno il diritto di istituire
scuole ed istituti di educazione, senza oneri per lo Stato.[...]
next reply other threads:[~2009-04-07 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 18:56 Massimo Maiurana [this message]
2009-04-07 19:17 ` kconfig: update-po-config broken in 2.6.29 Sam Ravnborg
2009-04-07 19:39 ` Massimo Maiurana
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=49DBA1E4.8000502@gmail.com \
--to=maiurana@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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