example 1.
example 2.(the word "don't").
JR is forcing us all to learn Greek.
;D
example 1.
example 2.(the word "don't").
For the time being comma one must spell out all of the punctuation marks period When quoting comma use the terms quote quote unquote and quote unquote unquote period And when doing possessives comma either spell out quote apostrophe unquote or comma for example comma instead of saying quote John apostrophe s house unquote comma say quote house of John unquote period
FR pages are supposed to be coded in UTF-8. That means you should be able to copy and paste Rooskie, Chinese, Arabic, whatever — not to mention curly quotes, em dashes, and funny apostrophes — and expect it to show up correctly in the user's browser.
That used to be true. However, in the last few days, something got broken in the FR server. Now, if you post UTF-8 (that matters — normal red-blooded American ASCII is also UTF-8, but doesn't need to be), you get garbage.
What appears to be happening is, the server scans posts for bytes falling outside the 7-bit ASCII range and substitutes HTML entities for each such byte. The result is a mess.
For instance, consider the word refugee enclosed in curly scare quotes, e.g., “refugee”. Have a closer look:
“refugee”
Notice that the open and close quotes have different shapes. That's why they are curly. In 7-bit ASCII, they would be the same — 7-bit ASCII can't represent curli-quotiness:
"refugee"
In the first example, in UTF-8, the curly quotes are each represented by three binary bytes. The left curly is e2 80 9c, and the right curly is e2 80 9d. When your browser encounters those sequences while operating in UTF-8 rendering mode, it correctly paints the left and right curlie shapes on your screen. IOW it just works.
However, if the recently introduced server bug gets a chance to intervene, it replaces e2, 80, 9c, and 9d with HTML entities representing those individual bytes. E.g.,
“refugee”
Your browser faithfully renders those corrupted entities, resulting in garbage:
“refugeeâ€
A circumflexed a followed by a Euro symbol followed by whatever. LOL!
The fix is obviously to revert the recent change.
Did the change get introduced as a result of the recent Google malware scare?
All I know is it happens when you cut and paste those symbols. When you type them it’s fine. Also, it’s always changed them in they typing box when you run spellcheck, but it still had them come out right when you post. It also adds paragraph html prompts when you run spell check. That can be annoying.
Me too
Thank you
iPhone 6+
I’m mixed on this phone btw
I got 10$ that the server runs on windows and is infected.
We all are.
It's some kind of utf-8 character encoding issue, I believe. There's probably a conflict between the content that people are posting, and the character encoding of the html page itself.
Such issues often involve apostrophes and the like.
Free Republic coding has a disgronifier built into it. The disgronifier software is on the fritz and had to be recoded strand by stand. Just think of the disgronifier as a text virtualizer, a text emulator and text simulator all rolled into one. Its not a lot on lines of code but they must be redone.