TroiOi - might be an out-of-memory issue; when the reader opens a non-UTF-16 file it actually creates a temporary file in memory containing the UTF-16-converted version of the file and then opens that. Does it help matters any if you clear out some more space in internal memory?
TroiOi/sfrrr/ipsi - the Tuttle and TCM dictionaries are coming later on, we actually haven't even received the source data for one of them yet. They'll probably only be available with the finished release, though worst-case they may not even come out until a month or two after that.
bodybag77 - on #1, can you give me some examples of characters that cause this problem? Or does it not seem to be tied to any particular characters (i.e. it'll sometimes happen and sometimes won't happen with any given character)? #2 might be a text width calculation issue, particularly with some of the anti-aliasing modes that can sometimes be mixed up by a couple of pixels. For #3, yes, Adso should be available too eventually. Not sure about #4, we haven't seen either of these problems here but we'll see if we can figure out a way to reproduce them.
TroiOi/sfrrr/ipsi - the Tuttle and TCM dictionaries are coming later on, we actually haven't even received the source data for one of them yet. They'll probably only be available with the finished release, though worst-case they may not even come out until a month or two after that.
bodybag77 - on #1, can you give me some examples of characters that cause this problem? Or does it not seem to be tied to any particular characters (i.e. it'll sometimes happen and sometimes won't happen with any given character)? #2 might be a text width calculation issue, particularly with some of the anti-aliasing modes that can sometimes be mixed up by a couple of pixels. For #3, yes, Adso should be available too eventually. Not sure about #4, we haven't seen either of these problems here but we'll see if we can figure out a way to reproduce them.