On Fri, 01 Dec 2006 13:20:11 -0800 Alex Roitman <[EMAIL PROTECTED]> wrote:
> A minor point: if you would like to send/attach a testcase, > please export into XML format. The file you attached is not > protable: it does not open outside the environment and that > only exists on your user account on your machine. Sorry about that, I wasn't sure whether 'gramps' default format was portable or not, or why. If it helps, attached is an XML export of the same database. > > The bug > > should be self-explanatory -- the child was born over 200 years > > before their 6 year old parent. > > I don't think this is a bug, although I see your point. > This is an error during data entry. We could add a feature > checking for things like this. > > > The suggested fix would be for 'gramps' to check for obvious > > contradictions in input, then inform the user. > > Yes. Not the fix though, but rather the feature. Gramps did exactly > what you asked it to do. If you misspell the words in your email > client, you would not call it bugs of your email client. You would > call them typos. The spell-checking is a useful feature that may or > may not be added. You're absolutely right, given that definition; it's a usage question. Debian uses the term 'bug' to encompass a broad (maybe too broad) range of software "issues". The ordinary usage of 'bug' is just as you say, a program not acting as intended due to some subtle design or coding error. Yet in Debian, a bug might be a wishlist feature, a typo, a design critique, you name it. Usage aside, I hadn't intended to imply that 'gramps' failed to meet its design or coding goals. The new 'wishlist' tag is unobjectionable, but I'd picked 'normal' as, IMHO, software should observe certain ranges of norms for input parsing and error checking, depending on how high-level the application is. System level software is often pretty rough, and "Garbage In, Garbage Out" is the rule, but I feel that a good GUI interface should strive to save users from themselves. Where to draw the line between user friendly interface design and GIGO is an open and developing topic on which reasonable people can disagree. BTW, I have noticed before that this broad usage of "bug" may irritate some Debian developers, who tend to have the same reactions. "The program works as designed, therefore if it doesn't work as a user expects, don't blame (or en-bug) my program." Other DD's feel it's a question of maintainer education -- DDs who don't know what a Debian "bug" means ought to know better. Still, perhaps Debian might be better served by a more narrow definition, in which case the broad definition would itself become a BTS bug/design flaw. Either way (indoctrination or reform) would be fine with me.
Impossible Family.xml
Description: application/xml
