Re: [vdr] vdr-1.5.3 - LANG="[EMAIL PROTECTED]" not recognized

2007-06-11 Thread Johannes Stezenbach
On Mon, Jun 11, 2007, Stefan Taferner wrote:
> 
> setlocale(LC_CTYPE, "") sets the locale to nothing -- what you probably meant
> is setlocale(LC_CTYPE, 0) ... just to clarify things, in case somebody wants
> to use the knowledge of these emails later :-)

This contradicts the setlocale(3) man page.


HTH,
Johannes

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Oleg Roitburd
Am Sonntag, 10. Juni 2007 15:45 schrieb Klaus Schmidinger:
> VDR developer version 1.5.3 is now available at
>
> ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2

Now I'm running this version.
And I would say: Converting of EPG to UTF-8 don't work
My system has  DVB-T card and I'm receiving only German "ÖRP" 
In schedule menuitem I can't see any umlaut or "ß" 
$LANG is setting to en_US.UTF-8
For my stable version 1.4.x I'm using UTF patch from Alexander Riedel. As I 
remember he has inserted extra field for channel codepage. And this works. 

Regards
Oleg Roitburd

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Klaus Schmidinger
On 06/11/2007 10:08 AM, Oleg Roitburd wrote:
> Am Sonntag, 10. Juni 2007 15:45 schrieb Klaus Schmidinger:
>> VDR developer version 1.5.3 is now available at
>>
>> ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2
> 
> Now I'm running this version.
> And I would say: Converting of EPG to UTF-8 don't work
> My system has  DVB-T card and I'm receiving only German "ÖRP" 
> In schedule menuitem I can't see any umlaut or "ß" 
> $LANG is setting to en_US.UTF-8

Please check whether the log says that the codeset is "known"
(should be right after VDR's startup message).

You may need to set LANG=en_US.utf8 (without the '-').
Maybe the strings in libsi/si.c should contain the extra '-'s,
not sure what's best.

All I can say is that this works just fine here.

> For my stable version 1.4.x I'm using UTF patch from Alexander Riedel. As I 
> remember he has inserted extra field for channel codepage. And this works. 

Using such an extra field is not the way to go, because there is no
standard way to fill it in (or is there?).

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Oleg Roitburd
Am Montag, 11. Juni 2007 10:14 schrieb Klaus Schmidinger:
> On 06/11/2007 10:08 AM, Oleg Roitburd wrote:
> > $LANG is setting to en_US.UTF-8
>
> Please check whether the log says that the codeset is "known"
> (should be right after VDR's startup message).

yes...you are right
Jun 11 10:10:53 compaq vdr: [18482] VDR version 1.5.3 started
Jun 11 10:10:53 compaq vdr: [18482] codeset is 'UTF-8' - unknown

>
> You may need to set LANG=en_US.utf8 (without the '-').
> Maybe the strings in libsi/si.c should contain the extra '-'s,
> not sure what's best.
>
> All I can say is that this works just fine here.

OK. this works
LANG=en_US.utf8 ./vdr -c /etc/vdr -P"softdevice -vo xv:"
I would say, vdr need better recognizing of locales (eliminated of "-" and 
tolower())

>
> > For my stable version 1.4.x I'm using UTF patch from Alexander Riedel. As
> > I remember he has inserted extra field for channel codepage. And this
> > works.
>
> Using such an extra field is not the way to go, because there is no
> standard way to fill it in (or is there?).

Automagicaly it was ever filled with iso8859-15, for all other codepages was 
handmade job

Regards
Oleg Roitburd

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Ludwig Nussel
Klaus Schmidinger wrote:
> On 06/11/2007 10:08 AM, Oleg Roitburd wrote:
> > Am Sonntag, 10. Juni 2007 15:45 schrieb Klaus Schmidinger:
> >> VDR developer version 1.5.3 is now available at
> >>
> >> ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2
> > 
> > Now I'm running this version.
> > And I would say: Converting of EPG to UTF-8 don't work
> > My system has  DVB-T card and I'm receiving only German "ÖRP" 
> > In schedule menuitem I can't see any umlaut or "ß" 
> > $LANG is setting to en_US.UTF-8
> 
> Please check whether the log says that the codeset is "known"
> (should be right after VDR's startup message).
> 
> You may need to set LANG=en_US.utf8 (without the '-').
> Maybe the strings in libsi/si.c should contain the extra '-'s,
> not sure what's best.

$ LC_ALL=en_US.utf8 locale collate-codeset
UTF-8

so the canonical spelling is "UTF-8". As already suggested using
nl_langinfo() instead of manually parsing enviroment variables is
probably the better choice though.

> > For my stable version 1.4.x I'm using UTF patch from Alexander Riedel. As I 
> > remember he has inserted extra field for channel codepage. And this works. 
> 
> Using such an extra field is not the way to go, because there is no
> standard way to fill it in (or is there?).

ACK, considering that libsi can automatically determine the encoding
for individual strings it seems to be awkward having to specify
encodings per channel in channels.conf.

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\   
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Klaus Schmidinger
On 06/11/2007 11:27 AM, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> On 06/11/2007 10:08 AM, Oleg Roitburd wrote:
>>> Am Sonntag, 10. Juni 2007 15:45 schrieb Klaus Schmidinger:
 VDR developer version 1.5.3 is now available at

 ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2
>>> Now I'm running this version.
>>> And I would say: Converting of EPG to UTF-8 don't work
>>> My system has  DVB-T card and I'm receiving only German "ÖRP" 
>>> In schedule menuitem I can't see any umlaut or "ß" 
>>> $LANG is setting to en_US.UTF-8
>> Please check whether the log says that the codeset is "known"
>> (should be right after VDR's startup message).
>>
>> You may need to set LANG=en_US.utf8 (without the '-').
>> Maybe the strings in libsi/si.c should contain the extra '-'s,
>> not sure what's best.
> 
> $ LC_ALL=en_US.utf8 locale collate-codeset
> UTF-8
> 
> so the canonical spelling is "UTF-8". As already suggested using
> nl_langinfo() instead of manually parsing enviroment variables is
> probably the better choice though.

Thanks, I'll change it then.

>>> For my stable version 1.4.x I'm using UTF patch from Alexander Riedel. As I 
>>> remember he has inserted extra field for channel codepage. And this works. 
>> Using such an extra field is not the way to go, because there is no
>> standard way to fill it in (or is there?).
> 
> ACK, considering that libsi can automatically determine the encoding
> for individual strings it seems to be awkward having to specify
> encodings per channel in channels.conf.

The latest version of libsi does use the character encodings specified
in the SI data for each string. Unfortunately, though, a certain German
pay tv broadcaster doesn't adhere to the standard and sends the data in
iso8859, but without marking the strings accordingly. So VDR assumes
that they are ISO6937 (which is the default if no encoding is specified)
and therefore converts the umlauts to garbage.
But that's their fault, not VDR's...

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Ludwig Nussel
Klaus Schmidinger wrote:
> The latest version of libsi does use the character encodings specified
> in the SI data for each string. Unfortunately, though, a certain German
> pay tv broadcaster doesn't adhere to the standard and sends the data in
> iso8859, but without marking the strings accordingly. So VDR assumes
> that they are ISO6937 (which is the default if no encoding is specified)
> and therefore converts the umlauts to garbage.
> But that's their fault, not VDR's...

How do standalone dvb receivers deal with that? Do they have an
extra workaround for that particular broadcaster?

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\   
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread Klaus Schmidinger
On 06/11/2007 11:50 AM, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> The latest version of libsi does use the character encodings specified
>> in the SI data for each string. Unfortunately, though, a certain German
>> pay tv broadcaster doesn't adhere to the standard and sends the data in
>> iso8859, but without marking the strings accordingly. So VDR assumes
>> that they are ISO6937 (which is the default if no encoding is specified)
>> and therefore converts the umlauts to garbage.
>> But that's their fault, not VDR's...
> 
> How do standalone dvb receivers deal with that? Do they have an
> extra workaround for that particular broadcaster?

I guess they do, because they need to be "certified for P***" ;-)

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] How to use vdr with DVB-T - channels.conf error

2007-06-11 Thread Pirlouwi

Hello everybody,
I live in Belgium, and would like to setup vdr with a budget DVB-T USB
Freecom Stick.
DVB-T is working well on my system with mplayer, xine, Kaffeine.
I have generated the required channels.conf for that, using scandvb
application.
But, with vdr (1.4.7), my channels.conf does not work.
I get this error:
$ ./runvdr
vdr: error while reading '/video/channels.conf'

When I use the original channels.conf given with vdr installation, I do not
get this error, but it does not correspond to my settings so it is useless.
The format of given channels.conf seems to be different from the one
generated by scandvb for DVB-T.
Here is an excerpt of both files:

Original VDR channels.conf
RTL Television,RTL;RTL World:12187:hC34:S19.2E
:27500:163:104=deu;106=deu:105:0:12003:1:1089:0


My channels.conf
LA
UNE:75400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:33:34:1

Could somebody help me on that issue?
Thx.

LOUIS
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] How to use vdr with DVB-T - channels.conf error

2007-06-11 Thread Andreas Mueller
Pirlouwi wrote:
> My channels.conf
> LA
> UNE:75400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:
>TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:33:34:1
>
> Could somebody help me on that issue?

Use scandvb with the option "-o vdr".

Andreas.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] How to use vdr with DVB-T - channels.conf error

2007-06-11 Thread Simon Baxter
You have the wrong format in channels.conf

check 'man 5 vdr'


  - Original Message - 
  From: Pirlouwi 
  To: vdr@linuxtv.org 
  Sent: Monday, June 11, 2007 10:15 PM
  Subject: [vdr] How to use vdr with DVB-T - channels.conf error


  Hello everybody,
  I live in Belgium, and would like to setup vdr with a budget DVB-T USB 
Freecom Stick.
  DVB-T is working well on my system with mplayer, xine, Kaffeine.
  I have generated the required channels.conf for that, using scandvb 
application. 
  But, with vdr (1.4.7), my channels.conf does not work.
  I get this error:
  $ ./runvdr
  vdr: error while reading '/video/channels.conf'

  When I use the original channels.conf given with vdr installation, I do not 
get this error, but it does not correspond to my settings so it is useless. 
  The format of given channels.conf seems to be different from the one 
generated by scandvb for DVB-T.
  Here is an excerpt of both files:

  Original VDR channels.conf
  RTL Television,RTL;RTL 
World:12187:hC34:S19.2E:27500:163:104=deu;106=deu:105:0:12003:1:1089:0


  My channels.conf
  LA 
UNE:75400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:33:34:1

  Could somebody help me on that issue? 
  Thx.

  LOUIS




--


  ___
  vdr mailing list
  vdr@linuxtv.org
  http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] VDR exited with status 134

2007-06-11 Thread Kartsa
Ville Skyttä kirjoitti:
> On Sunday 10 June 2007, Kartsa wrote:
>   
>> I've got fedora with runvdr from fedora vdr package and it tries to
>> restart VDR if exit code is something else than 0, 2 or 137. Sometimes
>> the exit code is 137 but most of the time it is 134. This causes VDR to
>> restart (or runvdr makes VDR to restart) and dvb drivers to reload.
>>
>> What does exit code 134 mean?
>> 
>
> >From "man bash":
> The return value of a simple command is its exit status, or 128+n if the 
> command is terminated by signal n.
>
> So 134 - 128 = 6, SIGABRT ("kill -l 6").  "info SIGABRT" says:
> This signal indicates an error detected by the program itself and reported by 
> calling `abort'.
>   
Ah, did not think of  that. Thanks.
>> Why is exit code sometimes 137 and most of the times 134?
>> 
>
> It's 137 when killproc (see /etc/init.d/functions) invoked 
> from /etc/init.d/vdr gets tired of waiting for "kill -TERM" to result in vdr 
> to shut down and issues a "kill -KILL" to really get rid of it.  It's 134 
> when you got a "crash" caused by SIGABRT.
>
> If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at 
> end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp.
>   
I'll give it a try. Would -t switch be helpfull with shutdown?
>> What should exit code be when VDR is shutting down either because the
>> user pushed power button or because there has been no user activity?
>> 
>
> 0 if all went well (and if I remember correctly).
>   
Seems that it never is 0. At least in my case. Maybe I'll try VDR with 
no plugins.
>> I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some
>> plugins not in fedora packaging).
>> 
>
> In my experience, crashes at vdr shutdown are almost always caused by plugin 
> bugs.  I'm not aware of any such in the Fedora plugin packages at the moment.
>
> By the way, which packaged plugins are you missing/adding?  The last 
> crash-at-shutdown bug I saw was in ttxtsubs; in case you're using it, my 
> patch for the crash is included in Rofa's "kermanekka" edition 
> (http://www.saunalahti.fi/~rahrenbe/vdr/patches/, Fedora 7 packages at 
> http://cachalot.mine.nu/ and possibly sometime soonish in Fedora proper).
>   
I am using ttxtsubs. I do not actually need it more than occasionally 
because I have no channels witch uses this subtitling system. Maybe I 
could try without it.
> Also, just in case you weren't aware of it, if your additional plugins don't 
> require patching vdr itself (patches for subtitles and ttxtsubs plugins are 
> already included), you can use Fedora's vdr and vdr-devel packages and build 
> additional plugins for it instead of building a whole vdr of your own, 
> see /usr/share/doc/vdr-*/README.package
>   
I am compiling vdr my self mostly because I like Soppalusikka :) I think 
there was some other reason(s) as well but I can not recall what :)
I had newer actually read the README.package and it was wery illuminating.
Maybe I'll have to start using readymade packages and give up using  
Soppalusikka :(


\\Kartsa

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] VDR exited with status 134

2007-06-11 Thread Ville Skyttä
On Monday 11 June 2007, Kartsa wrote:
> Ville Skyttä kirjoitti:
> >
> > If you wish to debug it further, uncomment
> > DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if
> > core dumps start to appear in /tmp.
>
> I'll give it a try. Would -t switch be helpfull with shutdown?

No idea, I've never used that switch myself.

One possibly way to find out if the abort is because of some plugin is to 
watch /var/log/messages when shutting down vdr and to see what the last 
output before "runvdr: VDR exited with status ..." is.  If it's not "vdr: 
[...] exiting" but rather "vdr: [...] stopping plugin: foo" or "vdr: [...] 
deleting plugin: foo", it's pretty likely that the foo plugin is somehow 
involved.

> I am compiling vdr my self mostly because I like Soppalusikka :) I think
> there was some other reason(s) as well but I can not recall what :)
> I had newer actually read the README.package and it was wery illuminating.
> Maybe I'll have to start using readymade packages and give up using
> Soppalusikka :(

I don't think soppalusikka (in case you're referring to the skin) requires any 
patches to vdr, so it should be usable and buildable with the packaged 
version too.  Some dirs are obviously a bit different than in the install 
instructions, but README.package and "rpm -ql vdr" should help with those.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] vdr-1.5.3 - issue with translations out of plugins

2007-06-11 Thread Alexander Riedel
Hi All, hi Klaus,

here is a patch for this problem:


--- /home/riedel/GENS/orig-vdr/vdr-1.5.3.orig/i18n.c2007-06-09 
10:44:54.0 +0200
+++ /home/riedel/GENS/orig-vdr/vdr-1.5.3/i18n.c 2007-06-11 23:40:43.0 
+0200
@@ -6820,7 +6820,7 @@
   *Converted = new tI18nPhrase[NumPhrases + 1];
   memset(*Converted, 0, sizeof(tI18nPhrase) * (NumPhrases + 1));
   }
-  if (!(*Converted)[NrPhrase][NrLanguage]) {
+  if (!(*Converted)[NrPhrase][NrLanguage] && Original[NrPhrase][NrLanguage] ) {
   cCharSetConv csc(Phrases[1][NrLanguage], 
cCharSetConv::SystemCharacterTable());
   (*Converted)[NrPhrase][NrLanguage] = 
strdup(csc.Convert(Original[NrPhrase][NrLanguage]));
   }


Now work it for other Languages, for example with OSDLanguage = 16

Klaus Schmidinger wrote:
> On 06/10/07 21:43, Joachim Wilke wrote:
>> Hi Klaus,
>>
>> I just installed vdr-1.5.3, but lcdproc plugin caused vdr to crash on
>> startup. I figured out that the problem is the translation of the
>> string "Volume ". Unlike the other strings that are used by the plugin
>> this string is provided by the vdr-core i18n.c This worked fine in
>> vdr-1.5.1. Adding a dummy translation of "Volume " directly in the
>> plugins i18n.c "fixed" the crash. Is this the intended behaviour? Or
>> was this a feature by accident? ;-)
> 
> This was certainly unintended.
> I'll look into it.
> 
> Klaus
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] updated text2skin for vdr-1.5.3 and enigma?

2007-06-11 Thread Stone

On 6/10/07, Stone <[EMAIL PROTECTED]> wrote:


Hello,

I am currently using vdr-text2skin-1.1-cvs_ext-0.10.tgz with
Enigma-0.4pre9 from vdrportal.  Is there an updated version of text2skin
for vdr-1.5.3 (or perhaps even better, a patch against current text2skin
cvs)?





Answering my own question, here is a patch to fix
vdr-text2skin-1.1-cvs_ext-0.10 for use with vdr-1.5.3 and Enigma-0.4pre9.
Please let me know if you spot any problems.
Regards.


vdr-1.5.3-t2s.diff
Description: Binary data


text2skin-1.1-cvs_ext-0.10-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] Plugin patches for vdr-1.5.3

2007-06-11 Thread Stone

Hi,

Attached is a patch for vdr-1.5.3 and the timeline-1.0.141 plugin.  Please
let me know if this patch is incorrect.  Also, I am currently looking for
patches to fix epgsearch-0.9.22, tvonscreen-0.7.0, and liemikuutio.


timeline-1.0.141-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Plugin patches for vdr-1.5.3

2007-06-11 Thread Stone

On 6/12/07, Stone <[EMAIL PROTECTED]> wrote:


Hi,

Attached is a patch for vdr-1.5.3 and the timeline-1.0.141 plugin.  Please
let me know if this patch is incorrect.  Also, I am currently looking for
patches to fix epgsearch-0.9.22, tvonscreen-0.7.0, and liemikuutio.





Here is also a fix for yaepg and vdr-1.5.3.

Regards.


vdr-1.5.3-core-yaepg.diff
Description: Binary data


yaepg-0.0.2.1-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3

2007-06-11 Thread VDR User
On 6/10/07, Rolf Ahrenberg <[EMAIL PROTECTED]> wrote:
> On Sun, 10 Jun 2007, Klaus Schmidinger wrote:
>
> > Well, it's a real pitty with the various systems putting files
> > at random places.
>
> How about setting the FONTDIR configurable through Make.config or ever
> commandline switch?

Yes, I also think this would be the best solution unless theres a sane
reason to not handle it like the video dir.  A default setting in
Make.config and a commandline switch to override.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr