Exchanging and Compiling Visual Layout

Transfer layout between visual Lookups and Features code, then compile the intended authoring source for proofing and export.

Open Window > Panels > Lookups for the intended font. When importing selected features, first select those feature rows in the Features panel; a selection in Lookups does not choose the import source.

Importing, Copying, and Compiling

The panel menu separates transferring editable data from making that data supply normal font previews and export.

Command What it does
Import All Features from Features Panel Compiles the current Features-panel code for conversion and replaces the whole Lookups document.
Import Selected Features from Features Panel Imports the feature rows selected in the Features panel, replacing those feature assignments while preserving unrelated features and shared lookup definitions.
Copy feature / Copy features Places FEA text for the selected feature scope on the clipboard. All features copies the current scope’s feature set.
Copy lookup / Copy lookups Places the selected lookup definitions and their referenced dependencies on the clipboard as FEA.
Compile Builds the Lookups document and makes it supply the Glyph window, Preview panel, and font export.

The last successful compilation in Lookups or Features selects which document supplies ordinary previews and export. Compile here chooses the Lookups document; Compile features in Features chooses that code. A failed compilation retains the preceding successful tables. The debugger makes a private build for its own trace and does not change this choice.

Some imported constructions can be inspected in retained binary form but cannot be edited and rebuilt visually without loss. Read any reported limitation before replacing working layout. The fact that an imported font can be debugged does not guarantee a lossless conversion to either editable representation.

Inspect Import and Compilation Diagnostics

Import into Lookups skips unsupported features and reports them. Inspect that report before treating an import as a complete replacement for the original layout. Missing glyph references stop compilation rather than silently dropping the affected rules. Correct the names or restore the needed glyphs and compile again; retain the previous working source while comparing results.

Exchanging Code with Visual Lookups

Use the Lookups panel when you want to inspect the rule structure, edit supported rules visually, or trace a text run. Its document is independent of the text here. Opening it on an imported font starts from available binary layout tables; you do not have to recompile decompiled FEA merely to inspect that data. See Debugging OpenType Layout for the visual editor and debugger workflow.

To replace visual data with code from Features:

  1. Finish the feature code you want to transfer. For a partial transfer, select the feature rows in the Features panel.
  2. Open the Lookups panel menu.
  3. Choose Import Selected Features from Features Panel to replace the selected feature assignments while retaining unrelated features and shared lookup definitions. Choose Import All Features from Features Panel to replace the whole Lookups document.
  4. Inspect the imported rules and test representative text. The import is undoable. It compiles the current code for conversion, including pending edits in Features, but does not publish a new font build.

A failed conversion leaves the visual document intact. Import All is a replacement operation; keep or copy visual work you intend to retain before using it.

To take visual work back to feature code, select the desired feature scope in Lookups and choose Copy feature or Copy features. Paste the FEA text into the Features panel or another editor. Selecting All features in the current scope copies that scope's feature set. Copy lookup or Copy lookups copies the selected definitions, including referenced dependencies; standalone lookup definitions can go in PREFIX and be referenced by a feature.

These clipboard operations generate FEA from the selected data. They do not reproduce an earlier author's comments or formatting, and they do not automatically replace the Features document. Check for existing declarations before pasting a second definition with the same name or feature tag. Compile in the Features panel when the pasted code is ready to supply normal previews and export.