Re: [vdr] vdr-1.5.3 - issue with translations out of plugins
On 06/13/07 00:21, [EMAIL PROTECTED] wrote: > unfortunately this patches do not fix Transtation problems complete. > i still have segmentation faults for example with softdevice plugin. > maybe this help: vdr has translation "none". softdevice as also > "none". > at this translation "none" have i core dumps... Well, it was just a quick shot. I'll look into it over the weekened. > Klaus what about gettext? This ist better alternative to "Home-made" > converting. In the long run this is the plan, but as a first step I wanted to do the freetype and UTF-8 stuff separately. > Or minimaly without on the fly converting of i18n strings, these string > use from the begin as utf8 strings. At least the German texts need to remain iso8859-1, because I maintain these myself ;-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Freeview Playback
Hi, My understanding is that the updated epg data has been transmitted here in the uK across all dvb-t mux's since about March/April. Not all channels may have completely updated there backend systems yet but all the major channels have done so. Clearly launching the Freeview Playback 'brand' and therefore its feature set means the epg data must be broadly available for these new PVR boxes to work as advertised. So the data must be there somewhere ;-) Andrew On 6/12/07, Dave P <[EMAIL PROTECTED]> wrote: On Tuesday 12 Jun 2007, Alex Stansfield wrote: > Hi, > > with the launch of Freeview Playback in the UK, I was wondering if > anyone here knew how the series links were sent to the dvb box. > > Freeview Playback is a system by which series link information is sent > to the dvb box, allowing someone to select to record a whole series. > Some sort of link information is sent, I guess in the epg, about each > episode so that the dvb box can be sure it's always recording unique > episodes of a series. > > I thought that support for Freeview Playback would be an excellent > addition to plugins like epgsearch. > > If anyone knows any more about how the system works or has the DTG > specification (can't see it on their website) please let me know. The EPG format is covered by this document (which I think is the latest issue) http://webapp.etsi.org/action/OP/OP20060428/en_300468v010701o.pdf so presumably the data fits in to the specification somehow. I looked through this and also checked the broadcast data with dvbsnoop last weekend but couldn't see anything obvious. Maybe no-one is broadcasting the links yet. It would certainly be an excellent addition to VDR. Dave ___ 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-1.5.3 - issue with translations out of plugins
unfortunately this patches do not fix Transtation problems complete. i still have segmentation faults for example with softdevice plugin. maybe this help: vdr has translation "none". softdevice as also "none". at this translation "none" have i core dumps... Klaus what about gettext? This ist better alternative to "Home-made" converting. Or minimaly without on the fly converting of i18n strings, these string use from the begin as utf8 strings. ?? -Original Message- Date: Tue, 12 Jun 2007 23:41:37 +0200 Subject: Re: [vdr] vdr-1.5.3 - issue with translations out of plugins From: Klaus Schmidinger <[EMAIL PROTECTED]> To: vdr@linuxtv.org On 06/12/07 22:54, [EMAIL PROTECTED] wrote: > Hi, > please try both patches together. > I have also problems after ma first patch with softdevice translations, > but now with Christian's patch is OK. I haven't had much time to look into this, yet, but I believe the attached patch should be all it takes to fix this. Can you please try this one? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
On 06/12/07 23:09, Oleg Roitburd wrote: > On Tue, 2007-06-12 at 17:46 +0200, Klaus Schmidinger wrote: >> The function ExchangeChars() in VDR/recording.c converts characters >> that can't be used in file names on Windows to "#XX", where XX is >> the hex code of the character. > > Sorry ... I don't understand and can't find any sence. > If you export for window, you make this with SAMBA. And you can > configure share with UTF-8 > man smb.conf > - > unix charset (G) >Specifies the charset the unix machine Samba runs on uses. Samba >needs to know this in order to be able to convert text to the >charsets other SMB clients use. > >This is also the charset Samba will use when specifying argu� >ments to scripts that it invokes. > >Default: unix charset = UTF8 > > > you can drop VFAT part > > Regards > Oleg Roitburd Well, that would be the optimal solution :-) Any objections? Klaus ___ 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
On 06/12/07 22:54, [EMAIL PROTECTED] wrote:
> Hi,
> please try both patches together.
> I have also problems after ma first patch with softdevice translations,
> but now with Christian's patch is OK.
I haven't had much time to look into this, yet,
but I believe the attached patch should be all it takes
to fix this.
Can you please try this one?
Klaus
--- i18n.c 2007/06/09 08:44:54 1.294
+++ i18n.c 2007/06/12 21:31:19
@@ -6851,7 +6851,8 @@
return t;
}
}
- p = Phrases;
+ p = OriginalPhrases = Phrases;
+ ConvertedPhrases = &Converted;
}
esyslog("%s%sno translation found for '%s' in language %d (%s)", Plugin ? Plugin : "", Plugin ? ": " : "", s, Setup.OSDLanguage, Phrases[0][Setup.OSDLanguage]);
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
On 06/12/07 23:31, [EMAIL PROTECTED] wrote: > Hi, > > i think we need a list of INVALID CHARACTERS and not inverted I thought I had asked for that... Klaus > -Original Message- > Date: Tue, 12 Jun 2007 17:46:39 +0200 > Subject: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars() > From: Klaus Schmidinger <[EMAIL PROTECTED]> > To: vdr@linuxtv.org > > The function ExchangeChars() in VDR/recording.c converts characters > that can't be used in file names on Windows to "#XX", where XX is > the hex code of the character. > > This was simple when VDR only worked with single byte character sets, > but now that it can handle UTF-8 this needs to be changed, too. > > Currently it has a list of characters that can be used "as is", > and converts everything else to "#XX". I guess it is better > to convert any "disturbing" characters to "#XX" and leave the > rest untouched. However, this requires that we know exactly > which characters can't be used with Windows. > > Does anybody have that kind of information? > Or should this be done completely different? > > Note that I don't use this feature myself, so unless there > is some input from others, I won't be changing anything here. > > Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
On Tue, 2007-06-12 at 17:46 +0200, Klaus Schmidinger wrote: > The function ExchangeChars() in VDR/recording.c converts characters > that can't be used in file names on Windows to "#XX", where XX is > the hex code of the character. Sorry ... I don't understand and can't find any sence. If you export for window, you make this with SAMBA. And you can configure share with UTF-8 man smb.conf - unix charset (G) Specifies the charset the unix machine Samba runs on uses. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use. This is also the charset Samba will use when specifying argu‐ ments to scripts that it invokes. Default: unix charset = UTF8 you can drop VFAT part Regards Oleg Roitburd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
Hi,i think we need a list of INVALID CHARACTERS and not inverted -Original Message- Date: Tue, 12 Jun 2007 17:46:39 +0200 Subject: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars() From: Klaus Schmidinger <[EMAIL PROTECTED]> To: vdr@linuxtv.org The function ExchangeChars() in VDR/recording.c converts characters that can't be used in file names on Windows to "#XX", where XX is the hex code of the character. This was simple when VDR only worked with single byte character sets, but now that it can handle UTF-8 this needs to be changed, too. Currently it has a list of characters that can be used "as is", and converts everything else to "#XX". I guess it is better to convert any "disturbing" characters to "#XX" and leave the rest untouched. However, this requires that we know exactly which characters can't be used with Windows. Does anybody have that kind of information? Or should this be done completely different? Note that I don't use this feature myself, so unless there is some input from others, I won't be changing anything here. 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] VDR 1.5.3: UTF-8 vs. ExchangeChars()
On 06/12/07 23:09, [EMAIL PROTECTED] wrote: > also * ? ! I was wondering already about "Invalid characters *include*", which to me means that there are probably more than these. Ok, so far we have . " / \ [ ] : ; = , and * ? ! However, '!' is in the list of characters that can be used "as is" right now, so where do you take it from that this character is also invalid? Also: the '.' is perfectly ok, unless at the end of a directory name. So, from my point of view the characters to be exchanged to "#XX" are " / \ [ ] : ; = , * ? and . at the end of a directory name Any others? Klaus "The day Microsoft invents something that doesn't suck, it will be a vacuum cleaner." - anon > -Original Message- > Date: Tue, 12 Jun 2007 18:28:10 +0200 > Subject: Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars() > From: Stone > To: "VDR Mailing List" > > > > On 6/12/07, KLAUS SCHMIDINGER wrote: The function ExchangeChars() > in VDR/recording.c converts characters > that can't be used in file names on Windows to "#XX", where XX is > > the hex code of the character. > > This was simple when VDR only worked with single byte character sets, > but now that it can handle UTF-8 this needs to be changed, too. > > Currently it has a list of characters that can be used "as is", > and converts everything else to "#XX". I guess it is better > to convert any "disturbing" characters to "#XX" and leave the > rest untouched. However, this requires that we know exactly > which characters can't be used with Windows. > > Does anybody have that kind of information? > Or should this be done completely different? > > Note that I don't use this feature myself, so unless there > is some input from others, I won't be changing anything here. > I use this FAT feature so I can mount my linux drive on windows and > stream movies with vdradmin to my windows machine. I have noticed > that VDR might currently be renaming a little more than is required. > Invalid characters include: . " / [ ] : ; = , > http://support.microsoft.com/kb/142982 [2] Regards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
also * ? ! -Original Message- Date: Tue, 12 Jun 2007 18:28:10 +0200 Subject: Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars() From: Stone To: "VDR Mailing List" On 6/12/07, KLAUS SCHMIDINGER wrote: The function ExchangeChars() in VDR/recording.c converts characters that can't be used in file names on Windows to "#XX", where XX is the hex code of the character. This was simple when VDR only worked with single byte character sets, but now that it can handle UTF-8 this needs to be changed, too. Currently it has a list of characters that can be used "as is", and converts everything else to "#XX". I guess it is better to convert any "disturbing" characters to "#XX" and leave the rest untouched. However, this requires that we know exactly which characters can't be used with Windows. Does anybody have that kind of information? Or should this be done completely different? Note that I don't use this feature myself, so unless there is some input from others, I won't be changing anything here. I use this FAT feature so I can mount my linux drive on windows and stream movies with vdradmin to my windows machine. I have noticed that VDR might currently be renaming a little more than is required. Invalid characters include: . " / [ ] : ; = , http://support.microsoft.com/kb/142982 [2] Regards. Links: -- [1] mailto:[EMAIL PROTECTED] [2] http://support.microsoft.com/kb/142982 ___ 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
Hi,
please try both patches together.
I have also problems after ma first patch with softdevice translations,
but now with Christian's patch is OK.
-Original Message-
Date: Tue, 12 Jun 2007 20:35:29 +0200
Subject: Re: [vdr] vdr-1.5.3 - issue with translations out of plugins
From: "Joachim Wilke"
To: "VDR Mailing List"
2007/6/12, Christian Wieninger :
> I still had crashes even when using Alexanders patch.
> I think the fix should look like this (diff against plain 1.5.3):
Hi,
I'm sorry but neither the first nor the second patch do work here. I
still get an segfault when lcdproc tries to translate "Volume ".
Regards,
Joachim.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--- /home/riedel/GENS/orig-vdr/vdr-1.5.3.orig/i18n.c 2007-06-09 10:44:54.0 +0200
+++ /home/riedel/GENS/orig-vdr/vdr-1.5.3/i18n.c 2007-06-12 22:47:38.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]));
}
@@ -6851,7 +6851,7 @@
return t;
}
}
- p = Phrases;
+ p = OriginalPhrases = Phrases;
}
esyslog("%s%sno translation found for '%s' in language %d (%s)", Plugin ? Plugin : "", Plugin ? ": " : "", s, Setup.OSDLanguage, Phrases[0][Setup.OSDLanguage]);
}
___
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/6/12, Christian Wieninger <[EMAIL PROTECTED]>: > I still had crashes even when using Alexanders patch. > I think the fix should look like this (diff against plain 1.5.3): Hi, I'm sorry but neither the first nor the second patch do work here. I still get an segfault when lcdproc tries to translate "Volume ". Regards, Joachim. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr in client-server configuration?
Klaus Schmidinger wrote: > On 06/12/07 18:02, Oliver Joa wrote: >> Hi, >> >> i use vdr since a long time, i still use version 1.3.23 on 3 Computers. >> The last months/years i did not follow the development. Is there already >> a solution for the client-server Problem? I wonder if it is possible to >> have 1 server recording and streaming to 2 client. And the clients >> possible to start recordings on the server. Maybe the possibility to see >> the osd of the server on the clients... > > Take a look at http://www.magoa.net/linux. Thats fairly ancient, there was short thread here 9.6.2007 with subject "Configuring vdr-sxfe to use a single vdr backend for recordings/dvb cards" ___ 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
Hi,
I still had crashes even when using Alexanders patch.
I think the fix should look like this (diff against plain 1.5.3):
--- vdr-1.5.3/i18n.c2007-06-09 10:44:54.0 +0200
+++ vdr-1.5.3-patched/i18n.c2007-06-12 19:40:42.0 +0200
@@ -6851,7 +6851,7 @@
return t;
}
}
- p = Phrases;
+ p = OriginalPhrases = Phrases;
}
esyslog("%s%sno translation found for '%s' in language %d (%s)",
Plugin ? Plugin : "", Plugin ? ": " : "", s, Setup.OSDLanguage,
Phrases[0][Setup.OSDLanguage]);
}
BR,
Christian
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
On 6/12/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote: The function ExchangeChars() in VDR/recording.c converts characters that can't be used in file names on Windows to "#XX", where XX is the hex code of the character. This was simple when VDR only worked with single byte character sets, but now that it can handle UTF-8 this needs to be changed, too. Currently it has a list of characters that can be used "as is", and converts everything else to "#XX". I guess it is better to convert any "disturbing" characters to "#XX" and leave the rest untouched. However, this requires that we know exactly which characters can't be used with Windows. Does anybody have that kind of information? Or should this be done completely different? Note that I don't use this feature myself, so unless there is some input from others, I won't be changing anything here. I use this FAT feature so I can mount my linux drive on windows and stream movies with vdradmin to my windows machine. I have noticed that VDR might currently be renaming a little more than is required. Invalid characters include: . " / \ [ ] : ; = , http://support.microsoft.com/kb/142982 Regards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr in client-server configuration?
On 06/12/07 18:02, Oliver Joa wrote: > Hi, > > i use vdr since a long time, i still use version 1.3.23 on 3 Computers. > The last months/years i did not follow the development. Is there already > a solution for the client-server Problem? I wonder if it is possible to > have 1 server recording and streaming to 2 client. And the clients > possible to start recordings on the server. Maybe the possibility to see > the osd of the server on the clients... Take a look at http://www.magoa.net/linux. > Klaus: Do you plan someting like this? I myself won't be working in that direction any time soon. There are too many other important things to do. 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
On 06/12/07 17:59, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> I'm considering compiling one font file directly into the program,
>> so that, in case no external fonts can be found, it can at least
>> run properly.
>>
>> Can somebody suggest a freetype font that looks good, covers all
>> necessary locales, and is really free, so that it can be redistributed
>> with the VDR source?
>
> What about falling back to the bitmap font vdr currently uses? It
> would only be able to display ASCII but that would be sufficient to
> at least start up vdr in english.
That was my first thought, too. But it would mean having an
additional font mechanism that, in almost all cases, would never
be used.
> OTOH you can always puts("install true type fonts"); exit(1) :-)
If I can't compile in a freetype font, that's pretty much what
it's going to be.
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Freeview Playback
On Tuesday 12 Jun 2007, Alex Stansfield wrote: > Hi, > > with the launch of Freeview Playback in the UK, I was wondering if > anyone here knew how the series links were sent to the dvb box. > > Freeview Playback is a system by which series link information is sent > to the dvb box, allowing someone to select to record a whole series. > Some sort of link information is sent, I guess in the epg, about each > episode so that the dvb box can be sure it's always recording unique > episodes of a series. > > I thought that support for Freeview Playback would be an excellent > addition to plugins like epgsearch. > > If anyone knows any more about how the system works or has the DTG > specification (can't see it on their website) please let me know. The EPG format is covered by this document (which I think is the latest issue) http://webapp.etsi.org/action/OP/OP20060428/en_300468v010701o.pdf so presumably the data fits in to the specification somehow. I looked through this and also checked the broadcast data with dvbsnoop last weekend but couldn't see anything obvious. Maybe no-one is broadcasting the links yet. It would certainly be an excellent addition to VDR. Dave ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr in client-server configuration?
Hi, i use vdr since a long time, i still use version 1.3.23 on 3 Computers. The last months/years i did not follow the development. Is there already a solution for the client-server Problem? I wonder if it is possible to have 1 server recording and streaming to 2 client. And the clients possible to start recordings on the server. Maybe the possibility to see the osd of the server on the clients... Klaus: Do you plan someting like this? Thanks Olli ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
Klaus Schmidinger wrote:
> I'm considering compiling one font file directly into the program,
> so that, in case no external fonts can be found, it can at least
> run properly.
>
> Can somebody suggest a freetype font that looks good, covers all
> necessary locales, and is really free, so that it can be redistributed
> with the VDR source?
What about falling back to the bitmap font vdr currently uses? It
would only be able to display ASCII but that would be sufficient to
at least start up vdr in english. OTOH you can always puts("install
true type fonts"); exit(1) :-)
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
[vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
The function ExchangeChars() in VDR/recording.c converts characters that can't be used in file names on Windows to "#XX", where XX is the hex code of the character. This was simple when VDR only worked with single byte character sets, but now that it can handle UTF-8 this needs to be changed, too. Currently it has a list of characters that can be used "as is", and converts everything else to "#XX". I guess it is better to convert any "disturbing" characters to "#XX" and leave the rest untouched. However, this requires that we know exactly which characters can't be used with Windows. Does anybody have that kind of information? Or should this be done completely different? Note that I don't use this feature myself, so unless there is some input from others, I won't be changing anything here. 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
On 06/10/07 19:45, Oleg Roitburd wrote: > On Sun, 2007-06-10 at 18:04 +0200, Klaus Schmidinger wrote: >> On 06/10/07 17:53, Anssi Hannula wrote: >>> Klaus Schmidinger wrote: >> Can't there be a *standard* for things like this? >> >>> + strcpy(FontOsd, "arialbd.ttf"); >>> + strcpy(FontSml, "arial.ttf"); >>> + strcpy(FontFix, "courbd.ttf"); >>> >>> I'd use some free-as-in-freedom font (Vera?) by default, that are more >>> likely installed in systems. > > Bitstream Vera isn't good enough...it doesn't provide Cyrillic part of > UTF-8 :-( M$ fonts are not free. > My suggestion is liberation ttf from RedHat > https://www.redhat.com/promo/fonts/ I'm considering compiling one font file directly into the program, so that, in case no external fonts can be found, it can at least run properly. Can somebody suggest a freetype font that looks good, covers all necessary locales, and is really free, so that it can be redistributed with the VDR source? 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
On 06/12/07 07:12, VDR User wrote: > 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. I'll first try using fontconfig, as has been suggested earlier. If that works, we probably won't be needing a FONTDIR at all. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.5.3 SUSE Linux rpm packages available
Hi, I've added vdr 1.5 to the buildservice now as well. Packages are available for 10.0, 10.1 and 10.2 at http://software.opensuse.org/download/vdr/ The package is called 'vdr15' and uses a different configuration directory so it can be installed in addition to the 1.4 version. The vdr-plugins package contains plugins both 1.4 as well as 1.5. 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
[vdr] Freeview Playback
Hi, with the launch of Freeview Playback in the UK, I was wondering if anyone here knew how the series links were sent to the dvb box. Freeview Playback is a system by which series link information is sent to the dvb box, allowing someone to select to record a whole series. Some sort of link information is sent, I guess in the epg, about each episode so that the dvb box can be sure it's always recording unique episodes of a series. I thought that support for Freeview Playback would be an excellent addition to plugins like epgsearch. If anyone knows any more about how the system works or has the DTG specification (can't see it on their website) please let me know. Cheers, Alex ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Plugin patches for vdr-1.5.3
Hi, > 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. I've uploaded a beta for epgsearch, that supports vdr-1.5.3: http://winni.vdr-developer.org/epgsearch/downloads/vdr-epgsearch-0.9.23-beta1.tgz But there still remains the problem with translations in plugins as already posted here. So you should also apply the patch provided by Alexander Riegel to fix this. BR, Christian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
