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

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

Hello,

On Tue, Jan 08, 2002 at 10:40:21AM +0900, Araki Ken wrote:
> 
>         Thanks a lot , but I have completely no idea why it happens:(
> 
>         Well , would you tell me fribidi version you use , ./configure options
>         you build mlterm with , and show me your ~/.mlterm/main , ~/.mlterm/font ?

Sorry for not providing this information last time. I am
using fribidi 0.9.1. I compiled mlterm with
--enable-fribidi --enable-debug. My ~/.mlterm/font is
ISO10646_UCS2_1=-gnu-fixed-*-*-*-h-8-160-*-*-*-*-iso10646-1
ISO10646_UCS2_1_BIWIDTH=-gnu-fixed-*-*-*-f-16-160-*-*-*-*-iso10646-1
and I don't have a ~/.mlterm/main or any of the other
configuration files.

> 
>         At my hand,
>         
>         $ LC_CTYPE=en_US.UTF-8 mlterm -w 20 -bi
>         
>         works fine with -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
>         font on NetBSD 1.5 Y current and XFree86 4.1.0.
> 
>          Default font size range is 10 - 24 , and if you want to use 8 dot font ,
>          please do something like

My mistake, I didn't realize that number was what the font
size referred to. 

> 
>          $ mlterm -km utf8 -w 8 -fsrange=8-24

When I run this it uses a size 8 font, but not the one I
want, and I get a different stack trace:

DEBUG: [ml_bidi()] visual order(29) of 0 is illegal.

Program received signal SIGABRT, Aborted.
0x402e9971 in kill () from /lib/libc.so.6
(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=0x80b1890, src=0x809d2d0, size=29)
    at ml_bidi.c:99
#4  0x0805ef1e in ml_imgline_render_bidi (line=0x809c8a8)
    at ml_image_line.c:910
#5  0x08051df4 in ml_image_render_bidi (image=0x8073030) at ml_image.c:1025
#6  0x0805b896 in ml_term_screen_stop_vt100_cmd (termscr=0x8072f28)
    at ml_term_screen.c:3860
#7  0x08056354 in ml_parse_vt100_sequence (vt100_parser=0x80a8408)
    at ml_vt100_parser.c:2426
#8  0x0806510a in receive_next_event (term_man=0xbffff650)
    at ml_term_manager.c:619
#9  0x080669c9 in ml_term_manager_event_loop (term_man=0xbffff650)
    at ml_term_manager.c:1523
#10 0x0805fcf9 in main (argc=6, argv=0xbffff994) at main.c:44
#11 0x402d75b0 in __libc_start_main () from /lib/libc.so.6

> 
>          10 - 24 seems so narrow that I'll set 6 - 30 as font size range by default.
> 
>          BTW , I didn't know such XLFD exist as
> 
>          -gnu-fixed-medium-r-normal-f-16-160-75-75-c-80-iso10646-1
>                                     ^^^^
>          -gnu-fixed-medium-r-normal-h-8-160-75-75-c-80-iso10646-1
>                                     ^^^
>          
>          uum ... "f-16" and "h-8" seems somewhat strange and designed only for xterm ,
>          but is it preferable to support these styles ? > Kubota san

I don't really know anything about fonts, but I was under
the impression that these two fonts made sense as values for
the ISO10646_UCS2_1 and ISO10646_UCS2_1_BIWIDTH parameters.
(The "f" and "h" stand for full-width and half-width, I
think.) I am curious as to what usual values for
ISO10646_UCS2_1 and ISO10646_UCS2_1_BIWIDTH are. I also use
these fonts in vim, as my "guifont" and "guifontwide".

Thanks a lot for your help!

Noah