Font conversion from Word for Windows to Pages

I get sent .doc and .docx files which I read in Pages by default.


I have one just now which uses 'Palatino Linotype' and 'Times New' [not a variant that I know]. Both are being converted to 'Times' though I have 'Palatino' [part of Apple's core set since the first LaserWriter], 'Times' and 'Times New Roman'.


The free rtf app Bean can work out on its own to use my Palatino and Times to render this document so I'd have thought apple could manage it as I think the fonts have been in Windows since Win 2000!


In my distant memory PageMaker let you create a lookup table, but I can't find a way to get Pages to do what it should be doing by default.

iMac (Retina 5K, 27-inch, Late 2015), macOS Sierra (10.12.2), iPad Pro

Posted on Feb 23, 2017 4:33 AM

Reply
13 replies

Feb 23, 2017 7:59 AM in response to Tom Gewecke

Gosh, I'm impressed: I've just looked for the iOS core font list and see it includes Bodoni 72 and Hoefler.


Odd that only a couple of days ago I saw someone complaining at how few there were in the supplied iOS set. Another of my old Pages documents contained Windings numbers in circles which did not render in iOS. I then found something on my Mac called Nanum Brush Script. It's a TrueType font that Pages and Bean show in the font list, but which TypeBook says is not installed! It produced enclosed numbers for me and it renders fine on iPhone and iPad despite not being listed at http://iosfonts.com/.


Back to my original question: I tried the .docx in my earlier version of Pages and despite the app having little more than half the footprint of the current version I see I'd forgotten that it actually allowed for the re-mapping of fonts, like PageMaker:

User uploaded file

Feb 23, 2017 9:38 AM in response to Colin Cohen

One can still purchase the iWork '09 DVD from Amazon and Ebay resellers. It requires the Apple iWork 9.3 updater for use with macOS Sierra, and that update brings Pages '09 v4.3. I know that Pages '09 v4.3 works with iCloud Drive. I do not use handoff.


Pages v5/v6 applications, having a substantial feature imbalance with Pages '09, will strip unsupported features from Pages '09 documents, or worst case, simply fail to open them. Once you allow these newer applications to “convert” the Pages '09 document, it becomes a Pages v5/v6 document, and is no longer directly backwards compatible with Pages '09. It will have to be first exported to the Pages '09 format.


Current implementations of Pages for {iOS, iCloud} will behave as do v5/v6, and can damage Pages '09 documents.


Hyphenation is broken in Pages '09 v4.3 on macOS Sierra.

Feb 23, 2017 4:51 AM in response to PeterBreis0807

As I said I get sent Windows documents, not the fonts.


Having started my career in printing with hand setting [in the days when fonts were founts over here, before Apple changed that too!] I am well aware that there are infinite versions of every font, to the extent I once had 30 variants of Times on an SE30 to do an evaluation.


If Bean can provide a sensible interpretation I can't believe it is impossible in Pages. By changing two different fonts to a generic Times it is not even possible for me to make an intelligent substitution as there seems no way in Pages to find what the original font was.

Feb 23, 2017 6:05 AM in response to Colin Cohen

By default, Word for Windows does not embed fonts in the document — only font references. Any version of Pages will attempt to reconcile the Word documents' font references to font families and faces (Palatino .vs. Palatino Linotype) currently installed on the Mac. When that reconciliation fails, then Pages will mention the missing font in its warning dialog (usually), and perform font substitution per preprogrammed guidelines. Word for Windows can optionally embed fonts, and these documents will not suffer font substitition, as Pages simply uses the included fonts — if they are compatible with the operating system.


Pages is doing exactly what it was programmed to do, not what it ought to do.


Bean v3.2.9 (specifically for macOS Sierra) will automatically, and quietly substitute Times Roman for any font that is not in the system font database. It will do that for Palatino Linotype too, though I suspect that it may simply convert it to just Palatino — I do not have P. Linotype to test here.


The free LibreOffice will allow one to create, and optionally use a font substitution list in its Preferences.


I have tools here that can show what fonts/font references are in a Word .docx document.

Feb 23, 2017 6:53 AM in response to VikingOSX

I only recently realised that Pages somehow embeds fonts when I looked at a Mac document on my iPhone and found a whole raft of non-core fonts correctly rendered [so glad to see it is no longer 'the age of Courier'].


If 'Pages is doing exactly what it was programmed to do, not what it ought to do' it is simply badly programmed. I use Bean 2.4.1 for preference for data entry and I think at one time Robin Hoover said it was not going to be developed further. I looked again at 3.2.9 recently and don't like it as much. As 2.4.1 runs happily with Siera I shall stick with it. My 3.2.9 must be different to yours as [see my earlier post] I get my Palatino in place of Linotype and my Times in place of theirs in both versions of Bean.


I'm not sure why Linotype have re-cut Palatino from the Stempel version that Apple got in conjunction with Adobe way back, as Stempel had already become the type design department of Linotype when I visited ithem in the mid-80s. Though it was designed for newspaper use on slug-setting machines it was by far the best font for legibility in the early, bad, days of photosetting and later Linotype made it available in all their film formats [you had to buy it again every time you got a new model of typesetter before PostScript!] and was also good on 300dpi lasers printers, while Times was terrible.


I guess this is just another deficiency in Pages: I've not needed to use it in years and having recently got 6.0.5 I get the impression that either it has lost features since 3.0.3, which is the last version I'd used, or made them harder to find. I guess this was to make it easier to port to iOS.

Feb 23, 2017 9:13 AM in response to Colin Cohen

Colin Cohen wrote:


Another of my old Pages documents contained Windings numbers in circles which did not render in iOS. I then found something on my Mac called Nanum Brush Script. It's a TrueType font that Pages and Bean show in the font list, but which TypeBook says is not installed! It produced enclosed numbers for me and it renders fine on iPhone and iPad despite not being listed at http://iosfonts.com/.




It's probably a different font than Nanum which is showing your circled numbers. These are a standard part of Unicode fonts for Asian languages, but your old Wingdings was probably non-Unicode and that's why iOS would not display them. Nanum in intended for Unicode Korean.

Feb 23, 2017 9:24 AM in response to Tom Gewecke

Thanks again.


Having had Macs almost since the get-go there is no knowing how or when I got fonts, especially as vendors kept sending them and I may have installed them to look at and never deleted them. It looks as if it was introduced in 2010, I did not realise TrueType had lasted than long.


When I select the glyphs it says they are Nanum, and if I change to another family the body size is a good bit smaller point for point. I'll keep on using them as they are there and for convenience have kept 1-10 at the bottom of the file to cut and paste in case they are ever needed again, though I can't imagine I'd use the rest of its character set!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Font conversion from Word for Windows to Pages

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.