VDR developer version 1.7.42 is now available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41-1.7.42.diff
MD5 checksums:
5a9ec132781045061325162fe03c2763 vdr-1.7.42.tar.bz2 011f2838026f849f031c40b2f06d9181 vdr-1.7.41-1.7.42.diff
Approaching version 2.0.0: ==========================
If there are no more serious bug reports, the final version 2.0.0 of VDR shall be released on March 31, 2013. So please test this developer version intensely and report any problems you might encounter as soon as possible.
The following language files still have the given number of untranslated texts:
da_DK.po: 134 el_GR.po: 197 hr_HR.po: 134 lt_LT.po: 1 nn_NO.po: 262 pt_PT.po: 28 sl_SI.po: 1 tr_TR.po: 134
If nobody takes care of these, they will remain untranslated in version 2.0.0.
DEADLINE FOR SUBMITTING TRANSLATIONS IS SATURDAY, MARCH 30!
The changes since version 1.7.41:
- Updated the Serbian OSD texts (thanks to Zoran Turalija). - Added maximum SNR and signal strength value for TechniSat SkyStar HD2 (thanks to Zoran Turalija). - Renamed the language file sr_SR.po to sr_RS.po (pointed out by Zoran Turalija). - Fixed loading the setup.conf file in case a parameter contains the '#' character (thanks to Johann Friedrichs). - The "Resume" button in the main menu is now only active if the respective recording actually exists (reported by Johann Friedrichs). - The cutter now allocates its buffers on the heap to avoid problems on systems with limited stack space (suggested by Juergen Lock). - Fixed formatting the channel definition example in the vdr(5) man page (thanks to Dominic Evans). - Updated the default channels.conf file.
Have fun!
Klaus
On 23.03.2013 13:16 , Klaus Schmidinger wrote:
VDR developer version 1.7.42 is now available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42.tar.bz2A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41-1.7.42.diff
Hi Klaus, I'm sorry for asking a stupid question. I noticed that the vdr.pc that get's generated has a wrong apiversion for the 1.7.42 version. I wonder if this is right, because i noticed that the plugins endling up under PLUGINS/lib have the 1.7.41 version instead of 1.7.42..
Best Regards,
René
On 24.03.2013 23:17, René wrote:
On 23.03.2013 13:16 , Klaus Schmidinger wrote:
VDR developer version 1.7.42 is now available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42.tar.bz2A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41-1.7.42.diffHi Klaus, I'm sorry for asking a stupid question. I noticed that the vdr.pc that get's generated has a wrong apiversion for the 1.7.42 version. I wonder if this is right, because i noticed that the plugins endling up under PLUGINS/lib have the 1.7.41 version instead of 1.7.42..
The apiversion is not wrong. Since there has been no change to the API, the version number has not been incremented. See config.h:
// When loading plugins, VDR searches them by their APIVERSION, which // may be smaller than VDRVERSION in case there have been no changes to // VDR header files since the last APIVERSION. This allows compiled // plugins to work with newer versions of the core VDR as long as no // VDR header files have changed.
Klaus
On 25.03.2013 24:22 , Klaus Schmidinger wrote:
The apiversion is not wrong. Since there has been no change to the API, the version number has not been incremented. See config.h:
// When loading plugins, VDR searches them by their APIVERSION, which // may be smaller than VDRVERSION in case there have been no changes to // VDR header files since the last APIVERSION. This allows compiled // plugins to work with newer versions of the core VDR as long as no // VDR header files have changed.
Oh, ok. This makes sense :-)
René
-
Klaus Schmidinger -
René