EPG Translator (Discussion thread)

[birdman]

Just for reference, this is not translating on OpenPLI for me.

Doesn't look good.
I'm working on 2.02, which currently:

• Overcomes the ~7500 byte limit on calls to Google translate (it splits, loops and stitches)
• Uses paths relative to the plugin.py script for icons, rather than hard-wiring paths.
• A few minor things.

So I'll get the fix in there for this, assuming I can find the problem.

EDIT: Difficult to see how a long could end up in any statement using + in that try clause (but I'm sure OpenPLi's enigma2 knows more than me about this).
I'll need to see whether I can get more info displayed (such as the line number for the Exception).

[birdman]

Hi Abu,

Could you drop this file in place and repeat, please? It will display the traceback for the Exception in the debug log.

plugin.py

At least the error was trapped and enigma2 kept running....

[abu baniaz]

Thanks. Got this

[EPGTranslator-Plugin] translateEPG error: unsupported operand type(s) for +: 'long' and 'str'
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGTranslator/plugin.py", line 633, in translateEPG
    to = int(self.event[epg_B] + self.event[epg_D] + 60*config.epg.histminutes.value)
TypeError: unsupported operand type(s) for +: 'long' and 'str'

[birdman]

Not sure what it thinks is a str.

I've assumed its the .value rather than .getValue() usage. Can you please check whether this one works?

plugin.py

I've also got it printing out the actual type of all three variables, just in case I'm wrong.
So even if it works, could you post the line containing "epg_B"?

[abu baniaz]

That worked on PLI. Thanks.

epg_B: <type 'long'> epg_D: <type 'long'> hmval: <type 'str'> hmget: <type 'int'>

[birdman]

That worked on PLI. Thanks.

epg_B: <type 'long'> epg_D: <type 'long'> hmval: <type 'str'> hmget: <type 'int'>

Thanks. On Vix that third value is an int too.

I'll add that in to the next release (should be ready this weekend).

[abu baniaz]

Also tried it on ViX and still works.

[birdman]

Next release is here. 2.02-rc1

This can handle "any" length of query to Google translate (by splitting it into pieces on a sentence boundary then putting it back together).
It adds an option to show a one-level traceback in the debug log if there is a problem translating (so I don't need to send Abu a debug version if PLi has a problem again - which it shouldn't).

There are also various internal code tidy-ups, simplifications and rationalizations.

You'll find it in the download thread.

[Huevos]

@Birdman, what is your plan for this? Is it open source? Can I add it to our plugins repo so we can build it from source rather than having a precompiled, third-party IPK?

1.jpg

2.jpg

[Huevos]

        except Exception as e:  # Use originals on a failure...
            print("[EPGTranslator-Plugin] translateEPG error:", e)
            if (CfgPlTr.showtrace,getValue()): traceback.print_exc()
            (t_title, t_descr) = (title, descr)

This line here:

if (CfgPlTr.showtrace,getValue()): traceback.print_exc()

You've got a comma in there.

I also got this:

[EPGTranslator-Plugin] translateEPG error: need more than 1 value to unpack

[birdman]

        except Exception as e:  # Use originals on a failure...
            print("[EPGTranslator-Plugin] translateEPG error:", e)
            if (CfgPlTr.showtrace,getValue()): traceback.print_exc()
            (t_title, t_descr) = (title, descr)

This line here:

if (CfgPlTr.showtrace,getValue()): traceback.print_exc()

You've got a comma in there.

!!!!????
How did that get there???
Fix along shortly....

I also got this:

[EPGTranslator-Plugin] translateEPG error: need more than 1 value to unpack

Which means it failed to translate - somehow. This is the message from a split() when what it is splitting on isn't there.
I'm still used to Perl, which does the more friendly option of setting the empty bits to undef.
But either way, it will have failed to translate and so have little or nothing to show.

[birdman]

2.02-rc2, with the type fixed is now in the download thread.

[birdman]

@Birdman, what is your plan for this? Is it open source?

Well, the original code came from a now defunct source. As far as I'm concerned all of my bits are open source.

Can I add it to our plugins repo so we can build it from source rather than having a precompiled, third-party IPK?

In theory, yes; but there isn't any method there at the moment to pre-compile it.

[Huevos]

In theory, yes; but there isn't any method there at the moment to pre-compile it.

Don't worry about that. I'll get that bit working.

[Huevos]

I've added to oe-alliance-plugins.
https://github.com/oe-alliance/oe-al.../EPGTranslator

Should be in the Release build.

One minor change, I have added button labels... doesn't affect the embedded skin.