Phone number detection should be a lot less sensitive
Almost every number in an event description is detected as phone number. This is especially bad with dates and times. The following are all detected as phone numbers:
10.06.
15.02.2018
15:20-15:45
09120
A phone number should have a reasonable minimum length (6+ digits?) and common pattern that are not phone numbers should be excluded (such as YYYY-MM-DD, DD.MM.YYYY, ...).
4
votes
Felix Eckhofer
shared this idea
-
Matt Martin
commented
YES! I often have the time of the event in the description field (e.g., 1230-1300) and BC2 sees it as a phone number. This needs to be fixed, please!