--no-unicode-fix commented, and README update

This commit is contained in:
Goffi 2010-09-28 18:00:06 +08:00
parent 62698fa1bd
commit 454c638727
2 changed files with 21 additions and 8 deletions

25
README
View File

@ -22,12 +22,12 @@ along with gcp. If not, see <http://www.gnu.org/licenses/>.
** WTF ? **
gcp is a file copier, loosely inspired from cp, but with high level functionnalities like:
gcp is a file copier, loosely inspired from cp, but with high level functionalities like:
- progression indicator
- gcp continue coping even when there is an issue: he just skip the file with problem, and go on
- journalization: gcp write what he is doing, this allow to now which files where effectively copied
- gcp continue copying even when there is an issue: he just skip the file with problem, and go on
- journalization: gcp write what he is doing, this allow to know which files where effectively copied
- fixing names to be compatible with the target filesystem (e.g. removing incompatible chars like "?" or "*" on vfat)
- if you launch a copy when an other is already running, the files are added to the first queue, this avoir you hard drive to move its head all the time
- if you launch a copy when an other is already running, the files are added to the first queue, this avoid your hard drive to move its head all the time
- files saving: you can keep track of files you have copied, and re-copy them later (useful when, for example, you always copy some free music to all your friends).
- gcp will be approximately option-compatible with cp (approximately because the behaviour is not exactly the same, see below)
@ -39,18 +39,31 @@ Pretty much like cp (see gcp --help).
Please note that the behaviour is not exactly the same as cp, even if gcp want to be option-compatible. Mainly, the destination filenames can be changed (by default, can be deactivated).
gcp doesn't implement yet all the options from cp, but it's planed.
** journalizaion **
The journal is planed to be used by gcp itself, buts remains human-readable. It is located in ~/.gcp/journal
3 states are used:
- OK means the file is copied and all operation were successful
- PARTIAL means the file is copied, but something went wrong (e.g. changing the permissions of the file)
- FAILED: the file is *not* copied
after the state, a list of things which went wront are show, separated by ", "
** What's next ? **
Several improvment are already planed:
Several improvment are already planed
- copy queue management (moving copy order)
- advanced console interface
- notification (xmpp and maybe mail) when a long copy is finished
- retry for files which where not correctly copied
- retry for files which were not correctly copied
- badly encoded unicode filenames fix
- file copy integrity check
... and other are with a "maybe"
- graphic interface
- desktop (Kde, Gnome, XFCE, ...) integration
- distant copy (ftp)
- basic server mode, for copying files on network without the need of nfs or other heavy stuff
** Credits **

4
gcp
View File

@ -498,8 +498,8 @@ class GCP():
parser.add_option("--preserve", action="store", default='mode,ownership,timestamps',
help=_("preserve the specified attributes"))
parser.add_option("--no-unicode-fix", action="store_false", dest='unicode_fix', default=True,
help=_("don't fixe name encoding errors")) #TODO
#parser.add_option("--no-unicode-fix", action="store_false", dest='unicode_fix', default=True,
# help=_("don't fixe name encoding errors")) #TODO
parser.add_option("--no-fs-fix", action="store_false", dest='fs_fix', default=True,
help=_("don't fixe filesystem name incompatibily"))