Still a problem with dollar sign in newsletter text

A non-profit client of mine just sent out a newsletter about their New Years fundraiser to about 500 people.

Unfortunately, the text came out like "Tickets are .00 each and includes Food, Alchohol, and a Champagne Toast at Midnight". Notice the price, or lack thereof. There was an issue before, but I thought it was fixed. Anyway, I need to have this guy push one of those "Ooops!" emails that nobody likes to send. Is this a JCE issue?

The newsletter was created in the 1.1x series. My guy actually sent it just about the same time as I uploaded the 1.2beta...one second it was in draft, the next, it was Sending...as I was writing the email to tell him not to send

Thanks!

Hello kenlyle,

Thanks for the bug report. Will be fixed in the next release (1.2).

tbh it is visible in the HTML preview on the send page inside Joomailer and also when you send a campaign test.
It's not JCE related.

Kind regards,
Pete

Ya, *I* know about the preview. My client is the greatest guy, but sometimes does crazy things. He said "I couldn't get the preview to work, so I just blasted it out" or something like that. Nothing can prevent users from taking illogical actions, so I definitely empathize with you guys, trying to make it as foolproof as possible, but no more so.

For today, the workaround is to just omit the dollar sign, I guess?

Best,
K

Currently a dollar sign followed by one or two digits in content articles gets removed. A workaround would be to make a space between the dollar sign and the following digits.

Kind regards,
Pete

Hm, is that in the code, you mean?

I just sent myself a test, and the dollar sign and amount came through, this is in 1.2 Beta.

Alexis says maybe my issue was UTF-8 on my template...which I DID NOT have, and have now corrected.
head
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
/head
(with the tag open and close, of course)

OK, it all looks good in Preview. Waiting on the Test email.

Yeah, it's a bug in the code. It also only happens on content articles, not the intro text you enter in the wysiwyg editor when creating a campaign.

Oh, Thanks for clarifying that. My testing above was on that very intro text that you mentioned. I'll let my guy know about the workaround. Sorry for the confusion.
K