免费转换 PFM 文件
专业的 PFM 文件转换工具
将您的文件拖放到这里
或点击浏览文件
支持的格式
以高质量在所有主要文件格式之间转换
桌面字体
TrueType Font - universal desktop font format developed by Apple and Microsoft in the 1980s. Uses quadratic Bézier curves for glyph outlines. Excellent screen rendering with hinting technology. Works on all platforms (Windows, Mac, Linux). Supports Unicode with up to 65,536 glyphs. Standard desktop font format with maximum compatibility. Perfect for document embedding, desktop publishing, and cross-platform typography. Universal support in all operating systems and applications. Reliable choice for general-purpose font usage.
OpenType Font - modern font format jointly developed by Adobe and Microsoft (1996) extending TrueType. Uses cubic Bézier curves (PostScript outlines) allowing more complex glyph shapes. Supports advanced typography features (ligatures, alternate glyphs, contextual substitutions). Can contain up to 65,536 glyphs enabling comprehensive language support. Cross-platform compatibility (Windows, Mac, Linux). Industry standard for professional typography and multilingual documents. Perfect for print design, branding, and high-quality typography. Superior to TTF for complex scripts and advanced typographic features.
Mac Data Fork Font - legacy Macintosh font format storing TrueType/PostScript data in data fork. Used in Mac OS 9 and earlier. Phased out with Mac OS X transition to .ttf and .otf. Contains complete font data in single file (unlike resource fork fonts). Limited compatibility with modern systems. Convert to TTF or OTF for current macOS and cross-platform use. Historical format important for accessing old Mac fonts. Mainly encountered when migrating legacy Mac systems.
Compact Font Format - Adobe's space-efficient font outline format used within OpenType fonts. Stores glyph outlines using PostScript-based charstrings. More compact than TrueType outlines. Used in OTF fonts with PostScript outlines. Not standalone font file - embedded in OTF. Professional typography standard. Better compression than TTF outlines. Extract from OTF or work with complete OTF fonts.
CID-Keyed Font - Adobe font format for large character sets (Asian languages with thousands of characters). Character ID based system for efficient large font handling. Used in professional CJK (Chinese, Japanese, Korean) typography. Complex format requiring PostScript RIP support. Legacy format superseded by Unicode OpenType. Convert to modern OTF with Unicode mapping for compatibility. Important for accessing legacy Asian language fonts.
Spline Font Database - FontForge's native font format. Editable font source format storing complete font data including editing information. ASCII or binary format with full font metadata. Used in font design and development. Convert to TTF/OTF for deployable fonts. Perfect for font design workflow. Maintains complete font development history. FontForge is free open-source font editor.
Unified Font Object - open source font source format (XML-based directory structure). Developed by font tool creators for interoperability. Stores complete font design data in human-readable XML. Used by modern font editors (RoboFont, Glyphs, FontForge). Perfect for font development and version control. Industry standard for open font source files. Compile to TTF/OTF for distribution. Excellent for collaborative font design.
网页格式
Web Open Font Format - font format specifically designed for web use (2009). Compressed TrueType/OpenType fonts reducing file size by ~40%. Supported by 99% of browsers (Chrome, Firefox, Safari, Edge). Includes metadata for licensing and font information. Perfect for website typography ensuring consistent rendering across devices. Industry standard for web fonts. Faster page loads than raw TTF/OTF. Essential for modern web design and custom typography. Recommended for broad web compatibility.
WOFF 2.0 - improved web font format (2014) with better compression using Brotli algorithm. 30% smaller than WOFF with faster decompression. Supported by all modern browsers (96%+ global coverage). Maintains WOFF's metadata and licensing features. Superior performance for web typography. Recommended format for modern websites. Falls back to WOFF for older browsers. Essential for optimizing website performance and reducing bandwidth. Default choice for contemporary web development.
Embedded OpenType - proprietary web font format developed by Microsoft for Internet Explorer. Compressed and subset fonts with DRM protection. Only supported by Internet Explorer (legacy browser). Obsolete format replaced by WOFF/WOFF2. Historically important for web fonts (1997-2010s). Still encountered in legacy websites. Not recommended for new projects. Convert to WOFF2/WOFF for modern browsers. Maintained only for backward compatibility with old IE versions.
SVG Font - vector-based font format embedded in SVG files. Defines glyphs as SVG paths allowing colors, gradients, and effects. Deprecated for web use in favor of WOFF. Limited browser support (only Safari supports SVG fonts). Larger file sizes than outline fonts. Mainly historical format. Useful for special effects and colored fonts. Modern alternative: OpenType-SVG. Not recommended for general use. Better options: WOFF2 with icon fonts or OpenType color fonts.
专业格式
PostScript Font Binary - Adobe Type 1 binary format for professional printing (1984). Contains glyph outlines in PostScript language. Excellent print quality with precise curves. Requires corresponding PFM or AFM metrics file. Standard in professional publishing and printing industry. Limited to 256 glyphs (single-byte encoding). Being replaced by OpenType. Still used in legacy publishing workflows. Convert to OTF for modern compatibility while preserving PostScript quality.
PostScript Font ASCII - Adobe Type 1 ASCII variant of PFB format. Human-readable PostScript code defining font outlines. Used for font development and debugging. Less efficient than PFB binary format. Requires PFM or AFM metrics file. Same quality as PFB for printing. Legacy format for professional typography. Convert to OTF for modern systems. Primarily historical significance in desktop publishing evolution.
Printer Font Metrics - Windows metrics file for Type 1 PostScript fonts. Contains font measurements (character widths, kerning pairs, bounding boxes). Required companion to PFB/PFA for proper rendering on Windows. Text file format with font metrics data. Does not contain glyph outlines. Legacy format from Windows 3.1/95 era. Used with PFB for complete Type 1 font installation. Modern OpenType fonts include metrics internally. Convert Type 1 fonts to OTF to consolidate metrics and outlines.
Adobe Font Metrics - Adobe's metrics format for Type 1 PostScript fonts. Contains character widths, kerning pairs, ligatures, and bounding boxes. ASCII text format readable by humans and applications. Companion to PFB/PFA outline files. Used by font design tools and professional publishing software. Essential for proper font spacing and kerning. Legacy format with historical importance in digital typography. Modern fonts embed metrics in OTF format. Convert to OpenType for integrated metrics and outlines.
Binary Font File - generic binary font data format used by various font tools and editors. Contains raw font outline data without specific format wrapper. Used in font development and conversion pipelines. Requires specific tools to process. Not a standard end-user format. Intermediate format in font creation workflow. Convert to TTF or OTF for usable fonts. Primarily relevant in font design and development contexts.
Mac Suitcase Font - legacy Macintosh font container (Mac OS Classic) storing multiple fonts in one file. Contains TrueType or PostScript fonts in resource fork. Used with Font Suitcase format (.suit extension). Obsolete with Mac OS X migration. Poor compatibility with modern systems. Required Font/DA Mover for installation on old Macs. Extract individual fonts and convert to TTF/OTF for modern use. Important for recovering fonts from classic Mac archives and systems.
PostScript Font Program - Adobe PostScript Type 1 font in PostScript language format. Contains font outlines as PostScript code. Used for printer font downloads and font development. Human-readable but inefficient. Legacy format from desktop publishing era. Convert to OTF for modern usage. Historical importance in professional typography. Mainly encountered in old publishing workflows.
PageMaker 3 Font - legacy font format from Aldus PageMaker 3.0 (1980s desktop publishing). Proprietary format specific to early PageMaker versions. Obsolete format with no modern support. Important only for recovering old PageMaker documents. Convert to TTF/OTF if font data recoverable. Historical artifact from desktop publishing evolution. Better alternatives available for all uses.
Type 11 Font - variant of PostScript CID-Keyed font format. Used for complex fonts with large character sets. Legacy format for Asian language fonts. Limited modern support. Convert to Unicode OpenType for compatibility. Historical format in CJK font development. Modern alternatives handle large character sets better with Unicode.
Type 42 Font - PostScript font format wrapping TrueType outlines. Hybrid format combining PostScript wrapper with TrueType data. Used for downloading TrueType fonts to PostScript printers. Primarily printer-internal format. Limited end-user relevance. Convert underlying TrueType to TTF/OTF. Historical bridge between TrueType and PostScript worlds.
如何转换文件
上传您的文件,选择输出格式,立即下载转换后的文件。我们的转换器支持批量转换并保持高质量。
常见问题
What is a PFM file and why does it accompany Type 1 fonts on Windows?
A PFM file contains the Windows-specific metric data required to measure and display PostScript Type 1 fonts.
It stores width tables, kerning pairs, and font properties that Windows GDI cannot extract from PFB alone.
Together, PFB and PFM provide a complete Type 1 font installation in Windows environments.
为什么 PFM 文件与 AFM 文件不同,尽管两者都存储度量信息?
AFM files use a text-based structure preferred by Adobe and UNIX platforms, while PFM files are binary and optimized for Windows.
PFM 专注于 GDI 的运行时效率,而 AFM 旨在提高人类可读性和跨平台兼容性。
由于这些差异,AFM 和 PFM 之间的转换通常需要专用工具。
Why can’t Windows render a Type 1 font if the PFM file is missing?
Windows relies on PFM data to calculate glyph positioning and spacing.
没有度量信息,系统无法确定字符宽度或应用字距调整规则。
因此,字体看起来不完整,无法被应用程序加载。
为什么 PFM 文件通常比 PFB 文件小?
PFM 仅存储度量和字体属性,而不存储字形轮廓。
二进制结构有效地压缩这些值,而没有描述性元数据。
这使得 PFM 相较于轮廓较重的 PFB 文件更轻量。
Why were PFM files essential before Windows gained native OpenType support?
Early Windows versions lacked the ability to interpret Adobe Type 1 outline data directly.
PFM 文件提供了系统光栅化器所需的缺失测量值。
They ensured reliable behavior in desktop publishing software like CorelDRAW and early Adobe apps.
为什么 Type 1 字体安装程序通常会自动生成 PFM 文件?
Foundries typically shipped AFM files, but Windows required a binary variant.
安装工具将 AFM 数据转换为 PFM 格式以确保兼容性。
This workflow allowed Type 1 fonts to function across both Windows and UNIX environments.
为什么字距调整对在 PFM 中与在 AFM 中存储的方式不同?
PFM 编码将字距调整表压缩为优化的二进制结构,以便在 GDI 中快速查找。
AFM 文件使用冗长的文本列表,更适合人类检查和编辑。
这两种格式反映了各自平台的不同优先级。
为什么某些 PFM 文件引用 AFM 文件中不存在的内部样式标志?
Windows uses system-level attributes such as weight classifications and pitch information.
这些属性是与 GDI 和传统字体选择对话框集成所必需的。
AFM 文件严格关注排版测量,省略了特定于操作系统的标志。
为什么 PFM 损坏会导致不正确的间距或文本对齐不当?
损坏的宽度表妨碍准确的字符放置。
无效的字距调整数据可能导致字母重叠或间距异常。
由于 PFM 是二进制格式,即使是轻微的损坏也可能破坏整段文本。
为什么许多转换工具需要同时使用 PFB 和 PFM 来重建完整的 Type 1 字体?
PFB 提供轮廓,但缺少基本的布局度量。
PFM 提供无法仅从轮廓中可靠推断的测量值。
结合两者确保在迁移到 OpenType 等格式时的精确再现。
为什么 PFM 文件针对低内存环境进行了优化?
Early versions of Windows operated under tight memory constraints.
二进制度量表在实时渲染过程中减少了 RAM 使用。
这使得 Type 1 字体在资源有限的硬件上可行。
为什么档案工作流程即使在存在 AFM 文件的情况下仍保留 PFM 文件?
PFM preserves the exact metrics used by Windows-based publications.
删除它可能在数十年后重新打开文档时改变换行或间距。
为了历史准确性,通常保留这两种度量格式。
为什么一些现代字体管理器仍然识别 PFM 文件?
它们保持向后兼容,以便继续使用传统的 Type 1 库的组织。
许多旧设计文件依赖于仅存在于 PFM 格式中的度量信息。
支持确保在更新旧项目时的平稳过渡。
为什么将 PFM 度量转换为 OpenType 有时会产生轻微的间距变化?
OpenType 使用不同的表结构来表示字距调整和宽度。
将二进制 PFM 值映射到 OpenType 需要解释而非直接复制。
这可能会在布局中引入小差异,可能需要手动调整。
为什么 PFM 被视为遗留格式,尽管它具有历史重要性?
它依赖于现代操作系统不再原生支持的字体架构(Type 1)。
OpenType 将度量和轮廓合并为一个文件,使单独的 PFM 数据变得不必要。
如今,PFM 仅在维护旧文档和打印系统时仍然相关。