Re: [Mlterm-dev-en] Invisible cursor with python curses module and start_color

[MINAMI H. <mi...@mi...>]

On Tue, 2005-01-04 at 01:21 -0500, Ian Ward wrote:
> > Just curious: what function are you going to add? 
> > I'm assuming that the knowledge of encoding should not
> > be neccesary to simply display some strings.
> 
> I need to know the encoding for things like word wrapping and cursor
> movement in edit boxes (sometimes the cursor should move 2 spaces).  I
> will also have to know how the terminal will behave when I send it
> combining characters and BiDi text.  I don't support BiDi yet -- That
> will be an interesting challenge.

As far as, I know there are no standard which defines
"proper" behavior of a terminal for BiDi/full-width/combining etc.

For mlterm, there are many options to do what is expected: 
--comb
--dyncomb
--multicol
--ac
--bi

Since most of these options are dynamically configurable,
it's very difficult to know what mlterm will do 
for a application running on it.

Maybe you can refer the way of mined (http://towo.net/mined/,
an unicode capable text editor runs on a terminal).

If mlterm was the only terminal in the world, we could take another 
approach. i.e. change the mlterm's configuration as your library want.
But that won't work other terminal emulators...

--
minami