French EPG issues

[lachape_one]

Salut

I found EPG123 thanks to you guys, awesome, it's been 4 years I looked for a way to complete the french new digital terrestrial tv ("TNT") channels guide, which remained desperately empty all these times. I also found that lineups includes my cable provider Numericable, it's just wonderful, i'l give it a try very soon, but for now, i give my feedback for these standard DTT (TNT) channels :

So, everything worked fine for these channels:
- L'équipe 21 HD
- 6Ter HD
- Numéro 23
- RMC Découverte HD
EPG123 downloaded successfully, but the cmd function is blocked at the step "Kick off reindexsearchboot task..":

but, when i look into MCE Guide, everything seems ok:



but there are some issues, each time i select these 2 channels in the lineups:
- HD1
- Chérie 25
EPG123 crashed, with these messages:



With a prompt to close the program


if it can help you to improve EPG123, i'll really appreeciate

Merci!

[rkulagow]

Can you provide a translation of what the error messages are saying?

[garyan2]

I am trying to determine the star rating of a movie and the field from Schedules Direct is not in the format I expect ... possibly have a letter in there.

Could you send me what postal code you used to get your lineups so I can run a test and find where my error handling is failing? Should be a real quick fix.

Thank you

[rkulagow]

Is there a way to do try/catch blocks, so that if there's an error it can spit out the program that failed? Or have a -debug mode that just dumps each program as it's being processed to the log, so that you can see which one causes the error? (instead of just 712/867)

[lachape_one]

Can you provide a translation of what the error messages are saying?

the msg seems to say "unhandled exception System.FormatException "Input string was not in a correct format."
At System.Number.parseDouble(String value,NumberStyles options, NumberFormatInfo numfmt)" and "EPG123 stopped working, windows will now close the program"

I am trying to determine the star rating of a movie and the field from Schedules Direct is not in the format I expect ... possibly have a letter in there.
Could you send me what postal code you used to get your lineups so I can run a test and find where my error handling is failing? Should be a real quick fix.
Thank you

the postal code i used is 78150 and the lineup is "Numéricable - Buc -Digital (Issy les Moulineaux)

Is there a way to do try/catch blocks, so that if there's an error it can spit out the program that failed? Or have a -debug mode that just dumps each program as it's being processed to the log, so that you can see which one causes the error? (instead of just 712/867)

sorry but i'm lost: how can i do that?

[garyan2]

the postal code i used is 78150 and the lineup is "Numéricable - Buc -Digital (Issy les Moulineaux)

Thanks, I'll troubleshoot this tonight and should have an answer for you early in the morning your time.

Is there a way to do try/catch blocks, so that if there's an error it can spit out the program that failed? Or have a -debug mode that just dumps each program as it's being processed to the log, so that you can see which one causes the error? (instead of just 712/867)

sorry but i'm lost: how can i do that?

That comment was directed to me for the epg123 code.

[lachape_one]

Formidable merci

[STC]

Nice to know this works for French terrestrial.

Most other countries where Gracenote has listings?

[Space]

Nice to know this works for French terrestrial.

Most other countries where Gracenote has listings?

http://www.schedulesdirect.org/regions

[STC]

^ specifically does EPG123 work for all these countries? I'm sure there are nuances that need to be tweaked due to language differences and other things.

[lachape_one]

^ specifically does EPG123 work for all these countries? I'm sure there are nuances that need to be tweaked due to language differences and other things.

Right. For french ie, I'm not developer but i know that most of the time, characters like "é", "ô", "à" or other "ç" causes some trouble because they are converted to ASCII code

[rkulagow]

The Schedules Direct JSON service is UTF-8 clean, so any sorts of "extended" characters are passed through to the client without issue. Of course, the client may then mangle them as it desires...

[garyan2]

... and I've tried to keep all this in mind. Everything is culturally insensitive, so should be presented as intended.

^except ... I meant to take care of this last build, but the OAD override is not insensitive and will mess things up a bit. I'll get that fixed next build as well.

[garyan2]

^^except for probably the difference between a rating of 2.5 vs. 2,5

Probably what happened.

[rkulagow]

If you can provide the programID then I can check what's on the master server.

[garyan2]

All good now. I was right in the 2.5 versus 2,5 ... code got confused. I'm going to scrub through the rest of the code to see if I missed anything else, but I think that should be it.

lachape_one, is it okay if I send you a build to try out? and you can let me know if there is anything else not right?

[rkulagow]

@garyan2

So this is something to do with i18n and not the source data from our servers?

[garyan2]

@garyan2

So this is something to do with i18n and not the source data from our servers?

I've gotta admit, I had to look that up ... but, yes, it was all about the number format and I'm fine with that. I prefer the source data to be predictable, so don't change a thing.

EDIT: Just to clarify, it was my code that was not taking into account the cultural format of the host computer when calculating the number of stars based on the data from SD.

[rkulagow]

@garyan2

So this is something to do with i18n and not the source data from our servers?

I've gotta admit, I had to look that up ... but, yes, it was all about the number format and I'm fine with that. I prefer the source data to be predictable, so don't change a thing.

EDIT: Just to clarify, it was my code that was not taking into account the cultural format of the host computer when calculating the number of stars based on the data from SD.

Ah, so in fact it was l10n, not i18n. ("localization")

[garyan2]

Ah, so in fact it was l10n, not i18n. ("localization")

Now you're just showing off.