6 replies to this topic

[DA-G-GURU]

Maybe MFL can update there header, as the no back space html code will put off a diamond question mark, if you save an HPM again. (frustrating)

 

This is what I am seeing by researching, they need to add the ISO to the header.

 

 

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 

 

 

[theeohiostate]

Maybe MFL can update there header, as the no back space html code will put off a diamond question mark, if you save an HPM again. (frustrating)

 

This is what I am seeing by researching, they need to add the ISO to the header.

 

 

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 

 

 

shoot in a support ticket , i'd ask them , but i've got several other tickets open right now lol

[DA-G-GURU]

No problem will do that. Thx

[UCanCallMeMitch]

Yep, been seeing the insertion of code #65533 since the update and lived with it.

 

�There is no doubt that the warheads contain chemical weapons,� Defense Minister Jerzy Szmajdzinski told TVN24. �The problem is what period they came from, whether the (Persian) Gulf War or earlier, and whether they were usable, partly usable or not at all.�

 

I've sent a support ticket in too.

[UCanCallMeMitch]

Here's the reply from MFL -

 

Hi Mitch,

Unfortunately that's not possible. Our content (as created by us and our partners) uses the UTF-8 character set encoding (you can only specify one character set). The black diamonds you see are the result of iso-8859-1 characters that can't be displayed in UTF-8. If we were to change that, then everyone else would get errors with UTF-8 characters that can't be displayed in iso-8859-1. UTF-8 is a more modern and with a much larger set of characters it can represent (pretty much every character in all foreign languages are supported). Even if we were able to let you pick the encoding you want, the rest of the content we create may include similar issues.

I assume you are seeing on text that you are copying from a source that's not using UTF-8. Based on your example, those appear to be fancy quotes that some sites use. There's no way to automatically fix that on our end. However, it may be possible if you copy and paste it to another editor (like Notepad or Word or something else) that depending on your OS settings it may clean it up for you.

Thanks,

Tony F.

[theeohiostate]

http://www.fileforma.../UTF-8/list.htm


This starting happening a few years ago when you re saved a message you copied and pasted.

Typically it was happening when we used . "&nbsp" for a space

See above link for UTF-8 HTML character set



Test typing and saving this in a HPM


<div>ttttttt tttttttt</div>

<div>tttttttt&nbsp;ttttttttt</div>

If using a text editor to write code, just set to UTF-8 and all characters will be correctly written for MFL

For multiple white space use CSS white-space:pre;

<div style="white-space:pre">ttttttt. . tttttttt</div>

[DA-G-GURU]

Nice i can use the UTF-8 just fine....   &#32;