.lang

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.

1.1M
total occurrences
218.3K
since 2019 (20.5%)
1970–2023
years active

Case variants in archive: .lang (1.1M), .Lang (5.7K), .LANG (715) — 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.

— or, if the button is blocked, use the link just below:
(fill the form to enable this link)
What happens after I submit?
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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… (2)

File formats, image formats, audio codecs and other non-PL entities that claim .lang 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 ↗
FormatClass (Wikidata P31)Suggested labelMIMENotesAction
GtkSourceView language definition Q105861241
file format
file formattext/xmlUse as new PL ↗
Mozilla lang file Q137838341
file format
file formatUse as new PL ↗

SWH-mined examples (3)

Real archived programs with this extension, byte-verified against the SWH archive. Useful for deciding what this extension actually is when the attribution is uncertain.
coq-ssreflect.lang · 9766 B · seen 771× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:d71277f42cc1f78b5905c827619f38c89e0948e7;origin=https://github.com/rocq-prover/coq-on-cachix;anchor=swh:1:rev:3031dc74aa4b42e83dba4e1a97ad4c520731cc14;path=/ide/coqide/coq-ssreflect.lang
Open in SWH · Raw bytes
coq.lang · 9946 B · seen 702× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:e9eab48de793b2d3f05da47ff823f6647c2b1e19;origin=https://github.com/princeton-vl/CoqGym;anchor=swh:1:rev:9d330faf0e8e8782d9d869b14f07021eace3f2f1;path=/coq/ide/coq.lang
Open in SWH · Raw bytes
coq.lang · 9954 B · seen 690× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:e6e813aca2b398abf383a5fa4daf604d8191e4d0;origin=https://github.com/rocq-prover/coq-on-cachix;anchor=swh:1:rev:3031dc74aa4b42e83dba4e1a97ad4c520731cc14;path=/ide/coqide/coq.lang
Open in SWH · Raw bytes
Request more SWH-mined examples
If the examples above don't disambiguate what .lang is, request a fresh mining run.
(or open the pre-filled issue directly)