[pacman-dev] libalpm does not use localized strings
Hi, I just noticed that pacman3 does not use the translated string (libalpm;error.c:96) I got this output: [root@athlon64 pierre]# pacman -Rcs clamav Fehler: Konnte Paket 'clamav' nicht hinzufügen (could not find or read package) Does anybody know why this happens? I checked the de.po file and error.c; both seem to be ok. -- http://www.archlinux.deHi,
On 3/5/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Hi,
I just noticed that pacman3 does not use the translated string (libalpm;error.c:96) I got this output:
[root@athlon64 pierre]# pacman -Rcs clamav Fehler: Konnte Paket 'clamav' nicht hinzufügen (could not find or read package)
Does anybody know why this happens? I checked the de.po file and error.c; both seem to be ok.
Hmm, can you run with --debug and see if all the debug output is untranslated?
Am Montag, 5. März 2007 19:22:48 schrieb Aaron Griffin:
On 3/5/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Hi,
I just noticed that pacman3 does not use the translated string (libalpm;error.c:96) I got this output:
[root@athlon64 pierre]# pacman -Rcs clamav Fehler: Konnte Paket 'clamav' nicht hinzufügen (could not find or read package)
Does anybody know why this happens? I checked the de.po file and error.c; both seem to be ok.
Hmm, can you run with --debug and see if all the debug output is untranslated?
Funny thing; it is only "half" translated: ... Fehlersuche: config: holdpkg: glibc Fehlersuche: config: noupgrade: eclipse/eclipse.ini Fehlersuche: config: new section 'current' Fehlersuche: Registriere Datenbank 'current' Fehlersuche: Öffne Datenbank 'current' Fehlersuche: Öffne Datenbank aus Pfad '/var/lib/pacman/current/' Fehlersuche: adding new server to database 'current': protocol 'ftp', server 'ftp.hosteurope.de', path '/mirror/ftp.archlinux.org/current/os/x86_64' Fehlersuche: config: new section 'extra' Fehlersuche: Registriere Datenbank 'extra' ... -- http://www.archlinux.de
On 3/5/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 3/5/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Hi,
I just noticed that pacman3 does not use the translated string (libalpm;error.c:96) I got this output:
[root@athlon64 pierre]# pacman -Rcs clamav Fehler: Konnte Paket 'clamav' nicht hinzufügen (could not find or read package)
Does anybody know why this happens? I checked the de.po file and error.c; both seem to be ok.
Hmm, can you run with --debug and see if all the debug output is untranslated?
Interesting. I tried this, which gives you the preprocessor output: gcc -I../../ -E alpm.c > alpm_preproc.c And all of the gettext calls are non-existent. It gets subbed out somehow. Then I notice #include config.h was never in this file, thus not enabling NLS (native lang support). Fixed in CVS. TODO: check includes in all files to make sure we are doing them right. We should always include global headers first (and only the ones we need), followed by config.h, and then the alpm headers. And now that I think about it, should config.h always go first, even before global headers? -Dan
On 3/5/07, Dan McGee <dpmcgee@gmail.com> wrote:
TODO: check includes in all files to make sure we are doing them right. We should always include global headers first (and only the ones we need), followed by config.h, and then the alpm headers. And now that I think about it, should config.h always go first, even before global headers?
I have some header cleanup on the way that is really needed- we had all sorts of issues with this as soon as I started reordering them (not present includes, etc.). -Dan
On 3/5/07, Pierre Schmitz <pierre@archlinux.de> wrote:
Hi,
I just noticed that pacman3 does not use the translated string (libalpm;error.c:96) I got this output:
[root@athlon64 pierre]# pacman -Rcs clamav Fehler: Konnte Paket 'clamav' nicht hinzufügen (could not find or read package)
Does anybody know why this happens? I checked the de.po file and error.c; both seem to be ok.
Steps to debug this kind of issue: 1. grep the source used to build the package (located at www.archlinux.org/~dan/pacman/) for the English string- see if it is gettextized, which means it will have the _( ) function call around it. 2. If it is, check the de.po files for this message and ensure it is not marked fuzzy; if it is update it and submit a patch. -Dan
Am Montag, 5. März 2007 19:24:47 schrieb Dan McGee:
2. If it is, check the de.po files for this message and ensure it is not marked fuzzy; if it is update it and submit a patch.
Well there are some "fuzzy" messages. Did not know that this will prevent them from beeing used. (just thought this is just a hint for the translators to review that translation) -- http://www.archlinux.de
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Pierre Schmitz