This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have been using Microsoft Word for iPad to write and edit documents for a while now and it has been working well. I have some custom fonts installed on my iPad, and those have been working great with Word as well. Until iOS 11. After I updated my iPad to iOS 11, I got an error message every time I opened a file that relied on my user-installed fonts: “There is insufficient memory or disk space. Word cannot display the requested font.”. And the file closes and/or stays open but doesn’t display my fonts. Is this a known issue? Anyone experiencing this? I’m hopeful that this will be addressed in the first post iOS 11 update for Word, but I haven’t seen anything about it online.
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi All,
The issue has been submitted to our related team for further investigation. If there is any update, I will post back to let you know.
Thanks,
Ran
I agree.
But do you really think Microsoft bothered before this fudge?
They didn‘t do anything for one year so don‘t expect a full solution from them.
This is very good news in some respects, though I have not yet tried it. But it’s only a fudge not a real solution.
On the other hand, it’s very bad news. You’ve just delivered Microsoft the ideal excuse to not even bother trying to find a solution to what is evidently a problem with Word 365.
It will be interesting to see what the next iOS version will dredge up!
I‘m curious too! Gaining further insights would require testing for which I currently don‘t have time ;-)
I guess we shouldn‘t rely on Microsoft to support OTFs, but this way is OK.
Thank you, Schnecko! I followed the instructions to the letter (converting OTF to TTF) and used iFont to install instead of AnyFont and it worked! I'm still curious why the OTF support broke and why AnyFont doesn't work (I didn't try to use AnyFont after converting to TTF). In any event, this fix was HUGE and now I can rely on my iPad to edit our published documents again.