[pacman-dev] Updated German translation
Hi, I synchronized the German translation to current pacman-cvs: http://svn.laber-land.de/pacman-de/trunk/lib/libalpm/po/de.po http://svn.laber-land.de/pacman-de/trunk/src/pacman/po/de.po BTW: I think for pacman 3.1 it would be nice to include alle user visible into one po-file and get rid of an libalpm po-file. We should left all debugging messages untranslated. This would make it a lot easier to write bug-reports. -- http://www.archlinux.de
On 3/3/07, Pierre Schmitz
BTW: I think for pacman 3.1 it would be nice to include alle user visible into one po-file and get rid of an libalpm po-file. We should left all debugging messages untranslated. This would make it a lot easier to write bug-reports.
Any message that goes to the user (normally) should not be in the backend- I really want to not need to use gettext in the backend, I think that would make a lot more sense. We'll try to figure out a solution to all of this once we start really tearing into the code. -Dan
Am Samstag, 3. März 2007 10:02:10 schrieb Dan McGee:
On 3/3/07, Pierre Schmitz
wrote: BTW: I think for pacman 3.1 it would be nice to include alle user visible into one po-file and get rid of an libalpm po-file. We should left all debugging messages untranslated. This would make it a lot easier to write bug-reports.
Any message that goes to the user (normally) should not be in the backend- I really want to not need to use gettext in the backend, I think that would make a lot more sense. We'll try to figure out a solution to all of this once we start really tearing into the code.
-Dan
In addition to this the backend or model should never communicate with the user. So every print statement in libalpm should be removed. -- http://www.archlinux.de
On 3/3/07, Pierre Schmitz
In addition to this the backend or model should never communicate with the user. So every print statement in libalpm should be removed.
We're well aware of these issues.
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Pierre Schmitz