Menu
▾
▴
#158 bindu ( 'M' ) not working correctly
On my both systems (Linux and WinXP) - the bindu
character doesn't show up in the edit screen. For
example : type "oM" in Extended Wylie.
When I save the file as .rtf, then open it using say,
Word or Wordpad, the text WILL show up correctly,
however copy/paste will not work in either direction.
I have tried both the original binaries from your
website and my own build (also both Windows and Linux).
m_podhorecki@yahoo.com
Logged In: NO
Also, I haven't had a chance to look at the code for more
than a few minutes, but it seems like the document object
contains correct data - i.e. stylecontexts are correct and
so are the character values. Could it be a problem with the
Swing's DefaultStyledDocument not handling data correctly
when they are passed to the display (sorry I'm pretty new
to Swing classes) ?
Thanks!
Michael
m_podhorecki@yahoo.com
Logged In: NO
Nope, the doc contents is actually bad. The last chracter
(the one that contains bindu in the font system you use) is
doubled for some reason. I wonder if that happens on every
fony change or just with the bindu .. I'll try to figure
that out...
Logged In: YES
user_id=1548644
Both the contents of the Document object and everything
through View class down to the way Java/Swing deals with
fonts is CORRECT. The problem is occuring because the
position where the bindu (or any diacritic character) is
supposed to be displayed is BEYOND the clipping region of
the area that belongs to the View assoc'd with the Element.
Put simply, if we have the following sequence :
TibetanMachineWeb '1'
TibetanMachineWeb7 'f'
the 'f' character should be displayed at the same position
as '1', but that is beyond the clipping area of the second
element.
Logged In: YES
user_id=1548644
I have the fix for that. It's a Java/Swing bug - if an
Element in a StyledDocument derived class contains
"diacritics" ONLY, the element will not be displayed,
because since there's no base character, horizontal span is
zero.
A temporary workaround would be to override default
LabelView getPreferredSpan () method - it should almost
never return zero.
m_podhorecki@yahoo.com