ＳｒｉｎＴｕａｒ wrote:
Ive also given tarballs a shot for this task, but sadly
cygwin is ascii-only.
To quickly respond to this side-topic: It is possible to enable UTF-8
in cygwin in a limited way although cygwin has only bogus locale
support.
Some applications, however, are able to support UTF-8 without locale
support:
- xterm works nicely in UTF-8 mode if configured properly
- rxvt-unicode can be patched to support UTF-8 (the package
includes my patch)
- my editor mined supports UTF-8 if it finds the terminal to be
running in UTF-8 mode
Because it works linux to linux, or at least fedora to fedora, and that
is really good enough for me,
Its not a major issue. But I'm curious to know if other have run into
this cross-platform problem, and how they
resolved it for themselves. That is, if anyone still reads this list.
How do you go about making a basic archive containing non-ascii
filenames that you can have confidence
will unpack well on most operating systems.
I have been irritated by this as well but I have no general solution.
May we find one together. I'll do some testing...
Kind regards,
Thomas Wolff
|