Date: Tue, 04 Jan 2005 14:29:05 -0600 From: "Jeremy Messenger" <mezz7@cox.net> To: "Joe Marcus Clarke" <marcus@freebsd.org> Cc: freebsd-gnome@freebsd.org Subject: Re: nautilus-cd-burner-2.8.6 needs UTF8 support in mkisofs Message-ID: <opsj3hur169aq2h7@mezz.mezzweb.com> In-Reply-To: <41DAFA60.8090008@FreeBSD.org> References: <1104856993.71147.45.camel@localhost.localdomain> <opsj3d54m39aq2h7@mezz.mezzweb.com> <opsj3f7vp49aq2h7@mezz.mezzweb.com> <41DAFA60.8090008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 04 Jan 2005 15:19:44 -0500, Joe Marcus Clarke <marcus@FreeBSD.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jeremy Messenger wrote: > | On Tue, 04 Jan 2005 13:09:30 -0600, Jeremy Messenger <mezz7@cox.net> > wrote: > | > |> On Tue, 04 Jan 2005 10:43:13 -0600, Daniel Johnson > |> <danjohnson@neonvolcano.net> wrote: > |> > |>> Hi, > |>> > |>> It appears nautilus-cd-burner is forcing mkisofs to use the UTF8 > |>> charset, however the version that gets installed as a dependency (via > |>> sysutils/cdrtools) does not support UTF8, which causes > |>> nautilus-cd-burner to hang at the ISO creation process. > |> > |> > |> Damn, I have the same problem when I tried to test > |> nautilus-cd-burner. Let's hope we can get the fix in ports tree in > |> the freeze. > |> > |> > http://cvs.gnome.org/viewcvs/nautilus-cd-burner/make-iso.c?r1=1.36&r2=1.37 > |> > |> > |> Do you (team or anyone) think above link caused this problem? > | > | > | Nope, not above link but I have a patch that fix this. Can you test > this? > | > | http://people.freebsd.org/~mezz/diff/nautilus-cd-burner.diff > | > | This bugzilla that developer fix user's problem, but it broke for us. > | So... I put those back and problem solved. > | > | http://bugzilla.gnome.org/show_bug.cgi?id=149486 > | > http://cvs.gnome.org/viewcvs/nautilus-cd-burner/make-iso.c?r1=1.35&r2=1.36 > | > http://cvs.gnome.org/viewcvs/nautilus-cd-burner/nautilus-cd-burner.c?r1=1.86&r2=1.87 > > > Why are we yanking out support the GNOME authors obviously intended > n-c-b to have? Wouldn't a better solution be to create a slave port of > cdrecord that has UTF-8 support? Maybe it would be just as easy to > include UTF-8 support in cdrecord by default. Or using cdrtools-cjk port that has UTF-8 support. I found this link below, but I haven't test it yet. GNOME authors are using unoffical patch of mkisofs? http://www.dbforums.com/t1080777.html Cheers, Mezz > Joe > > - -- > Joe Marcus Clarke > FreeBSD GNOME Team :: gnome@FreeBSD.org > FreeNode / #freebsd-gnome > http://www.FreeBSD.org/gnome > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (Darwin) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFB2vpfb2iPiv4Uz4cRAlJFAJ9+7TJxPu7+o27vHqeDxSluXW8NkACfWEXS > xvLXKkoqscBe9gaumt8mPEA= > =eAKO > -----END PGP SIGNATURE----- -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opsj3hur169aq2h7>