Audio Asylum Thread Printer
Get a view of an entire thread on one page
|For Sale Ads|
In Reply to: RE: Hmm posted by 1973shovel on April 09, 2017 at 06:53:42
Yes, you guessed correctly.
This is one of these areas where we should have left well enough alone. Some time ago, we converted the database to UTF-8 which is one of those great relatively new things. Afterward, we found problems with 8 bit characters and differences between the Windows and ISO character sets and translations along with some platform issues. We've done some workarounds for the common characters, but you found another one.
So, when one of the characters gets saved to the db, it truncates the post after that character. Because the posts also get saved in an html format on disk, you can see the old post in your edits and that character gets shown as the funny black diamond whereas the messages you see are generated from the db where it is truncated.
You can still edit the post and copy the original from a saved edit version and replace the diamond character with a non-correct 'u' for the microfarad symbol.
The new responsive code base that we're working on now will have a re-written post routine and one of the things we're going to try to do is to get that bug licked completely.
My original reply, using the correct microfarad symbol, posted correctly. It's when I went to edit it today that the trouble started.
I followed your suggestion, substituting 'u', and my last edit posted correctly, so thanks.
Will the new code be a blanket fix, or will you need to know each individual character we use? I ask, because another one I use occasionally is Alt. 0186 which creates the "degree" symbol.
Thanks again, Rod.
I wish I was expert enough in this area to give you an absolute answer. Our objective is surely to solve it. OTOH, it may not be that easy.
Post a Message!
This post is made possible by the generous support of people like you and our sponsors: