Re: [vdr] polarization character case in channels.conf

2012-12-03 Thread Klaus Schmidinger
On 08.11.2012 21:14, Klaus Schmidinger wrote: On 08.11.2012, at 20:43, Stefan Huelswitt wrote: Hi, I can confirm this problem, at least in 1.7.27 (which I'm using at the moment). I use the attached patch to resolve it. Am 08.11.2012 10:19, schrieb Klaus Schmidinger: Well, there is a touppe

Re: [vdr] polarization character case in channels.conf

2012-11-08 Thread Klaus Schmidinger
On 08.11.2012, at 20:43, Stefan Huelswitt wrote: > Hi, > > I can confirm this problem, at least in 1.7.27 (which I'm using at the > moment). I use the attached patch to resolve it. > > Am 08.11.2012 10:19, schrieb Klaus Schmidinger: Well, there is a toupper() in cDvbTransponderParameters:

Re: [vdr] polarization character case in channels.conf

2012-11-08 Thread Stefan Huelswitt
Hi, I can confirm this problem, at least in 1.7.27 (which I'm using at the moment). I use the attached patch to resolve it. Am 08.11.2012 10:19, schrieb Klaus Schmidinger: Well, there is a toupper() in cDvbTransponderParameters::Parse(), so I would expect that all characters can be given in e

Re: [vdr] polarization character case in channels.conf

2012-11-08 Thread Mike Hay
Well, there is a toupper() in cDvbTransponderParameters::Parse(), so I would expect that all characters can be given in either upper- or lowercase. Are you sure the case was the problem? Klaus I'm pretty sure it is the case as I have tested the following two strings with no other changes and

Re: [vdr] polarization character case in channels.conf

2012-11-08 Thread Klaus Schmidinger
On 07.11.2012 17:12, Mike Hay wrote: Well, there is a toupper() in cDvbTransponderParameters::Parse(), so I would expect that all characters can be given in either upper- or lowercase. Are you sure the case was the problem? Klaus I'm pretty sure it is the case as I have tested the following t

Re: [vdr] polarization character case in channels.conf

2012-11-07 Thread Timothy D. Lenz
I have used upper and lower case to denote for different sources in the past in diseqc.conf and it worked. Case needs to, or needed to in the past, match. On 11/7/2012 9:12 AM, Mike Hay wrote: Well, there is a toupper() in cDvbTransponderParameters::Parse(), so I would expect that all characte

Re: [vdr] polarization character case in channels.conf

2012-11-07 Thread Mike Hay
Well, there is a toupper() in cDvbTransponderParameters::Parse(), so I would expect that all characters can be given in either upper- or lowercase. Are you sure the case was the problem? Klaus I'm pretty sure it is the case as I have tested the following two strings with no other changes and

Re: [vdr] polarization character case in channels.conf

2012-11-07 Thread Klaus Schmidinger
On 07.11.2012 15:36, Mike Hay wrote: Hi list, I recently lost access to all vertically polarised channels and after quite a bit of floundering about I discovered the reason for this is due to the case of the polarisation character in channels.conf. According to the vdr changelog it has been p

[vdr] polarization character case in channels.conf

2012-11-07 Thread Mike Hay
Hi list, I recently lost access to all vertically polarised channels and after quite a bit of floundering about I discovered the reason for this is due to the case of the polarisation character in channels.conf. According to the vdr changelog it has been possible to specify this in either up