From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hints for using Unison?
Date: Mon, 1 Aug 2005 08:15:14 -0700 [thread overview]
Message-ID: <5bdc1c8b050801081552381f74@mail.gmail.com> (raw)
In-Reply-To: <20050801084245.61ceac6c@hactar.digimed.co.uk>
On 8/1/05, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Sun, 31 Jul 2005 16:52:15 -0700, Mark Knecht wrote:
>
> > Possibly this problem is really an NFS issue or a 1394 issue? Neither
> > of these are overly tested, at least on my system under Gentoo. I ran
> > the same system with FC2 for quite awhile. 1394 worked fine as far as
> > I could tell, but I never used NFS much and I only jsut set up NFS
> > today to try out Unison so maybe it's one of those systems causing the
> > problem?
>
> You don't use NFS with Unison, give it hostnames and it will copy ther
> files with SSH.
>
> e.g. unison this box:/home/somedir ssh://otherbox/home/somedir
>
Neil,
Thanks. This is helping me get to the root cause. It appears that
the real problem has something to do with non-standard characters for
American English. The first directory that was failing was a Spanish
Edition of a CD. When I went and looked at it there were three songs
that used different sorts of accent character over vowels. I changed
these characters on both machines and then unison got further, so I
changed a second CD and it got further yet. Unfortunately I've been at
this about an hour and am just finishing up changing the "A"'s so I'd
like to try and understand what the issue here really is ad find a fix
that doesn't require making any changes.
The failure in unison is a dialog box with this message:
Uncaught exception Glib.convert.error(1, "Invalid byte sequence in
conversion input")
This failure is from the name "Angelique Kidjo" where a forward accent
appears over the first 'e' in Angelique. When I remove this unison
goes further but fails for more stuff like this.
I use a program called Aqualung (not in portage unfortunately) to
play these directories and it doesn't have any trouble with these
non-standard accent characters so why does unison?
One last thing. I note that when I change these characters on the
local machine that it takes one backspace in a terminal to erase the
character, while on the remote machine (logged in through ssh like
unison would be) it takes two backspaces to change the character. Does
this mean anything to you? It's beyond me. Note that locales are
probably not identical between the two machines.
Again, thanks to you and the other folks who responded. At least I
could probably get past this problem with a couple of days of work but
I'm hoping for a more internationalized solution.
Cheers,
Mark
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-01 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 20:43 [gentoo-user] Hints for using Unison? Mark Knecht
2005-07-31 22:00 ` Neil Bothwick
2005-07-31 23:34 ` Mark Knecht
2005-07-31 23:52 ` Mark Knecht
2005-08-01 4:59 ` Glenn Enright
2005-08-01 5:16 ` Mark Knecht
2005-08-01 6:51 ` Glenn Enright
2005-08-01 7:42 ` Neil Bothwick
2005-08-01 15:15 ` Mark Knecht [this message]
2005-08-01 17:48 ` Mark Knecht
2005-08-01 7:34 ` [gentoo-user] " Moshe Kaminsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b050801081552381f74@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox