Re: [rdiff-backup-users] Charset problem windows->linux backup

[Gregy]

>It looks like the ext3 filesystem does not support your Windows-1250 files
> natively.

Yes that seems to be the problem or maybe rather then filesystem,
system encoding is the problem.

>Using rdiff-backup over ssh to or from Windows is the recommended,
> and best, solution not only because it fixes the filenames, but because it
> restores the Windows metadata as well (which Linux/ext3 does not preserve on
> its own).

But I am using rdiff-backup + plink (ssh).

> Another option would be to use the --override-chars-to-quote option and
> quote the native characters (see the recent posts on the list for how to get
> that working before 1.2.6 is released).
>
Will try as soon as I get the chance.

2009/1/8 Andrew Ferguson <address@hidden>:
> On Jan 8, 2009, at 3:31 AM, Gregy wrote:
>>>
>>> Given that it restores back to Windows correctly, that doesn't sound
>>> like a bug to me.  rdiff-backup is not meant to do any character
>>> reencoding.
>>>
>>> Matt Flaschen
>>
>> Problem is that I cannot restore the backup any other way then via ssh
>> to windows.
>
> Gregy,
>
> Did you catch what Matt first wrote:
>
> The problem is Linux naturally doesn't have first class support for
> Windows 1250, since it's a proprietary Microsoft encoding
> (http://en.wikipedia.org/wiki/Windows-1250).  See e.g.
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/112089
>
>
> It looks like the ext3 filesystem does not support your Windows-1250 files
> natively. Using rdiff-backup over ssh to or from Windows is the recommended,
> and best, solution not only because it fixes the filenames, but because it
> restores the Windows metadata as well (which Linux/ext3 does not preserve on
> its own).
>
> Another option would be to use the --override-chars-to-quote option and
> quote the native characters (see the recent posts on the list for how to get
> that working before 1.2.6 is released).
>
>
> Andrew
>