Re: lynx-dev lynx and other character sets

[dickey]

> > It is limited to the character sets for which people have written 
> > translation tables. 
>  
> Two things here: 
>  
> 1. How can I add a character set to lynx? 

Most of it is a table (src/chrtrans/*).  There's some inline tables in
the source code.  Character set tables are (presently) compiled-in,
though some people would like to have them dynamically loaded (but
no one's working on that).  If we did this dynamically, it'd be
easier to say how to add character sets...
  
> 2. What do you mean by display character set? Where is it defined? In a 
> terminfo database 
> or similar? What should I do if I want to define a display myself to support 
> my character set? 
>  
> > Note that <BDO and dir= are not necessary for bidirectional text in 
> > HTML4; the browser is expected to know the natural direction for 
> > every Unicode character which has a unique direction (HTML is always 
> > Unicode from an internal processing point of view) and to honour Unicode 
> > direction overrides.  It is probably desirable to have dir= on the HTML 
> > tag to allow for direction neutral characters (it is also reccommended 
> > to have lang=, but I never see it!) 
> >  
> > BDO is only needed for material where characters of well defined 
> > directionality violate the Unicode rules. 
> >  
> > The point here is that most of the complexity arises from bi-directional 
> > text, not from the associated HTML elements and attributes. 
>  
> Aha!  So is there any schedule to do this?  We need this, and I think I

no (send patches and we'll try to integrate them to make a nicer Lynx)

> can find some volunteers here in Iran to add anything that will be needed
> for Persian support.  If only it's not that much hard...  Will you help? 
> We are GNU fans, and among the few Iranians who are fighting for software
> freedom, so it will be all nice. 
>  
> > (Linux can be put into Unicode mode, but can only display 
> > the subset corresponding to the loaded code page; I don't think that 
> > it does BIDI.) 
>  
> I can't understand. You are talking about a TERMINAL supporting bidi? 

The application would have to support bidi (the TERMINAL only does what
it's told to do).  Though ISO 6429 (iirc) provided for terminals with
different directionality, I'm not aware of any that implement it (and
in the context I remember, it would apply to the whole display - not
really suitable for this application, where we're thinkin in terms of
mixed text types).

> > I'm not aware of anyone interested in Korean, Arabic, Hebrew, or to 
> > the extent that it is not covered by Japanese support, Chinese. 
>  
> I am now in the list, and I will do somethings for BIDI if I can get to it. 
> I will try to attract other Iranians also... 
>  
> --roozbeh 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey