Truncation bug?

Question

Looks like Balsor-40 has "extra" spaces in Nickname and then WikiTree display
Eliza "Jane " "Jane" Balsor

I guess we need some truncation of names in the fields  

This profile was created using GEDCOM import so maybe that is the place to do the change

Comments

Eliza Balsor-40's Proper First Name and Prefered Name fields shows two blank spaces after the "a" on Eliza. If you try to save blank spaces after a name in Proper First Name or Prefered Name fields on any profile, ending blank spaces are truncated.

Then, ending blank spaces (or unidentified charactes) on Balsor-40's fields were saved while the GEDCOM import process.

As you say Magnus, the GEDCOM import process let this invisible "extra characters" in.

---

I did a cut (of "Jane") and then a save and then a paste and that repaired the appearance.  I can't explain it but I've found that repairs this problem.

---

@Vincent

1. The Jane name is saved with an extra space
   1. The display of the names don't understand that Jane<space> is the same as Jane ==> we get the odd display
2. The GEDCOM import allow names with ending spaces to be imported
3. Using the web interface then the space is truncated 

==> This is a bug

 

And as WIkiTree just have G2G for bugs then I add a post in G2G and pray that it will be fixed ;-)

---

Your reply is a winner. I edited out the old nickname, saved, reentered and saved. Bingo, we have it.

---

I like this jeg about the angels Magnus!! (I think I will steal it lol) Actually I like all your funny pics to add a little humor to some serious problems!!

---

These leading and trailing whitespace characters should be stripped or trimmed by performing an administrative update directly on the database columns where this may occur. All name and location columns are candidates for this treatment. All spaces, tabs CR, LF, VT, NBSP, and possibly others should be stripped from both ends, and interior sequences of one or more whitespace characters should be replaced by a single blank. For the future, all strings should be conditioned this way before writing to db.

Answer 1

Magnus,

At Creation of Profile:

First Name and Preferred Name fields = Eliza "Jane "

Aditionally, Nicknames field = Jane

The odd display of the names in the image of the profile's page in your question can be expalined as follows:

1) At the top we have:

Usual name display format = [First Name] + LNAB,

= Eliza "Jane " + LNAB

(Note the blank space after Jane and the (" ")s were into the First Name field since the profile's creation).

2) Above Born (DOB) in (POB):

Usual names display format is:

= [First Name] + ([Preferred Name]) + "[Nicknames]" + LNAB

When  [Preferred Name] = [First Name], the format is: 

= [First Name] + "[Nicknames]" + LNAB

= Eliza "Jane " "Jane" + LNAB

Exactly as it looks like.

This is an undeniable proof of names in GEDCOM imported records are not properly filtered (Names can only contain letters, spaces, periods, dashes and apostrophes).

I hope someone able to fix this issue read this post.

Comments

I fixed by editing out the nickname,saving and reentering as per another response. But you are right, there is a bug in the system.

Answer 2

Thanks for identifying the problem. Please see

I did a cut (of "Jane") and then a save and then a paste and that repaired the appearance.  I can't explain it but I've found that repairs this problem.

commented 21 hours ago by Vincent Piazza G2G6 Pilot

I edited out nickname, saved, reentered, and saved. Viola!!