"“! “! “!"
Posted on 01/07/2016 9:06:36 PM PST by Boomer
And with a $20 monthly you get a modern GUI interface.
Yes, I get those quite a bit...they’re annoying as all get out!
It’s not only my posts; it’s everyone’s.
I will remember that. I guess we need to get the word out to everyone to do the same thing.
"“! “! “!"
Yes, I get it sometimes too.
Was that supposed to say “pew pew pew”? :D
Everyone’s getting the same thing as you. I’m surprised that it haven’t been fixed already.
This thing has pretty well been hashed to death by now. Until Jim and John can come up with a solution we’re stuck with workarounds. I must assume you’ve not been on FR in a while.
That’s kinda why I brought it up. It has been going on for months now. I did a search about the issue a month or so ago and it sounded like the fix was fairly straight forward. Just wondering if it was just me now. Now that I know everyone is having the same issue; I’ll continue to try and ignore it.
It does make it difficult to read the comments and original post sometimes though.
I am reminded of the Sears Roebuck catalog of 1897: “If you don’t find it in the Index, look very carefully through the entire catalog.”
A few years later Thomas J Watson founded IBM. Humans should THINK. Machines should work!
Then Google and Amazon came along. Now those machines are really busy!
Nobody should be replacing curly quotes with straight quotes by hand (or in any other way — curly quotes are curly because the look better that way).
Click my name if you don't like seeing the likes of ’.
Here were are again, cynwoody!
Test 1: 閪曬
and sure enough, cantonese is marked up because something in the ingest or render pipeline doesn’t understand UTF-8.
That’s without preview.
To be current, you need to upgrade to El Capitan.
But of course, that won't fix the problem. It's a bug in the FR server, not in Mac OS.
I'm running El Capitan, and I don't see the problem. That's because I'm running user scripts that correct for the problem client side.
Click my name if you'd like to try out my user scripts.
Test 2 was built by copying the raw HTML &xxx markup from the result of test 1. It didn’t suffer from the snowball effect that others see.
Something in the software is not understanding UTF-8.
Test 3: &#E996AA;
Heh, if you google “Cantonese Profanity” on google and click the wikipedia, you’ll see it.
It’s “hai saai”, which is a way of saying “epic fail”. But ruder.
Your scripts are ninja and people should use them until this nonsense gets fixed.
Oh, nifty. How did you do that?
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.
