Turkish Characters Not Displayed Correctly in Signature Texts

• The issue stems from the email's encoding at the time it is sent. We do not modify or override the encoding of outgoing emails — the original encoding is preserved.

• When the encoding is set to us-ascii, Turkish characters may appear as “???” in the email content. This happens because us-ascii does not support special characters, and once sent, the corrupted characters cannot be fixed within the email body.

• Since the signature is generated by our system, we have the ability to address this issue specifically within the signature block.

• By enabling the "Replace HTML Characters" option in the NextClaimer Rule Properties options, Turkish characters in the signature will be displayed correctly — even in emails sent using us-ascii or other limited encoding formats.

  • 

    Rule Properties Options

• This feature was implemented based on customer feedback and is recommended for all users dealing with non-English characters in signatures.

View On Owa Client:

Correct View On OWA Client

View On Outlook Classic:

Correct View On Outlook Classic

View On Gmail:

Correct View On Gmail

View On IOS Mail:

Correct View On IOS Mail

Encoding Charset:

• To identify potential issues with Turkish characters, a test email was sent using the same encoding value. In this test, us-ascii encoding was used. However, since us-ascii only supports standard English characters, Turkish-specific letters (such as ç, ğ, ı, ö, ş, ü) may not display correctly with this format.

• Upon further review, it was observed that when using iso-8859-9 (Latin-5) as the encoding value, Turkish characters were displayed properly without any issues. iso-8859-9 supports Turkish characters and is more compatible with systems commonly used in Turkey.

Note: If your email content includes Turkish characters, it is recommended to use iso-8859-9 or preferably utf-8, which provides broader character support.