Eric Lee / smarc-fsl-linux-kernel

07 Jun, 2011

1 commit

01 Oct, 2010

1 commit

20 Sep, 2009

1 commit

11 Apr, 2009

1 commit

  • 612c280ef   kconfig: fix update-po-config to accect backslash in input ... Browse Code »

    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
    Tested-by: Massimo Maiurana
    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

26 Jul, 2007

1 commit

  • 03d291227   kconfig: attach help text to menus ... Browse Code »

    Roman Zippel wrote:
    > A simple example would be
    > help texts, right now they are per symbol, but they should really be per
    > menu, so archs can provide different help texts for something.

    This patch does this and at the same time introduce a few API
    funtions used to access the help text.

    The relevant api functions are introduced in the various frontends.

    Signed-off-by: Sam Ravnborg
    Cc: Roman Zippel

    Sam Ravnborg
     

17 Jul, 2007

1 commit

  • b70e325cf   kconfig: fix update-po-config ... Browse Code »

    Massimo Maiurana reported that
    update-po-config was broken:
    1) spelling errors in Makefile so arch/um failed
    2) UTF-8 was not supported

    The following patch address the above problems.
    kxgettext now append the output to the .pot file
    generated by xgettext - so we have a header.
    In all places UFT-8 is specifed so we now flawlessly
    support UTF-8.
    The Kconfig files had an empty string in a few cases -
    these are now supressed in kxgettext.

    With this the translators can now pick up where they left
    and get it all translated.
    There are ~11000 strings to be translated...

    Signed-off-by: Sam Ravnborg
    Cc: Massimo Maiurana
    Cc: Arnaldo Carvalho de Melo

    Sam Ravnborg
     

05 Sep, 2005

2 commits

  • 964267e62   [PATCH] kconfig: kxgettext: EOL fix ... Browse Code »

    The end of line character doesn't exist on end of help in all case, check it
    first.

    Signed-off-by: Egry Gabor
    Cc: Arnaldo Carvalho de Melo
    Cc: Roman Zippel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Egry Gabor
     
  • c196eff30   [PATCH] kconfig: kxgettext: message fix ... Browse Code »

    The gettext doesn't handle the {CONFIG}:00000 markers as sources. I added a
    simple comment prefix for them.

    Signed-off-by: Egry Gabor
    Cc: Arnaldo Carvalho de Melo
    Cc: Roman Zippel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Egry Gabor
     

06 May, 2005

1 commit

  • 3b9fa0931   [PATCH] Kconfig i18n support ... Browse Code »

    This patch adds i18n support for make *config, allowing users to have the
    config process in their own language.

    No printk was harmed in the process, don't worry, so all the bug reports,
    kernel messages, etc, remain in english, just the user tools to configure
    the kernel are internationalized.

    Users not interested in translations can just unset the related LANG,
    LC_ALL, etc env variables and have the config process in plain english,
    something like:

    LANG= make menuconfig

    is enough for having the whole config process in english. Or just don't
    install any translation file.

    Translations for brazilian portuguese are being done by a team of
    volunteers at:

    http://www.visionflex.inf.br/kernel_ptbr/pmwiki.php/Principal/Traducoes

    To start the translation process:

    make update-po-config

    This will generate the pot template named scripts/kconfig/linux.pot,
    copy it to, say, ~/es.po, to start the translation for spanish.

    To test your translation, as root issue this command:

    msgfmt -o /usr/share/locale/es/LC_MESSAGES/linux.mo ~/es.po

    Replace "es" with your language code.

    Then execute, for instance:

    make menuconfig

    The current patch doesn't use any optimization to reduce the size of the
    generated .mo file, it is possible to use the config option as a key, but
    this doesn't prevent the current patch from being used or the translations
    done under the current scheme to be in any way lost if we chose to do any
    kind of keying.

    Thanks to Fabricio Vaccari for starting the pt_BR (brazilian portuguese)
    translation effort, Thiago Maciera for helping me with the gconf.cc (QT
    frontent) i18n coding and to all the volunteers that are already working on
    the first translation, to pt_BR.

    I left the question on whether to ship the translations with the stock kernel
    sources to be discussed here, please share your suggestions.

    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arnaldo Carvalho de Melo