Edited by Lozus, 16 March 2017 - 21:49.
Timers.xml
Re: Timers.xml #21
Re: Timers.xml #22
Re: Timers.xml #23
Re: Timers.xml #24
Posted 17 March 2017 - 14:02
How do you create timers yourself? In an illegal encoding? Everything on the box runs in utf-8!
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Timers.xml #25
Posted 17 March 2017 - 14:34
I can chose utf or iso.
I press EPG button on remote, when yellow button, go to the program what I want to record. Press menu and create autotimer. At first I can choose program name, time, day etc. After I press ok I see nex menu where I can chose a lot of parameters and encoding also.
Re: Timers.xml #26
Posted 17 March 2017 - 14:52
All data on the box is encoded in UTF-8. All other encodings are illegal.
So if you add a timer that is encoded in an ISO characterset, Enigma will crash when it attempts to process thr XML. That is why I want to know how you manage to add a timer in an ISO set, as all EPG data in the system is UTF-8.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Timers.xml #27
Re: Timers.xml #28
Re: Timers.xml #29
Posted 17 March 2017 - 21:05
Took some time to view the video.
Why do you change the encoding when you create the autotimer? If you are not 100% sure you have EPG data in an ISO encoding, you should not touch that?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Timers.xml #30
Re: Timers.xml #31
Posted 18 March 2017 - 12:59
I have to say I'm not sure what that setting does, as I'm pretty sure all EPG data is in utf-8. Perhaps the author of the autotimer plugin can comment on this.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Timers.xml #32
Posted 18 March 2017 - 13:20
EPG is mostly not sent as UTF-8 (EIT), they have all sorts of weird encodings more or less specific to DVB. The xml EPG should in UTF-8, but the EIT is convered to UTF-8 on the go. Sources for xml EPG seem be often non-UTF-8 as well and are converted by the rytec guys.
So, there are various stage where conversions take place. If the source doesn't advertise the encoding of it's content properly, it will go wrong and I've seen it happen many times.
Encoding are a curse, it should have been UTF-8 for years and years now.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: Timers.xml #33
Posted 18 March 2017 - 13:28
The point here is that there is a setting in the Autotimer, which explicitly defines the EPG data as being in a specific encoding. Regardless of what it actually is. So if you select anything other than UTF-8 there, you end up with illegal data in the xml, since the timers.xml parser expects the data to be in UTF-8.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Timers.xml #34
Posted 18 March 2017 - 16:13
AFAIK the encoding in the autotimer is only used for comparison. A bit weird if you think of it, as the internal representation is indeed UTF-8. It might signify the characterset you use to enter the search string
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Re: Timers.xml #35
Re: Timers.xml #36
Re: Timers.xml #37
Re: Timers.xml #38
Re: Timers.xml #39
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users