Francis Galiegue wrote:
On Mon, Jun 6, 2011 at 14:26, Stefan G. Weichinger <[email protected]> wrote:
Am 25.10.2010 09:59, schrieb Marc Muehlfeld:
You fixed this in 2.5.1p2
(http://groups.yahoo.com/group/amanda-hackers/message/5233), but it came
back in 3.1.1 and is still there in 3.2.0.
Jean-Louis, could you tell us if there is a chance to get that fixed
again? Unfortunately I am not able to find that old patch ...
On this particular page, you have to click on the "Message info" link
and then "Show original", but the patch will be mangled.
Maybe I can help. What is the issue exactly? I don't have a pointer to
the original thread.
The patch replace an octal representation \000 by one byte (this is done
in amindexd).
As all backup are run in the C locale, all non-ASCII characters are in
octal representation in the index file.
amrecover is run in the user locale, it should be able to display
characters in user locale (The patch do it)
On recovery, the application is also run in the C locale, but can it
accept non-ASCII characters? some can and some can't.
That's why the patch can't be committed.
Also, it can be possible to have filename in a different locale, using
the root locale to display them can make it harder.
I would prefer to have an amrecover setting that enable the translation
of an octal representation to a single bytes.
There is a workaround, octal characters must be preceded by 4 backslash:
amrecover> add \\\\303\\\\275
Jean-Louis
