44 replies to this topic

[Dimitrij]

In other images this has long been removed.

[Dimitrij]

>>> match = 'blöd'
>>> match.encode('UTF-8')
b'bl\xc3\xb6d'
>>> match = 'blöd'
>>> match.encode('ISO8859-15')
b'bl\xf6d'

 

[WanWizard]

In other images this has long been removed.

 

That can only be done if you are sure all strings contain UTF-8.

 

 

>>> match = 'blöd'
>>> match.encode('UTF-8')
b'bl\xc3\xb6d'
>>> match = 'blöd'
>>> match.encode('ISO8859-15')
b'bl\xf6d'

 

This is not relevant, as you start out with strings with valid encoding.
 

[Dimitrij]

After changing the encoding you will never find a match, this option was originally wrong.

 

The same problems arise when we try to compare a case-insensitive match.

If it is not English, then there will never be a match, it is a different character set.

Edited by Dimitrij, 19 November 2024 - 16:28.

[WanWizard]

Ok.

 

Question remains how that ISO8859-15 string got into the autotimer.xml. Because that is the root cause of this problem.

[Dimitrij]

 

 

Question remains how that ISO8859-15 string got into the autotimer.xml. Because that is the root cause of this problem.

 

        # Encoding
        default = timer.encoding
        selection = ['UTF-8', 'ISO8859-15']
        if default not in selection:
            selection.append(default)
        self.encoding = NoSave(ConfigSelection(choices=selection, default=default))

 

I checked each enabled Autotimer entry and found one which had ISO8859-15 encoding set.
I changed it to UTF-8 and it seems the problem was fixed.

 

[WanWizard]

Yes, I can read.

 

But that doesn't answer my question

 

I checked each enabled Autotimer entry and found one which had ISO8859-15 encoding set.

 

which is "why was it ISO8859-15 in the first place", as everything in E2 should be UTF-8.

[klorinczi]

> so if you have an entry in ISO8859-15, there may be more bugs to fix...

I did set ISO8859-15 encoding accidentally for a newly created Autotimer item.

But the EPG text arrived in UTF-8, so this was interfering with the ISO8859-15 encoding setting.

There should be an encoding detection in the Autotimer plugin, which could handle the encoding error and avoid such fatal plugin errors, what resulted the plugin to stop working.

[WanWizard]

Thanks for the feedback.

 

How did you "set ISO8859-15"? Just trying to understand what exactly you did.

[klorinczi]

Created a new Autotimer for an event and (maybe accidentally) changed the encoding from UTF-8 to ISO8859-15.

Doesn't matter why.
It is just possible and it seems it can make the Autotimer plugin to stop working.

[arkovda]

After removing the autotimer.xml and adding them back manually it start working.

My old autotimer.xml looked like this:

<?xml version="1.0" ?>

<autotimer version="8">

 

 <defaults location="/media/usb/movie/" offset="5">

 </defaults>

 

 <timer name="Allt för Sverige" match="Allt för Sverige" enabled="yes" location="/media/usb/movie/Serier/Allt för Sverige/">

  <afterevent>auto</afterevent>

  <exclude where="title">®</exclude>

 </timer>

 

 <timer name="Whitechapel" match="Whitechapel" enabled="yes" location="/media/usb/movie/deckare/Whitechapel/" offset="5">

  <serviceref>1:0:19:1D7F:1B:46:E080000:0:0:0:</serviceref>

  <serviceref>1:0:19:1D80:1B:46:E080000:0:0:0:</serviceref>

 </timer>

 

 <timer name="Morden i Sandhamn" match="Morden i Sandhamn" enabled="yes" location="/media/usb/movie/deckare/Morden i Sandhamn" offset="5">

  <serviceref>1:0:19:57D:E:46:E080000:0:0:0:</serviceref>

  <afterevent>auto</afterevent>

  <exclude where="title">®</exclude>

 </timer>

.....

</autotimer>

[WanWizard]

What EPG produces titles with a ® ?
 
And I still have no clue what you mean by
 

Created a new Autotimer for an event and (maybe accidentally) changed the encoding from UTF-8 to ISO8859-15.

 

encodings don't easily change, that is hard work.

[arkovda]

I did not put in the ®. It was created by your site

Should be "(" +"R" + ")" 

where="title">®</exclude>

[klorinczi]

And I still have no clue what you mean by

Created a new Autotimer for an event and (maybe accidentally) changed the encoding from UTF-8 to ISO8859-15.

encodings don't easily change, that is hard work.

See screenshot2, where I changed the encoding to ISO8859-15.

Attached Files

•  screenshot1.png   300.25KB   0 downloads
•  screenshot2.png   305.29KB   0 downloads

[WanWizard]

I did not put in the ®. It was created by your site

 

What do you mean by "your site"?

 

Autotimers are created either manually (you type  in the title and search criteria), or you create it from an EPG entry.

 

Assuming you did the last, I was wondering where the EPG data came from.

 

Did you receive it OTA from the channel provider ( in which case I would like to know provider and channel as we might have an EPG reader issue ) or from EPG Import ( in which case the data in the xmltv import was incorrect ).

[arkovda]

When I pasted in the values they where modified by this webb.

I pasted in a left parantes and an R and a right parantes and that was modified by openpli.org to ®

Edited by arkovda, 21 November 2024 - 17:29.

[littlesat]

® when I type ( r ) (without spaces) on this forum. ©

Edited by littlesat, 21 November 2024 - 17:57.

[WanWizard]

Ok, so this is not about the autotimer and the encoding at all... Confusing.

[littlesat]

Yep it is about our forum software. Indied confusing (p)

[WanWizard]

And the question still remains: where did the ISO8859-15 text in the autotimer come from?