Hi all,
I'm using a VDR system with 4 skystar2 cards.
I'm disabled vdr watchdog and code line who jumps out vdr when the signal is
noisy, because when this enabled, and I have noise in one frequency, vdr
jumps out and ruins all other input recordings.
But there are some times that all recordings fa
Kartsa kirjoitti:
> Jukka Tastula kirjoitti:
>
>> On Friday 10 August 2007 10:14:32 Ville Skyttä wrote:
>>
>>
>>
>>> Hm, so you have an ADV7175 based one currently? Sorry, I don't think that
>>> helps - again, as far as I know, the WSS stuff only works with ADV7170
>>> based cards. The
Hi Halim,
Halim Sahin wrote:
> If I write unset $LANG
> all apps are producing english output.
yes that is excatly what VDR also does but if I have not defined LANG
then I'm not able to select another language in the OSD of VDR and that
is the issue I tried to address.
Everything else is fine.
On 08/19/07 22:02, Eddi wrote:
> Hi,
>
> Klaus, any news about support for multiple frontends?
>
> What about integrating my patch in 1.5.x?
Well, to be absolutely honest, this is still dangling in my
inbox and I have so many other things to do that I just
can't seem to find the time right now.
On 08/24/07 16:00, Klaus Schmidinger wrote:
> ...
> One more thing: this also reduces I18nTranslate() to
>
>
> const char *I18nTranslate(const char *s, const char *Plugin)
> {
> if (s && CurrentLanguage) {
> const char *t = Plugin ? dgettext(Plugin, s) : gettext(s);
> if (t != s)
>
On 08/24/07 15:35, Klaus Schmidinger wrote:
> On 08/19/07 14:58, Matthias Becker wrote:
>> ...
>> One way of doing this would be to introduce a new macro similar to
>> trNOOP( ). A plugin author would then tag the vdr-core texts with this
>> new macro and xgettext would ignore these texts.
>>
>> Wh
On 08/24/07 15:37, Anssi Hannula wrote:
> ...
> For the record, gettext also has context support:
> http://www.gnu.org/software/gettext/manual/gettext.html#Contexts
>
> But if it needs too many changes, maybe it is not worth it.
I thought about that shortly, but decided not to use it.
There's not
Klaus Schmidinger wrote:
> On 08/23/07 13:48, Christian Wieninger wrote:
>> Hi,
>>
>> I just noticed a small change in the context handling of translations
>> since vdr-1.5.7. Till now it was possible to have e.g.
>>
>> const char AllowedChars[] = trNOOP("$
>> abcdefghijklmnopqrstuvwxyz0123456789
On 08/19/07 14:58, Matthias Becker wrote:
> Hi,
>
> plugins can re-use VDR-core translations. With the old "i18n.c" method
> plugin authors just did not provide a plugin specific translation for
> these texts.
> With the new translation method identifying these text got harder for
> plugin transla
On 08/23/07 13:48, Christian Wieninger wrote:
> Hi,
>
> I just noticed a small change in the context handling of translations
> since vdr-1.5.7. Till now it was possible to have e.g.
>
> const char AllowedChars[] = trNOOP("$
> abcdefghijklmnopqrstuvwxyz0123456789-.,#~\\^$[]|()*+?{}/:%@&");
>
>
On Fr, Aug 24, 2007 at 02:03:22 +0200, Matthias Fechner wrote:
> Hi Anssi,
>
> Anssi Hannula wrote:
> > AFAICS that is only needed if the user locale settings are set to "C",
> > "POSIX" or invalid values.
> >
> > This behaviour was added to glibc in 2001, likely to fix something else.
> > http:
Hi Anssi,
Anssi Hannula wrote:
> AFAICS that is only needed if the user locale settings are set to "C",
> "POSIX" or invalid values.
>
> This behaviour was added to glibc in 2001, likely to fix something else.
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/intl/dcigettext.c.diff?r1=1.22&r2=
12 matches
Mail list logo
