home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
Import TV channel groups: "Invalid character in the given encoding"
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="rsbrux" data-source="post: 1300730" data-attributes="member: 49539"><p>According to <a href="https://en.wikipedia.org/wiki/Windows_code_page" target="_blank">Wikipedia</a>, 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 <a href="https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page" target="_blank">Microsoft</a>, 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.</p></blockquote><p></p>
[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]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Import TV channel groups: "Invalid character in the given encoding"
Contact us
RSS
Top
Bottom
