Dear experts,
I am currently trying to convert a string to ISO-8859-1 using the
following code fragment:
cCharSetConv conv(NULL, ISO-8859-1);
const char *s_converted = conv.Convert(string);
Running VDR with UTF-8, this conversion failes (i.e., s_converted == string).
This is due to the
On 05/18/08 18:27, Joachim Wilke wrote:
Dear experts,
I am currently trying to convert a string to ISO-8859-1 using the
following code fragment:
cCharSetConv conv(NULL, ISO-8859-1);
const char *s_converted = conv.Convert(string);
Running VDR with UTF-8, this conversion failes
2008/5/18 Klaus Schmidinger [EMAIL PROTECTED]:
On 05/18/08 18:27, Joachim Wilke wrote:
Is there a reason for this?
systemCharacterTable is only set if it is a single byte character set,
which UTF-8 is not.
The conversion works fine, if I use UTF-8 instead of NULL:
cCharSetConv
Hello
I use the function Skins.QueueMessage from a
background thread.
Example:
Skins.QueueMessage( mtInfo, TEST, 40 );
I set a time of 40 seconds, but if time watchdog is
less than 40 seconds, vdr exit with a segmentation
fault.
Is this normal? Is possible set a message with a time
greater of
2008/5/18 lukkinosat [EMAIL PROTECTED]:
I use the function Skins.QueueMessage from a
background thread.
Skins.QueueMessage( mtInfo, TEST, 40 );
I set a time of 40 seconds, but if time watchdog is
less than 40 seconds, vdr exit with a segmentation
fault.
Is this normal?
Yes, because
lukkinosat wrote:
I set a time of 40 seconds, but if time watchdog is
less than 40 seconds, vdr exit with a segmentation
fault.
Is this normal? Is possible set a message with a time
greater of time watchdog?
It is. VDR 1.4.x even used a dirty workaround to display the 5 minute
shutdown
On 05/18/08 18:53, Joachim Wilke wrote:
2008/5/18 Klaus Schmidinger [EMAIL PROTECTED]:
On 05/18/08 18:27, Joachim Wilke wrote:
Is there a reason for this?
systemCharacterTable is only set if it is a single byte character set,
which UTF-8 is not.
The conversion works fine, if I use UTF-8
Hi,
on my e-tobi based 1.6 setup, the CAM menu umlauts are broken, while all
the other menu items (that I checked so far) use the correct encoding.
Is there a recoding missing between the CAM and the vdr OSD?
What LANG environment are u using? Please look at your /etc/defaults/vdr
file.
