Package: eog
Version: 2.28.0-1sugi
Severity: normal
eog shows wrong Japanese date string.
patch follows.
--- po/ja.po.orig 2009-10-13 19:12:49.0 +0900
+++ po/ja.po2009-10-13 18:49:17.0 +0900
@@ -607,12 +607,12 @@
#. A strftime-formatted string, to display the date the i
# From: Raphael Hertzog <[EMAIL PROTECTED]>
# Subject: Re: Bug#436693: libdbd-pg-perl: no effect pg_enable_utf8 flag on
string array columns
# Date: Fri, 17 Aug 2007 12:35:27 +0200
> Please can you post sample code demonstrating the bug you're describing?
> Give the code, the expected result and
Package: libdbd-pg-perl
Version: 1:1.49-2
Severity: normal
Hi, mainteiner.
I found a bug on DBD::Pg.
On enabling a pg_enable_utf8 attribute flag and use string array columns such
as text[] or varchar[], not effective encodings convert.
I found probrems on insert, update, select commands.
Perhap
Package: dwww
Version: 1.10.0
Severity: normal
dwww-convert sets charset header at 'text/*' mime_type.
but not english encoding documents fails decide charsets.
every mime_type's 'Content-type:' header shuld have no 'charset=' element.
I deleted at dwww-convert script line 478-486.
Deciding char
Thank you for reassign, Mr.Gunnar Wolf.
I test that test code in some versions of SQL::Statement.
( I got these versions from CPAN )
I've got an error in 1.10, 1.11, 1.12, 1.13, 1.14.
but I've not got an error in version 1.09.
/// Toshinori Su
Package: libdbd-csv-perl
Version: 0.2100-2
Severity: normal
my perl script get error in bellow SQL statement
update tbl set a = a + 1;
when use column name in right side.
I remember that SQL statement had done correctly in Feb/2005.
Error message is:
DBD::CSV::db do failed: Can't use an undef
Package: mew
Version: 1:3.3+0.20040715-5
Severity: wishlist
New Upstream version 4.2 is available.
The up-grade of the package is not done for a long
time, and package a new by all means version, please.
/// Toshinori Sugita --- Digital Pad
7 matches
Mail list logo
