==============================================================================
Gaspar Sinai <gsinai@yudit.org> 2002-11-12
Need to add Lao:
  Requestor: Anthony Souphavanh <asouphav@us.ibm.com>
  font: http://laonux.muanglao.com/fonts/hongkadu.ttf
Need to add Tibetan
  Requestor: Gregory Mokhin <mokhin@bog.msu.ru>
  font: http://www.yudit.org/download/fonts/utibetan.ttf
==============================================================================
Miikka-Markus Alhonen <miikka@tigatieto.com> Wed, 09 Oct 2002 08:45:43 +0300

As for Tibetan, I think it can still wait, since we don't even
have an OTF font to test it with yet. Maybe it can be incorporated
in the next release together with implicit BiDi? I don't know of any
Arabic/Hebrew OCR software, but I guess making a simplistic reverse-BiDi
algorithm just for Yudit isn't too difficult... I'll try to concentrate
on developing one later on.

==============================================================================
Jungshik Shin <jshin@mailaps.org> 2002-05-12

>   One more thing to have in Yudit(I'm sorry to keep coming up with
> new feature requests...) is to make U+302E and U+302F
> (Hangul tone marks) work. According to Unicode model, they're supposed
> to follow Hangul syllables (represented either in precomposed form or
> with Hangul Jamos) and be rendered on the *left* of syllables.
> Sequences like 'U+AC00 U+302F' and 'U+1100 U+119E U+11C8 U+302E'
> have to be treated as clusters as well.  PARK Won Kyu's fonts
> 18x18Bko.bdf and 18x18ko.bdf at
>
>    http://chem.skku.ac.kr/~wkpark/project/font/iso10646/
>   
> have glyphs for them suitable for overstriking with glyphs for
> Hangul syllables.
>  Ogulim.ttf has a gsub table, but I don't have a tool to
> read that off. It may or may not have OTF ligatures. You may
> wish to take a look at it now that I put it up. BTW,
> if it doesn't, you may want to grab
> <http://jshin.net/i18n/korean/mid_kor.tar.gz> and take a look
> at mslvta.otp, mslvtb.otp and mslvtc.otp.  Because of the
> way Omega translation process works, I had to do the necessary
> translation in three steps. Hopefully, they're commented clearly
> enough for you to understand what those files are for.
-------------------------------------------------------------------

The following things should be done:
1. Adding more Indic scripts. 
  Need kmap for Lao, Thai , Sinhala, otherwise in theory they work 
  In addition extra work may need to be done to peroperly support:

  o Tibetan
  o Khmer U+1780-U+17FF
  o Myanmar U+1000-U+109F
  o Tone letters 02E5..02EB

2.Version 2.5 broke background printing. It shuld be restored.
 The problem is that all events are handled now in a job and 
 when a job is executed the job is removed already. So event next
 does not call the updating job!

The following classes need cleanup:
 swindow/SX11* 
  Make focus work on multiple panes, modal handling cleanup.
  Remove unncecessary code
  Handle colormap change.
  Add one big happy pixmap instead of creating many small ones
  (like in swindow/swin32/SWin32.cpp)
 swindow/SFontImpl
  Need external encoding support for X11 fonts.

a) If support unicode STextData should change:
  - memory mapped data file.
  - along with these changes minor changes need to be made on
    rendering engine and widget set, like:

b) Not using unicode internally would have very good effect on
 any application. I am thinking about using unicode for compatibility
 reasons only. The format I want to use internally should have
 the following attributes:
 - character type determined from character code with a bit mask.
   This  would make it possible for application to avoid loading
   huge data strucutres. It would even make things possible like
   ameking a non-spacing mark as spacing-mark with a bit-mask.
 - character shaping determined by a very clear and short calculation.
 - there is one way to represent one character.
 I have constantly added things to these attributes. The goal is to
 make _only_conversion_routines_ aware of the huge database unicode
 applications currently holding, leaving the application with
 the task to perform their duties in a nice and elegant way. When
 a new character is introduced the character should automatically
 collate/shape e.t.c.

3. Make a configuration screen
 A configuration screen would make Yudit more easy to use

4. Add an ability to specify the exact unicode ranges of fonts.

5. Adjusting of the line gaps as some fonts.

6. Make kmap list translatable.

Gaspar Sinai
gsinai@yudit.org
Tokyo 2002-12-11
