On 12 Dec 2002 09:53:48 -0800, Nadim Shaikli wrote: > > Mikhael/Olivier, I had sent an email with regards to the attached > patch to FBidiJoin.c to this list (as well as in private) so as > to include the the required changes/fixes to the shaping/joining > file. I'm not sure if my email was received as I didn't get any > responses nor did I see the changes committed to CVS. > > I'm attaching an archive which include a 'diff -ubB' (patch) of > the changes as well as the entire file itself (it'll include > cosmetic changes along with the fixes). > > Apologies if this issue has already been taken care of.
Ok, I reformatted the resulting file again to follow the same formatting as in other our sources. But please never use in the future diff -bB options, because the patched version will contain a mix of TAB indented lines and 5 space indented lines at random (very strewn). I tested the results and seems to work ok with unicode and iso8859-8. But I can't see iso8859-6 in titles now. I have a lot of iso8859-6 fonts and I was able to see it in the past. I run: xterm -name Arabic -title "`env LANG=ar_JO.iso8859-6 date`" Now, I can see joined Arabic with unicode font: Style Arabic Font StringEncoding=iso8859-6:*-arabeyes-*/iso10646-1 (so all these font prefixes and suffixes may be useful after all). But if I use iso8859-6 font directly I see only reversed question signs: Style Arabic Font -lbi-naskhi-medium-r-normal--12-120-75-75-m-70-iso8859-6 This font does work if I use it with xterm -fn '*naskhi-medium*-12*' and I see Arabic in it after: env LANG=ar_JO.iso8859-6 date So something does not work. Can anyone see iso8859-6 text and font? Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
