Bug#328699: wmppp.app: Displays truncated connection speed when speed is too high

2005-09-16 Thread jguiton
Package: wmppp.app
Version: 1.3.0-7
Severity: normal
Tags: patch

When the download speed is too high, wmppp can't display it because it has
only 5 digit. The most significant digits are hidden !

This small patch display the speed in K when it is too high.


diff -ru wmppp.app-1.3.0/wmppp/wmppp.c wmppp.app-1.3.0.new/wmppp/wmppp.c
--- wmppp.app-1.3.0/wmppp/wmppp.c   2005-09-16 21:55:42.469298984 +0200
+++ wmppp.app-1.3.0.new/wmppp/wmppp.c   2005-09-16 22:05:03.281042640 +0200
@@ -770,6 +770,11 @@
 void PrintLittle(int i, int *k) {
 
switch (i) {
+   case -2:
+   *k -= 5;
+   /* Print the k letter */
+   copyXPMArea(11*5-5, 86, 4, 9, *k, 48);
+   break;
case -1:
*k -= 5;
copyXPMArea(13*5-5, 86, 4, 9, *k, 48);
@@ -838,6 +843,13 @@
 
k = 30;
 
+   /* If speed is greater than 9, display it in K */
+   if (speed  9 )
+   {
+   speed /= 1024 ;
+   PrintLittle(-2, k) ;
+   }
+
do {
PrintLittle(speed % 10, k);
speed /= 10;



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8.custom
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages wmppp.app depends on:
ii  libc6   2.3.5-6  GNU C Library: Shared libraries an
ii  ppp 2.4.3-20050321+2 Point-to-Point Protocol (PPP) daem
ii  xlibs   6.8.2.dfsg.1-6   X Window System client libraries m

wmppp.app recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#274571: gqmpeg: Accented characters breaks menus and GUI

2005-07-23 Thread jguiton
Package: gqmpeg
Version: 0.90.0-2
Severity: important
Tags: patch l10n

GTK2 needs UTF-8 strings. So we must call :

bind_textdomain_codeset(PACKAGE, UTF-8) ;

to ensure internal strings will be retrieved and converted from .po
files to UTF-8 codeset.

When we do that, menus and widgets will be ok, but messages printed on
stdout will be in UTF-8 altogether, which is ugly if your locale is
different.

So we must change all printf(_(...)) calls to g_print(_(...)) calls.
For consistency we can remove the print_term() function, and replace it
also by g_print.

I include a diff -ru of the corrections.

Hope this helps.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8.custom
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages gqmpeg depends on:
ii  libatk1.0-01.8.0-4   The ATK accessibility
toolkit ii  libc6  2.3.2.ds1-22  GNU C Library:
Shared libraries an ii  libglib2.0-0   2.6.4-1   The
GLib library of C routines ii  libgtk2.0-02.6.4-3  
The GTK+ graphical user interface  ii  libpango1.0-0  1.8.1-1   
   Layout and rendering of internatio ii  libpng12-0
1.2.8rel-1PNG library - runtime ii  libx11-6  
4.3.0.dfsg.1-14   X Window System protocol client li ii  mpg321 [mpg123]
   0.2.10.3  A Free command-line mp3 player, co ii 
vorbis-tools   1.0.1-1.3 Several Ogg Vorbis Tools ii 
xlibs  4.3.0.dfsg.1-14   X Keyboard Extension (XKB)
configu ii  zlib1g 1:1.2.2-4.sarge.2 compression library
- runtime

-- no debconf information
diff -ru gqmpeg-0.90.0/src/io_mpg123.c gqmpeg-0.90.0.new/src/io_mpg123.c
--- gqmpeg-0.90.0/src/io_mpg123.c   2004-03-13 12:00:11.0 +0100
+++ gqmpeg-0.90.0.new/src/io_mpg123.c   2005-07-23 13:22:57.0 +0200
@@ -156,9 +156,9 @@
mpg123_version = MPG123_VER_0_59O;
if (debug_mode || !warning_done)
{
-   printf(_(mpg123 version prior to 0.59o 
found!\n));
-   printf(_(assuming 0.59o compatible\n));
-   printf(_(The version line reported 
was:\n%s\n), text);
+   g_print(_(mpg123 version prior to 0.59o 
found!\n));
+   g_print(_(assuming 0.59o compatible\n));
+   g_print(_(The version line reported 
was:\n%s\n), text);
}
warning_done = TRUE;
}
@@ -168,13 +168,13 @@
mpg123_version = MPG123_VER_UNKNOWN;
if (debug_mode || !warning_done)
{
-   printf(_(unknown version of mpg123, assuming 
%s compatible\n), MPG123_VER_STRING);
-   printf(_((GQmpeg requires mpg123 0.59o or 
later)\n));
-   printf(_(The version line reported 
was:\n%s\n), text);
+   g_print(_(unknown version of mpg123, assuming 
%s compatible\n), MPG123_VER_STRING);
+   g_print(_((GQmpeg requires mpg123 0.59o or 
later)\n));
+   g_print(_(The version line reported 
was:\n%s\n), text);
}
warning_done = TRUE;
}
-   if (debug_mode) printf(_(mpg123 version detected: %d\n), 
mpg123_version);
+   if (debug_mode) g_print(_(mpg123 version detected: %d\n), 
mpg123_version);
 
return TRUE;
}
@@ -427,7 +427,7 @@
/* ignore lines that begin with an escape sequence (0.59r) */
if (text[0] == 27  text[1] == ']') return;
 
-   printf(_(Warning, unrecognized mpg123 output:\%s\\n), text);
+   g_print(_(Warning, unrecognized mpg123 output:\%s\\n), text);
 
if (debug_mode)
{
@@ -497,7 +497,7 @@
{
gchar *buf;
 
-   printf(_(Error, mpg123 reported:\%s\\n), text);
+   g_print(_(Error, mpg123 reported:\%s\\n), text);
buf = g_strdup_printf(mpg123: %s, text);
warning_dialog(_(GQmpeg: mpg123 error), buf);
g_free(buf);
@@ -519,7 +519,7 @@
 
 static void handle_end_of_file(void)
 {
-   printf(_(mpg123 disappeared! (unexpected EOF)\n));
+   g_print(_(mpg123 disappeared! (unexpected EOF)\n));
stop_playing_file();
module_playback_error(current_sd);
current_sd = NULL;
@@ -527,7 +527,7 @@
 
 static void handle_read_error(void)
 {
-   printf(_(error reading from mpg123!\n));
+   g_print(_(error reading from mpg123!\n));
stop_playing_file();
module_playback_error(current_sd);
current_sd = NULL;
@@ 

Bug#319266: wily: The win tool doesn't start --- correction

2005-07-20 Thread jguiton
Package: wily
Version: 0.13.41-6
Severity: normal
Tags: patch

*** Please type your report below this line ***

Oups, I filed the bug #318828 too quickly...

The patch I suggested was more a symptom than a solution.

If I understand well, the problem is that, on my custom kernel, I did
not enable /dev/ptyxx, only the new /dev/ptmx one :.

--- extract from my kernel config :
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set

But the script wily-0.13.41/tools/win/configure doesn't detect
/dev/ptmx. In fact it produces the following (non fatal) error message :
/bin/test not found... On Debian test is in /usr/bin, not /bin.

Looking at the configure script, the only place where /bin/test is
used, is when we are trying to find if /dev/ptmx is used... In every
other place, there's no path before test. 

The win binary can be correctly compiled on my system if :
1. I change /bin/test in test in the configure script
2. I suppress the config.cache file which is curiously provided in
   wily_0.13.41.orig.tar.gz
3. I run a fresh new configure, then make.

Of course the correction must be done in configure.in also.

I don't know if there is a way to provide a binary package working on
all systems, independantly of the kernel configuration.

Hope this helps.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8.custom
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages wily depends on:
ii  libc62.3.2.ds1-22GNU C Library: Shared
libraries an ii  xlibs4.3.0.dfsg.1-14 X Keyboard
Extension (XKB) configu

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#318828: wily: The win tool doesn't start.

2005-07-18 Thread jguiton
Package: wily
Version: 0.13.41-6
Severity: normal
Tags: patch


Lauching the win tool from wily fail with the message :

win: unable to open master pty at win.c:729 in __FUNCTION__()

Recompiling from Debian sources gives the same error. But if I add the
-DHAVE_DEV_PTMX=1 option in the Makefile for win, it works. Below is the very
small diff -u :


--- wily-0.13.41/tools/win/Makefile 2005-07-17 23:41:49.103931704 +0200
+++ wily-0.13.41.ok/tools/win/Makefile  2005-07-18 00:08:15.000838728 +0200
@@ -13,7 +13,7 @@
 
 CC = gcc
 CFLAGS = -g -O2 -Wall -I../.. -I$(srcdir)/../../include
-DEFS   =  -DHAVE_LIBNSL=1 
+DEFS   =  -DHAVE_LIBNSL=1 -DHAVE_DEV_PTMX=1
 LIBS   = -lnsl  ../../libmsg/libmsg.a  ../../libXg/libXg.a
 LDFLAGS= 
-
 
The win compiled with -DHAVE_DEV_PTMX=1 runs fine and give a shell in wily,
as expected.

By the way, the above error message shows that the code
stringize(__FUNCTION__) doesn't work. It stops gcc warnings about __FUNCTION__
beeing deprecated, but don't replace __FUNCTION__ with the real name of the C
function.

May you excuse my bad english and be thanked for your work.



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8.custom
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages wily depends on:
ii  libc62.3.2.ds1-22GNU C Library: Shared libraries an
ii  xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]