Arrested Trump Rally Protester is Convicted Bomber of Marine Recruitment Center

Conservative Treehouse ^ | 11/19/2015

[TXnMA]

I SAW your test ex as:

“ He‘s a friend... “ (Curly quotes & apostrophe)

But, when I PASTEd it in FR's editor to quote it back to you, it LOOKED LIKE THIS when previewed:

“ He’s a friend... “ (Curly quotes & apostrophe)

~~~~~~~~
But, using metmom's "replacement scheme" looks like this:

" He's a friend... " (STRAIGHT quotes & apostrophe)

For FReeping — I can live with that!!
~~~~~~~~

---

As my East Texas neighbors would say, “If you're of a mind to hurt your head a bit, think on this:”

" " ASCII: quotation mark
# # ASCII: number sign
$ $ ASCII: dollar sign
% % ASCII: percent sign
& & ASCII: ampersand
' ' ASCII: apostrophe-quote

‘ ‘ ASCII: Opening Single Quotation Mark
’ ’ ASCII: Closing Single Quotation Mark
“ “ ASCII: Opening Double Quotation Mark
” ” ASCII: Closing Double Quotation Mark
• • ASCII: Bullet
– – ASCII: Hyphen or En-dash
— — ASCII: Em-dash

Those are the applicable "ampersand hex" codes for the character ranges in which we're interested, (with a little hexadecimal & HTML fudging to get them to display properly on FR...)

~~~~~~~~~~~~~~~~

I believe you will find it instructive to

1) COPY your "test x" -- as it is displayed in FR's preview, PASTE it into the editor -- and, preview it again.

2) To get a better look at what's happening, COPY the section of the table above from #145 through #151, Paste it into the editor -- and, preview it...

Is this what you see?

‘ ‘ ASCII: Opening Single Quotation Mark ’ ’ ASCII: Closing Single Quotation Mark “ “ ASCII: Opening Double Quotation Mark ” ” ASCII: Closing Double Quotation Mark • • ASCII: Bullet – – ASCII: Hyphen or En-dash — — ASCII: Em-dash

(With <BR>s added to fix the formatting:)

‘ ‘ ASCII: Opening Single Quotation Mark
’ ’ ASCII: Closing Single Quotation Mark
“ “ ASCII: Opening Double Quotation Mark
” ” ASCII: Closing Double Quotation Mark
• • ASCII: Bullet
– – ASCII: Hyphen or En-dash
— — ASCII: Em-dash

Perhaps that will give you a clue as to how FR's parser is misinterpreting characters above #128 (but, not their codes)....

With some thought -- and careful comparison to the original -- maybe it will begin to make sense... '-)

Good luck! '-)

[DoughtyOne]

Thank you for your suggestion. I can’t do it tonight, but I’ll give it a go in the morning.

[betty boop]

(Did you notice that I sneaked in a few "EMDashes" — by using the AmpCode in FR's editor...?) '-)

God bless you! I love em-dashes! So nice to have them back again: —.

Also I love en-dashes: – .

Thank you for giving them back to me, dear brother in Christ!

[betty boop]

... inserting the "Ampersand codes" takes just a mouse click — and I know they will be interpreted directly by FR’s HTML interpreter.

Actually, if you care at all about reproducing special characters, you’re stuck with inserting the “Ampersand codes”. It turns out the simple cut-and-replace operation described above gets rid of “offending objects”; but it cannot restore the special character. What you get is a “reduction” to a character available on a standard keyboard.

There are hundreds of special typographic characters. But a standard keyboard only has 46 keys, which means that, with the help of the shift key, only 92 characters can be accessed. These are basically the standard English alphabet, the cardinal numbers, common numerical signs and other symbols, and the elements of punctuation.

No “curly quotes” or apostrophes or en- or em-dashes there!

So if you want to use special characters in your text, you need their ASCII special-character codes. You provided some of the more common ones — and they work!

But it’s still a lot of work to insert the ASCII codes, even with copy-and-paste. I wonder what has changed recently systemwide at FR that this problem has even cropped up. I've been around here for going-on 18 years, and have not seen this problem before.

Thank you so much, dear brother in Christ!

[TXnMA]

If you are composing offline in a word processor or (as I do) in a code editor, you probably have (and have used) its "Global Search-and-Replace" feature.

That's what I do. It may take multiple "passes", but it is simpler than replacing "offenders" one at a time...

Anyway, you're right: if you are an "O-C/AR" stickler like me, getting those “Curly Opening” and “Curly Closing” quotes and m/n dashes right is a must -- for anything other than a short, simple blurb like this -- which I do in FR's editor... And, for that, I can live with "WYSIWYG"... '-)

You're welcome, Dear Sister! (Actually, I had fun, sending this 78-year-old brain back to analyzing in hexadecimal once again, after all these years...)

FWIW, something in FR's character parser is messing up -- in the 8th or 9th bit of the character table... (Says the physical chemist...) LOL!

[DoughtyOne]

That sounds like a good process.