Stone wrote:
The problem is not being able to share the linux directory over the
network to a windows box, it is trying to open a file with invalid
chars. When a file contains invalid DOS chars, it will display
incorrectly and windows will not be able to play it.
Yes, apparently i
Am Mittwoch, 13. Juni 2007 11:23 schrieb Marius Heidenstecker:
I do use a FAT32 external USB-HDD on which I store VDR-recordings with the
VFAT-option enabled. That way I can take VDR-recordings on that HDD to
friends' Windows boxes and watch it there with VLC for example. So I'd like
to keep
Am Mittwoch, 13. Juni 2007 13:39 schrieb Pertti Kosunen:
Oleg Roitburd wrote:
Sorry ... I don't understand and can't find any sence.
If you export for window, you make this with SAMBA. And you can
configure share with UTF-8
Yes you can use Samba and UTF-8, but some characters are still
On 06/13/2007 03:27 PM, Oleg Roitburd wrote:
Am Mittwoch, 13. Juni 2007 11:23 schrieb Marius Heidenstecker:
I do use a FAT32 external USB-HDD on which I store VDR-recordings with the
VFAT-option enabled. That way I can take VDR-recordings on that HDD to
friends' Windows boxes and watch it
On 6/13/07, Pertti Kosunen [EMAIL PROTECTED] wrote:
Oleg Roitburd wrote:
As maintainer of ArVDR ( VDR distribution for Russian user) I would say,
that
in 1.5 years as we use UTF-8 patch without VFAT part, I havn't heard any
complaints about this issue.
touch 'foo:bar'
And dir in Windows
On 6/12/07, Klaus Schmidinger [EMAIL PROTECTED] wrote:
The function ExchangeChars() in VDR/recording.c converts characters
that can't be used in file names on Windows to #XX, where XX is
the hex code of the character.
This was simple when VDR only worked with single byte character sets,
but
On 06/12/07 23:09, Oleg Roitburd wrote:
On Tue, 2007-06-12 at 17:46 +0200, Klaus Schmidinger wrote:
The function ExchangeChars() in VDR/recording.c converts characters
that can't be used in file names on Windows to #XX, where XX is
the hex code of the character.
Sorry ... I don't understand
