[pacman-dev] Translation problem
Hi, I participated in the German translation of pacman3. So far, we haven't been able to make sense out of the following lines: #: lib/libalpm/conflict.c:201 #, c-format msgid "target '%s' is also in target list, using NEW conflicts" I assume there is a reason for using capital letters here - some fixed convention I simply don't know about. So what exactly does NEW refer to? Capital letters also appear as "DESC", "FILES" and "DEPENDS" - any explanation for a non-programmer would be welcome.
On 4/10/07, Matthias Gorissen <siquame@web.de> wrote:
Hi,
I participated in the German translation of pacman3. So far, we haven't been able to make sense out of the following lines:
#: lib/libalpm/conflict.c:201 #, c-format msgid "target '%s' is also in target list, using NEW conflicts"
I assume there is a reason for using capital letters here - some fixed convention I simply don't know about. So what exactly does NEW refer to? Capital letters also appear as "DESC", "FILES" and "DEPENDS" - any explanation for a non-programmer would be welcome.
Not sure why NEW is capitalized, but the reason for the other three is probably because these are files that exist in the pacman DB. Take a look at the files listed under /var/lib/pacman/local/*/ (just pick a package directory). -Dan
Am Dienstag 10 April 2007 20:55:35 schrieb Dan McGee:
Not sure why NEW is capitalized, but the reason for the other three is probably because these are files that exist in the pacman DB. Take a look at the files listed under /var/lib/pacman/local/*/ (just pick a package directory).
-Dan
Yepp, I see what you mean - but the mystery about NEW remains. I simply assumed that there must an equivalent NEW file (which I cannot find) - and to assume that NEW was capitalized accidentally doesn't make sense either: Why should pacman use "new conflicts"? I thought it should read "NEW conflicts [with %S]" Still clueless, Matt
On 4/10/07, Matthias Gorissen <siquame@web.de> wrote:
Am Dienstag 10 April 2007 20:55:35 schrieb Dan McGee:
Not sure why NEW is capitalized, but the reason for the other three is probably because these are files that exist in the pacman DB. Take a look at the files listed under /var/lib/pacman/local/*/ (just pick a package directory).
-Dan
Yepp, I see what you mean - but the mystery about NEW remains. I simply assumed that there must an equivalent NEW file (which I cannot find) - and to assume that NEW was capitalized accidentally doesn't make sense either: Why should pacman use "new conflicts"? I thought it should read "NEW conflicts [with %S]"
Still clueless, Matt
Best guess is that someone just wanted to accent the fact that it was new. Basically boldface on the console. -Dan
On 4/10/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 4/10/07, Matthias Gorissen <siquame@web.de> wrote:
Am Dienstag 10 April 2007 20:55:35 schrieb Dan McGee:
Not sure why NEW is capitalized, but the reason for the other three is probably because these are files that exist in the pacman DB. Take a look at the files listed under /var/lib/pacman/local/*/ (just pick a package directory).
-Dan
Yepp, I see what you mean - but the mystery about NEW remains. I simply assumed that there must an equivalent NEW file (which I cannot find) - and to assume that NEW was capitalized accidentally doesn't make sense either: Why should pacman use "new conflicts"? I thought it should read "NEW conflicts [with %S]"
Still clueless, Matt
Best guess is that someone just wanted to accent the fact that it was new. Basically boldface on the console.
-Dan
Yeah, feel free to ignore it.
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Matthias Gorissen