diff options
author | Sam Ravnborg <sam@ravnborg.org> | 2009-04-08 02:42:48 -0400 |
---|---|---|
committer | Sam Ravnborg <sam@ravnborg.org> | 2009-04-11 02:18:07 -0400 |
commit | 612c280ef2400c70ea2fd8f2e17549c95002368c (patch) | |
tree | f4c3ad90864f58aa8098c313d21d6638907058f5 /scripts | |
parent | 79ff807cf23ffb527f3f35bdececf56cabcdee07 (diff) |
kconfig: fix update-po-config to accect backslash in input
Massimo Maiurana reported (slightly edited):
=====
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.
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.
=====
This patch implements the suggested escaping.
Reported-by: Massimo Maiurana <maiurana@gmail.com>
Tested-by: Massimo Maiurana <maiurana@gmail.com>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'scripts')
-rw-r--r-- | scripts/kconfig/kxgettext.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/scripts/kconfig/kxgettext.c b/scripts/kconfig/kxgettext.c index 6eb72a7f2562..8d9ce22b0fc5 100644 --- a/scripts/kconfig/kxgettext.c +++ b/scripts/kconfig/kxgettext.c | |||
@@ -43,6 +43,10 @@ static char *escape(const char* text, char *bf, int len) | |||
43 | ++text; | 43 | ++text; |
44 | goto next; | 44 | goto next; |
45 | } | 45 | } |
46 | else if (*text == '\\') { | ||
47 | *bfp++ = '\\'; | ||
48 | len--; | ||
49 | } | ||
46 | *bfp++ = *text++; | 50 | *bfp++ = *text++; |
47 | next: | 51 | next: |
48 | --len; | 52 | --len; |