• No se han encontrado resultados

Competitividad e innovación (análisis de factores)

In document UNIVERSIDAD AUTÓNOMA DE BAJA CALIFORNIA (página 131-153)

CAPITULO IV. Análisis de resultados

4.4 Competitividad e innovación (análisis de factores)

To switch the Font window to the Names mode, click the button on the Font Window command bar (top position) or choose the Names mode from the Mode popup menu (bottom position).

The Encoding combo box (top position) or Encoding popup menu (bottom

position) shows the encoding table currently assigned to the font. When you open the combo box/popup menu, you will see many encodings that are installed and available in FontLab Studio. In the bottom position of the Font Window command bar the encodings are shown in groups.

An encoding table performs one of two functions:  Type 1 encoding table

 glyph arrangement table

As a Type 1 encoding table, an encoding table is used as the source of the character encoding in Type 1 fonts or (in some rare cases) TrueType fonts.

As a glyph arrangement table, type designers use an encoding table to visually arrange glyphs in a particular order during the design process of a font (Type 1, TrueType or OpenType). Such a glyph arrangement table can be used as a “visual map” for the font family so the designer knows what glyphs need to be designed in all members of the family – this way, you will not miss an important glyph.

There is no visual distinction in the Encodings list between Type 1 encoding tables and glyph arrangement tables. Any encoding table can theoretically serve either function. In order, in FontLab Studio the same user interface element (the encoding tables) serve two different purposes.

An encoding table is either just a sequential list of glyph names or maps local character codes to glyph names. FontLab Studio will look up the glyphs in the current font that have glyph names specified in the encoding table and will present the glyphs visually in the sequence specified by the encoding table. If the encoding table is used as a Type 1 encoding table, the same mapping will be written to the Type 1 font and used as its encoding.

41 42 43 20 5A 5D 6F 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 20 space 21 exclam 22 quotedbl 23 numbersign 24 dollar 25 percent 41 A 42 B ! exclam quotedbl # numbersign $ dollar % percent A A B B Source text as sequence

of codes Identification of characters in the font Font

Encoding table

We will now discuss the most common encoding tables included in FontLab Studio.

Type 1 Encoding Tables

Type 1 encoding tables are used as source for the character encoding in Type 1 fonts as well as Multiple Master fonts (whenever we speak of Type 1 encoding, the same applies to Multiple Master).

Type 1 fonts have two fundamentally different kinds of encoding:

Standard Encoding and custom encoding.

The rule of thumb is that a Western Roman Type 1 font should be encoded using Standard Encoding, and a non-Western Type 1 font (e.g. Central European, Cyrillic, Greek) should use custom encoding.

With the default settings of FontLab Studio, if any encoding from the Type 1 Western/Roman group is active in the Font Window, the Type 1 font will be generated using Standard Encoding. If a different encoding is active, the font will be generated using custom encoding that will exactly reflect the active encoding table.

Type 1 Western/Roman group

If Tools > Options > Generating Type 1 > Encoding Options is set to Select encoding automatically or Export Unicode codepage…, then

FontLab will generate a Standard Encoding-encoded Type 1 font if one of the encodings from this group is active. Please refer to the “FontLab Studio Options” section for more discussion on this. Use any of these encodings when you are working on a typical Western Roman Type 1 font. If you are working on a Western Roman Type 1 font that will be generated as Windows Type 1 and as Mac Type 1, use MacOS Roman as your encoding since this will give you the entire character set that is required to be present in your font.

Adobe

Standard Encoding The “native” representation of the Adobe Standard Encoding Default Encoding The simulation of what a Standard Encoding-encoded Type 1

font will appear to the user if installed on the current operating system

MS Windows 1252

Western (ANSI) The simulation of what a Standard Encoding-encoded Type 1 font will appear to the user if installed on Microsoft Windows

MacOS Roman The simulation of what a Standard Encoding-encoded Type 1 font will appear to the user if installed on Mac OS. Use this when you are working on a typical Western Roman Type 1 font.

Type 1 non-Western groups

If any of the encodings from these groups is active, the Type 1 font will be generated with custom encoding if Tools > Options > Generating Type 1 > Encoding options is set to any value except Always write Standard Encoding.

These encodings can be used as the source of encoding for single-codepage non-Western Type 1 fonts, e.g. Mac Cyrillic or Windows Greek. If you’re creating a non-Western Type 1 font, make sure to select the appropriate encoding here, and also set the matching character set in File > Font Info > Encoding and Unicode > Microsoft Character Set and Mac script and FOND ID. Only a combination of the correct encoding in the Font Window

and the correct character set setting in Font Info will give you a working non-Western Type 1 font.

Example encodings in this group:

MS Windows 1251

Cyrillic Encoding for a Windows Cyrillic Type 1 font MacOS Cyrillic Encoding for a Mac Cyrillic Type 1 font

Adobe Symbol Encoding for fonts that include mathematical and symbol characters, defined by Adobe.

“Imported” Encoding

If Tools > Options > Opening Type 1 > Find matching encoding table if possible is enabled, when FontLab Studio opens a custom-encoded Type 1

font, it will try to match the font’s encoding to known custom encodings. If the encoding cannot be matched, “Imported” is shown. The “Imported” encoding will also appear if the user opens a .vfb file that uses an encoding not present on this user’s machine.

The user can choose Glyph > Glyph Names > Save Encoding to save the

imported encoding into a new .enc file so next time, FontLab Studio will match the encoding correctly.

In document UNIVERSIDAD AUTÓNOMA DE BAJA CALIFORNIA (página 131-153)