Bug#645594: This is not a bug, it's a feature!
Ciao! Il Dom, 13 Novembre 2011 1:53 pm, Alexis Huxley ha scritto: It seems to me that bodrato's argument for not changing the code depends on whether one thinks that seconds are important or not. If seconds are important then maybe flite should be telling us what they are! When you say quarter past eight, seconds are not important. But when you express a measure, the concept of error is important. Unless explicitly expressed, the error in a measure is plus or minus a given symmetric range. If bodrato still thinks then code should not be changed, then please feel free to close my bug report; it's not a big issue, and in all other respects I'm very impressed with flite. Thanks. I just think that the current behaviour was not a bug, but was deliberately intended. Moreover, in my opinion, it is correct. A good compromise can be to mention it on the man page, so that surprised users can find it explained. The command: flite_time $(date +%H:%M) will say exactly during both the full minute before and the full minute after the exact time. Regards, Marco -- http://bodrato.it/software/strassen.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645594: This is not a bug, it's a feature!
According to Alexis, the original reporter, flite actually used to say exactly only for 0, but I can't find a trace of that, Alexis? Not quite; I said that, by examining the code, it looked as if there had been (at some earlier time) a different method of working out if rhe word exactly should be used. But from bodrato's explanation regarding seconds, I see that I was interpolating the history of the code's development incorrectly. Sorry for any confusion. So I change my bug report from a bug report to a change request. It seems to me that bodrato's argument for not changing the code depends on whether one thinks that seconds are important or not. If seconds are important then maybe flite should be telling us what they are! And if seconds are not important then the code should be changed so that 4 minutes past is not 5 minutes past. is? That behavior would mean that it is exactly half past four during two whole minutes, is that expected? Of course, when one has *developed* the code then its behaviour seems logical and intuitive, but to the average *user* exactly 5 past at 4 minutes past cannot be expected or logical or intuitive. If bodrato still thinks then code should not be changed, then please feel free to close my bug report; it's not a big issue, and in all other respects I'm very impressed with flite. Thanks. Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645594: This is not a bug, it's a feature!
Hello, (Note to debian-accessibility: we are talking about the flite_time command which speaks the current time) bodr...@mail.dm.unipi.it, le Wed 09 Nov 2011 17:04:51 +0100, a écrit : When should we say exactly? Is 4:30'30 exactly half past four? No, it isn't, because it's 30 second later... But if you ignore seconds, then you can say exactly. What about 30 seconds earlier? 4:29'30 is as far from exactly as 4:30'30 is. That's why the program correctly pronounce the same sentence in both cases: when it is less then one minute before or less than one minute after the exact timing. Right, but is 4:29:01 really as much exactly half past four as 4:30:59 is? That behavior would mean that it is exactly half past four during two whole minutes, is that expected? It seems to me that people usually just look at minutes, not seconds, and would thus accept 4:30:59 as exactly half past four, but not 4:29:01. I hope that the original behaviour will not be changed. According to Alexis, the original reporter, flite actually used to say exactly only for 0, but I can't find a trace of that, Alexis? Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645594: This is not a bug, it's a feature!
Package: flite Followup-For: Bug #645594 When should we say exactly? Is 4m30'30 exactly half past four? No, it isn't, because it's 30 second later... But if you ignore seconds, then you can say exactly. What about 30 seconds earlier? 4m29'30 is as far from exactly as 4m30'30 is. That's why the program correctly pronounce the same sentence in both cases: when it is less then one minute before or less than one minute after the exact timing. I hope that the original behaviour will not be changed. Regards, Marco -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.29-tm290 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages flite depends on: ii dpkg 1.16.1.1 Debian package management system ii install-info 4.13a.dfsg.1-5 Manage installed documentation in ii libasound21.0.24.1-4 shared library for ALSA applicatio ii libc6 2.13-10Embedded GNU C Library: Shared lib ii libflite1 1.4-release-2 a small run-time speech synthesis flite recommends no packages. Versions of packages flite suggests: pn alsa-base none (no description available) -- no debconf information -- http://bodrato.it/papers/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
