Home · Extensions · .emf

`.emf`

0 claimants 0 primary 0 secondary

SWH popularity

From the SWH-MSR-ARV dataset (Desmazières, Di Cosmo, Lorentz, MSR 2025; file nb_extensions_alphanum.csv) — one row per (ext, year) in the full SWH archive. Case-aggregated. citation.

76.3K

total occurrences

27.6K

since 2019 (36.2%)

2000–2023

years active

Case variants in archive: .emf (73.7K), .EMF (2.4K), .Emf (154) — aggregated above.

Help label this extension

No PL in our taxonomy claims this extension. If you know what it's used for, fill the form below. Vocabulary reference: docs/extension_labels.md.

Label * If label has <...>, fill it here (e.g. for pl/<id> type rust). For multi-PL submissions, enter several pl/<id> separated by commas. Friendly name (optional) Reference URL (optional, but recommended — spec / Wikipedia / vendor) Evidence / notes *

— or, if the button is blocked, use the link just below:

(fill the form to enable this link)

What happens after I submit?

A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
A curator script (tools/process_extension_labels.py) fetches all ext-review issues and writes their parsed contents into data/derived/extension_labels.csv with curator_status="new". Until this script runs, your submission lives only as the GitHub issue.
Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
For pl/<id> labels, build_pl_taxonomy.py promotes accepted labels into ext_claim.csv with source="manual_review:<your-login>" and strength="proposed". The next site rebuild then shows your claim on this extension's page and on the language's page.
Friendly-name + reference-URL labels (e.g. binary:image for .png) are not promoted into ext_claim.csv (they aren't PL claims) but are surfaced on this page's "Prior labels" table so anyone landing here sees them next to the auto-detected category.

In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.

Wikidata says… (8)

File formats, image formats, audio codecs and other non-PL entities that claim .emf on Wikidata (property P1195) or in the Wikipedia infobox. Source: data/derived/external_extension_index.csv. Click Use as new PL on any row to open the Add-PL form pre-filled with that entry's name, Wikipedia/Wikidata URL, and this extension — one submission creates the PL + claim.

Right entry isn't listed? Add manually ↗

Format	Class (Wikidata `P31`)	Suggested label	MIME	Notes	Action
Enhanced Metafile Format Plus Extensions Q136714229 file format	image file format	binary:image	`image/emf`	—	Use as new PL ↗
Windows Enhanced Metafile Q3054349 file format	file format family	—	`image/emf`	—	Use as new PL ↗
Windows Metafile Q1072083 file format	image file format	binary:image	`image/wmf`	wp-only	Use as new PL ↗
HyperVision EMF ASCII Format Q105858382 file format	file format	—	`text/plain`	—	Use as new PL ↗
Jasspa's MicroEmacs Macro File Q105858296 file format	file format	—	`—`	—	Use as new PL ↗
Windows Enhanced Metafile, version 1.0 Q122947210 version 1.0 of Windows Enhanced Metafile	file format	—	`—`	—	Use as new PL ↗
Windows Enhanced Metafile, version 2.0 Q122947259 version 2.0 of Windows Enhanced Metafile	file format	—	`—`	—	Use as new PL ↗
Windows Enhanced Metafile, version 3.0 Q122947391 version 3.0 of Windows Enhanced Metafile	file format	—	`—`	—	Use as new PL ↗

SWH-mined examples (0)

No claimants, heuristics, or SWH samples indexed for .emf yet.