AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Even using a very elaborate scholarly font like Cardo (on which Tohu is based) does not solve the basic issues because Android also has EXTREMELY limited support for kerning (gpos look up tables etc). Modern Hebrew is not that bad at all but things really screw up when you mix western LTR and Hebrew RTL. The reason all this BS is needed is because ANDROID doesn't handle (pointed) hebrew MIXED with western scripts properly. Anyone who comes across any errors is welcome to mail me or post here and I'll code the required exceptions into my font and translation table. Using Bwhebb is not ideal due to licencing but also the approach would yield some nasty illegible code IMHO (yes, I'm implying my code IS legible BTW!).įor now the Tohu font only includes wide vowels. When a vowel is detected there will be a check if it needs to be replaced by a small one in stead of the wide one (default) This should fix 99% of the remaining few alignment issues. Vowels (theoretically all nikudot) are added twice, one for pairing with a wide consonant and another for pairing with a small consonant. It boils down to dividing the consonants into two (or more) groups of "Wide" and "Small" characters. I have also looked at the bwhebb font that Dotan so kindly reminded me of (I was hoping to be able to forget that carp in the age of unicode.) The trick they use is quite dirty when it comes to human use, but perfectly suited to machine translation, so I will be adding that to my solution at a later date. The good news: Due to the nice hooks structure in 2.0 it all fits in one file! (not counting the required font, that is). I finally ported my modifications to AnkiDroid 2 and it tests out fine!Īlas, the work is based on the zip download as I have spent way more time getting eclipse and git to play nice together than I consider worthwile. I have quite a bit of experience with Hebrew I don't have an Android device at the moment, but if I can help in any > How? Cardo doesn't render the vowels properly as far as I know. > You also mention that you have already done something similar for Cardo. > appreciated and will lead to a better solution. > not going to use the fix myself, so any advice and feedback is greatly > have practically zero knowledge on Hebrew language and Unicode RTL and I'm > If on the other hand you don't have time, I'll try to do it myself, but I > If you need any help/advice on the coding part, please ask. > go into .HebrewFix.java in the method applyHebrewFix. > consider 2.0 version, the master branch in github), but the mapping should > I don't know how familiar you are with the AnkiDroid code (please only > preference that explains how and where to find the required font. > For now, we can popup a dialog when the user activates the Hebrew-Fix > required, but it's a bit of bloat to put that into AnkiDroid proper, since A separate plugin can include a downloader if I would like to move all these hackish solutions and workarounds to I'm not the expert on AnkiDroid licencing. > licencing of the font expects within AnkiDroid just in order to circumvent I'm not sure if we can include a "clear attribution to Bibleworks" as the > I think we can make the fix for now without worrying about the downloading Would have mentioned it, I did mention my experiences here on the I don't recall if vowel points worked correctly or not. Numbers were displayedīackwards, though, which is something that I've never seen in any My decks are in Hebrew as that is my native language. I had opportunity to use AnkiDroid for a few weeks in April, and all Solution would be to fix the Hebrew support. ![]() ![]() That is not a solution, and it is hardly a workaround. > with AnkiDroid because of licencing (and it's better to not fatten up the > installed in the AnkiDroid/fonts directory. > The only hurdle is that the font should be downloaded by the user and > This mapping will be done on the fly, just within webview. ![]() > By mapping the Unicode characters to latin and forcing use of this font! On the other hand, this provides an alternative way to fix the problem:
0 Comments
Read More
Leave a Reply. |