@utzer [Friendica] It’s the second time this month that people reports encoding issues with Friendica output. It should have been simple, Friendica always outputs UTF-8 text, even if it doesn’t say so explicitly. But some platforms defaults to ISO 8859-1, a remnant of a distant path, when they don’t get explicit encoding information.

It is starting to piss me off that we will have to ensure the encoding is set in all outgoing requests.

@utzer [Friendica] Here are my initial findings:

- https://social.yl.ms/objects/e18176ef-1265-69cb-ae0b-50b145353709 doesn't show the encoding issue in the mention display name
- https://friendica.mrpetovan.com/display/e18176ef-1265-69cb-ae0b-50b145353709 shows the encoding issue in the display name

However, I wasn't able to retrieve a source message for this post, so I don't know how it looked when it reached my node, but the mention shows OK:

@Michael Vogel @Hypolite Petovan maybe something todo with Diaspora... don't know.

I will see what happens in the future.

Here it happened again.
https://friendica.utzer.de/display/f4fa78b9-2465-6bb9-e506-35f740657970

Here is some test post which looks fine on both my servers and Mastodon.
https://social.yl.ms/display/e18176ef-2065-6cac-e7d3-6ec761380172

@Hypolite Petovan and it happened again, would like to know if Rainer sees your post in the same way.

See his reply here: https://diasp.org/posts/e18176ef-2065-6cac-e7d3-6ec761380172#03f36d90742a013c3a1428a1592b385a