Inventory shortcuts and edit supported font identities

Match the deliverable to the original task

A shortcut owner needed a file pairing each shortcut name with its target and later confirmed a CSV solution. That workflow used Windows COM and the live Start Menu. T323 accepts selected existing LNK originals and inventories stored components. A declared path can be useful evidence even when the browser cannot resolve the current target.

Two font authors asked to separate internal identities, explicitly distinguishing names inside a font from its filename. T324 changes supported existing name records in one unsigned static TrueType font per run. Four same-family fonts require four explicit identity sets and separate runs; installation or application grouping remains a separate assessment.

Choose an ANSI policy before reading shortcut strings

Leave ANSI at unconfirmed when the original system codepage is unknown. Such values remain null, with source path, offset, byte length and SHA256 referring to an exported original. Unicode fields still decode strictly. A literal UTF-16 BOM remains a character, not a stripped header.

Explicit WHATWG windows-1252 decodes every byte with the official mapping, including its control mappings. It is not a guess based on the current computer, ConsoleFE or a file’s creator. GBK, Shift-JIS and other ANSI choices are refused. Local and network LinkInfo may coexist; do not collapse one into an invented canonical target.

• Inspect the five StringData fields and all flags, including raw versus effective show command.
• Environment, MSI, icon, tracker and folder values stay stored declarations. IDList, Console, PropertyStore and unknown payloads remain explicitly opaque where interpretation is unsupported.
• Never activate the exported LNKs as part of this inventory. The tool does not execute a shortcut, command or URL.

Use the shortcut originals and complete report

The 524-byte controlled example has one source row with local and network declarations and literal arguments. Its original name begins with a formula character and includes SVG-like text. Names and values are inert data. The JSON preserves original values; CSV alone adds a leading apostrophe for a formula-leading cell.

shortcut-inventory.zip contains controlled sources/NNNN.lnk, shortcut-inventory.json and shortcut-map.csv. Every raw-reference offset resolves into its exact original bytes. All source rows are available in the table, with 2,000 UTF-16 units per preview cell; use the complete ZIP for long strings and every ExtraData span. resolvedTarget stays null and no existence check is performed.

Enter all four font identities explicitly

The controlled normal TTF is 960 bytes with ten tables, sixteen name records and two glyphs. Family=New, fullName=aNew, postScript=Review and uniqueId=Different change ten supported existing records. The output is 848 bytes because the name storage is rebuilt; all non-name table bytes remain identical except head.checkSumAdjustment. Container offsets and padding can change.

Each identity is 1–63 printable ASCII characters. PostScript additionally excludes whitespace and [](){}<>/%. Existing IDs 1/3/4/6/16/18/21 are edited; style IDs 2/17/22, copyright, license and other names remain. Names are not synthesized and style metadata is not inferred.

Selected Unicode platform 0 encodings 0–4 and Windows 3 encodings 0/1/10 use strict UTF-16BE. Mac 1 encoding 0 receives exact ASCII, while its prior MacRoman value remains null plus raw hex. Unknown unselected codecs stay opaque; unknown selected codecs and malformed known Unicode refuse the whole font.

Retain language and table evidence without loading fonts

Name formats 0 and 1 support sorted unique records, exact and substring original string sharing, and all bounded format-1 LangTags. RFC 5646 syntax is checked, including private-use and grandfathered forms, without promising registration or canonicalization. JSON retains every language offset and raw byte string.

edited.ttf is produced without loading, rendering or installing the supplied font. Every source table checksum and complete 0xB1B0AFBA checksum is checked. name is rebuilt and head.checkSumAdjustment repairs the global checksum. Glyf, loca, cmap, metrics and all other table bytes are retained; their complete semantics are not certified.

Signed DSIG, variable tables, CFF/CFF2, TTC and WOFF containers refuse atomically. FontTools 4.66.1 reads every edited name and all tested glyph outlines, but emits format-1 storageOffset warnings and does not expose LangTag records. Independent struct checks cover every preserved language byte and offset; this gap is not hidden as universal compatibility.

Apply simultaneous budgets and recover the same originals

T323 allows 1,000 files, each 1 MiB and combined 32 MiB, 10,000 ExtraData blocks and 10,000 IDList items per file, and 100,000 total structure visits. Its complete JSON plus safe CSV is limited to 40 MiB. The 74 MiB ZIP allocation guard is dominated by those budgets.

T324 allows one 20 MiB file, 256 tables, 4,096 name records and 1,024 LangTags. Every stored name/language string is at most 8,192 bytes; source and rebuilt distinct pools are at most 65,535 bytes. Complete JSON plus safe CSV is limited to 16 MiB. A strict incremental report lower bound can refuse early; its error reports minimumBytes rather than an invented complete byte count.

Both tools limit original filenames to 512 UTF-16 units and refuse the whole result on a malformed file or budget excess. Cancellation discards partial outputs; same-source recovery uses a new Worker. Native evidence covers genuine positive incomplete cancellation on 1,000 shortcuts and 4,096 name records; browser interaction acceptance is tracked separately.

Tools used in this article