I don't really know if it is a RFE or a bug. As shown in the text of bug 9940 (in 'Additional Comments From Ben Bucksch 2001-09-17 00:11'), bugzilla doesn't handle a space in the bug number and doesn't create the correct link. As bug IDs are over 100 000, it should perhaps handle it?
Summary: Bugzilla doesn't handle space in numbers → Bugzilla doesn't handle space when parsing bug IDs
100 000 isn't a number... it's two numbers (one hundred & zero)... bugs should be referenced by numbers (all digits, no spaces/punctuation), not "shorthand". Recommend WONTFIX.
Isn't the comma separated number an american notation ? In France we use a space.
It vary well may be (I'm American, and I use a comma). I think some countries use a period. My take on this is that bug numbers should have NO delimters. There is already a precident for this in Bugzilla as accourding to American grammer rules, any number greater than 9999 has to have a comma in it (the comma is optional at 1,000 but is required at 10,000).
I recommend an underscore. No one uses it (I think), so we aren't biasing towards anyone.
People seem perfectly happy typing bug numbers as e.g. bug 100000, without the need for any separators. ParseUrls has already been rewritten for speed once; I'd be worried about complicating the regexps in it any further. Gerv
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
clearing target on DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as untriaged if they get reopened.
Target Milestone: Future → ---
You need to log in before you can comment on or make changes to this bug.