[vdr] Understanding .po-translation

Hi, I've some problems understanding the "new method" for translation. How do I have to start when programming a new plugin? Is there any kind of documentation? For me it looks like I have to check every single line which is given in the .po-files. #: hello.c:-->17<-- msgid "Hello" ms

Re: [vdr] Understanding .po-translation

Hi Klaus, first thanks for your lightning like reply, but I'm afraid it doesn't help me. After the newplugin-script there is no po-folder, no pot/po/mo-file. If I do what you wrote (README.i18n), then it gives this: - Change into the source directory. - Do a 'make i18n' to have the curre

Re: [vdr] Understanding .po-translation

Ah great! Thanks, that worked. Sorry for confusing, I had some translations, but all were done manually by copying an existing po-folder. After your post I tried to go through the steps of the README.i18n and moved the po-folder in order to start from the beginning. Maybe the "make po/plugin.pot"

[vdr] Errorreturncode from Makefile possible?

Hi, I would love it, if the Makefile could give an errorcode if something went wrong. Normally I'm using "make plugins && ./runvdr" when testing plugins. But if the compile of one or many plugins failes, the makefile gives an OK, and vdr starts (with the old plugincode). Would be great if this co

[vdr] [Wishlist] Loggingsection in the PLUGIN.html

Hi Klaus, I noticed there isn't any wird about the loggingmechanism in the plugin.html, so you have to search through the existing code in order to see how to use it. Maybe this should be added. Shure, it's not very important, but because there is a common loggingmechanism, it should receive one o

[vdr] Help of SVDRP commands

Hi, I noticed new SVDRP commands are limited to 9 characters. ./svdrpsend.pl help [...] 214-Plugin dummy v0.0.1 - Enter description for 'dummy' plugin 214-123456789 [...] [...] static const char *HelpPages[] = { "12345678901234567890\n" "Print some stuff.", [...] I foun

Re: [vdr] Help of SVDRP commands

> To be honest, I never would have expected anybody to implement > SVDRP commands that long - after all, you have to type them. > Is there really a need for such long command names? No, not really, but I was wondering why this was implemented. I prefer readable commands like "ISTIMERRUNNING" (just

[vdr] Plugindefined svdrp-commands not working?

Hi List, sorry but it's me again :/ I'm still trying to get plugindefined svdrp-commands to work, but even the svdrpdemo-plugin doesn't work: > [EMAIL PROTECTED]:/usr/src/vdr/vdr$ ./svdrpsend.pl help > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:20:53 2007 > 214-This is VDR version

Re: [vdr] Plugindefined svdrp-commands not working?

On Thu, September 27, 2007 09:56, Andreas Mair wrote: > Hi! > > > You should try > ./svdrpsend.pl PLUG svdrpdemo DATE > > > Regards, > Andreas Ah thank you Andreas, where do you have this information from? I was searching in the PLUGIN.html and the manpages, but I didn't find any hint. Maybe ther

[vdr] diff and po-files = huge patches?

Hi, while working on a patch I noticed a small problem creating such a patch with the "new" translation. When adding new translations, you have to call "make i18n" in order to get the translation generated to the gettext-files, but when doing this, all linenumbers get updated. The diff looks like t

Re: [vdr] diff and po-files = huge patches?

> I've noticed this, too, and will make it so that the line numbers will > no longer be added to the *.po files by using the --no-location option. Ah ok, then sorry for bothering you :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bi

[vdr] Architecture difference between recording and viewing?

Hello, I still have problems with my Tevii S470 with DVB-S2-channels. The problem (as already posted long ago at http://www.vdr-portal.de/board/thread.php?threadid=93713) is: The buffer runs full buffer usage: 70% (tid=12493) buffer usage: 60% (tid=12493) buffer usage: 70% (tid=12493) buf