[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't translate pathname 'x/y' to UTF-8

To: Colin Percival <cperciva@tarsnap.com>
Subject: Re: Can't translate pathname 'x/y' to UTF-8
From: Chris Webb <chris@arachsys.com>
Date: Wed, 30 Nov 2011 18:35:06 +0000
Cc: The big chief <Jacques.Piguet@bluewin.ch>, tarsnap-users@tarsnap.com
In-reply-to: <4ED674D4.5080805@tarsnap.com>
References: <4ED547AD.8020105@bluewin.ch> <4ED674D4.5080805@tarsnap.com>

Colin Percival <cperciva@tarsnap.com> writes:

> Depending on how your system handles non-ASCII characters and locales Tarsnap
> sometimes fails to convert characters to UTF-8.  This seems to be an issue on
> Linux systems in particular.  Tarsnap is storing the path name "raw" rather
> than as UTF-8 as a result.

Is there an easy way to force tarsnap to store all file names as literal
byte-sequences and not attempt any character-set conversion on both backup
and restore? It'd be a nice option if not.

Best wishes,

Chris.

Follow-Ups:
- Re: Can't translate pathname 'x/y' to UTF-8
  - From: Colin Percival <cperciva@tarsnap.com>

References:
- Can't translate pathname 'x/y' to UTF-8
  - From: The big chief <Jacques.Piguet@bluewin.ch>
- Re: Can't translate pathname 'x/y' to UTF-8
  - From: Colin Percival <cperciva@tarsnap.com>

Prev by Date: Re: Can't translate pathname 'x/y' to UTF-8
Next by Date: [patch] nodump breakage on linux
Previous by thread: Re: Can't translate pathname 'x/y' to UTF-8
Next by thread: Re: Can't translate pathname 'x/y' to UTF-8
Index(es):
- Date
- Thread