Re: [vdr] translation context handling in vdr >= 1.5.7

2007-08-27 Thread Christian Wieninger
Klaus Schmidinger wrote: > gettext() may or may not return the original string, so if no translation > is found, the context needs to be stripped. > > Please try this: sorry for the late response. gmx seemed to be blacklisted again ;) Works like a charm. BR, Christian

Re: [vdr] translation context handling in vdr >= 1.5.7

2007-08-24 Thread Klaus Schmidinger
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

Re: [vdr] translation context handling in vdr >= 1.5.7

2007-08-24 Thread Anssi Hannula
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

Re: [vdr] translation context handling in vdr >= 1.5.7

2007-08-24 Thread Klaus Schmidinger
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-.,#~\\^$[]|()*+?{}/:%@&"); > >

[vdr] translation context handling in vdr >= 1.5.7

2007-08-23 Thread Christian Wieninger
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-.,#~\\^$[]|()*+?{}/:%@&"); Note the 2 '$'. The first one only helps to have the second one