#12 fontforge don't compile wine-font

closed-fixed
None
5
2005-07-13
2005-07-13
YunSong Hwang
No

[hys545@localhost fonts]$ cat error
fontforge -script ../fonts/genttf.ff wine_courier.sfd
Copyright (c) 2000-2005 by George Williams.
Executable based on sources from 15:42 12-Jul-2005.
FontForge does not support your encoding (eucKR), it will try to
use iconv()
or it will pretend the local encoding is latin1
wine_courier.sfd is not in a known format (or is so badly corrupted
as to be unreadable)
Open: Failed to open: wine_courier.sfd
Called from...
../fonts/genttf.ff: line 2
make: *** [wine_courier.ttf] 오류 1

I use 200507013 cvs
I use 2005-6-24 version . iT is success

Discussion

  • YunSong Hwang
    YunSong Hwang
    2005-07-13

     
    Attachments
  • YunSong Hwang
    YunSong Hwang
    2005-07-13

    Logged In: YES
    user_id=43886

    append

     
  • YunSong Hwang
    YunSong Hwang
    2005-07-13

     
    Attachments
    • assigned_to: nobody --> pfaedit
    • status: open --> closed-fixed
     
  • Logged In: YES
    user_id=201273

    PLEASE DO NOT OPEN A NEW BUG just to report more information
    on the old one.

    Also please do not use the bug tracker, instead report bugs
    to the mailing list.

    I am well aware that the cvs was completely broken last
    night. I fixed it this morning. I have also fixed the error
    you were having.

    The cvs tree is currently unstable as I am trying to make
    major changes to the internal data structures. Try using one
    of the released versions unless you are prepared for this
    instability.

     
  • YunSong Hwang
    YunSong Hwang
    2005-07-14

    Logged In: YES
    user_id=43886

    I update cvs 2005-7-14 8:00(?)
    I found error
    segment fault

     
  • YunSong Hwang
    YunSong Hwang
    2005-07-14

    Logged In: YES
    user_id=43886

    fixed

     
  • Logged In: YES
    user_id=201273

    I believe you.
    This fact is irrelevant however.

    The behavior of the 20-July cvs was wrong and has been
    corrected. If you wish the history of the bug please look at
    the discussion in the mailing list.