Latin Compress Std Standard Font Free Download ((BETTER))
Quirino Rico
Type 1 fonts are a specialized form of PostScript program and are the original file format used for type display on all PostScript printers. The PostScript language was later extended to support the later TrueType and OpenType font standards. Any new Adobe PostScript language device made today supports all three font standards.
Adobe PostScript Type 1 is a worldwide standard for digital type fonts (International Standards Organization outline font standard, ISO 9541). Adobe Systems was a pioneer for Type 1 for use in PostScript printers. Adobe has set the standards for the design and manufacturing of the Type 1 software. Hundreds of companies around the world followed suit, designing and releasing more than 30,000 fonts in the Type 1 format.
TrueType is a standard for digital type fonts that was developed by Apple Computer, and later licensed to Microsoft Corporation. Each company has made independent extensions to TrueType, which is used in both Windows and Macintosh operating systems. Like Type 1, the TrueType format is available for development of new fonts.
OpenType is a new standard for digital type fonts, developed jointly by Adobe and Microsoft. OpenType supersedes Microsoft's TrueType Open extensions to the TrueType format. OpenType fonts can contain either PostScript or TrueType outlines in a common wrapper. An OpenType font is a single file, which can be used on Macintosh and Windows platforms without conversion. OpenType fonts have many advantages over previous font formats because they contain more glyphs, support more languages (OpenType uses the Unicode standard for character encoding). OpenType fonts also support rich typographic features such as small caps, old style figures, and ligatures, all in a single font.
Character encoding is a table in a font or a computer operating system that maps character codes to glyphs in a font. Most operating systems today represent character codes with an 8-bit unit of data known as a byte. Thus, character encoding tables today are restricted to at most 256 character codes. Not all operating system manufacturers use the same character encoding. For example, the Macintosh platform uses the standard Macintosh character set as defined by Apple Computer, Inc., while the Windows operating system uses another encoding entirely, as defined by Microsoft. Fortunately, OpenType fonts (and standard Type 1 fonts) contain all the glyphs needed for both these encodings, so they work correctly not only with these two systems, but others as well.
Not all operating system manufacturers use the same character encoding. For example, the Macintosh platform uses the standard Macintosh character set as defined by Apple Computer, Inc., while the Windows operating system uses another encoding entirely, as defined by Microsoft. Fortunately, standard Type 1 fonts contain all the glyphs needed for both these encodings, so they work correctly not only with these two systems, but others as well.
Also see character, glyph, keyboard layout.
No. OpenType is based on the Unicode encoding standard, which can support virtually any or all world languages. Adobe has released several Japanese OpenType fonts, as well OpenType fonts that support Arabic, Chinese, Cyrillic, Devanagari, Greek, Gurmukhi, Hebrew, Korean, and Thai.
The decision to work together came from a desire to provide the best solution for customers, and to provide an environment for future joint innovations. Both companies agree that merging the Type 1 and TrueType formats is the best solution for customers. The two font standards can now be supported seamlessly on both Windows and Macintosh platforms.
Style-linking is used with fonts of all formats in standard Windows applications. Most Windows applications only show the "base font" of any style-linked group in their font menus. The additional style-linked fonts won't show up separately in the font menu of these applications.
Adobe packages its OpenType fonts so that they will get the correct icon when unpacked. In OS 8 and 9, the file Type and Creator codes are used in conjunction with the Mac OS Desktop DB file to assign correct icons to files. If the Type and Creator codes are incorrect or missing, or the Desktop DB is corrupt or damaged, icons may not display properly. Additionally, moving OpenType fonts from other operating systems, such as Windows or Unix, may damage or eliminate the Mac OS resource fork, which contains the Type and Creator codes, and custom icons. The standard OpenType icon is seen from the Type "sfnt" and the Creator "ATMC".
First I thought it would be more logical to encode the embedded font subset as contiguous entries instead of leaving holes inside and using the original character location. But then I realized, that by using an encoding vector to the font subset with original entries, characters which are often used can have less bits set to 1 in their byte and can be compressed in a better way (it may lower the entrophy of the overall text this way).
Unicode code points (18 code points): 0041 00DF 0401 015F 00DF 01DF F000 10FFFF 000D 000A 0041 00DF 0401 015F 00DF 01DF F000 10FFFF UTF-16 code units (20 code units) 0041 00DF 0401 015F 00DF 01DF F000 DBFF DFFF 000D 000A 0041 00DF 0401 015F 00DF 01DF F000 DBFF DFFF Compressed (35 bytes) 41 DF 12 81 03 5F 10 DF 1B 03 DF 1C 88 80 0B BF FF FF 0D 0A 41 10 DF 12 81 03 5F 10 DF 13 DF 14 80 15 FF 10 Possible Private Extensions (Informative) During the design and review phase of the compression scheme, the extensions described in this section were suggested. Although these extensions were not accepted as part of the compression scheme itself, they are documented here as examples of how certain problems can be solved by adding higher-level protocols, for use by consenting parties. 10.1 Avoiding Control Byte Values With a simple re-mapping, the SCSU encoded data stream can be made free of most control byte values so that it can be passed where ASCII text is expected. This re-mapping is not as costly as more general schemes for converting binary data to text and leaves the text parts of compressed Latin-1 text fully readable. After encoding, replace any control byte by DLE (0x10) followed by the original byte plus 0x40. NUL becomes DLE followed by '@' (0x40). DLE is replaced by DLE followed by U+0050. Before decoding, the opposite transformation must be performed. 10.2 Handling Runs of the Same Character Longer runs of the same character allow additional compression. Because this scenario is unusual, it was omitted from the standard algorithm. In situations where sender and receiver can agree on the additional specification and where runs are common, the following method is suggested: Before encoding, replace any run of four or more Unicode characters by '@' (U+0040), followed by the character to repeat, followed by a 16-bit count (packed into one Unicode character). The sequence of 33 hyphens --------------------------------- becomes '@' '-' '!' (0x40, 0x2D, 0x21). Any occurrence of @ sign by itself is replaced by @@U+0001. After decoding, the reverse operation must be performed.
References [BOCU] BOCU-1: MIME-Compatible Unicode Compression
Binary Ordered Compression for Unicode (BOCU) [FAQ] Unicode Frequently Asked Questions
For answers to common questions on technical issues; see in particular [Feedback] Reporting Errors and Requesting Information Online
[Glossary] Unicode Glossary
For explanations of terminology used in this and other documents. [Reports] Unicode Technical Reports
For information on the status and development process for technical reports, and for a list of technical reports. [SampleCode] Sample Java code with a full implementation of SCSU
or
[SampleMini] Sample C code with a minimal implementation of an SCSU encoder; see Section 8.4, Minimal Encoder
or
[Unicode] The Unicode Consortium. The Unicode Standard, Version 4.0. Reading, MA, Addison-Wesley, 2003. 0-321-18578-1. [Versions] Versions of the Unicode Standard
For details on the precise contents of each version of the Unicode Standard, and how to cite them. [XML 1.0] Extensible Markup Language (XML) 1.0 (Third Edition)
W3C Recommendation 04 February 2004
-xml/
In particular, see Section F,Autodetection of Character Encodings
-xml/#sec-guessing Acknowledgements The authors would like to thank Dr. Laura Wideburg for assistance in copy editing. Thanks to David Pope, Doug Ewell and Roman Czyborra for bug reports. Markus Scherer proposed the signature sequence for SCSU. David Starner suggested a section on worst-case behavior. Authors The original concept of a standard compression scheme for Unicode was implemented at Reuters and proposed by Misha Wolf and Charles Wicksteed. Extensions and refinements were proposed by Mark Davis, Ken Whistler and Martin Duerst. The final text for the Technical Report and the original sample implementations were created by Asmus Freytag. The Technical Report is now maintained by Markus Scherer, who also contributed the scsumini sample. Revisions Note: none of the fixes imply a change to the specification.
As regards fonts, pdfsizeopt will recode fonts to the very compressed CFF format, and take care of subsetting and duplication issues. I haven't investigated deeply, but in my tests it seems that of the 2 options for type 1 encoded T1 (multilingual) tex fonts, the Latin Modern fonts generally produce significantly larger PDFs than the CM-Super version (which is unfortunate, because Latin Modern is superior in just about every other way (see this question). I just did a quick experiment and this difference in size seems to be only for the pre-pdfsizeopt pdfs: after pdfsizeopt, Latin Modern is the same or smaller than CM-Super.
Using true type fonts that are specified in the PDF standard (and thus available with every conforming pdf viewer) dramatically reduces for me the file size of PDFs generated with pdflatex. Else, other fonts are included in the generated PDF which increases the file size.
df19127ead