Re: Arial Baltic does not work on fm7/fm8

Article View: adobe.framemaker

Article #891

#891

From: Arnis_Gubins
Date: Fri, 06 Feb 2009 01:41

13 lines
1232 bytes

Damian,

Due to the unicode usage in FM8 and onwards, FM no longer recognizes
synthetically derived codepage fonts from a WGL TTF or OTF font. You
need to actually have a physical font file with the correct encoding
and naming for each of your derived fonts if you wish to continue work
with these font names.

The alternative is to re-work your templates to use unicode fonts and
remap the non-standard codepage specific characters to unicode values.
The second part may be easier with a script on a MIF file.

Yeah, I know, a royal PITA...

Technical Details

Message-ID: <gl6mo497pk3urdckgsqgh8ju75cg49r7uh@4ax.com>

Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newshub.sdsu.edu!webcrossing

References: <59b792f2.-1@webcrossing.la2eafNXanI> <59b792f2.9@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: fd315,7bfb030ff25c52ce
X-Google-Attributes: gidfd315,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Arnis_Gubins@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.framemaker
Subject: Re: Arial Baltic does not work on fm7/fm8
Message-ID: <gl6mo497pk3urdckgsqgh8ju75cg49r7uh@4ax.com>
Date: Thu, 5 Feb 2009 17:41:04 -0800
References: <59b792f2.-1@webcrossing.la2eafNXanI> <59b792f2.9@webcrossing.la2eafNXanI>
Lines: 13
X-Newsreader: Forte Agent 4.2/32.1118
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message