Find content
Display name historySee screenshot2, where I changed the encoding to ISO8859-15.And I still have no clue what you mean by
encodings don't easily change, that is hard work.
Created a new Autotimer for an event and (maybe accidentally) changed the encoding from UTF-8 to ISO8859-15.
- Forums
- → Viewing Profile: Posts: klorinczi
ATTENTION !!!
Due to a database corruption issue, we were forced to restore last-nights backup. This means all posts of Saterday Febuary 17th have been lost.Community Stats
- Group Senior Member
- Active Posts 28 ( per day)
- Profile Views 1,290
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
Contact Information
0
Neutral
User Tools
Friends
klorinczi hasn't added any friends yet.
Latest Visitors
No latest visitors to show
Posts I've Made
In Topic: Autotimer stopped adding new timers since a few days
21 November 2024 - 12:44
In Topic: Autotimer stopped adding new timers since a few days
19 November 2024 - 18:31
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.
Doesn't matter why.
It is just possible and it seems it can make the Autotimer plugin to stop working.
In Topic: Autotimer stopped adding new timers since a few days
19 November 2024 - 17:48
> 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.
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.
In Topic: Autotimer stopped adding new timers since a few days
19 November 2024 - 15:37
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.
The Autotimer notification about update was displayed again, the missing Timer entries were added.
It seems there is a bug, when other than UTF-8 encoding is set, then fails to finish the process.
Maybe this problem was fixed by Dima73 in his last commit.
I changed it to UTF-8 and it seems the problem was fixed.
The Autotimer notification about update was displayed again, the missing Timer entries were added.
It seems there is a bug, when other than UTF-8 encoding is set, then fails to finish the process.
Maybe this problem was fixed by Dima73 in his last commit.
In Topic: Autotimer stopped adding new timers since a few days
19 November 2024 - 15:20
Thank you, I found it.
In
Menu / Plugin browser / Autotimer / Menu button / Edit new timer defaults / EPG Encoding
The EPG Encoding is already set to UTF-8.
In
Menu / Plugin browser / Autotimer / Menu button / Edit new timer defaults / EPG Encoding
The EPG Encoding is already set to UTF-8.
- Forums
- → Viewing Profile: Posts: klorinczi
