Re: [Mlterm-dev-en] Re: [I18n]Bidi on mlterm

[Noah L. <nl...@co...>]

Hello,

I checked mlterm out of cvs a couple of hours ago, and I'm
having crash and other problems with bidi and with utf8
generally, even after applying your patch. I'm using linux
2.4.8 and xfree86 3.3.6. When I start mlterm
$ LANG=en_US.UTF-8 mlterm
I get a blank window. The blank window happens with or
without bidi. I open mlconfig and set the font size to 14
(it starts at 17), and then it crashes:

(gdb) bt
#0  0x4033bcc6 in free () from /lib/libc.so.6
#1  0x4033bc24 in free () from /lib/libc.so.6
#2  0x4014e4e6 in kik_mem_free (ptr=0x809b440, file=0x8069cbd "ml_char.c", 
    line=148, func=0x8069cc7 "ml_str_delete") at kik_mem.c:185
#3  0x0804fa80 in ml_str_delete (str=0x809b440, size=80) at ml_char.c:148
#4  0x0805dce2 in ml_imgline_final (line=0x80934a8) at ml_image_line.c:81
#5  0x08051b2e in ml_image_resize (image=0x8090680, num_of_cols=114, 
    num_of_rows=38) at ml_image.c:904
#6  0x08058b6e in window_resized (win=0x8090578) at ml_term_screen.c:1110
#7  0x0805a35d in font_size_changed (termscr=0x8090578)
    at ml_term_screen.c:2518
#8  0x0805a3af in change_font_size (p=0x8090578, font_size=14)
    at ml_term_screen.c:2539
#9  0x08063fda in sig_child (self=0x8090804, pid=15020) at ml_config_menu.c:267
#10 0x08068981 in sig_child (sig=17) at ml_sig_child.c:52
#11 0x402e97c8 in killpg () from /lib/libc.so.6
#12 0x080669c9 in ml_term_manager_event_loop (term_man=0xbffff670)
    at ml_term_manager.c:1523
#13 0x0805fcf9 in main (argc=1, argv=0xbffff9b4) at main.c:44
#14 0x402d75b0 in __libc_start_main () from /lib/libc.so.6

On the other hand, if I specify the font size when I start
mlterm:
$ LANG=en_US.UTF-8 mlterm --fsrange=14-14
then the window opens and I see a prompt. When I press a
key, it crashes:

(gdb) bt
#0  0x402e9971 in kill () from /lib/libc.so.6
#1  0x402e9775 in raise () from /lib/libc.so.6
#2  0x402eada3 in abort () from /lib/libc.so.6
#3  0x08068183 in ml_bidi (order=0x8090900, src=0x8087830, size=27)
    at ml_bidi.c:99
#4  0x0805ef1e in ml_imgline_render_bidi (line=0x8087540)
    at ml_image_line.c:910
#5  0x08051df4 in ml_image_render_bidi (image=0x8091630) at ml_image.c:1025
#6  0x0805b896 in ml_term_screen_stop_vt100_cmd (termscr=0x8091528)
    at ml_term_screen.c:3860
#7  0x08056354 in ml_parse_vt100_sequence (vt100_parser=0x80a1558)
    at ml_vt100_parser.c:2426
#8  0x0806510a in receive_next_event (term_man=0xbffff660)
    at ml_term_manager.c:619
#9  0x080669c9 in ml_term_manager_event_loop (term_man=0xbffff660)
    at ml_term_manager.c:1523
#10 0x0805fcf9 in main (argc=2, argv=0xbffff9a4) at main.c:44
#11 0x402d75b0 in __libc_start_main () from /lib/libc.so.6

This last one's less critical.

When I run mlterm with bidi disabled, it works, but it seems
to refuse to use the fonts I specify in ~/.mlterm/font. So,
I copied those fonts to their own directory and tried this:

$ ls -l
-rw-r--r--    1 nlevitt  nlevitt    784156 Dec  9 22:37 unifontd.pcf.gz
-rw-r--r--    1 nlevitt  nlevitt     74014 Dec  9 22:37 unifonts.pcf.gz
$ mkfontdir
$ cat fonts.dir 
2
unifontd.pcf.gz -gnu-fixed-medium-r-normal-f-16-160-75-75-c-80-iso10646-1
unifonts.pcf.gz -gnu-fixed-medium-r-normal-h-8-160-75-75-c-80-iso10646-1
$ xset fp $PWD
$ xset fp rehash
$ LANG=en_US.UTF-8 mlterm --bi=false
a font for displaying us ascii chars is not found.

This is dvdeug's version of unifont, which I have used
successfully with xterm-utf8. What's wrong here? 

Noah