If you're seeing an error like WinAnsi cannot encode "ā" (0x0101) in your PDF generator automation, one or more mapped fields contain an unsupported character.
Supported Characters
Printable WinAnsi / Windows-1252 characters:
U+0020-U+007E | !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ |
U+00A0-U+00FF | ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ |
U+0152-U+0153 | Œ œ |
U+0160-U+0161 | Š š |
U+0178 | Ÿ |
U+017D-U+017E | Ž ž |
U+0192 | ƒ |
U+02C6 | ˆ |
U+02DC | ˜ |
U+2013-U+2014 | – — |
U+2018-U+201A | ‘ ’ ‚ |
U+201C-U+201E | “ ” „ |
U+2020-U+2022 | † ‡ • |
U+2026 | … |
U+2030 | ‰ |
U+2039-U+203A | ‹ › |
U+20AC | € |
U+2122 | ™ |
Workaround
A potential workaround can be to use an Airtable formula that replaces any troublesome characters, either with nothing, or with their closest 'regular' counterpart. This formula could work, for example:
SUBSTITUTE(SUBSTITUTE(SUBSTITUTE({TITLE},"ā","a"),"Ā","A"),"","")
This would substitute ā with a, Ā with A, and remove the zero width space character (that character may be stripped from this article, so you may need to insert it again between the second-to-last set of quotation marks if you're copying this example formula), in a field called TITLE.
You'd then use that formula field in the field mappings for the PDF generator, instead of the original text field containing the special character(s). ChatGPT can help you generate the full formula, if you come across a lot of different problematic characters.