Reply to thread

Message

According to Wikipedia, Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports two code pages in addition to UTF-8 (OEM and ANSI). According to Microsoft, UTF-8 has been the preferred character set since 2019. If TV Server (or its import routine) were using UTF-8, then umlauts wouldn't be a problem. Since I haven't encountered this problem before, I suspect that it is a bug in MP TV Server that has been introduced since 2021. As a workaround, I plan to delete from the import file all of the channels with special characters in their names and map those by hand. At least that way I can recover most of my previous mappings.

[QUOTE="rsbrux, post: 1300730, member: 49539"] According to [URL='https://en.wikipedia.org/wiki/Windows_code_page']Wikipedia[/URL], Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports two code pages in addition to UTF-8 (OEM and ANSI). According to [URL='https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page']Microsoft[/URL], UTF-8 has been the preferred character set since 2019. If TV Server (or its import routine) were using UTF-8, then umlauts wouldn't be a problem. Since I haven't encountered this problem before, I suspect that it is a bug in MP TV Server that has been introduced since 2021. As a workaround, I plan to delete from the import file all of the channels with special characters in their names and map those by hand. At least that way I can recover most of my previous mappings. [/QUOTE]

Verification