bug#3190: marked as done (parse-time-string chokes on unicode day/month names)

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]


Your message dated Sun, 16 Aug 2009 10:37:10 -0400
with message-id <877hx325bd.fsf@cyd.mit.edu>
and subject line Re: parse-time-string chokes on unicode day/month names
has caused the Emacs bug report #3190,
regarding parse-time-string chokes on unicode day/month names
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3190: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3190
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 6430 bytes --]

From: Jan Seeger <jan.seeger@thenybble.de>
To: bug-gnu-emacs@gnu.org
Subject: parse-time-string chokes on unicode day/month names
Date: Sat, 02 May 2009 15:58:16 +0200
Message-ID: <874ow31u9z.wl%jan.seeger@thenybble.de>


Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

parse-time-string skips unicode characters in date strings. Example:

(setq german-month-names
      '(("jan" . 1)
	("feb" . 2)
	("m=E4r" . 3)
	("apr" . 4)
	("mai" . 5)
	("jun" . 6)
	("jul" . 7)
	("aug" . 8)
	("sep" . 9)
	("okt" . 10)
	("nov" . 11)
	("dez" . 12)))

(mapc (lambda (x) (add-to-list 'parse-time-months x))
      seeger-german-month-names)

(parse-time-string "Sa, 02 M=E4r 2009 15:05:24 +0200")
 -> (24 5 15 2 nil 2009 6 nil 7200)

Expected:

(24 5 15 2 nil 2009 6 3 7200)

This error is due to parse-time-string chars using the parse-tim-syntax tab=
le to check for valid characters.

Regards,
Jan Seeger

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/22.3/etc/DEBUG for instructions.


In GNU Emacs 22.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.14.7)
 of 2009-04-24 on dumper
Windowing system distributor `The X.Org Foundation', version 11.0.10503000
configured using `configure  '--prefix=/usr' '--host=x86_64-pc-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--program-suffix=-emacs-22' '--infodir=/usr/share/info/emacs-22' '--without-carbon' '--with-sound' '--with-x' '--without-toolkit-scroll-bars' '--with-jpeg' '--without-tiff' '--with-gif' '--with-png' '--with-xpm' '--with-x-toolkit=gtk' '--without-hesiod' '--without-kerberos' '--without-kerberos5' '--libdir=/usr/lib64' '--build=x86_64-pc-linux-gnu' 'build_alias=x86_64-pc-linux-gnu' 'host_alias=x86_64-pc-linux-gnu' 'CFLAGS=-O2 -pipe -march=nocona' 'LDFLAGS=-Wl,-O1''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: de_DE.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Major mode: Text

Minor modes in effect:
  show-paren-mode: t
  display-time-mode: t
  shell-dirtrack-mode: t
  display-battery-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t

Recent input:
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-j C-j C-p C-x C-f ~ / . d e a <backspace> 
<backspace> <backspace> d <backspace> <backspace> d 
e a d <return> C-n C-n C-s e m a c s C-s C-s C-n C-n 
C-s C-s C-s C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-p C-p C-p C-p C-p C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-a C-SPC C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n 
C-n C-n C-n C-p M-w <S-down> C-x b <return> C-y C-p 
C-p M-< M-f C-f J <backspace> SPC J a n SPC S e e g 
e r C-c C-c y q C-h f C-g C-h v e r <backspace> <backspace> 
r e <tab> p <tab> o r t - e m a c s <tab> C-g M-x r 
e p o r t - e m <tab> <return>

Recent messages:
Mark saved where search started [2 times]
Mark set
Auto-saving...done
Success: Get.
Mark set [2 times]
Send this bug report to the Emacs maintainers? (y or n) 
Exit MIME editor mode.
Sending...done
Quit
Making completion list... [2 times]
Quit




[-- Attachment #3: Type: message/rfc822, Size: 1361 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Jan Seeger <jan.seeger@thenybble.de>
Cc: 3190-done@emacsbugs.donarmstrong.com
Subject: Re: parse-time-string chokes on unicode day/month names
Date: Sun, 16 Aug 2009 10:37:10 -0400
Message-ID: <877hx325bd.fsf@cyd.mit.edu>

> I have written a quick fix for parse-time.el that uses POSIX character
> classes instead of a vector. I'm a novice elisp hacker, so if there's
> anything wrong with this patch, tell me.

Thanks for pointing out the problem.  I've reworked the patch, and
checked it into CVS trunk.