Separate file declarations from installed behavior
A stored shortcut path or edited font name is concrete file evidence; current target resolution, OS caches and application grouping need separate proof.
Keep the source question and its gap together
The shortcut author’s CSV success is useful first-person feedback. It also used COM, which can supply Shell-resolved targets from a live Windows installation. Exporting stored LNK declarations satisfies a limited selected-file inventory, without claiming the browser reproduces that resolver. An empty or unavailable resolved target must not silently become a successful current path.
The font authors wanted internal identity changes, not renamed copies. Editing supported names delivers a changed file. A signed Tahoma variant, OTF/CFF input, OS cache or application grouping can still block the original broader goal; keep those gaps visible when choosing an original and evaluating the output.
Distinguish declaration, byte preservation and external behavior
A shortcut can store simultaneous local and UNC components, an environment string, an installer identifier and an opaque IDList. They are different evidence channels, not competing candidates for one guessed path. The inventory preserves each literal declaration, raw span and exact original. No target is checked for existence and no command is run.
A font’s name table can change while the glyph outlines and metrics remain byte-identical. That is a meaningful, auditable edit. It does not prove that the OS installed the font, flushed its cache or grouped it into the intended family. The output report identifies the changed records and keeps application behavior outside its claims.
| Statement | Evidence available here | Separate evidence needed |
|---|---|---|
| The shortcut stores this suffix | Full raw span and strict decoded value | Whether a current target resolves |
| These internal font names changed | Every old/new name record and encoded bytes | Whether applications select the new family |
| Glyph table bytes stayed equal | All table SHA256 and tested independent outlines | Universal rendering/installation compatibility |
Let unknown values stay unknown
Unconfirmed ANSI strings remain null with raw references. Explicit WHATWG windows-1252 uses a defined mapping; it does not stand in for arbitrary Windows codepages. Unknown payloads remain exportable rather than disappearing from the inventory. A source name resembling HTML or a spreadsheet formula stays data, with formula protection only in CSV.
A prior MacRoman font name is also not guessed. The report keeps its original hex and null Unicode value, while a selected supported record receives the requested ASCII identity. Unknown selected encodings refuse the font; unknown unselected records are preserved. Language tags receive syntax checks, without inventing registration status.
Keep complete outputs and reachable budget evidence
The new production schemas include T323 or T324, so their serialized capacity vectors were regenerated. LNK JSON/CSV is exactly 40 MiB at the positive boundary and exceeds it by one actual CSV safety byte in the refusal vector. TTF JSON/CSV likewise reaches exactly 16 MiB and refuses one real excess byte. No padded output is used to manufacture those ceilings.
The LNK archive keeps exact originals under controlled names. The TTF report keeps every name and language record and all table provenance; edited.ttf may have a different container layout. Preview cells are shortened for interaction, so use full downloads for audit or long fields. Neither workflow removes private names, paths, arguments, copyright or license data.
- Keep originals separate from edited or exported artifacts.
- Treat all declared paths, launch strings and font data as inert during review.
- After cancellation, rerun the same original bytes; distinguish native proof from current browser acceptance.
References
- Original shortcut-name/target export task
Original question and rob.irvin’s own CSV-success follow-up read and preserved on 2026-10-07. Their COM Start Menu workflow resolves targets; this browser task instead exports selected stored declarations and preserves that gap.
- Original author’s empty target despite visible shortcut data
Full Mythio question and author identity read on 2026-10-07. No current Shell/installer/StoreApp resolution or target classification is promised.
- Original need to separate four same-family fonts
Full Axonn body read on 2026-10-07: changing filenames did not change internal identities; no original fonts were supplied, so unsupported OTF/CFF variants remain outside scope.
- Original internal Tahoma7 identity request
Full RubyWedge body read on 2026-10-07. Potential signed original and installation/cache/coexistence behavior remain unsupported gaps.
- Microsoft Shell Link stored LinkInfo structure
Relevant fields and relative offsets read on 2026-10-07; specification supports byte interpretation, not demand evidence or current target resolution.
- Explicit WHATWG windows-1252 mapping
All 128 high-byte entries read and independently verified on 2026-10-07, including control mappings; host Windows locale is never inferred.
- OpenType name records and language tags
Formats 0/1, name IDs and platform records read on 2026-10-07. Limited existing-record edits do not prove application recognition.
- SFNT directory and checksum rules
Relevant directory/alignment/checksum sections read on 2026-10-07. Other table semantics remain raw passthrough rather than universal validation.
- Language-tag syntax
Syntax, private use and grandfathered forms read on 2026-10-07. No IANA registration or canonicalization guarantee.
Tools in this category
Expand a tool to see its steps, options and supported formats, then open its workspace.
Inventory Windows shortcut declarationsRead stored paths, arguments and opaque components from local LNK originals and export a complete inventory without activating shortcuts.
Select existing LNK files. Inspect all stored local and network declarations, strings, flags and ExtraData, while keeping unresolved targets explicit. Download one ZIP with exact originals and complete JSON/CSV.
Steps
- Select the original LNK files; preserve a separate copy.
- Leave ANSI unconfirmed unless WHATWG windows-1252 is the intended decoding.
- Run and inspect source names, simultaneous path declarations, arguments and unresolved fields.
- Download the ZIP and inspect complete JSON/CSV and exact originals.
Available options
- Explicit ANSI interpretation
- Unconfirmed: retain raw bytes · WHATWG windows-1252
Capabilities and limits
- Up to 1,000 originals, each 1 MiB and combined 32 MiB. Each filename is at most 512 UTF-16 units. One malformed file refuses the whole batch.
- Strict 76-byte Shell Link header; all flags, unsigned decimal FILETIME values, signed icon index and raw/effective show command are retained. Local and network LinkInfo declarations can coexist. Unicode volume, share, device, path and suffix values remain separate stored fields.
- All five StringData fields are read. Ordinary fields permit up to 260 units; command arguments use the uint16 wire limit of 65,535 units. Strict UTF-16 preserves literal BOM characters; malformed strings and embedded NUL are refused.
- ANSI defaults to unconfirmed: values remain null with exact raw references. Only an explicit WHATWG windows-1252 choice enables ANSI decoding. Host locale, ConsoleFE and installed Windows codepages are never guessed; other codecs are outside this release.
- All 11 known ExtraData signatures are framed and required sizes/offsets checked. IDList items, Console, PropertyStore and unknown payloads remain explicitly opaque where interpretation is unsupported. Environment and installer strings are literal, without expansion or resolution.
- At most 10,000 ExtraData blocks and 10,000 IDList items per file, and 100,000 structure visits across the batch. Complete compact JSON plus formula-protected CSV must fit 40 MiB. The 74 MiB ZIP cap is a dominated allocation guard, not a separately reachable supported ceiling.
- The ZIP contains controlled sources/NNNN.lnk originals, shortcut-inventory.json and shortcut-map.csv. JSON keeps original names and values; CSV alone prefixes formula-leading cells. The table keeps all source rows, with cells shortened to 2,000 UTF-16 units; complete fields and every raw span remain in downloads.
- No COM, Shell activation, commands, URL navigation, filesystem/network lookup, environment expansion, installed-application resolution or target existence check. resolvedTarget is always null. This is stored-declaration inventory, not a scan of your live Start Menu or anonymization.
Edit TrueType font namesRewrite explicit internal identities in a supported static TTF while preserving glyph and other table bytes and rebuilding checksums.
Select one static, unsigned glyf/loca TrueType font and enter four explicit internal identities. Edit every supported existing name record, preserving style names, glyphs and other tables. Download edited.ttf and a complete change report.
Steps
- Keep the original and confirm that it is a supported unsigned static TTF.
- Enter all four internal names explicitly; changing the filename is a separate operation.
- Run and inspect every edited-record count and unchanged-table evidence.
- Download edited.ttf plus complete JSON/CSV; assess installation and application behavior separately.
Available options
- Family
- New
- Full name
- aNew
- PostScript name
- Review
- Unique ID
- Different
Capabilities and limits
- One sfnt 0x00010000 TrueType original, at most 20 MiB, with head/name/glyf/loca/maxp/cmap/hhea/hmtx. At most 256 sorted unique aligned tables. Every table checksum and the complete 0xB1B0AFBA checksum are checked; directory bounds, head/maxp and loca ranges are validated.
- Name formats 0 and 1 only, with at most 4,096 sorted unique records and 1,024 LangTags. Every stored name or language string is at most 8,192 bytes; original and rebuilt distinct string pools are each at most 65,535 bytes. Exact and substring source string sharing is supported.
- Existing IDs 1/3/4/6/16/18/21 are edited. Existing style IDs 2/17/22, copyright, license and all other names remain unchanged. Family, full name, PostScript name and unique ID are four explicit 1–63 printable ASCII strings; PostScript excludes whitespace and [](){}<>/%. No names or style metadata are inferred.
- Selected Unicode platform 0 encodings 0–4 and Windows platform 3 encodings 0/1/10 use strict UTF-16BE. Mac platform 1 encoding 0 writes exact ASCII; the old MacRoman value remains null with raw hex. Unknown unselected codecs remain opaque; an unknown selected codec refuses the whole font. Malformed known Unicode also refuses unselected records.
- Every format-1 LangTag is preserved, with RFC 5646 syntax checks including private use and grandfathered forms. No IANA registration or canonicalization is promised. Version-0 custom platforms 240–255 may retain high language IDs.
- Only name is rebuilt; head.checkSumAdjustment changes to repair the global checksum. Every other table is byte-identical. Container offsets, gaps and padding may change. Complete JSON keeps all old/new name bytes, language records and table offsets/SHA256; complete CSV protects formula-leading cells.
- Filename at most 512 UTF-16 units; complete JSON plus safe CSV at most 16 MiB. An incremental report lower-bound guard can refuse before allocating an oversized full report. Edited-font 21 MiB and combined 37 MiB allocation guards are dominated by source/string/report limits; no independent exact ceiling is promised.
- DSIG, variable tables including fvar/avar/STAT/gvar/cvar/HVAR/VVAR/MVAR, CFF/CFF2, TTC, WOFF and WOFF2 are refused. No font loading, installation, glyph bytecode execution, rendering, style inference or full OpenType semantic validation. OS caches and applications may still group or reject edited fonts; compatibility and coexistence are not guaranteed. Table cells are previews of at most 2,000 UTF-16 units.