Error Message: Characters not available in the specified database code page '1252'

[gimpfam]

Hi, 
I recently updated my Frame license to Version 17.0.4. 628 from an older version (I think I went from Frame 2020 (Version 16.x.x) to Frame 2022. I have a set of about 15 docs that I work on. Most of the documents are delivered as PDFs, but I have one large document that I generate Reponsive HTML5 output (using the Publish command). I turn that output over to our development team to add to a web-based product. 

The HTML5 output generates fine and I can open the index.html file and look at the content/images, click links, search, etc. It all seems to work just fine and I don't see any bad characters or errors in the content. However, when the development team tries to add it to the product to the build, the following error displays: 

A string was provided with characters that are not available in the specified database code page '1252'.

I used the default Encoding (which I understand is UTF-8) from the Publish command. The development team tells me that is the correct setting to use. 
Does anyone have any idea how one goes about finding the bad characters (not in Code Page 1252) that are causing this problem? I had never heard of Code Page 1252 before last week. Sadly, this is way beyond my level of expertise. We have been following the same process with the earlier version of Frame and never had this problem. The team is blaming the problem on the the update of Framemaker, but I have no way of know to know if something changed in Framemaker to cause this. 
Has anyone ever seen anything like this or do you have any advice as to how I can resolve it? 
Many thanks, 
Marcia

[Jeff_Coatsworth]

I suspect it's a font that you're using that is causing the grief. @Bob_Niland may have more insight - he's a code page guru with stuff like this 😁

[gimpfam]

Thank you. Hopefully Bob will chime in with advice. I'll check my fonts. I
use pretty standard ones - Roboto, Lato, Courier New, etc.

Marcia

Marcia E. Allen
Sahara Development Group, Inc.
marcia.e.allen@gmail.com

[Bob_Niland]

gimpfam: However, when the development team tries to add it to the product to the build, the following error displays:
What application is reporting this? I get the impression that it's something unrelated to FM, that is trying to integrate the generated HTML5 into some web framework. I've never seen the following error from FM, which more commonly just renders a “?” when it can't render the intended glyph.

re: A string was provided with characters that are not available in the specified database code page '1252'.
That's referring to Microsoft Windows Code Page 1252, described to a useful level in the Wiki Windows-1252 page.
That character set is the pre-Unicode 8-bit set that has ASCII in the low half, and Latin extensions in the upper.

That error tends to suggest that whatever this processing code is, it's expecting only single-byte characters. While FM still only supports Unicode BMP, that includes 1, 2, 3 & 4-byte characters. Indeed many characters commonly used in FM, formerly in CP1252 (e.g. ƒ†‡™˜•) are now in Unicode, and would be output as UTF-8, 2-bytes each at least.

[gimpfam]

Thank you Bob for that information. I will discuss it with the development team and see what I can find out.

I am not seeing "?" characters in my HTML outout.
I may reach out again, depending on what I find out. 
Best regards, 

Marcia

[Matt-Tech Comm Tools]

You should probably update to Fm 17.0.7, just in case this is something that was fixed in the intervening updates.