Page 1 of 1

Text Encoding problems in the Editor

Posted: Mon Apr 24, 2017 4:28 pm
by chrish
I've seen some problems with nonstandard text entry in the Editor. I wonder if they come down to the encodings for the various fields in the editor or on the server.

In one case, I was working with a language that uses non-ascii glyphs. The text was copy, pasted into the editor (as a plaque title), but the glyph did not make the transition to the app. Going back to the editor later, the glyph was missing. A question mark in a box appeared.

In the other case, an emoji was copy pasted into the editor (in a plaque description), and saving the plaque and reopening erased both the emoji and all text following it. Entering the html for the emoji (typing in the literal unicode maybe) works.

I haven't had time to hunt this down very far, but it seems that the editor responds to non-ascii text entry in not fully predictable ways. Some help for avoiding these problems from those in the know would be helpful.

Re: Text Encoding problems in the Editor

Posted: Mon Apr 24, 2017 10:13 pm
by djgagnon
Did this behavior begin recently? I wonder if it has something to do with our migration to a new data center with new servers?

Re: Text Encoding problems in the Editor

Posted: Mon Apr 24, 2017 10:52 pm
by chrish
The former instance was earlier this spring. February. The latter was today.

Re: Text Encoding problems in the Editor

Posted: Mon Apr 24, 2017 11:20 pm
by djgagnon
Thanks for the info Chris. What symbols messed it up?

Re: Text Encoding problems in the Editor

Posted: Tue Apr 25, 2017 12:37 pm
by chrish
U+0141 Ł Ł Ł Latin Capital Letter L with stroke