Comment #6 on issue 26344 by [email protected]: FontLinux.cpp ASSERT(fromX != -1 && toX != -1); triggered on Chrome Linux http://code.google.com/p/chromium/issues/detail?id=26344
(in reply to comment 5) Yes. This issue is caused by the normalization code that changes the character offset. (I think this normalization is needed because many TrueType fonts expect it.) As suggested by evan, this issue (maybe other issues also) can be solved by adding another table from the char index for the original string to the char index for the normalized string. In my personal opinion, it may be better to add an inner class (such as NormalizedString) which encapsulates this mapping and improve the readability of this function. Regards, -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
