[pacman-dev] pacman 3 cvs output issues
Hello, i'm using CVS version of pacman and have some output issues (they are locale specific). My locale is ru_RU.UTF-8 and pacman handles this locale incorrectly at least in two places - trans.c and util.c output of pacman -Qi gtk2: .... Зависит от : libtiff>=3.8.2 atk>=1.11.4 pango>=1.12.1 libxcursor libxinerama libxrandr Удаляет : Не указано Требуется пакетами : mozilla-firefox xchat ettercap ethereal mlterm gvim fluxconf libglade librsvg trayer gqview .... this is `Depends On' and `Required By' in english - they break at multiline display because of incorrect string length calculation (function list_display @ util.c). output of pacman -Ss lsof: .... убираем за собой... готово. (1/1) проверка конфликтов файлов [###########] 100% (1/1) обновление lsof [###########] 100% .... This is `Cleaning up... done.', `checking for file conflicts' and `upgrading lsod' in english. i'm attaching a very simple (and very dirty) patch for this issue - hope it helps :)
Am Sonntag, 18. März 2007 12:51:34 schrieb shild:
Hello, i'm using CVS version of pacman and have some output issues (they are locale specific). My locale is ru_RU.UTF-8 and pacman handles this locale incorrectly at least in two places - trans.c and util.c
This is related to this bug: http://bugs.archlinux.org/task/6437 I think this has to be fixed in a more generic way. (full utf8 support) -- http://www.archlinux.de
On 3/18/07, shild <sxp@bk.ru> wrote:
Hello, i'm using CVS version of pacman and have some output issues (they are locale specific). My locale is ru_RU.UTF-8 and pacman handles this locale incorrectly at least in two places - trans.c and util.c
Appreciate your patch, but for now we are going to hold this out of pacman 3.0. I know its annoying but it is just a cosmetic issue. :) However, this is something pretty high on my TODO list for 3.1- I'd like to ensure everything is fully internationalized, including dates, floating point numeric values, and text output. If you look at the CVS history on these files, you'll see my feeble attempts to solve the problems. If you are interested at looking at it more and ensuring it is fixed everywhere, that would be awesome. I'm looking at your patch a bit more to see what was done, I swear I tried similar things. -Dan
participants (3)
-
Dan McGee
-
Pierre Schmitz
-
shild