Skip Menu |

This queue is for tickets about the Lingua-EN-NameParse CPAN distribution.

Report information
The Basics
Id: 75337
Status: resolved
Priority: 0/
Queue: Lingua-EN-NameParse

People
Owner: kimryan [...] cpan.org
Requestors: lloyd.fourn [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 1.30
Fixed in: (no value)



Subject: tripple initial matches three letter names
When setting the NameParse initials option to 3 the name 'Bob Smith' would have the 'Bob' part interpreted as the initials. It should only be considered initials if its in all caps imo. At the very least if the first letter is in caps and the other letters are in lower case it should be considered to be a name. Thanks. Great module btw! Saved my life.
On Mon Feb 27 05:21:21 2012, M0ast wrote: Show quoted text
> When setting the NameParse initials option to 3 the name 'Bob Smith' > would have the 'Bob' part interpreted as the initials. > > It should only be considered initials if its in all caps imo. At the > very least if the first letter is in caps and the other letters are in > lower case it should be considered to be a name. > > Thanks. Great module btw! Saved my life.
Hi Lloyd, glad you like the module. What you have identified is an ambiguity. What you read as 'Bob' another person will want to read it as 'B.O.B' By setting initials to 3, you are giving the B.O.B case a higher precedence than 'Bob'. So I don't really know how to resolve this ticket. If I code for what you need, it will then be interpreted as a bug for someone else. Also, a lot of data comes in as all capitals, so that makes things more confusing. You could code around this by checking if the name is in title case, then move the number of initials back to only 2. You could also define your own list of known first names in your wrapper code, to help the program understand the data better.
The prgram is working as designed. I have outlined coding approaches to avoid this problem.
From: Lloyd
On Fri May 11 19:50:29 2012, KIMRYAN wrote: Show quoted text
> The prgram is working as designed. I have outlined coding approaches to > avoid this problem.
Thanks. I ended up modifying your code like you said. Works great.
Working as designed, no changes applied.