Bug#645594: This is not a bug, it's a feature!
(Note to debian-accessibility: we are talking about the flite_time
command which speaks the current time)
firstname.lastname@example.org, 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
> 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?