This font works in Photoshop but not in Word. Is there a way to fix it?

fontie's picture

I have this free font provided by EPSON. It's a very old font that used to be shipped with printer drivers in the 90s. I can use it in Windows without a problem. I now want to use it on my Mac (OSX 10.8) and see that the font name is garbled when I install it but the contents in the preview show up fine. I can use it in Photoshop alright but I mainly want to use it in MS Word 2011. In Word I can see the font listed (name garbled) but can't select it. I tried selecting some text and then choosing the font but it defaults to the previously selected font.

I don't know much about fonts but still I tried a more hands-on approach. I downloaded TTFEdit and replaced the gabled font name characters with regular ones. After doing this the font won't even show up in the font list either in Photoshop or MS Word! I tried different things in the editor all with the same outcome.

I would really love to be able to use this font on my mac since it is the only font that has the biggest set of japanese kanji in textbook format (strokes that can be clearly seen). It's a very good teaching tool and it's free. I can't afford the paid alternatives.

The actual font name is: EPSON 教科書体M, pronounced kyoukasho tai M, which translates to "textbook body".

Here's the original, unmodified font file: epkyouka.ttf

HVB's picture

Quite a few of the internal font names need to be changed. I don't know how much control you have available in TTFEDIT, but in Fontforge, I changed about a dozen of the font name instances to EPSON-KYOKASHO and it all now works fine. This includes all of the entries that go into what FontLab calls 'Additional Open-Type Names'. - Herb

fontie's picture

Herb,

Thanks for your prompt response. I've installed Fonrforge and tried renaming all the fields like you suggested but I can't find the Additional Open-Type Names. Where exactly are those?

Also, when exporting I'm using the default settings for TTF. Is there anything special that I should set there?

So far I have:

HVB's picture

Those are exactly the way I have them (with insubstantial differences between Mac and PC and possibly versions of FontForge). I saved the file as .OTF and as .TTF. Both work for MS Word 2003 under Windows 7 and my ancient CS2 Adobe applications.
I'm not even sure where the TTF export default settings are ... I didn't go near that screen.
- Herb

JanekZ's picture

You have /hyphen in the first window but /endash in the second!

HVB's picture

JanekZ - How could you tell?

fontie's picture

Oh Herb, this font file DOES work on my Windows machine. I cannot make it work properly on my Mac! I have tried SO many options in Fontforge. Nothing seems to be working. Maybe it would help if you could post your own version of the file so that I could try it on my end.

JanekZ, I pasted the same name on every window. What you are seeing might be that the program uses a different font to show the dialog boxes. Anyway, I'm sure all those names are exactly the same.

JanekZ's picture

OK, I was wrong...
(rem)

fontie's picture

janekZ, thanks for giving this a go! I can now see the font in Word but can't use it (one step forward at least!)

Here's a short screencast of what happens when I try to use it. As you can see in the video, I just can't get Word to "apply" the font wither by selecting it from the menu or by typing it manually on the box.

George Thomas's picture

I tried your original font in Word 2008 Mac (OS X 10.8.3) and it seems to work fine, so it could be an issue with Word 2011.

I assume you set up your Mac for Japanese input?

::edit:: Just found this link to an updated version of the font (3.1e). It's for Windows but more likely to work with Word 2011. http://www.epson.jp/dl_soft/readme/9296.htm

fontie's picture

George,

Thanks for jumping in. I tried the font you linked to and had similar results. However this new font file IS being recognized by other programs on my Mac (TextEdit, Illustrator, etc) and that's good enough for me. This clearly is a Word 2011 issue and even after applying the latest available updates the issue remains.

Thanks all for the patience and help!

Fontie

PS: I'm not getting emails when this thread is updated and have to come check manually :(

George Thomas's picture

Another thing to consider is problems between Font Book and Word 2011. If you are using Font Book, for this font I would avoid it and copy the font directly to my User > Library > Fonts folder.

fontie's picture

George, I didn't know there was a difference. I though Font Book just copied it. Still, I just tried it with same results. Will keep in mind this for the future though. Thanks for the tip!

JanekZ's picture

Did you try OTF?
(rem)
[os/2 ver. changed from 1 to Automatic, and in Panose "monospaced" changed to "proportional"]

fontie's picture

JanekZ,

When I tried OTF no programs would recognize the font. Using your version, all other programs do recognize it except for... Word (no surprise there). Thanks for giving it a shot though. I really appreciate it!

Here's a screenshot with your OTF version on the right (TextEdit) and Word on the left with the default font.
Note that the TextEdit screenshot says "Helvetica" because that what it shows when you un-select text, but you can clearly see that the font is the one I want (brush strokes are more evident and it's a little slanted).

JanekZ's picture

What a merde! I have no more ideas.
Is there a Japanese font (OFL preferably) that works in your system?

fontie's picture

I have a whole bunch of Japanese fonts installed: some came with the system, and some others were installed by Office like MS Mincho, and MS Gothic (but I can't post these as they are surely copyrighted till the ends of time).

All these work perfectly in any program. Now that you mention it, I haven't tried installing a japanese font other than this. I will download and install a bunch of free japanese fonts and will post back my findings. If those install fine I will provide links for you to compare.

JanekZ's picture

Last try, (rem)
(Code page set)

fontie's picture

JanekZ I tried your new version with same results.

I downloaded at least 20 japanese fonts from around the web and Word seemed to dislike them all until I found a page in the Univeristy of Tokyo where they posted an archive with a font that worked properly. I don't know if this will server of any purpose, but here it is: GT2000-01.zip.

I wouldn't have thought that this would be so complicated...

JanekZ's picture

We can try if FontForge makes something Word dislike...
The same font regenerated by FF: https://dl.dropbox.com/u/19437300/GT2000-011.ttf

fontie's picture

Nice catch! It doesn't work! So it's gotta be something FontForge is doing. I also tried with TTFEdit initially but knowing nothing about typography I'm sure I didn't export properly. Dear lord, the amount of options available when exporting a font are endless...

JanekZ's picture

There is one thing - fake DSIG...
Without DSIG: https://dl.dropbox.com/u/19437300/GT2000-012.ttf

fontie's picture

Nope :(

JanekZ's picture

no joy

fontie's picture

Thanks for helping me out anyways. I really appreciate it!

Karl Stange's picture

This may have something to do with it:

http://support.microsoft.com/kb/295062

Particularly in light of:

Microsoft Office does not support custom fonts. This includes any fonts that were manipulated by a font or typography program.

Is FontForge leaving telltale metadata that is being picked up by word? Have you tried opening the saved file with TTX and running a search? Also, if the naming metadata does not conform to Word standards this could be causing problems. It might be worth checking Adam Twardoch's updated naming guide.

Karl Stange's picture

I have managed to get this working with FontLab, but I do not think it has anything to do with FontLab specifically. Running the fonts through DTL OTMaster it flagged the following naming irregularities:

The amended names look like this in FontForge:

fontie's picture

Karl,

Thanks for the info. Could you post a screenshot of the "PS Names" pane in FontForge. Even though I enter the names exactly as in your screenshot, fontforge complains about about the PS Names. It would be great if you could post your own version so that I could try it here.

I checked out the link you posted and found it very insightful. So Bill says "Microsoft Office does not support custom fonts. This includes any fonts that were manipulated by a font or typography program."
They realize that EVERY font is manipulated by a font program, right? I mean, every font, theirs too... unless they have a guy who can just type out the font's binary code rain man style! hahaha

Karl Stange's picture

They realize that EVERY font is manipulated by a font program, right? I mean, every font, theirs too... unless they have a guy who can just type out the font's binary code rain man style! hahaha

Exactly what I thought when I first saw that!

The PS names are as follows (sorry, juggling an offline computer with a mobile device and not easy to post a screenshot on the fly):

Fontname: EpsonKyokasho
Family Name: Epson Kyokasho
Name For Humans: EpsonKyokasho
Weight: Book
Version: 3.00
sfnt Revision: 3
Base Filename: [blank]
Copyright: (c) 2000 SEIKO EPSON CORP. All rights reserved.

fontie's picture

Karl, after following the steps you described the font won't even show up on Word at all BUT an odd thing happened for the first time which is that while Word was loading, a sign popped up "regenerating font list" which has never happened before.
Note that if I type the font name on the font box, the autocomplete does recognize the font but Word won't render it.

I've been a software developer for 12 years and I've written software for websites that get millions of hits per month but this --installing a font-- is what stumps me. Seriously. :(

Karl Stange's picture

If it was easy...

Here are some more screen shots from FontForge and Word:

Karl Stange's picture

and some shots from FontLab:

I hope these help, let me know if you want to see anything else.

charles ellertson's picture

Based on those screen shots:

Probably what follows is worthless, I don't really know what I'm doing, but this has worked for me (with fonts small enough that FontLab can handle them) when there were naming issues.

First thing I would do, without knowing why -- just because it has worked -- is to click on the big red "X" in the Additional Open Types dialog panel. That resets things. Let FontLab build what it wants.

And as a note, I'd watch the parentheses in the copyright information panel. With PostScript Type 1 & Windows, anyway, they are invalid -- you need to use the escape characters -- \(C\).

Save it as a .vfb.

Now, export it as whatever it is (TrueType? PostScript?). Maybe even use an OpenType format.

Problem is, you might solve one issue & create others by doing this.

Karl Stange's picture

First thing I would do, without knowing why -- just because it has worked -- is to click on the big red "X" in the Additional Open Types dialog panel. That resets things. Let FontLab build what it wants.

That was how I got to the version in the screenshot, re-building the naming from scratch and then structuring everything there (Additional OpenType names) afterwards.

Syndicate content Syndicate content