Issue with special characters

Incident Report for Xink

Resolved

This incident has been resolved.

Posted Jan 15, 2024 - 13:39 CET

Update

We are getting reports that v.4.1.0 adds a strange character to some email signatures.
We are looking into it as a priority.

Posted Jan 12, 2024 - 10:01 CET

Monitoring

We have pushed the add-in 4.1.0, which addresses the special characters issue with Outlook's 'classic' desktop version 2312.

Posted Jan 12, 2024 - 09:21 CET

Identified

Microsoft launched Outlook 2312 on 4 Jan, which changes the encoding from UFT-8 to CP-1252.

Learn more on GitHub:
https://github.com/OfficeDev/office-js/issues/3892

We recommend returning to 2311 until Microsoft fixes the Outlook ‘classic’ desktop.

WORKAROUNDS

You can switch to the New Outlook.
You can use Outlook on the web.
You can click the email signature in the Xink add-in.
You can update email signatures using the Xink client.
You can move to a server-side email signature.

RESOLUTION (pending while we wait for the Microsoft fix)

Our add-in developer team are investigating if they can fix the encoding via the add-in (not likely).
Our template team is investigating if we can change the built-in designer source (likely).

Sorry about the inconvenience.
Jesper Frier

Posted Jan 10, 2024 - 12:25 CET

This incident affected: EU Data Centre (Microsoft Azure Cloud) (Outlook Add-in).