Apostrophe bug when naming/activating new trackables

[+Spacemann Spiff]

This bug has been occurring for quite some time, and I kept thinking it would eventually get fixed, but then I realized maybe no one else is reporting it.

 

When activating a new trackable, I often put "John's" (my name) in front of the existing/default name of the geocoin.  I do this in Step 2 of the activation process.  (See example screenshot 01).

 

 

However, once you proceed to the next step, the apostrophe somehow morphs into random characters.  (See example screenshot 02).

 

 

 

 

I'm used to the error, so I know I always have to go back and fix it afterward.  It can be easily fixed by going into the Edit function of the trackable and changing the random characters back into an apostrophe again.  (See example screenshot 03).

 

 

 

 

Once this is (re-)done, the apostrophe shows correctly.  (See example screenshot 04).  But it never works when done in the original step during activation, only by going back and doing another Edit step afterward.

 

 

 

 

Can this be fixed so that the apostrophe "translates" correctly the first time, during the initial naming/activation step?  Many members don't even notice that it happens, and their trackable/geocoin goes out into the world with a bunch of random characters in the middle of its name.

 

Let me know if you need some examples of ones that have been released unnoticed.  I've seen a couple just within the past two or three weeks, but it would probably take me a bit to remember where I'd seen them.  Hoping the screenshots/explanation will help you to track down the problem.

Thanks!
 

 

 

[+Nite*Owls]

I've seen a few of these too. Definitely should be fixed as it makes the trackable name look garbled. People rarely double-check things to make sure they are good and correct so it doesn't surprise me that this happens.

[+cerberus1]

This happens with email as well.  You see it as your example one, but the person receiving it sees it "corrected".

IIRC, it has to do with another's setup, and it's been a "thing" so long it doesn't seem it can be "fixed"...