Julia Falling Posted May 13, 2016 Share Posted May 13, 2016 Hey – This displays properly on the Mac, but not on my iPad. Same font choice (Gentium Basic). Where there are boxes, there ought to be ≠ signs. P.S. I'm guessing there is a way to report this directly from the iPad instead of here? Help … ? Link to comment Share on other sites More sharing options...
Michel Gilbert Posted May 13, 2016 Share Posted May 13, 2016 Hi Julie and Acc,This is similar to the problems I’m having with Ugaritic texts. There seems to be isolated problems with Unicode on the iPad, either in font assignments for specific modules or with Unicode values themselves. The boxes appear when an OS can’t recognize an assigned value.Regards,Michel Link to comment Share on other sites More sharing options...
Julia Falling Posted May 13, 2016 Author Share Posted May 13, 2016 (edited) Michel – Does switching to a particular font fix it? My husband is using Palatino and sees the same issue — I don't think Palatino is unicode, but I could be wrong. Looks like we may have to wait for an iOS update for a fix. Edited May 13, 2016 by Julie Falling Link to comment Share on other sites More sharing options...
Michel Gilbert Posted May 13, 2016 Share Posted May 13, 2016 If you’re using Gentium from SIL, I think it is Unicode. I just tried Palatino in Pages and it’s Unicode also. The underlying code matches a font and a character value. If Acc assigned a Unicode font and all the Unicode characters are assigned correctly, any Unicode font will work. It wouldn’t hurt to try another Unicode font like Times New Roman or Arial. If one of them works, the problem is with Gentium or Palatino. If they don’t, the problem is with the Unicode assignments.Of course, I’m just offering my opinion that there might be a common issue here. Link to comment Share on other sites More sharing options...
Chris Rockwell Posted May 13, 2016 Share Posted May 13, 2016 Hey Julie, As Michel mentioned, this does seems to be related to his issue and we hope to have a fix in our next release. This is good info and I can hopefully reproduce this case which will assist us in finding a fix. Thanks, Chris 1 Link to comment Share on other sites More sharing options...
Julia Falling Posted May 13, 2016 Author Share Posted May 13, 2016 (edited) Michel – I tried at least a dozen different fonts. None displayed correctly. I'm not sure it's a general font problem, but maybe just a special character problem? Chris – Thanks for looking into this. Edited May 13, 2016 by Julie Falling Link to comment Share on other sites More sharing options...
Michel Gilbert Posted May 13, 2016 Share Posted May 13, 2016 Michel – . . . but maybe just a special character problem? I think so. And, the majority of strange characters or boxes appear to be rendering combination characters, and I know Acc has had trouble with them before. Link to comment Share on other sites More sharing options...
Julia Falling Posted May 13, 2016 Author Share Posted May 13, 2016 Well, we've got the problem IDed and Chris & the iAccord team know about it. Is iAccord 2.3.2 the latest version? Any iOS testing going on right now? Link to comment Share on other sites More sharing options...
Chris Rockwell Posted May 13, 2016 Share Posted May 13, 2016 Julie, Yes, 2.3.2 is the current version and we haven't release a 2.3.3 external beta yet, but it's in the works. Chris. Link to comment Share on other sites More sharing options...
Julia Falling Posted May 14, 2016 Author Share Posted May 14, 2016 Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now