Reply to thread

Message

In older releases of MP, TV Server and/or the client TV Plugin had a bug in the handling of code pages. Although characters that were part of the ASCII set displayed correctly, a small number of more-specialised characters displayed incorrectly. Owlsroost fixed this bug sometime in 2018.

Look at the beginning of the export file to see if there is an xml tag that specifies the code page. Do this for an export file from 1.36, and then compare it with the file that you are trying to import.

You could try changing the code page specified in the import file to the value specified in the 1.36 export file, but this still does not guarantee that the file will import correctly. So I think that you might have to resort to editing the import file to correct the characters that are causing the problem. Hopefully there will not be too many of these bad characters.

Once the errors are corrected, you should be able to export and import without problem (but note that I have never tested this as the UK does not have any channel names that contain specialised characters).

-- from CyberSimian in the UK

<blockquote data-quote="CyberSimian" data-source="post: 1300724" data-attributes="member: 141969">In older releases of MP, TV Server and/or the client TV Plugin had a bug in the handling of code pages. Although characters that were part of the ASCII set displayed correctly, a small number of more-specialised characters displayed incorrectly. Owlsroost fixed this bug sometime in 2018. Look at the beginning of the export file to see if there is an xml tag that specifies the code page. Do this for an export file from 1.36, and then compare it with the file that you are trying to import. You could try changing the code page specified in the import file to the value specified in the 1.36 export file, but this still does not guarantee that the file will import correctly. So I think that you might have to resort to editing the import file to correct the characters that are causing the problem. Hopefully there will not be too many of these bad characters.Once the errors are corrected, you should be able to export and import without problem (but note that I have never tested this as the UK does not have any channel names that contain specialised characters).-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1300724, member: 141969"] In older releases of MP, TV Server and/or the client TV Plugin had a bug in the handling of code pages. Although characters that were part of the ASCII set displayed correctly, a small number of more-specialised characters displayed incorrectly. Owlsroost fixed this bug sometime in 2018. Look at the beginning of the export file to see if there is an xml tag that specifies the code page. Do this for an export file from 1.36, and then compare it with the file that you are trying to import. You could try changing the code page specified in the import file to the value specified in the 1.36 export file, but this still does not guarantee that the file will import correctly. So I think that you might have to resort to editing the import file to correct the characters that are causing the problem. Hopefully there will not be too many of these bad characters. Once the errors are corrected, you should be able to export and import without problem (but note that I have never tested this as the UK does not have any channel names that contain specialised characters). -- from CyberSimian in the UK [/QUOTE]