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: 1300725" data-attributes="member: 49539"><p>Thanks for responding. Unfortunately, neither the old export file nor a new one created by 1.36 contains any code page information. In fact, I didn't even try to import the old export.xml file directly. Instead, I copied the "channelgroup" sections from the old export. xml file into a copy of the one created by 1.36.</p><p>The old export.xml file is from 2021, so the fix you refer to should already have been in place.</p><p>Where do you think MP is getting the code page information? How can I even find out what code page MP is assuming?</p><p>For that matter, why does MP even use code pages anymore? Wouldn't UTF be more robust?</p><p>Since 1.36 has already entered the channel names <em>with umlauts</em> into its channel list, I am afraid that editing them out of the channelgroups in the XML file will result in a failure to map them properly to the existing channels in the TV Server DB.</p><p>If I edit the channel names in the TV Server configuration, then they won't match the EPG anymore. Isn't there a more elegant way to handle this?</p></blockquote><p></p>
[QUOTE="rsbrux, post: 1300725, member: 49539"] Thanks for responding. Unfortunately, neither the old export file nor a new one created by 1.36 contains any code page information. In fact, I didn't even try to import the old export.xml file directly. Instead, I copied the "channelgroup" sections from the old export. xml file into a copy of the one created by 1.36. The old export.xml file is from 2021, so the fix you refer to should already have been in place. Where do you think MP is getting the code page information? How can I even find out what code page MP is assuming? For that matter, why does MP even use code pages anymore? Wouldn't UTF be more robust? Since 1.36 has already entered the channel names [I]with umlauts[/I] into its channel list, I am afraid that editing them out of the channelgroups in the XML file will result in a failure to map them properly to the existing channels in the TV Server DB. If I edit the channel names in the TV Server configuration, then they won't match the EPG anymore. Isn't there a more elegant way to handle this? [/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