- Yep Solarized dark. I set up eclipse to solarized dark and then when setting up the colors in terminal use the magnifying glass feature to sample the actual colors so they match perfectly. The default terminal fonts monaco, menlo and andale mono.
- Looking for Terminal fonts? Click to find the best 18 free fonts in the Terminal style. Every font is free to download!
This relies on the very nice fonts github repo from Frank Hassanabad with a bunch of fonts stored - but you could change the curl url to wherever the font you want is located online. The clever way the cd into a directory, download and pop out again came from user Atle's answer here.
Installation
latest version: 3.0.2| 64-bit | |
| macOS (.app) | 3.0.2 |
| Windows (.exe) | 3.0.2 |
| Debian (.deb) | 3.0.2 |
| Fedora (.rpm) | 3.0.2 |
| Other Linux distros (.AppImage) | 3.0.2 |
Project Goals
The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards. In the beginning, our focus will be primarily around speed, stability and the development of the correct API for extension authors.
In the future, we anticipate the community will come up with innovative additions to enhance what could be the simplest, most powerful and well-tested interface for productivity.
Extensions
Extensions are available on npm. We encourage everyone to includehyper in the keywordsfield in package.json.
Then edit .hyper.js and add it to plugins
Hyper will show a notification when your modules are installed to .hyper_plugins.
Keymaps
All command keys can be changed. In order to change them, edit.hyper.js and add your desired change to keymaps.
Then Hyper will change the default with your custom change.
Example: 'window:devtools': 'Cmd+Alt+O'
Default keymaps:
Configuration
Config location
| macOS | ~/Library/Application Support/Hyper/.hyper.js |
| Windows | $Env:AppData/Hyper/.hyper.js |
| Linux | ~/.config/Hyper/.hyper.js |
Note: config at ~/.hyper.js still supported, but will be ignored, if config in application directory present. Otherwise it will be moved to the application directory at first run.
The config object seen above in.hyper.js admits the following
| Property | Default | Description |
updateChannel | 'stable' | The update channel to receive updates from |
fontSize | 12 | The default size in pixels for the terminal |
fontFamily | 'Menlo, DejaVu Sans Mono, Lucida Console, monospace' | The font family to use with optional fallbacks |
uiFontFamily | '-apple-system, BlinkMacSystemFont, Segoe UI, Roboto, ...' | The font family to use for the UI with optional fallbacks |
fontWeight | 'normal' | The default font weight: 'normal' or 'bold' |
fontWeightBold | 'bold' | The font weight for bold characters: 'normal' or 'bold' |
cursorColor | 'rgba(248,28,229,0.8)' | The color of the caret in the terminal |
cursorAccentColor | '#000' | The text color under BLOCK cursor |
cursorShape | 'BLOCK' | The shape of the caret in the terminal. Available options are: 'BEAM', 'UNDERLINE', 'BLOCK' |
cursorBlink | 'false' | If true, cursor will blink |
foregroundColor | '#fff' | The color of the main text of the terminal |
backgroundColor | '#000' | The color and opacity of the window and main terminal background |
selectionColor | 'rgba(248,28,229,0.3)' | The background color/opacity of the text selection in terminal |
borderColor | '#333' | The color of the main window border and tab bar |
css | ' | Custom CSS to include in the main window |
padding | '12px 14px' | CSS padding values for the space around each term |
colors | { black: '#000000', red: '#ff0000', ... } | A list of overrides for the color palette. The names of the keys represent the 'ANSI 16', which can all be seenin the default config. |
shell | ' | A path to a custom shell to run when Hyper starts a new session |
shellArgs | '['--login']' | An array of shell arguments |
env | {} | An object of environment variables to set before launching shell |
windowSize | [540, 380] | The default width/height in pixels of a new window |
scrollback | 1000 | The number of rows to be persisted in terminal buffer for scrolling |
copyOnSelect | false | If true, selected text will automatically be copied to the clipboard |
quickEdit | false | If true, on right click selected text will be copied or pasted if no selection is present (true by default on Windows) |
defaultSSHApp | true | If true, Hyper will be set as the default protocol client for SSH |
modifierKeys | {altIsMeta: false} | Change the behaviour of modifier keys to act as meta key |
showHamburgerMenu | true on Linux/Windows, false on macOS | Change the visibility of the hamburger menu. Available options are: true, false |
showWindowControls | ' | Change the position/visibility of the window controls. Available options are: true, false, 'left' |
Extensions API
Extensions are universal Node.js modules loaded by both Electron and the renderer process.
The extension system is designed around composition of the APIs we use to build the terminal: React components andRedux actions.
Instead of exposing a custom API method or parameter for every possible customization point, we allow you to intercept and compose every bit of functionality!
The only knowledge that is therefore required to successfully extendHyper is that of its underlying open source libraries.
You can find additional details about plugin developmentin the Hyper repository.
Your module has to expose at least one of these methods:
| Method | Invoked from | Description | ||||||
onApp | Electron | Invoked when the app first loads. If a plugin reloads, it's invoked again with the existing app. Parameters:
| ||||||
onWindow | Electron | Invoked when each window is created. If a plugin reloads, it's invoked again with the existing windows. Parameters:
| ||||||
onUnload | Electron | Invoked when a plugin is removed by the user. Parameters:
| ||||||
decorateConfig | Electron / Renderer | v0.5.0+. Allows you to decorate the user's configuration. Parameters:
| ||||||
decorateEnv | Electron | v0.7.0+. Allows you to decorate the user's environment by returning a modified environment object. Parameters:
| ||||||
decorateMenu | Electron | Invoked with the Electron's Parameters:
| ||||||
decorateBrowserOptions | Electron | Allows you to decorate Electron's Parameters:
| ||||||
onRendererWindow | Renderer | Invoked when a plugin is first loaded or subsequently reloaded in each window. Parameters:
| ||||||
middleware | Renderer | A custom Redux middleware that can intercept any action. Subsequently we invoke the | ||||||
reduceUIreduceSessionsreduceTermGroups | Renderer | A custom reducer for the
| ||||||
getTabsProps | Renderer | Passes down props from
| ||||||
getTabProps | Renderer | Passes down props from
| ||||||
getTermGroupProps | Renderer | Passes down props from
| ||||||
getTermProps | Renderer | Passes down props from
| ||||||
mapHyperStatemapTermsStatemapHeaderStatemapNotificationsState | Renderer | A custom mapper for the state properties thatcontainer componentsreceive. Note that for children components to get these properties, you have to pass them down using the corresponding methods (like Must return an extended object of the map passed.
| ||||||
mapHyperDispatchmapTermsDispatchmapHeaderDispatchmapNotificationsDispatch | Renderer | A custom mapper for the dispatch properties. Must return an extended object of the map passed.
| ||||||
decorateHyperdecorateNotificationsdecorateNotificationdecorateHeaderdecorateTabsdecorateTabdecorateTermsdecorateTermGroupdecorateSplitPanedecorateTerm | Renderer | Invoked with the Parameters:
|
Module loading
The user can hot-load and hot-reload plugins by pressing Command + R (refresh). Please strive to make plugins that don't require a complete restart of the application to work.
Notice
Plugins affecting the `BrowserWindow` will the effect on new windows after hot-reload.
In the future we might do this automatically.
When developing, you can add your plugin to.hyper_plugins/local and then specify it under the localPlugins array in.hyper.js. We load new plugins:
- Periodically (every few hours)
- When changes are made to the configuration file (
pluginsorlocalPlugins) - When the user clicks Plugins > Update all now
The process of reloading involves
- Running
npm pruneandnpm installin.hyper_plugins. - Pruning the
require.cachein both electron and the renderer process - Invoking
on*methods on the existing instances and re-rendering components with the fresh decorations in place.
Plugins location
| macOS | ~/Library/Application Support/Hyper/.hyper_plugins |
| Windows | $Env:AppData/Hyper/.hyper_plugins |
| Linux | ~/.config/Hyper/.hyper_plugins |
Note: plugins at ~/.hyper_plugins still supported, but will be ignored, if plugins in application directory present. Otherwise they will be moved to the application directory at first run.
Note: on the main process, plugins are registered as soon as possible (we fire onLoad). On the browser, it's up to the user to trigger their load by pressing command+R. We put the user in control of the loading in this way to prevent them from losing critical work by extensions that reset state or don't preserve it correctly.
Decorating components
We give you the ability to provide a higher order component for every piece of the Hyper UI.
Its structure is as follows:
All the decorate* methods receive the following references in an object passed as the second parameter:
React | The entire React namespace. |
notify | A helper function that shows a desktop notification. The first parameter is the title, the second is the optional body of the notification, and the third is another optional parameter which can be used to log details to the development console. To pass these details, simply provide and object with an |
Notification | The Notification component in case you want to re-use it. |
All the components accept the following two properties to extend their markup:
customChildren | An array of Element or a singleElement to insert at the bottom of the component. |
customChildrenBefore | The same as the above property, but inserted as the first child element(s) of the component. |
Your higher order component can supply a onDecoratedproperty to the decorated component to get a reference to its instance.
Your Term higher order component can supply anonCursorMovehandler property that be called when cursor has moved with an object parameter representing its relative position to Term origin:
x | Horizontal position in pixels |
y | Vertical position in pixels |
width | Cursor width in pixels |
height | Cursor height in pixels |
col | Horizontal position in columns |
row | Vertical position in rows |
We encourage you to maintain compatibility with other decorators. Since many can be set, don't assume that yours is the only one.
For example, if you're passing children, compose potential existing values:
Or if you use onDecorated property
Actions and Effects
All theRedux actionsare available for you to handle through your middleware and reducers. For an example, refer to the Hyperpowerreference plugin.
Side effects occur in two fundamental forms:
- Some actions dispatch other actions based on state.
- Some actions do async work by communicating over the RPC channel to the main process
In all cases, the side effect is passed as the effect key in the action and later handled by our middleware.
This means that you can override, compose or completely eliminate effects! In other words, this is how you can change the default functionality or behavior of the app.
As an example, consider the action we use to increase the font size when you press Command+=:
The underlying terminal
Hyper achieves a lot of its speed and functionality thanks to the power ofxterm.js
Additional APIs
The Electron app objects are extended with the following properties:
config | An Object with the config block from.hyper.js. |
plugins | An Object with helpers for plugins. |
getWindows | A Function that returns an Set of all the open windows. |
createWindow | A Function that will create a new window. Accepts an optional callback that will be passed as the new window's init callback. |
Electron BrowserWindow objects are extended with the following parameters:
rpc | An EventEmitter that allows for communication with the window process. |
sessions | A Map of Sessionobjects which hold the communication with each term's pty.. |
Renderer windows are similarly extended with:
rpc | An EventEmitter that allows for communication with the window process. |
store | The Redux Store object. This allows access todispatch actions or read the global state withgetState. |
The rpc object is symmetrical between browser and renderer process. The API is the same as Node.js, with the exception that it only admits a single object as its parameters only:
Example theme: Hyperyellow
The following extension simply alters the config to add CSS and yellow colors! Here's thecode.
Themes are simply plugins! Only one hook, decorateConfigis needed:
I grabbed the class names by inspecting the term with Devtools, which you can trigger from View -> Toggle Developer Tools. When you do so, notice that some classes are automatically generated and followed by a random nonce (e.g.: term_13hv8io). Ignore those: they change with every new window!
Notice the emphasis on playing nice with other extensions. Specifically, we create a new object, extend only the keys we are interested in, and we compose the CSS to preserve the user's setting and that of other authors':
Example extension: Hyperpower
The following extension renders particles as the caret moves:
Let's walk throughits code.
First, we intercept the Redux action SESSION_ADD_DATA. You can find the full list of actionsin the repository.
Notice that we don't re-dispatch the action, which means we never render the output of the command to the terminal. Instead, we dispatch an action of our own, which we grab in the uiReducerand later map:
We then want to decorate the <Term> component so that we can access the underlying caret.
However, <Term> is not a container that we can map props to. So we use getTermProps to pass the property further down:
The extension thenreturnsa higher order component to wrap <Term>. Notice we pass the onDecoratedproperty to access the base Term component and its DOM ref, and theonCursorMove property to use Hyper cursor API:
Apple's Macintosh computer supports a wide variety of fonts. This support was one of the features that initially distinguished it from other systems.
Fonts[edit]
System fonts[edit]
The primary system font in OS X El Capitan and above is San Francisco. OS X Yosemite used Helvetica Neue, and preceding versions largely employed Lucida Grande. For labels and other small text, 10 pt Lucida Grande was typically used. Lucida Grande is almost identical in appearance to the prevalent Windows font Lucida Sans, and contains a larger variety of glyphs.
MacOS ships with multiple typefaces, for multiple scripts, licensed from several sources. MacOS includes Roman, Japanese and Chinese fonts. It also supports sophisticated font techniques, such as ligatures and filtering.
Many of the classic Macintosh typefaces included with previous versions remained available, including the serif typefaces New York, Palatino, and Times, the sans-serif Charcoal and Chicago, Monaco, Geneva and Helvetica. Courier, a monospaced font, also remained.[1]
In the initial publicly released version of Mac OS X (March 2001), font support for scripts was limited to Lucida Grande and a few fonts for the major Japanese scripts. With each major revision of the OS, fonts supporting additional scripts were added.
Zapfino[edit]
Zapfino is a calligraphic typeface designed by and named after renowned typeface designer Hermann Zapf for Linotype.[2][3] Zapfino utilizes advanced typographic features of the Apple Advanced Typography (AAT) 'morx' table format and is included in OS X partially as a technology demo. Ligatures and character variations are extensively used. The font is based on a calligraphic example by Zapf in 1944. The version included with macOS is a single weight. Since then, Linotype has introduced “Linotype Zapfino Extra” which includes the additional “Forte” weight with more options and alternates.
Several of the GX fonts that Apple commissioned and originally shipped with System 7.5 were ported to use AAT and shipped with Mac OS X 10.2 and 10.3. Hoefler Text, Apple Chancery and Skia are examples of fonts of this heritage. Other typefaces were licensed from the general offerings of leading font vendors.
LastResort[edit]
The LastResort font is invisible to the end user, but is used by the system to display reference glyphs in the event that glyphs needed to display a given character are not found in any other available font. The symbols provided by the LastResort font place glyphs into categories based on their location in the Unicode system and provide a hint to the user about which font or script is required to view unavailable characters. Designed by Apple and extended by Michael Everson of Evertype for Unicode 4.1 coverage, the symbols adhere to a unified design. The glyphs are square with rounded corners with a bold outline. On the left and right sides of the outline, the Unicode range that the character belongs to is given using hexadecimal digits. Top and bottom are used for one or two descriptions of the Unicode block name. A symbol representative of the block is centered inside the square. The typeface used for the text cutouts in the outline is Chicago, otherwise not included with macOS. LastResort has been part of Mac OS since version 8.5, but the limited success of Apple Type Services for Unicode Imaging (ATSUI) on the classic Mac OS means that only users of macOS are regularly exposed to it.
Lucida Grande[edit]
Of the fonts that ship with macOS, Lucida Grande has the broadest character repertoire. This font provides a relatively complete set of Arabic, Roman, Cyrillic, Hebrew, Thai and Greek letters and an assortment of common symbols. All in all, it contains a bit more than 2800 glyphs (including ligatures).
In macOS v10.3 ('Panther'), a font called Apple Symbols was introduced. It complements the set of symbols from Lucida Grande, but also contains glyphs only accessible by glyph ID (that is, they have not been assigned Unicode code points). A hidden font called .Keyboard contains 92 visible glyphs, most of which appear on Apple keyboards.
Font management[edit]
System 6.0.8 and earlier[edit]
Originally, the Macintosh QuickDraw system software supported only bitmapped fonts. The original font set was custom designed for the Macintosh and was intended to provide a screen legibility. These system fonts were named after large cities, e.g. New York, Chicago, and Geneva. (See Fonts of the Original Macintosh.)
Bitmapped fonts were stored as resources within the System file. A utility called Font/DA Mover was used to install fonts into or remove fonts from the System file. Fonts could be embedded into Macintosh applications and other file types, such as a HyperCard stack. Unused fonts were stored in a suitcase file.
The ImageWriter printer supported a higher resolution mode where bitmap fonts with twice the screen resolution were automatically substituted for 'near letter quality' printing. (For example, a 24-point bitmapped font would be used for 12-point printing.) This feature was sometimes called two-times font printing. Some later Apple QuickDraw-based laser printers supported four-times font printing for letter quality output.
With the introduction of the LaserWriter and support for PostScript-compatible printers, the Mac system software initially supported outline fonts for printing only. These outline fonts could be printed in letter quality at any size. PostScript fonts came with two files; a bitmap font was installed into the System file, and an outline font file was stored in the System Folder. Some of the bitmapped “city” fonts were automatically replaced by PostScript fonts by the printer driver. Commercial typefaces such as Times and Helvetica began to be distributed by Apple, Adobe Systems and others.
The Adobe Type Manager (ATM) system extension allowed PostScript outline fonts to be displayed on screen and used with all printers (PostScript or not). This allowed for true WYSIWYG printing in a much broader set of circumstances than the base system software, however with a noticeable speed penalty, especially on Motorola 68000-based machines.
After the release of System 7, Apple added System 6 support for TrueType outline fonts through a freely available system extension, providing functionality similar to ATM. Apple provided TrueType outline files for the bitmapped 'city' system fonts, allowing letter quality WYSIWYG printing.
A reboot was required after installing new fonts unless using a font management utility such as Suitcase, FontJuggler or MasterJuggler.
System 7 – Mac OS 9[edit]
A highly touted feature of System 7 was integrated TrueType outline font support, which received industry support from Microsoft. Fonts were still stored in the System file but could be installed using drag-and-drop. To install new fonts, one had to quit all applications.
Despite this, ATM and PostScript Type 1 fonts continued to be widely used, especially for professional desktop publishing. Eventually Adobe released a free version of their utility, called ATM Light.
In System 7.1, a separate Fonts folder appeared in the System Folder. Fonts were automatically installed when dropped on the System Folder, and became available to applications after they were restarted. Font resources were generally grouped in suitcase files. However, rules for storing printer fonts varied greatly between different system, printer and application configurations until the advent of the new Fonts folder. Typically, they had to be stored directly in the System Folder or in the Extensions Folder.
System 7.5 added the QuickDraw GX graphics engine. TrueType GX supported ligatures and other advanced typography features. However little software supported these features and PostScript remained the standard.
Starting with Mac OS 8.5, the operating system supported data fork fonts, including Windows TrueType and OpenType. In addition, Apple created a new format, called>.dfont. PostScript variant.
Fonts in the /System/Library/Fonts folder and the /Library/Fonts folder are available to all users. Fonts stored in a user's ~/Library/Fonts folder are available to only that user. Previously, up to OS X 10.4, both Mac OS 9 applications running in the legacy Classic Environment and native applications could access fonts stored in the Mac OS 9 system folder
macOS includes a software rasterizer that supports PostScript. Thus eliminating the need for the Adobe Type Manager Light program. The built-in text editing supports advanced typesetting features such as adjustable kerning and baseline, as well as a few OpenType features.
Support for QuickDraw GX fonts was dropped in macOS in favor of TrueType fonts using AAT features. Bitmap fonts are only used on screen if there is a corresponding vector form (which is always used in printing).
Since OS X v10.3 (Panther), a utility called Font Book has been included with the operating system allowing users to easily install fonts and do basic font management.
Third-party font managers[edit]
As desktop publishing took off and PostScript and other outline font formats joined the bitmap fonts, the need for unified font management grew. A number of third parties have created tools, such as Suitcase, for managing font sets. For example, they allowed enabling or disabling fonts on-the-fly, and storing fonts outside of their normal locations. Some even allow the use of Windows .ttf font files natively on systems prior to macOS.
Font technology[edit]
TrueType and PostScript[edit]
TrueType is an outline font standard developed by Apple in the late 1980s, and later licensed to Microsoft, as a competitor to Adobe's Type 1 fonts used in PostScript, which dominated desktop publishing.
The outlines of the characters in TrueType fonts are made of straight line segments and quadratic Bézier curves, rather than the cubic Bézier curves in Type 1 fonts. While the underlying mathematics of TrueType is thus simpler, many type developers prefer to work with cubic curves because they are easier to draw and edit.
While earlier versions of the Mac OS required additional software to work with Type 1 fonts (as well as at least one bitmap copy of each Type 1 font to be used), macOS now includes native support for a variety of font technologies, including both TrueType and PostScript Type 1.
Microsoft, together with Adobe, created an extended TrueType format, called OpenType. Apple, however, continued to develop TrueType. A Zapf table, for example, maps composite glyphs to characters and vice versa and adds other features. The table was named after typeface creator Hermann Zapf with permission.[3]
QuickDraw GX[edit]
QuickDraw GX was a complete overhaul of the Macintosh graphics system, including the font system, which was rolled out for System 7.5 in 1995. QuickDraw GX fonts could be in either TrueType or PostScript Type 1 formats and included additional information about the glyphs and their purpose. Advanced features, such as ligatures, glyph variations, kerning information and small caps, could be used by any GX enabled application. Previously, they had typically been reserved for advanced typesetting applications.
Microsoft was refused a license to GX technology and chose to develop OpenType instead. GX typography and GX technology as a whole never saw widespread adoption. Support for GX was dropped in later versions.
AAT covers much of the same ground as OpenType. It incorporates concepts from the Multiple Master font format, which allows multiple axes of traits to be defined and an n-dimensional number of glyphs to be accessible within that space. AAT features do not alter the underlying characters, but do affect their representation during glyph conversion.
AAT is supported in IBM’s open source ICU library, which implements support for AAT fonts under Linux and other open source operating systems.
Mac Terminal Default Font
Hinting technology[edit]
Hinting is the process by which TrueType fonts are adjusted to the limited resolution of a screen or a relatively low resolution printer. Undesired features in the rendered text, such as lack of symmetry or broken strokes, can be reduced. Hinting is performed by a virtual machine that distorts the control points that define the glyph shapes so that they fit the grid defined by the screen better. Hinting is particularly important when rendering text at low effective resolution: that is, with few pixels per character.
Hinting is part of the TrueType specification, but Apple held three patents in the United States relating to the process:
- US 5155805 'Method and apparatus for moving control points in displaying digital typeface on raster output devices' (filed May 8, 1989)
- US 5159668 'Method and apparatus for manipulating outlines in improving digital typeface on raster output devices' (filed May 8, 1989)
- US 5325479 'Method and apparatus for moving control points in displaying digital typeface on raster output devices' (filed May 28, 1992)
Until they expired, Apple offered licensing of these patents. Microsoft had access to Apple's TrueType patents through cross-licensing. These patents have proven problematic to developers and vendors of open source software for TrueType rendering, such as FreeType. To avoid infringing on the patents, some software disregarded the hinting information present in fonts, resulting in visual artefacts. FreeType developed an automatic hinting engine, but it is difficult to beat the explicit hinting guidelines provided by the typeface designer. The problem of lacking hinting could also be compensated for by using anti-aliasing, although a combination of the two produces the best result.
Subpixel rendering[edit]
OS X/macOS uses subpixel rendering. Version 10.2 introduced subpixel rendering of type and Quartzvector graphics. This feature is enabled using the System Preferences panel 'General' (10.2) or 'Appearance' (10.3), by setting the font smoothing style to 'Medium — best for Flat Panel'. OS X 10.4 introduced an 'Automatic' setting which transparently chooses either 'Medium' or 'Standard,' depending on the type of main display. The quality of the rendering compared to Microsoft's ClearType and FreeType is contested, and is largely a matter of reader preference. However, Apple's approach differs from that of ClearType and FreeType in that TrueType hinting instructions are discarded for all but the smallest type sizes. This results in more consistency of rendering on Mac OS at the expense of allowing type designers a level of fine tuning through hints.
Fonts of the original Macintosh[edit]
Approximately 12 fonts were included with the classic Mac OS (versions 1–9). With the sole exception of Bill Atkinson's Venice typeface, the fonts included with the original Macintosh were designed by Susan Kare, who also designed most of the Macintosh's original icons.
The Macintosh was an early example of a mainstream computer using fonts featuring characters of different widths, often referred to as proportional fonts. Previously, most computer systems were limited to using monospaced fonts, requiring, for example, i and m to be exactly the same width. Vector-based fonts had yet to appear in the personal computer arena, at least for screen use, so all the original Mac's typefaces were bitmaps. Fonts were available in multiple sizes; those sizes installed on a system would be displayed in the font menu in an outline style.
From System 1 through Mac OS 7.6, the default system fonts for Mac OS were Chicago for menus and window titles and Geneva for Finder icons, and they could not be customized. The fonts for Finder icons became customizable starting in System 7. It is accessible in the 'Views' control panel. In Mac OS 8 and Mac OS 9, the default system font was changed to Charcoal menus and window titles, but it could be customized in Preferences.
Naming[edit]
After designing the first few fonts, the team decided to adopt a naming convention. First, they settled on using the names of stops along the Paoli, Pennsylvania, commuter rail line: Overbrook, Merion, Ardmore, and Rosemont. Steve Jobs had liked the idea of using cities as the names, but they had to be 'world class' cities.[4]
Variants[edit]
Variants of each font were algorithmically generated on-the-fly from the standard fonts. Bold, italic, outlined, underlined and shadowed variations were the most common, though some applications also included subscript and superscript.
Outline, shadow and underline are not always supported by modern software and fonts.
Apple logo[edit]
Apple's fonts and the Mac OS Romancharacter set include a solid Apple logo. One reason for including a trademark in a font is that the copyright status of fonts and typefaces is a complicated and uncertain matter. Trademark law, on the other hand, is much stronger. Third parties cannot include the Apple logo in fonts without permission from Apple.[citation needed] Apple states in the MacRoman to Unicode mapping file that:
On regular US QWERTY keyboards, the logo character can be typed using the key combination Shift Option K (⇧⌥K). In MacRoman, the Apple logo has a hex value of 0xF0. The Apple logo has not been assigned a dedicated Unicode code point, but Apple uses U+F8FF () in the Private Use Area.
Note that the logo does have a unique PostScript name in the Adobe Glyph List - /apple, mapping to F8FF.
List[edit]
- Athens (slab serif)
- Cairo was a bitmapdingbat font, most famous for the dogcow at the z character position.
- Chicago (sans-serif) was the default Macintosh system font in System 1–7.6. Also seen on LCD screens of earlier iPod models.
- Geneva (sans-serif) is designed for small point sizes and prevalent in all versions of the Mac user interface. Its name betrays its inspiration by the Swiss typeface Helvetica. Nine point Geneva is built into Old World ROM Macs.
- London (blackletter) was an Old English–style font.
- Los Angeles (script) was a thin font that emulated handwriting.
- Mobile was a bitmapdingbat font. Before System 6, it was known as Taliesin.
- Monaco (sans-serif, monospaced) is a fixed-width font well-suited for 9–12 pt use. Ten point Monaco is built into Old World ROM Macs.
- New York (serif) was a Times Roman–inspired font. The name alluded to the inspiration, even though the Times for which Times Roman was created was that of London, not New York.
- San Francisco was a whimsical font where each character looked as if it was a cutout from a newspaper, creating an intentional ransom note effect.
- Toronto (slab serif) was a geometric design. It was removed from System 6 and later.
- Venice (script) was a calligraphic font designed by Bill Atkinson.
See also[edit]
References[edit]
- ^'Fonts supplied with Mac OS'. Microsoft. 2001-05-29. Retrieved 2008-07-17.
- ^Strizver, Ilene (2015-06-29). 'Hermann Zapf, ITC & Apple: The History of ITC Zapf Chancery & ITC Zapf Dingbats'. CreativePro.com. Retrieved 2017-05-27.
- ^ ab'The TrueType Font File - The Zapf table'. TrueType Reference Manual. Apple Computer, Inc. 2000-09-14. Retrieved 2017-07-25.
- ^'World Class Cities'. Folklore.org. Retrieved 2008-07-17.
External links[edit]
- 'Mac OS 7.x, 8.x 9.x: Fonts Included With Major System Releases'. Apple Inc. 2002-06-11. Retrieved 2008-07-17.