Youlin writes:
> > The real problem is when trying to restore a file, with the tar and zip
> > methods the filename comes also garbled.
>
> I have a similar problem with the Chinese support. Files backed up
> with rsyncd would yield garbled file names when they are restored
> through Samba, or vice versa. At least this is a problem in V 3.0.0.
Rsync does not change file name encoding, so $Conf{ClientCharset}
should be set to the client's charset.
In contrast, by default samba converts to utf8 on the unix side,
so $Conf{ClientCharset} should be empty, or set to utf8.
Are you changing $Conf{ClientCharset} when you switch between
rsync and samba?
> I'd think it is ok if you restore the files with rsyncd, ie. the same
> method as the backup process.
Yes, that should work.
> There are still issues with the Unicode support. Craig is aware of that.
The remaining issues are:
- old (2.x) backups don't display correctly because no charset
conversions were done. I'm trying to fix this but it is tricky.
Part of the fix is to save the client charset in the backups
file, but that means you can't switch restore XferMethods
since the restore charset will be based on the backups file.
- single file restore doesn't display the correct file name in
the browser "Save As..." dialog for IE and Opera. Firefox is
fine. Does anyone know where I can find information on how
browsers expect the file name to be encoded in this case?
IE now works correctly in CVS, but it looks like a hack to
me.
Craig
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
