免费转换 T11 文件
专业的 T11 文件转换工具
将您的文件拖放到这里
或点击浏览文件
支持的格式
以高质量在所有主要文件格式之间转换
桌面字体
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.
如何转换文件
上传您的文件,选择输出格式,立即下载转换后的文件。我们的转换器支持批量转换并保持高质量。
常见问题
什么是 T11 字体文件,它通常用于哪里?
T11 文件是用于日本 TeX 系统(如 pTeX 和 upTeX)的位图字体。
它存储特定 JIS 编码的基于像素的字形,具有固定的点大小。
这些文件对早期日本排版工作流程至关重要。
为什么 T11 字体是基于位图而不是基于矢量?
早期的 TeX 工作流程依赖于位图表示,以确保稳定、像素完美的输出。
当 T11 格式标准化时,矢量日本字体并不广泛可用。
位图字体确保在低分辨率设备上可预测的渲染效果。
为什么 T11 文件存在多种大小,而不是缩放单一字体?
位图字体无法在不失真的情况下进行干净的调整大小。
每个点大小都需要自己精心设计的位图网格。
这确保了数学和日文文本组合的清晰度。
为什么在拉丁 TeX 使用 PK 或 TFM 文件时,T11 字体对日本 TeX 是必要的?
日文脚本需要数千个字形,远远超过典型的 PK 字体。
T11 提供了针对东亚排版量身定制的结构化位图表。
它使 TeX 引擎能够高效处理复杂脚本。
为什么 T11 字体包含映射到特定 JIS 代码的字形?
日本 TeX 引擎历史上依赖于 JIS X 0208 编码。
T11 将每个位图映射到其确切的 JIS 位置,以确保一致的索引。
这确保了与传统日本出版工作流程的兼容性。
为什么 T11 字体在现代 PDF 输出中有时会显得像素化?
它们是针对经典打印设备优化的低分辨率位图。
在高分辨率屏幕上显示时,像素结构变得可见。
现代 TeX 引擎更喜欢 OpenType 替代品以避免此问题。
为什么 T11 字体与 TFM 度量文件分开存储?
TFM 文件仅包含宽度和高度等度量,而不包含实际的字形。
T11 文件提供渲染器使用的实际像素字形。
这两个组件都是完整排版所必需的。
为什么日本出版商依赖 T11 字体用于技术和学术文件?
TeX 提供无与伦比的数学排版质量。
T11 提供与 TeX 严格排版引擎兼容的可靠日本字形。
这种组合成为研究论文和科学书籍的标准。
为什么一些 TeX 发行版在采用 OpenType CJK 字体后仍然提供 T11 字体?
围绕位图工作流程构建的遗留文件仍然引用 T11 文件。
向后兼容性对于长期可重复的研究至关重要。
T11 确保档案在不修改的情况下仍然可渲染。
为什么用矢量 CJK 字体替换 T11 字体并不总是简单?
一些 TeX 宏期望精确的位图尺寸以保持换行一致性。
矢量替代可能会稍微改变基线或方向。
需要仔细调整以保持文档的保真度。
为什么T11字体加载速度比基于矢量的替代品快?
位图不需要曲线解释或光栅化计算。
TeX引擎直接将像素模式快速绘制到输出缓冲区。
这种简单性非常适合旧硬件。
尽管是基于位图,为什么T11文件仍然很大?
每个字形图像可能占用相当大的空间,尤其是在较高的像素分辨率下。
日文字体需要数千个这样的位图。
即使没有矢量数据,整体大小也会迅速增长。
为什么T11字体有时包含为日本排版量身定制的独特间距逻辑?
传统的日本排版使用全宽网格和独特的间距规则。
T11字体通过固定的位图尺寸强制执行这些规则。
这保留了排版惯例,如等宽汉字对齐。
为什么设计师很少直接编辑T11文件?
它们存储原始像素字形,而没有高级编辑元数据。
修改它们需要专门的位图编辑工具。
大多数设计师在矢量格式中工作,并允许TeX工具自动生成位图。
为什么T11被认为是遗留格式,即使它仍然出现在现代TeX档案中?
位图字体对于高分辨率出版来说已经过时。
OpenType CJK字体提供了更优质和灵活性。
T11仅保留用于与历史TeX文档的向后兼容性。