Menu ▾ ▴

#6 Can't read certain CD files (encoding)

open
None
5
2006-02-01
2006-01-27
simkin
No

Hello,
I've find this problem with an important quantity of cd
in my collection. CDCollect (0.5.1 here) fails to
import files in the CD because of the encoding. I've
attached an example output of the error message.
Then, when failing, the app doesn't do anything, you
are forced to cancel de importing manually. I can
submit lots of this type output but all them look similar.
Firstly the encoding problem should be solved and
secondly if something fails like this the app should
give an error message to the user after some time.
Thanks a lot for your time. Regards.

Discussion

  • Nobody/Anonymous

    Logged In: NO

    Could you please send me a file where the program fails? As
    you said it seems that the encoding is failing somewhere but
    I cannot seem to find where.. :-?

    You can send a small file to jrhbcn@gmail.com

     
  • Javier Ruiz Hidalgo

    • assigned_to: nobody --> jrh
     
  • simkin

    simkin - 2006-02-01

    Logged In: YES
    user_id=1117839

    I'm using ISO-8859-1 in my system, but exporting UTF-8 on a
    console and executing cdcollect on it doesn't make any
    difference. I attach a little file of a DVD that fails, I'm
    not sure in what encoding was that DVD burned, might be UTF,
    but I'm not sure. Btw, I'll also send it to your mail. thanks.

     
  • simkin

    simkin - 2006-02-01
     
  • Javier Ruiz Hidalgo

    Logged In: YES
    user_id=16869

    Argg, I can not reproduce this on my system :-( if I copy
    the file into my system and execute cdcollect the file is
    imported without problems... :-?

    This has definitely something to do with encoding, so let's
    try to find out, let me ask you a couple of questions:
    - What version of mono are you using?
    - Are you using the debian package or compile it by yourself?
    - Does it work if you copy the file from DVD to a directory
    in your disk on a UTF-8 console and try to import it from
    there? (just change the preferences in cdcollect so the
    mount point is the directory you copied the file).

    later,

     
  • simkin

    simkin - 2006-02-02

    Logged In: YES
    user_id=1117839

    Mono version:

    Mono JIT compiler version 1.1.12.1, (C) 2002-2005 Novell,
    Inc and Contributors. www.mono-project.com
    TLS: __thread
    GC: Included Boehm (with typed GC)
    SIGSEGV : normal

    CDCollect is compiled by myself.

    If I copy the file to a directory, it stills fails:

    ** Message: Bad encoding for
    '/home/simkin/temporal/dvdrom/10 - Rossell\xf3.met'Consider
    using MONO_EXTERNAL_ENCODING

    I've tested on both UTF-8 and 8859-1 console locale.

    If I create a file (touch) with the same name on an UTF-8
    console, it's read by cdcollect correctly. However making so
    on my standard console (ISO-8859-1) fails with the same
    error. Then seems that there is problems with non UTF-8
    systems...

     
  • Javier Ruiz Hidalgo

    Logged In: YES
    user_id=16869

    I wonder what this "MONO_EXTERNAL_ENCODING" is.... is it a
    enviromental variable? maybe you can try setting it up and
    see what happens?

    Other possibility to try to reproduce the error on my
    computer is that you can send me the same test file but
    inside a .iso file (created on your ISO-8859-1 system). I
    might be able to burn it to a CD and try to see if I
    reproduce the error here...

     
  • simkin

    simkin - 2006-02-13

    Logged In: YES
    user_id=1117839

    I've tried to set "MONO_EXTERNAL_ENCODING" to some encoding
    but nothing changed. I will email the ISO file to you, I
    can't attach it here. Let's see if you can reproduce it :)

     
  • simkin

    simkin - 2006-06-09

    Logged In: YES
    user_id=1117839

    Hi. With Mono 1.1.15 and setting:

    export MONO_EXTERNAL_ENCODINGS="ISO-8859-1"

    Cdcollect seems to be able to read the file names not UTF
    encoded. At least it starts reading the media outputting the
    file name in the progress window, and it's not showing any
    error about encoding in the console. However I can not
    confirm it because at that point (while reading) it stops,
    mono go crazy and eats 100% cpu.

     
  • simkin

    simkin - 2006-07-05

    example and native stacktrace

     
  • simkin

    simkin - 2006-07-05

    Logged In: YES
    user_id=1117839

    Here I attach an example:
    1. Fresh install in a UTF-8 system
    2. Error while importing ISO-8859-1 encoded filenames
    3. export MONO_EXTERNAL_ENCODINGS="ISO-8859-1" as suggested
    by mono
    4. SIGSEGV as result

     

Log in to post a comment.