-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 10, 2003 10:41 am, Aubin Paul wrote:
> On Thu, Jul 10, 2003 at 12:41:56AM -0300, James Oakley wrote:
> > That's what I didn't like about this temporary solution. If all channels
> > were numeric, I could simply use .isdigit() and it wouldn't be
On Thu, Jul 10, 2003 at 12:41:56AM -0300, James Oakley wrote:
> That's what I didn't like about this temporary solution. If all channels were
> numeric, I could simply use .isdigit() and it wouldn't be so bad, but this is
> not the case.
How does the TV tuner card cope with non-numeric channels?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 10, 2003 12:08 am, Aubin Paul wrote:
> How does a channel with letters in it work? Agh. So there is no way to
> be sure then? This could be annoying.
That's what I didn't like about this temporary solution. If all channels were
numeric, I co
On Thu, Jul 10, 2003 at 12:02:54AM -0300, James Oakley wrote:
> There's no guarantee of the order of those elements, especially in other
> grabbers when they start using this convention. Ed Avis said that people
> writing applications should use the one with the single number as the channel
> an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 9, 2003 11:15 pm, Aubin Paul wrote:
> > for dn in channels['display-name']:
> > if len(dn.split()) == 1:
> > channelnum = dn
> > else:
> > display_name = dn
> >
> > This works for tv_grab_na, but I'm not sure ab
On Wed, Jul 09, 2003 at 07:20:37PM -0300, James Oakley wrote:
> It will be in 0.6.
Cool...
> for dn in channels['display-name']:
> if len(dn.split()) == 1:
> channelnum = dn
> else:
> display_name = dn
>
> This works for tv_grab_na, but I'm not sure about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 9, 2003 10:03 am, Aubin Paul wrote:
> Eep. How would we cope with that? Wouldn't the second 'display_name'
> override the first? I'm guessing this won't affect our current
> implementation because we don't use display_name but since I want to
>
Eep. How would we cope with that? Wouldn't the second 'display_name'
override the first? I'm guessing this won't affect our current
implementation because we don't use display_name but since I want to
move to generating the channels automatically without creating a local
array of entries, it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> That's a known deficiency in XMLTV 0.5 that's fixed in 0.6. Until then, the
> format of display-name shouldn't change.
As it turns out, I'm wrong about this. tv_grab_na in XMLTV 0.5.15 uses a
different format for display-name. I'll quote Ed Avis: