User fonts not working in Word for iPad after iOS 11

Anonymous
2017-10-02T14:45:51+00:00

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.

Microsoft 365 and Office | Word | For home | Windows

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-03T07:17:41+00:00

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

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

75 additional answers

Sort by: Oldest
  1. Anonymous
    2018-03-12T00:17:04+00:00

    I tried it, but with no success. Word still crashes if I select my user-installed fonts, even if converted to TTF.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-12T16:38:45+00:00

    Yawning... did you try rebooting your ipad and killing word app before trying? ;-)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-12T21:48:28+00:00

    Gee, sorry i am keeping you up.  Yes, i have restarted. I have deleted microsoft apps and reinstalled. Same problem.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-03-13T08:36:11+00:00

    Hi All,

    We are still working on this issue. But we don't have an ETA when it will be fixed. 

    Thanks for your understanding and patience.

    Regards,

    Ran

    Was this answer helpful?

    0 comments No comments