Just Solve the File Format Problem - User contributions [en]

Category:File formats with extension .sd

2026-08-22T22:00:47Z

Dan Tobias: Created page with "S"

[[Category:File formats by extension|S]]

Cartrivision

2026-08-09T17:17:00Z

Dan Tobias: Created page with "{{FormatInfo |formattype=physical |subcat=Magnetic tape |subcat2=Videotape |subcat3=Video Cassette |released=1972 }} '''Cartrivision''' was an early (1972) attempt at home vid..."

{{FormatInfo
|formattype=physical
|subcat=Magnetic tape
|subcat2=Videotape
|subcat3=Video Cassette
|released=1972
}}
'''Cartrivision''' was an early (1972) attempt at home video, consisting of a combination TV and video tape player that was designed to play rented movies in a proprietary cassette format. Notably, the consumer devices were incapable of rewinding the tapes, enforcing that rented movies only be played once and could only be rewound at the store from which they were rented. There was also an alternate Cartrivision cassette format that could be rewound, used in purchasable tapes, which could be played on the same players but with rewinding enabled. The rewindable cassettes were black, while the non-rewindable ones were red.

Cassettes were 7 inches by 6.5 inches by 1.5 inches, and contained two reels of half inch magnetic tape mounted on top of one another. Recording capacity was 114 minutes. The recording method was based on [https://patents.google.com/patent/US3718755 US Patent 3,718,755], an improvement over that of [https://patents.google.com/patent/US3359365 US Patent 3,359,365].

== Links ==
* [[Wikipedia:Cartrivision|Wikipedia page]]
* [https://www.mrbetamax.com/CartCassetteHist1.htm Detail of Cartrivision cassette]

Magnetic tape

2026-08-09T17:01:13Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|thiscat=Magnetic tape
}}
'''Magnetic tape''' was for a long time a popular medium for audio recording and data storage. A number of different formats existed.

* [[Audio Cassette]] (includes uses as computer data storage medium)
* [[DC International Cassette]]
* [[Digital Audio Tape]] (DAT)
* [[Digital Compact Cassette]] (DCC)
* [[Digital Data Storage]] (DDS)
* [[Elcaset]]
* [[Endless-loop tape cartridge]]
** [[4-Track]]
** [[8-Track]]
** [[Echo-matic]] (Cousino tape cartridge)
** [[Orrtronics 8-Track]]
* [[Jingle Card Cassette]]
** [[SONIFEX]]
* [[Linear Tape File System]]
* [[Magnetic tape data storage]]
* [[NT]] cassette (Scoopman)
* [[Open Reel Audiotape]]
* [[Pocket Rockers]]
* [[Sanyo Tape Cartridge]] [https://www.youtube.com/watch?v=JJUYI3XkvT4]
* [[Videotape]]
** [[Open Reel Videotape]]
** [[Video Cassette]]

== Links ==
* [http://archive.org/details/bitsavers_memorextapediaUndertheMicroscopeOct68_10523866 Magnetic Recording Media Under the Microscope (October 1968)]
* [http://hackaday.com/2014/02/08/building-a-tape-recorder-in-1949/ Building A Tape Recorder In 1949]
* [http://crawford.com/format-obsolescence-an-urgent-crisis/ Format Obsolescence: An Urgent Crisis]
* [https://strandgames.com/blog/magnetic-scrolls-games-source-code-recovered Magnetic Scrolls Original Games Source Code Recovered!]

Videotape

2026-08-09T17:00:59Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|subcat=Magnetic tape
|thiscat=Videotape
}}

* [[Open Reel Videotape]]
* [[Video Cassette]]

== Resources ==

* [http://www.arts.state.tx.us/video/pdf/video.pdf Videotape Identification and Assessment Guide], Texas Comission on the Arts, 2004.

Video Cassette

2026-08-09T17:00:45Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|subcat=Magnetic tape
|subcat2=Videotape
|thiscat=Video Cassette
}}

* [[8mm Formats]] (including [[Digital 8]], [[Hi8]], [[Video8]])
* [[Betacam]]
* [[BetacamSP]]
* [[BetacamSX]]
* [[Betamax]]
* [[Cartrivision]]
* [[D2]]
* [[D3]]
* [[Digital Betacam]]
* [[DV Formats]] (Including [[DVCAM]], [[DVCPro]], [[MiniDV]], [[HDV]])
* [[MicroMV]]
* [[U-matic 1/2"]]
* [[U-matic 3/4"]]
* [[U-matic 3/4" SP]]
* [[U-matic HB]]
* [[VHS]] Formats (Including [[S-VHS]]. [[VHS-C]], [[S-VHS-C]], [[D-VHS]])
* [[Video 2000]]

Videotape

2026-08-09T16:58:21Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|subcat=Magnetic tape
|thiscat=Videotape
}}

* [[Cartrivision]]
* [[Open Reel Videotape]]
* [[Video Cassette]]

== Resources ==

* [http://www.arts.state.tx.us/video/pdf/video.pdf Videotape Identification and Assessment Guide], Texas Comission on the Arts, 2004.

Magnetic tape

2026-08-09T16:57:55Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|thiscat=Magnetic tape
}}
'''Magnetic tape''' was for a long time a popular medium for audio recording and data storage. A number of different formats existed.

* [[Audio Cassette]] (includes uses as computer data storage medium)
* [[DC International Cassette]]
* [[Digital Audio Tape]] (DAT)
* [[Digital Compact Cassette]] (DCC)
* [[Digital Data Storage]] (DDS)
* [[Elcaset]]
* [[Endless-loop tape cartridge]]
** [[4-Track]]
** [[8-Track]]
** [[Echo-matic]] (Cousino tape cartridge)
** [[Orrtronics 8-Track]]
* [[Jingle Card Cassette]]
** [[SONIFEX]]
* [[Linear Tape File System]]
* [[Magnetic tape data storage]]
* [[NT]] cassette (Scoopman)
* [[Open Reel Audiotape]]
* [[Pocket Rockers]]
* [[Sanyo Tape Cartridge]] [https://www.youtube.com/watch?v=JJUYI3XkvT4]
* [[Videotape]]
** [[Cartrivision]]
** [[Open Reel Videotape]]
** [[Video Cassette]]

== Links ==
* [http://archive.org/details/bitsavers_memorextapediaUndertheMicroscopeOct68_10523866 Magnetic Recording Media Under the Microscope (October 1968)]
* [http://hackaday.com/2014/02/08/building-a-tape-recorder-in-1949/ Building A Tape Recorder In 1949]
* [http://crawford.com/format-obsolescence-an-urgent-crisis/ Format Obsolescence: An Urgent Crisis]
* [https://strandgames.com/blog/magnetic-scrolls-games-source-code-recovered Magnetic Scrolls Original Games Source Code Recovered!]

PC-DOS 360K format

2026-05-07T04:57:26Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|subcat=Floppy disk
|wikidata={{wikidata|Q29167905}}
}}
The '''PC-DOS 360K format''' was a very common floppy disk format in the 1980s, used on IBM PCs and compatibles. It replaced earlier [[PC-DOS 160K format|160K]], [[PC-DOS 180K format|180K]], and [[PC-DOS 320K format|320K]] formats using either fewer sectors, single-sided disks, or both, with a new format getting the most out of a double-sided, double-density 5 1/4" floppy disk. It had 40 tracks per side, with 9 sectors per track, and 512 bytes per sector. The disk turned at 300 RPM.

These disks were generally used with [[FAT12]] file systems under the MS-DOS or PC-DOS operating system, but (far more rarely) were used with other filesystems too (e.g CP/M-86). The sector headers, etc, were based on [[IBM 3740 format]], albeit with [[MFM encoding]] (double density) replacing the original [[FM encoding]] (single density).

After being a commonplace format for most of the 1980s, this format declined in favor of the high-density [[PC-DOS 1.2M format]] and the 3 1/2" [[PC-DOS 720K format]] and [[PC-DOS 1.44M format]]. (There were compatibility issues in reading 360K disks on low-density drives after they were written to with a high-density drive, even though the writing is done in an emulation of the old format, due to the different drive head on the newer drives. The high-density drive heads were smaller, and the data written by them might not be picked up correctly by the larger low-density heads, particularly if the new data was overwriting data stored earlier using large-headed drives, which might not be completely overwritten.)

In the late '80s and early '90s, it was common for desktop PCs to have both 5 1/4" and 3 1/2" disk drives in order to be compatible with all software and data, which might be distributed on either format. Often the 5 1/4" drive was drive A, and the 3 1/2" one was drive B. Later PCs, however, were more likely to have only a 3 1/2" drive, set up to respond to both drive letters. Eventually, PCs stopped having floppy disk drives altogether as other data storage and transfer media took over.

== Links ==
* [http://www.textfiles.com/programming/FORMATS/formats.pro Info on MS-DOS 1.x - 2.x disk formats]
* [http://67.185.176.54:8080/diskette_handling.html Working with old diskettes]
* [http://www.computerhistory.org/_static/atchm/microsoft-ms-dos-early-source-code/ Early PC-DOS source code]

[[Category:IBM]]
[[Category:Microsoft]]
[[Category:MS-DOS]]

IBM 3740 format

2026-05-07T04:56:45Z

Dan Tobias:

{{FormatInfo
|formattype=physical
|subcat=Floppy disk
|released=1973
}}
The '''IBM 3740 format''' of 8" floppy disks was used in the 1970s IBM 3740 data entry system, which replaced keypunch systems that stored data on [[punched card]]s.

The disk format was single-sided, single-density, and had 73 tracks with 26 sectors storing 128 bytes per sector. The total capacity was 237.25 KB. [[FM encoding]] was used.

Although 8-inch floppies were extremely rare on IBM PCs, the physical format of IBM PC 5.25 inch and 3.5 inch floppies is directly descended from that of the IBM 3740, with various enhancements – as well as the physical shrink in the disk size, there was also the switch to double-sided, double density ([[MFM encoding]]) instead of single density ([[FM encoding]]), and support for sectors larger than 128 bytes (most IBM PC floppy controllers support any power-of-2 sector size between 128 and 4096, but the vast majority of floppies were formatted with 512 byte sectors.) This includes inheriting various obscure and rarely used IBM 3740 features, such as "deleted sectors".

[[DEC RX01]] use the same physical format as IBM 3740, and [[DEC RX02]] floppies are the same but double-density (MFM). 3740 was also the most popular recording format for CP/M.

An ASCII version of the (originally EBCDIC) IBM 3740 filesystem was standardised by ECMA as ECMA-58 and ECMA-67. While many CP/M systems, Microsoft Standalone Disk Basic, and IBM PC's copied the IBM 3740 track format (sector headers, etc), CP/M and DOS did not copy the IBM 3740 filesystem. Systems that supported the IBM 3740 filesystem included IBM mainframes and mainframe peripherals, IBM midrange systems (System/32, System/34, System/36, System/38, AS/400), IBM Series/1 minicomputer, Olivetti P6060, Nixdorf 8820 (see [https://github.com/kkaempf/nixdisk/blob/main/nixdisk.rb tool to read Nixdorf 8820 floppies]). DEC also offered a utility to read the 3740 filesystem under RSTS-11, [https://github.com/hanshuebner/rsts10/blob/main/170052/flint.bas FLINT].

(See IBM document GA21-9182-1 to -5.)

== Links ==
* [[Wikipedia:IBM 3740|Wikipedia article]]
* [http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/3740/GA21-9152-2_IBM_3740_DataEntrySystem_SystemSummary_and_InstallationManual_PhysicalPlanning_Jun74.pdf Manual]
* [https://www.ibm.com/ibm/history/exhibits/rochester/rochester_4016.html IBM archives page]

[[Category:IBM]]

Document

2026-05-04T17:59:32Z

Dan Tobias: /* Desktop Publishing */

{{FormatInfo
|formattype=electronic
|thiscat=Document
|image=Text-editors.jpg
}}

== General and multi-function ==

* [[602Pro PC Suite]]
* [[ActiveMime]] (format used to store macros within MS Office documents)
* [[Airtable]] (cloud-based documents combining database and spreadsheet functionality)
* [[BeagleWorks]]
* [[COSMI MultiMedia]]
* [[EIOffice]] (Chinese office suite alternative)
* [[Farallon Replica]] ('90s cross platform document)
* [[Google Document]] (.gdoc)
* [[iWork]] (Apple; used for Pages, Numbers, and Keynote)
* [[Microsoft Compound File]] (OLE Compound Document)
* [[Microsoft Office]]
* [[Microsoft Works]]
* [[Office Open XML]]
* [[OpenDocument]] (ODF; OASIS)
* [[OpenOffice.org XML]]
* [[PerfectWorks]] (Novell WordPerfect)
* [[PFS:First Choice]]
* [[StarOffice binary formats]]
* [[UOF]] (Chinese office document format)
* [[Synology Office]] (.odoc, .osheet, .oslides)

== Collaboration ==

* [[Microsoft OneNote]] (ONE, ONEPKG)

== Desktop Publishing ==

* [[3M Printscape]]
* [[3M Post-It]]
* [[Affinity Publisher]] (.afpub)
* [[Calamus]] (.cdk)
* [[Canvas]]
* [[Corel Print House]] (.cph)
* [[Corel Print Office]] (.cpo)
* [[Dynamic Publisher]]
* [[Express Publisher]] (.epd)
* [[GEM Desktop Publisher]] (.gwd)
* [[Greenstreet Publisher]] (.dtp)
* [[Hallmark Card Studio]]
* [[Impression]]
* InDesign / InCopy
** [[InDesign INDD]]
** [[IDML]]
** [[InDesign INX]]
** [[InDesign Book]] (.indb)
** [[InDesign Library]] (.indl)
** [[InCopy]] (.icml)
* [[iPublish]] (.did)
* [[Logitech Finesse]] (.fin)
* [[Microsoft Home Publishing]] (.php)
* [[Microsoft Publisher]] (.pub)
** [[PUZ]] (archived "Pack and Go" file)
* [[The Newsroom|Newsroom, The]]
* [[PageMagic]] (.dtp)
* [[PageMaker]] (originally from Aldus, later Adobe)
* [[PFS First Publisher]] (.pub)
* [[PrintMaster]]
* [[PrintPartner]]
* [[The Print Shop|Print Shop, The]] (Broderbund)
* Publish It!: See [[Timeworks Publisher]]
* [[QuarkXPress]]
* [[Ragtime]]
* [[Ready, Set, Go!]]
* [[Scribus]] (.sla, .scd)
* [[Serif PagePlus]] (.ppp)
* [[Timeworks Publisher]] (also released as Publish It!) (.dtp)
* [[Ventura Publisher]] (Corel) (.chp)
* [[VivaDesigner]] (.desd)
* [[VivaPress]] (.vpd)

== Document Processors ==
(similar to word processors and desktop publishing but designed particularly for building structured documents such as technical documentation)

* [[Bikeshed]]
* [[DITA]] (Darwin Information Typing Architecture)
* [[FrameMaker]]
** [[Element Definition Document]]
** [[Maker Interchange Format]] (MIF)
* [[LaTeX]]
* [[Scribe]]
* [[TeX]]
* [[troff]]

=== Documentation combined with source code ===
* [[CWEB]]
* [[Doxygen]]
* [[Javadoc]]
* [[Noweb]]
* [[Pod]]
* [[RDoc]]
* [[WEB]]

== Document storage/exchange formats (non-program-specific)==
* [[AFP]] (Advanced Format Printing)
* [[CSV]] (Comma Separated Values)
* [[Common Ground]]
* [[Data Interchange Format]] (DIF)
* [[DDIF]]
* [[DjVu]]
* [[Envoy]]
* [[FTXT]]
* [[IBM BookManager book]]
* [[OpenXPS]]
* [[PDF]] (Portable Document Format)
** [[XDP]]
** [[XFA]]
** [[XFDF]]
* [[Plain text]] (TXT) (Un-structured text document)
* [[Portable Text]] [https://github.com/portabletext/portabletext]
* [[PostScript]]
* [[RTF]] (Rich Text Format)
* [[RTFD]] (Rich Text Format Directory)
* [[SYLK]] (Symbolic Link)
* [[WWF]] (non-printable variant of PDF)

== Label making ==
* [[Avery Labels]]
* [[P-touch Editor Label]] (.lbt, .lbx)
* [[JWL]] (Roxio Label Creator)
* [[NTI JewelCase Maker]] (.jwc)
* [[Discus]] (.cdl)

== Presentation ==
* [[ARTstor Presentation]] (.prs)
* [[Astound Presentation]] (.asd)
* [[Asymetrix Compel]] (.cpl)
* [[Corel Presentations]] (.shw, .mst)
* [[DemoMaker (R. Janorkar)]]
* [[Harvard Graphics]]
** [[SPC Runtime Presentation]] (.ply)
* [[Keynote]] (Apple iWork/iCloud)
* [[OpenDocument Presentation]] (.odp, .otp)
* [[Persuasion]] (.pr2, .pr3)
* [[PmDraw]]
* [[Microsoft PowerPoint|PowerPoint]]
** [[PPT]] (PowerPoint presentation)
** [[PPTX]] (PowerPoint presentation, XML format)
** PPS, PPSM, PPSX, POT, POTM, POTX, PPTM: See [[Microsoft PowerPoint|PowerPoint]].
* [[SHW (Corel)]]
* [[Stanford Graphics]]
* [[SXI]] (StarOffice / OpenOffice.org) (.sxi, .sti)

See also:
* [[Presentation file creation software]]

== Spreadsheet ==
* [[Ability Spreadsheet]] (.aws, .ast)
* [[As-Easy-As]]
* [[Corel Calculate]]
* [[CSS STATISTICA]] (.css; spreadsheet format used in [[Statistica]])
* [[DeskMate Worksheet]] (.wks)
* [[Full Impact]]
* [[Gnumeric]] (.gnumeric, .gnm)
* [[Google Sheet]] (.gsheet)
* [[Lotus 1-2-3]] (.wks, .wk1, .wk2, .wk3, .wk4)
* [[Lotus Improv]] (.imp, .imx)
* [[Lotus Symphony]]
* [[Microsoft Excel]]
** [[SpreadsheetML]] (XML format preceding later XLSX format)
** [[XLM]] (Excel spreadsheet macro, old pre-XML format)
** [[XLS]] (Excel spreadsheet old pre-XML format)
** [[XLSB]] (Excel binary workbook)
** [[XLSM]] (Excel macro-enabled spreadsheet format, XML version)
** [[XLSX]] (Excel spreadsheet format, XML version)
** [[XLT]] (Excel template, old pre-XML format)
** [[XLTM]] (Excel macro-enabled template, XML version)
** [[XLTX]] (Excel template, XML version)
* [[Microsoft Works Spreadsheet]] (.wks)
* [[Mouse Calc]] (Apple II)
* [[MOXCEL]] (.mxl) [http://yoksel.net.ru/FormatMOXCEL/Zagolovok 1]
* [[MultiPlan]] (early Microsoft spreadsheet)
* [[Numbers]] (Apple iWork/iCloud)
* [[OpenDocument Spreadsheet]] (.ods, .ots)
* [[PC-Calc]]
* [[pfs:Plan]]
* [[Quattro Pro]]
* [[SDC]] (StarOffice spreadsheet)
* [[SuperCalc 3]]
* [[Swift Spreadsheet]] (Atari 8-bit)
* [[SXC]] (OpenOffice.org 1.0 Spreadsheet) (.sxc, .stc)
* [[VisiCalc]]

See also:
* [[Spreadsheet file creation software]]

== Word Processor ==
* [[Ability Write]] (.aww, .awp)
* [[AbiWord]] (.abw)
* [[Ami Pro]] (.sam)
* [[AppleWorks]]
* [[Bank Street Writer]]
* [[Breeze]]
* Brother WP Typewriters
** [[Brother 120k]]
** [[Brother 240k]]
** [[Brother HD]]
* [[Canon Cat]]
* [[ChiWriter]] (.chi)
* [[ClarisWorks]] (Mac) (CWK)
* [[Corel Write]]
* [[Cut & Paste]] (Electronic Arts Home Management Software)
* [[DavkaWriter]] (.dwd)
* [[DeskMate Text]] (.doc)
* [[DisplayWrite]] (IBM)
* [[DotWriter]] (TRS-80, Apple II)
* [[TechWriter|EasiWriter / TechWriter]] (Word processor file format)
* [[Easywriter]]
* [[The Electric Pencil]] (word processor for 8080/Z-80 machines, and later IBM PC)
* [[Envision Publisher]]
* [[EPOC Word]]
* [[FullWrite]] (Mac)
* [[geoWrite]]
* [[HomeWord]] (Sierra Online, Apple II)
* [[HWP]] (Hancom Word, Korean)
* [[HWPML]] (Hangul Word Processor Markup Language, Korean)
* [[IBM Displaywriter]] (dedicated word processing machine)
* [[IBM Writing Assistant]] (.iwa)
* [[Ichitaro]] (.jtd)
* [[JOT]] (Juggler Of Text; experimental word processor by Ted Nelson c. 1980)
* [[JustWrite]]
* [[Kingsoft Office]] (.wps, .wpt)
* [[LocoScript]]
* [[Lotus Word Pro]] (.lwp)
* [[MacWrite]]
* [[Magic Window]]
* [[Maple]]
* [[Microsoft Word]]
** [[DOC]] (Word document)
** [[DOCM]] (Word macro-enabled document)
** [[DOCX]] (Word document, XML format)
** [[DOT]] (Word template)
** [[DOTM]] (Word macro-enabled template)
** [[DOTX]] (Word template, XML format)
** [[Microsoft Word for Macintosh]]
** [[WordProcessingML]] (XML format preceding later DOCX one)
* [[Microsoft Works Word Processor]] (.wps, .wpt)
* [[Microsoft Write]] (.wri)
* [[Mouse Word]] (Apple II)
* [[Mousewrite]] (Apple II; apparently a different program from Mouse Word)
* [[MultiMate Professional Word Processor]] (.dox, .pat)
* [[Nisus Writer]]
* [[Nota Bene]] (.nb)
* [[OpenDocument Text]] (.odt, .ott)
* [[Pages]] (Apple iWork/iCloud)
* [[PC-Outline]]
* [[PC-Type]]
* [[PC-Write]]
* [[Perfect Writer]]
* [[pfs:Write]]
* [[PIE Writer]] (Hayden Software, Apple II)
* [[@PROMT]] (.std)
* [[Psion Series 3 Word]] (.wrd)
* [[QR-Tekst]] (.qrt)
* [[RFT]]
* [[Samna Word]]
* [[ScreenWriter II]] (for Apple II; formerly SuperScribe II)
* [[Scripsit]]
* [[Scrivener]] (.scriv)
* [[SDW]] (StarOffice Writer)
* [[Storyist]] (.story)
* [[Student Writing Center]]
* [[SXW]] and [[STW]] (OpenOffice.org 1.0 Text) (.sxw, .stw)
* [[TAG]]
* [[TechWriter]] (Scientific word processor file format)
* [[TI-Writer]]
* [[Volkswriter]]
* Wang (dedicated word processing machines)
** [[Wang 1200]] (1972; used cassette storage)
** [[Wang OIS]] (1977; used disks)
* [[WordPerfect]]
* [[WordStar]]
** [[WordStar 2000]]
* [[WriteNow]]

See also:
* [[Document file creation software]]

== Screenwriting ==
* [[Adobe Story]] (.astx)
* [[Celtx]] (.celtx or .cxscript)
* [[Dramatica]]
* [[FadeIn]]
* [[Final Draft]] (.fdr, .fdx)
* [[Fountain]]
* [[Hollywood Screenplay]] (.hss)
* Movie Magic
** [[ScreenWriter]] (.scw)
** [[Scheduling Export File]] (.sex)
* [[Movie Master]] [https://www.vice.com/en/article/wxdeay/the-dune-screenplay-was-written-in-ms-dos 1]
* [[Open Screenplay]] (.xml)
* [[Scriptware]] (.scr)

==Indexing==
* [[Cindex]]

== Other ==
* [[ACL]]
* [[CCF]]
* [[Computable Document Format]] (.cdf)
* [[DBT]]
* [[EGT]]
* [[FDX]]
* [[FTM]]
* [[FTX]]
* [[IBM Storyboard Text Maker Document]]
* [[MBP]]
* [[Most]]
* [[Notability]]
* [[OBD]]
* [[ODM]]
* [[OLE 1.0 object]]
* [[OMM]]
* [[OTT]]
* [[PAP]]
* [[PaperLess MicroViewer]]
* [[PDAX]]
* [[Photoshop Text Engine Data]]
* [[PowerBI]] (.pbix)
* [[QUOX]]
* [[RIFF STYL]]
* [[RPT]]
* [[SHS]]
* [[SNP]]
* Tableau
** [[Tableau WorkBook]] (.twb, .twbx)
** [[Tableau Bookmarks]] (.tbm)
** [[Tableau Data Source]] (.tds, .tdsx)
** [[Tableau Data Extract]] (.hyper, .tde)
** [[Tableau Flow File]] (.tfl, .tflx)
* [[UOML]]
* [[VIA]]
* [[WRD]]
* [[WRF]]

See also [[Markup]]

== Links ==
* [http://me.veekun.com/blog/2013/01/09/cvs-and-file-extensions/ CVs and File Extensions]
* [http://forums.xkcd.com/viewtopic.php?f=7&t=107195 Trustworthiness of Information by File Extension] (xkcd comic with discussion thread)
* [http://crookedtimber.org/2011/07/30/text-editors-in-the-lord-of-the-rings/ Text editors in ''Lord of the Rings'']
* [http://standards.data.gov.uk/proposal/sharing-collaborating-government-documents Sharing or collaborating with government documents] (UK government proposal)
* [http://lifehacker.com/four-skills-that-will-turn-you-into-a-spreadsheet-ninj-1525058930 Four Skills That Will Turn You Into a Spreadsheet Ninja]
* [http://documentfreedom.org/en/ Document Freedom Day: Celebrating information accessibility and raising awareness of Open Standards.]
* [http://www.flax.co.uk/blog/2013/11/01/g-cloud-and-open-file-formats-a-cautionary-tale/ G-Cloud and open file formats, a cautionary tale]
* [http://www.msnbc.com/rachel-maddow-show/watch/redaction-rules-how-best-to-keep-the-secrets-258076739607 Redaction rules: How best to keep the secrets]
* [http://qanda.digipres.org//49/a-tool-to-detect-encrypted-office-documents Testing for encrypted Office documents]
* [http://johnmacfarlane.net/pandoc/ Pandoc: Document format conversion swiss-army knife]
* [http://givemetext.okfnlabs.org/ Give Me Text: online converter of various document formats to plain text]
* [http://andybrandt531.com/2015/08/writers-guide-to-word-processing-file-formats/ The Writer's Guide to Word Processing File Formats]
* [http://www.documentliberation.org/ Document Liberation Project]
* [https://archive.org/details/businesscase The Business Case: Office software runnable in-browser at Internet Archive]
* [[Wikipedia:Indexing_Software| Indexing Software : Wikipedia]]

[[Category:Desktop Publishing]]
[[Category:Presentation]]
[[Category:Spreadsheet]]
[[Category:Word Processor]]

Category:File formats with extension .ags

2026-05-03T17:31:40Z

Dan Tobias: Created page with "A"

[[Category:File formats by extension|A]]

Filesystem

2026-03-18T23:05:06Z

Dan Tobias: /* Links */

{{FormatInfo
|formattype=electronic
|thiscat=Filesystem
|image=Office Supplies File Cabinet 02.png
}}
'''Filesystems''' are [[Electronic_File_Formats|Electronic Formats]] that are a prerequisite to being able to read any [[file]] off a digital medium — you have to be able to mount the filesystem, and thus read it, in order to be able to read a file.

== Single-system filesystems ==
(How files are organized on one system, device, or medium, such as a disk, tape, or flash memory; see next category for networked and cloud filesystems. Of course, any filesystem can be made available on a network to remote devices, but these are the native filesystems present on the storage device/medium itself.)

* [[+D filesystem]] (Sinclair, SAM Coupé)
* [[Acer Fast Filesystem]] (SCO OpenServer)
* [[ADFS]] (Acorn MOS, RISC OS)
* [[AdvFS]] (Advanced File System, Digital/Tru64 Unix)
* [[Ami-FileSafe]] (AFS, Amiga)
* [[APF Imagination Machine disk file system]]
* [[Apple DOS file system]] (Apple II; see also ProDOS below)
* [[Apple File System]] (APFS) (2017 system for Apple devices)
* [[Atari File Management Subsystem]] (FMS: Atari 400/800)
* [[AtheOS File System]] (AtheOS/Syllable)
* [[BetrFS]]
* [[BFS]] (BeOS)
* [[Btrfs]] (Linux)
* [[CBMFS]] (Commodore 64, PET, etc.; 5.25" disks)
** [[Commodore 1581 filesystem]] (3.5" disks)
** [[GEOS VLIR]] (GEOS Variable Length Index Record )
** [[CMDFS]] (CBMFS extension by Creative Micro Designs)
* [[Compucolor file system]]
* [[CMS filesystem]] (IBM mainframe z/VM operating system, formerly known as VM/CMS)
* [[CP/M file system]]
* [[DDFS]] (Data Domain File System)
* [[DTFS]] (Desktop File System, [[SCO OpenServer]])
* [[EFS]] (Extent File System, SGI IRIX. Replaced by [[XFS]])
* [[EOS file system (Coleco)]] (Coleco ADAM "data pack" tape drives and disks)
* [[ext]] (developed for Linux, previously used MINIX fs)
* [[ext2]], [[ext3]], [[ext4]] (these are all just variants of each other)
* [[F2FS]], (Flash Friendly Filesystem)
* [[FAT]]
** [[FAT8]]
** [[FAT12]]
** [[FAT16]]
** [[FAT32]]
** [[exFAT]] (Microsoft, for flash memory)
* [[FFS]] (Amiga Fast File System)
* [[Files-11]] (VMS)
* [[Firmware File System]]
* [[Fossil]] (Plan 9)
* [[HAMMER]] (DragonflyBSD)
** [[HAMMER2]] (successor to HAMMER)
* [[HFS]] (MacOS)
* [[HFS+]]
* [[HFS (IBM)]] (IBM mainframe Unix filesystem, not to be confused with Apple HFS)
* [[High Sierra]]
* [[HPFS]] (OS/2 native file system)
* [[iPod Filesystem]]
* [[ISO 9660]] (optical discs)
* [[JFFS]]
** [[JFFS2]]
* [[LanyFS]] (Lanyard Filesystem)
* [[Linear Tape File System]] (LTFS)
* [[LogFS]]
* [[MDR (Floppy Disk)|MDR]] (audio instrument format close to MSDOS)
* [[MFS]] (ancient Macintosh filesystem)
* [[MINIX file system]]
* [[NILFS]] (and NILFS2)
* [[North Star DOS file system]]
* [[NOVA (filesystem)|NOVA]]
* [[NTFS]]
* [[OFS]] (Amiga Old File System)
* [[PFS]] (Professional File System, Amiga)
* [[PRAMFS]] (Persistent & Protected RAM File-System)
* [[ProDOS file system]] (Apple II) (also used in Apple III SOS)
* [[QFS]]
* [[ReFS]] (Microsoft's new FS- Resilient Filesystem, on Windows 8 Server)
* [[ReiserFS]]
** [[Reiser4]]
* [[SDFS]] (OpenDedup deduplication based filesystem)
* [[securefs]]
* [[SFS (Amiga)|SFS]] (Smart File System, Amiga)
* [[Sinclair QL filesystem]]
* [[SkyFS]] (SkyOS)
* [[TFS]]
* [[TI-99/4A file system]]
* [[TR-DOS filesystem]] (ZX Spectrum)
* [[TRSDOS file system]] (Tandy)
* [[UBIFS]]
* [[UCSD p-System Filesystem]] (UCSD Pascal)
* [[UFS]] (Unix File System, Solaris and BSD)
** [[UFS2]]
* [[Universal Disk Format]] (UDF) (optical discs)
* [[VMUFAT]] (Filesystem for Dreamcast VMU units)
* [[VSAM]] (Virtual Storage Access Method – not a filesystem per se, runs on top of IBM's VTOC filesystem)
* [[VTOC]] (Native filesystem of the IBM z/OS aka OS/390 aka MVS and z/VM aka DOS/VSE mainframe operating systems)
* [[VxFS]] (VERITAS File System)
* [[WAFL]] (NetApp's commercial file system)
* [[WBFS]]
* [[Xiafs]] (Linux, dropped in favour of ext2)
* [[XFS]] (SGI)
* [[YAFFS]]
* [[ZFS]] (Sun)
* [[ZFS (IBM)]] (IBM mainframe Unix filesystem, not to be confused with Sun's ZFS)

== Compressed filesystems ==
(Filesystems and related topics whose main purpose is [[compression]]. Not all filesystems that support compression are listed here.)

* [[cramfs]]
* [[Cromfs]]
* [[DWARFS]]
* [[Isofs transparent compression]]
* [[Squashfs]]
* [[zisofs]]
* [[EROFS]]

See also [[Compression#Disk compression]] and [[Compression#Transparent file compression]].

== Networked and cloud filesystems ==
(Used to make files available to/from multiple systems over a local or wide area network, including "on the cloud" via the Internet; systems access files through a protocol or API. The low-level storage details, usually concealed from end users and even most developers, may be within one or more of the single-device filesystems above, and the networked/cloud filesystem is generally defined independently of such details and might have very different characteristics and rules as to how the files are named, addressed, and structured.)

* [[Amazon S3]]
* [[Andrew File System]] (Carnegie Mellon University)
* [[Ceph]]
* [[Elastic File System]] (AWS)
* [[EOS file system (CERN)]] (open-source file system used at CERN)
* [[Filecoin]] (a cryptocurrency and file system)
* [[Google Drive]]
* [[Google File System]]
* [[Hadoop Distributed File System]] (HDFS)
* [[IPFS]]
* [[Keybase filesystem]]
* [[Longaccess]]
* [[MEGA file system]]
* [[NetWare File System]] (Novell NetWare, replaced by [[NSS]])
* [[NFS]] (Unix network filesystem protocol)
* [[NSS]] (Novell Storage Services)
* [[OneDrive]] (Microsoft)
* [[OpenStack Swift]]
* [[Permacoin]] (also a [[currency]])
* [[POHMELFS]] (distributed Linux filesystem)
* [[SDFS]] (OpenDedup deduplication based filesystem)
* [[SFS]] (SyncFS)
* [[SMB]] (Server Message Block, a protocol for a networked filesystem)
* [[Storj]] (another currency/filesystem scheme)
* [[WebDAV]] (network filesystem implemented as extensions to HTTP)
* [[XtreemFS]], (Linux, distributed file system)

== Virtual filesystems ==
* [[%clay vane]] (Urbit)
* [[AVFS]]
* [[FUSE]]
* [[GnomeVFS]]
** [[GVfs (GNOME)]]
* [[Virtual File System for Git]] (was GVFS)

== Other / Misc. ==
* [[πfs]]
* [[BrowserFS]]
* [[Magikfs]]
* [[ProFS]]
* [[RockFAT]]
* [[SAFS]]
* [[Stegfs]]

== File content signature ==
(used to match files to a hash table or similar system in order to detect duplicates, help find specific files when their exact
location is unknown, handle distributed networked filesystems, etc. See also [[Error detection and correction]].)

* [[FWKCS]]

== File lists ==
* [[Everything File List]] (.efu)

== Format details, etc. ==
* [[AAIP]]
* [[Android File Structure]]
* [[AppleDouble]]
* [[Apple ISO 9660 extensions]]
* [[Apple Partition Map]]
* [[AppleSingle]]
* [[ARCHIMEDES ISO 9660 extension]]
* [[Auto-created directories]]
* [[desktop.ini]] (Windows)
* [[Desktop Services Store]] (Mac OS X)
* [[DMF (Distribution Media Format)]]
* [[DOS/Windows file attributes]]
* [[EA DATA. SF]]
* [[El Torito]]
* [[GUID Partition Table]]
* [[Joliet]]
* [[Master Boot Record]] (MBR)
* [[RAID]]
* [[Resource Fork]] (MacOS)
* [[Rock Ridge]]
* [[System Use Sharing Protocol]] (SUSP)
* [[TRANS.TBL]]
* [[VFAT]]
* [[XDF (Extended Density Format)]]

== Links ==
* [[Wikipedia:List of file systems|List of file systems (Wikipedia)]]
* [http://www.dreamhost.com/dreamscape/2013/09/12/cloud-storage-architectures/ Cloud Storage Architectures]
* [https://www.usenix.org/legacy/event/hotos09/tech/full_papers/seltzer/seltzer.pdf Hierarchical File Systems are Dead]
* [http://qanda.digipres.org/176/filesystem-checksums-value-digital-preservation-context Do filesystem-based checksums add value in a digital preservation context?]
* [http://lists.gnu.org/archive/html/coreutils/2014-08/msg00012.html My experience with using cp to copy a lot of files (432 millions, 39 TB)]
* [https://www.csail.mit.edu/crash_tolerant_data_storage Crash-proof filesystem]
* [http://l-o-c-a-l-h-o-s-t.com/wiki/doku.php?id=localhost:events:rwx:know_your_filesystem Know Your Filesystem]
* [https://danluu.com/file-consistency/ File crash consistency and filesystems are hard]
* [https://github.com/mgree/ffs ffs] for mounting structured data (like JSON) as a file system for interacting with.

Programming Languages

2026-03-14T17:52:33Z

Dan Tobias: /* Programming languages */

{{FormatInfo
|formattype=Languages
|thiscat=Programming Languages
|released=~1950
|image=Babbage difference engine drawing.gif
|caption=Babbage's Difference Engine
}}
'''Programming languages''' are languages expected to be executed (interpreted, compiled, etc.) by a machine in order to perform operations or algorithms. They are distinct from markup languages, which represent the structure of a document rather than specific operations to be performed, though it is possible to combine both in a document (e.g., HTML containing embedded JavaScript, or PHP code which includes HTML). Programming language code is stored as [[source code]] which may be directly interpreted by a machine or compiled or assembled into [[executables]].

== Programming languages ==

* [[ABC (programming language)]]
* [[ActionScript]] (Flash)
** [[ActionScript Byte Code]]
* [[Ada]]
* [[AIR-J]]
* [[ALGOL]]
* [[Anim8or Scripting Language]]
* [[APL]]
* [[AppleScript]]
* [[APT (programming language)|APT]]
* [[Arc (programming language)|Arc]]
* [[Arduino programming language]]
* [[Assembly language]] (.asm, .s) (various versions for different machine architectures)
* [[Aussie++]]
* [[Austral]]
* [[AutoHotkey]]
* [[AutoLISP]]
* [[AWK]]
* [[B]]
* [[BASIC]] (Beginner's All Purpose Symbolic Instruction Code) (.bas) -- See also [[Tokenized BASIC]]
* [[Batch file]] (DOS, Windows, OS/2)
* [[BCPL]]
* [[BLISS]]
* [[Blitz BASIC]]
** [[Blitz3D]]
* [[BlooP, FlooP, and GlooP]]
* [[Bourne shell script]] (.sh)
* [[Brainfuck]]
* [[Breder]]
* [[C]] (.c, .cc, .h)
* [[C Sharp|C#]] (.cs)
* [[C shell script]]
* [[C++]] (.cpp, .cxx)
* [[C+=]]
* [[CakeML]]
* [[CEEMAC]]
* [[CFEngine]]
* [[CHIP-8]]
* [[ChordQL]]
* [[Clipper (programming language)]]
* [[Clojure]]
** [[ClojureScript]]
* [[COBOL]] (COmmon Business-Oriented Language)
* [[CoffeeScript]]
* [[ColdFusion]]
* [[COMAL]]
* [[COMIT]]
* [[COW]]
* [[Coq]]
* [[CORC]] (Cornell Computing Language)
* [[CPL]]
* [[Crystal]]
* [[CUPL]] (Cornell University Programming Language)
* [[Cython (Pyrex)]]
* [[D]]
* [[Dart]] (was Dash)
* [[Dern]]
* [[dBase programming language]]
* [[DogeScript]]
* [[Dylan]]
* [[Elixir]]
* [[Elm]]
* [[Erlang]]
* [[Expect]]
* [[Extended Batch Language]] (EBL)
* [[F Sharp|F#]]
* [[Fantom]]
* [[Fish shell]] (*.fish)
* [[Flare]]
* [[Flow]]
* [[Forth]]
* [[FORTRAN]] (FORmula TRANslation)
* [[FoxPro programming language]]
* [[Free Pascal]]
* [[Fusion (programming language)|Fusion]] (.fu, .ci)
* [[GAMS]] (.gms)
* [[GDL Script]] - scripting language used in ARCHICAD (.gdl)
* [[Gherkin]]/Cucumber
* [[Go]]
* [[Graphics Programming Language]] (GPL) (mid-level language on TI computers)
* [[Groovy]]
* [[HamsterSpeak]]
* [[Haskell]]
* [[Haxe]]
* [[High Level Shading Language]] (HLSL)
* [[Hoon]]
* [[Hopscotch]]
* [[HyperTalk]]
* [[IDL]]
* [[INTERCAL]]
* [[Ioke]]
* [[Java]] (.j, .jav, .java)
** [[Java bytecode]] (JVM)
* [[JavaScript]] (JScript, [[ECMAScript]]) (.js)
** [[Node.js]]
** [[React]]
** [[TypeScript]]
* [[JCL]] (Job Control Language; used on IBM mainframes)
* [[JOSS]]
* [[JSONata]] [http://jsonata.org/]
* [[JSX]]
* [[Julia]]
* [[Kotlin]]
* [[LISP]]
* [[LiveScript]]
* [[Logo]]
* [[LOLCODE]]
* [[Lollipop]]
* [[Lua]]
* [[Lurk]]
* [[Machine language]] (various versions for different machine architectures)
* [[MATLAB script file]] (.m)
* [[MDL (programming language)|MDL]] (.mud)
* [[Microcode]]
* [[mIRC scripting language]]
* [[ML]]
* [[MUMPS]] (Massachusetts General Hospital Utility Multi-Programming System)
* [[Music Macro Language]] (.mmi)
* [[Nim]]
* [[Nock]]
* [[NetLogo]]
* [[Object Pascal]] (including Delphi)
* [[Objective-C]] (.m, .h) (used in Mac and iOS development)
* [[OCaml]]
* [[OpenGL Shading Language]] (GLSL)
* [[P (Microsoft programming language)|P]] (Microsoft)
* [[Pascal]] (.pas)
* [[Pawn]]
* [[Perl]] (.pl, .pm)
* [[PHP]] (.php)
* [[Piet]]
* [[PikaScript]]
* [[PILOT]]
* [[Pixie (programming language)|Pixie]]
* [[Pixilang]] (.pixi)
* [[PL/I]]
* [[PLASMA]]
* [[PostScript]]
* [[PowerShell]]
* [[Processing]]
* [[Programmable Command Language]] (PCL), for TOPS-20
* [[Prolog]]
* [[Pyramid]]
* [[Python]] (.py, .pyc, .pyo, .pyd)
* [[QML]]
* [[Q Sharp|Q#]]
* [[Quorum]]
* [[R]]
* [[Racket]]
* [[Raku]]
* [[Rant]]
* [[Ratfor]]
* [[Redcode]]
* [[RenderWare object]] (.rwx)
* [[RobotWar]]
* [[RPG]]/RPGLE/RPG IV/RPG ILE (.rpgle, .sqlrpgle)
* [[Ruby]]
* [[Rust]]
* [[S]]
* [[SAIL]]
* [[Scala]]
* [[Scheme]]
* [[SCODL]]
* [[Scratch]]
* [[Server Side Includes]]
* [[Shen]]
* [[Sikuli]]
* [[Skip]]
* [[Smalltalk]]
* [[SNOBOL]]
* [[Solidity]]
* [[Squiggle]]
* [[Squirrel]]
* [[Standard ML]]
* [[StarLogo]]
* [[Swift]] (Apple) (.swift)
* [[Swift (parallel scripting)]]
* [[SYSDOOM]]
* [[Tabloid (programming language)|Tabloid]]
* [[Tcl]]
* [[TECO]]
* [[TRAC programming language]]
* [[TUTOR]]
* [[TypeScript]]
* [[Verilog]]
* [[vim script]]
* [[Visual Basic]]
* [[VBScript]]
* [[Vue.js]] component files
* [[WaveGL]]
* [[WebAssembly]]
* [[Wenyan]] (文言)
* [[Windows Script File]]
* [[WMLScript]]
* [[Wolfram Language]]
* [[Wuffs]]
* [[ZAP]]
* [[Z-code]]
* [[ZIL]]

== Logical assertion languages ==
* [[SNARK]]

== Query languages ==
* [[Fauna Query Language]] (FQL)
* [[PRQL]]
* [[SPARQL]]
* [[SQL]]

== Templates, macros, preprocessors, etc. ==
* [[Cascading Style Sheets|CSS]]
* [[doT]]
* [[DSSSL]]
* [[Jinja]]
* [[Jsonnet]] [https://jsonnet.org/]
* [[Liquid]] (.liquid)
* [[M4]] (.m4)
* [[Pug]]
* [[Smarty]]
* [[XSL]]
* [[XSLT]]

For additional macro formats, especially binary formats, see [[Executables#Macros or automated scripting]].

See also [[Web#Scripts/Applets/Plug-Ins/Frameworks/APIs/Templating]].

See [[Wikipedia:Category:Template engines]] for another list of template systems.

== Other/Miscellaneous ==
* [[Nomyx language]]
* [[Programmable calculators]]

== See also ==
* [[Development]]
* [[Executables]]
* [[Interactive Fiction]] engines often use specialized programming languages for game development.
* [[Resources]]
* [[Source code]]

== External links ==
===Resources===
* A comprehensive list of over 2000 programming languages and a small sample programs for each of them is available [http://www.99-bottles-of-beer.net/ here]
* [http://rosettacode.org/ Rosetta Code] attempts to present solutions to the same task in different programming languages.
* [http://storify.com/carlzimmer/coding-for-middle-school-girls?utm_content=storify-pingback&utm_source=t.co&utm_campaign=&awesm=sfy.co_s2LP&utm_medium=sfy.co-twitter Coding for middle-school girls] (tips on introducing them to programming)
* [http://langpop.corger.nl/ Programming language popularity chart (based on Github and StackOverflow activity)]
* [http://hivelogic.com/articles/top-10-programming-fonts Top 10 programming fonts]
* [http://www.integralwebsolutions.co.za/Blog/EntryId/901/What-s-The-Most-Popular-Programming-Language.aspx What’s The Most Popular Programming Language?]
* [http://lifehacker.com/which-programming-language-should-i-learn-first-1477153665 Which programming language should I learn first?]
* [http://exple.tive.org/blarg/2013/10/22/citation-needed/ Why array indices start at zero; historical info]
* [http://www.codecademy.com/ Code Academy: learn to code interactively online]
* [http://howto.cnet.com/8301-11310_39-57615356-285/best-free-sites-for-learning-how-to-write-code/ Best free sites for learning how to write code]

=== Commentary ===
* [http://boingboing.net/2013/02/27/what-most-schools-should-reall.html Why you should learn to program]
* [http://mentalfloss.com/article/53160/meet-refrigerator-ladies-who-programmed-eniac Meet the 'Refrigerator Ladies' Who Programmed the ENIAC]
* [http://devblog.avdi.org/2014/01/31/the-moderately-enthusiastic-programmer/ The Moderately Enthusiastic Programmer]
* [http://techcrunch.com/2013/10/10/my-experience-as-a-fourth-grade-hacker/ My Experience As A Fourth Grade Hacker]
* [https://medium.com/learning-to-code/565fc9dcb329 Things I Wish Someone Had Told Me When I Was Learning How to Code]
* [http://michaelochurch.wordpress.com/2012/01/15/the-problem-with-programming-language/ A problem with the term, programming “language”]
* [http://animalnewyork.com/2014/artists-notebook-ramsey-nasser/ Discussion of creating programming languages in Arabic]
* [http://www.viva64.com/en/b/0260/ The Last Line Effect]
* [http://bost.ocks.org/mike/algorithms/ Visualizing algorithms]
* [http://www.playthepast.org/?p=4982 Excavating Code: An Archaeological Record of Software Development]
* [https://medium.com/towards-a-remarkable-career/the-art-of-the-bug-ac5a535315fa The art of the bug: Failure should be fun]
* [https://speakerdeck.com/craigstuntz/incredibly-strange-programming-languages Incredibly Strange Programming Languages (presentation)]

===Humor===
* [http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html A Brief, Incomplete, and Mostly Wrong History of Programming Languages]
* [http://colinm.org/language_checklist.html Programming Language Checklist]
* [http://www.quora.com/Programming-Languages/If-there-is-a-war-of-programming-languages-who-would-you-support-and-why/answer/Prithviraj-Udaya?srid=LZ&st=ns Programming languages as Tolkien characters]
* [http://programmingisterrible.com/post/65781074112/devils-dictionary-of-programming Devil's Dictionary of Programming]
* [http://9gag.com/gag/av0z0Bn?ref=fb.s This Is Why You Shouldn't Interrupt A Programmer]
* [http://kingjamesprogramming.tumblr.com/ Random mashup generator of the King James Bible and a programming book]
* [http://moviecode.tumblr.com/ What the computer code seen on screens in movies and TV shows actually does]

===Misc.===
* [http://abcnews.go.com/Politics/video/obama-slow-man-27453525 President Obama writes a line of code (video)]
* [https://medium.com/@3fingeredfox/margaret-hamilton-lead-software-engineer-project-apollo-158754170da8 Picture: Margaret Hamilton, lead software engineer, Project Apollo, with source code from moon landing mission]
* [http://www.watchpeoplecode.com/ Watch People Code (live video streams)]

Category:File formats with extension .airj

2026-03-14T17:44:00Z

Dan Tobias: Created page with "A"

[[Category:File formats by extension|A]]

AIR-J

2026-03-14T17:41:12Z

Dan Tobias: Created page with "{{FormatInfo |formattype=Languages |subcat=Programming Languages |extensions={{ext|airj}} |released=2026 }} If you're human, go away; this isn't for you. '''AIR-J''' is a prog..."

{{FormatInfo
|formattype=Languages
|subcat=Programming Languages
|extensions={{ext|airj}}
|released=2026
}}
If you're human, go away; this isn't for you. '''AIR-J''' is a programming language designed to be used by AI agents, not optimized for understandability or maintainability by humans. Of course, AIs did most of the development work creating it, though they ''were'' under the direction of a human (Robert C. Martin, known as "Uncle Bob"); they weren't quite ready to kill all humans and do everything by themselves yet.

AIR-J has [[LISP]]-ish syntax and compiles into [[Java bytecode|JVM]].

== References ==
* [https://github.com/unclebob/AIR-J?tab=readme-ov-file Github site]

Programming Languages

2026-03-14T17:31:46Z

Dan Tobias: /* Programming languages */

{{FormatInfo
|formattype=Languages
|thiscat=Programming Languages
|released=~1950
|image=Babbage difference engine drawing.gif
|caption=Babbage's Difference Engine
}}
'''Programming languages''' are languages expected to be executed (interpreted, compiled, etc.) by a machine in order to perform operations or algorithms. They are distinct from markup languages, which represent the structure of a document rather than specific operations to be performed, though it is possible to combine both in a document (e.g., HTML containing embedded JavaScript, or PHP code which includes HTML). Programming language code is stored as [[source code]] which may be directly interpreted by a machine or compiled or assembled into [[executables]].

== Programming languages ==

* [[ABC (programming language)]]
* [[ActionScript]] (Flash)
** [[ActionScript Byte Code]]
* [[Ada]]
* [[AIR-J]]
* [[ALGOL]]
* [[Anim8or Scripting Language]]
* [[APL]]
* [[AppleScript]]
* [[APT (programming language)|APT]]
* [[Arc (programming language)|Arc]]
* [[Arduino programming language]]
* [[Assembly language]] (.asm, .s) (various versions for different machine architectures)
* [[Aussie++]]
* [[Austral]]
* [[AutoHotkey]]
* [[AutoLISP]]
* [[AWK]]
* [[B]]
* [[BASIC]] (Beginner's All Purpose Symbolic Instruction Code) (.bas) -- See also [[Tokenized BASIC]]
* [[Batch file]] (DOS, Windows, OS/2)
* [[BCPL]]
* [[BLISS]]
* [[Blitz BASIC]]
** [[Blitz3D]]
* [[BlooP, FlooP, and GlooP]]
* [[Bourne shell script]] (.sh)
* [[Brainfuck]]
* [[Breder]]
* [[C]] (.c, .cc, .h)
* [[C Sharp|C#]] (.cs)
* [[C shell script]]
* [[C++]] (.cpp, .cxx)
* [[C+=]]
* [[CakeML]]
* [[CEEMAC]]
* [[CFEngine]]
* [[CHIP-8]]
* [[ChordQL]]
* [[Clipper (programming language)]]
* [[Clojure]]
** [[ClojureScript]]
* [[COBOL]] (COmmon Business-Oriented Language)
* [[CoffeeScript]]
* [[ColdFusion]]
* [[COMAL]]
* [[COMIT]]
* [[COW]]
* [[Coq]]
* [[CORC]] (Cornell Computing Language)
* [[CPL]]
* [[Crystal]]
* [[CUPL]] (Cornell University Programming Language)
* [[Cython (Pyrex)]]
* [[D]]
* [[Dart]] (was Dash)
* [[Dern]]
* [[dBase programming language]]
* [[DogeScript]]
* [[Dylan]]
* [[Elixir]]
* [[Elm]]
* [[Erlang]]
* [[Expect]]
* [[Extended Batch Language]] (EBL)
* [[F Sharp|F#]]
* [[Fantom]]
* [[Fish shell]] (*.fish)
* [[Flare]]
* [[Flow]]
* [[Forth]]
* [[FORTRAN]] (FORmula TRANslation)
* [[FoxPro programming language]]
* [[Free Pascal]]
* [[Fusion (programming language)|Fusion]] (.fu, .ci)
* [[GAMS]] (.gms)
* [[GDL Script]] - scripting language used in ARCHICAD (.gdl)
* [[Gherkin]]/Cucumber
* [[Go]]
* [[Graphics Programming Language]] (GPL) (mid-level language on TI computers)
* [[Groovy]]
* [[HamsterSpeak]]
* [[Haskell]]
* [[Haxe]]
* [[High Level Shading Language]] (HLSL)
* [[Hoon]]
* [[Hopscotch]]
* [[HyperTalk]]
* [[IDL]]
* [[INTERCAL]]
* [[Ioke]]
* [[Java]] (.j, .jav, .java)
* [[JavaScript]] (JScript, [[ECMAScript]]) (.js)
** [[Node.js]]
** [[React]]
** [[TypeScript]]
* [[JCL]] (Job Control Language; used on IBM mainframes)
* [[JOSS]]
* [[JSONata]] [http://jsonata.org/]
* [[JSX]]
* [[Julia]]
* [[Kotlin]]
* [[LISP]]
* [[LiveScript]]
* [[Logo]]
* [[LOLCODE]]
* [[Lollipop]]
* [[Lua]]
* [[Lurk]]
* [[Machine language]] (various versions for different machine architectures)
* [[MATLAB script file]] (.m)
* [[MDL (programming language)|MDL]] (.mud)
* [[Microcode]]
* [[mIRC scripting language]]
* [[ML]]
* [[MUMPS]] (Massachusetts General Hospital Utility Multi-Programming System)
* [[Music Macro Language]] (.mmi)
* [[Nim]]
* [[Nock]]
* [[NetLogo]]
* [[Object Pascal]] (including Delphi)
* [[Objective-C]] (.m, .h) (used in Mac and iOS development)
* [[OCaml]]
* [[OpenGL Shading Language]] (GLSL)
* [[P (Microsoft programming language)|P]] (Microsoft)
* [[Pascal]] (.pas)
* [[Pawn]]
* [[Perl]] (.pl, .pm)
* [[PHP]] (.php)
* [[Piet]]
* [[PikaScript]]
* [[PILOT]]
* [[Pixie (programming language)|Pixie]]
* [[Pixilang]] (.pixi)
* [[PL/I]]
* [[PLASMA]]
* [[PostScript]]
* [[PowerShell]]
* [[Processing]]
* [[Programmable Command Language]] (PCL), for TOPS-20
* [[Prolog]]
* [[Pyramid]]
* [[Python]] (.py, .pyc, .pyo, .pyd)
* [[QML]]
* [[Q Sharp|Q#]]
* [[Quorum]]
* [[R]]
* [[Racket]]
* [[Raku]]
* [[Rant]]
* [[Ratfor]]
* [[Redcode]]
* [[RenderWare object]] (.rwx)
* [[RobotWar]]
* [[RPG]]/RPGLE/RPG IV/RPG ILE (.rpgle, .sqlrpgle)
* [[Ruby]]
* [[Rust]]
* [[S]]
* [[SAIL]]
* [[Scala]]
* [[Scheme]]
* [[SCODL]]
* [[Scratch]]
* [[Server Side Includes]]
* [[Shen]]
* [[Sikuli]]
* [[Skip]]
* [[Smalltalk]]
* [[SNOBOL]]
* [[Solidity]]
* [[Squiggle]]
* [[Squirrel]]
* [[Standard ML]]
* [[StarLogo]]
* [[Swift]] (Apple) (.swift)
* [[Swift (parallel scripting)]]
* [[SYSDOOM]]
* [[Tabloid (programming language)|Tabloid]]
* [[Tcl]]
* [[TECO]]
* [[TRAC programming language]]
* [[TUTOR]]
* [[TypeScript]]
* [[Verilog]]
* [[vim script]]
* [[Visual Basic]]
* [[VBScript]]
* [[Vue.js]] component files
* [[WaveGL]]
* [[WebAssembly]]
* [[Wenyan]] (文言)
* [[Windows Script File]]
* [[WMLScript]]
* [[Wolfram Language]]
* [[Wuffs]]
* [[ZAP]]
* [[Z-code]]
* [[ZIL]]

== Logical assertion languages ==
* [[SNARK]]

== Query languages ==
* [[Fauna Query Language]] (FQL)
* [[PRQL]]
* [[SPARQL]]
* [[SQL]]

== Templates, macros, preprocessors, etc. ==
* [[Cascading Style Sheets|CSS]]
* [[doT]]
* [[DSSSL]]
* [[Jinja]]
* [[Jsonnet]] [https://jsonnet.org/]
* [[Liquid]] (.liquid)
* [[M4]] (.m4)
* [[Pug]]
* [[Smarty]]
* [[XSL]]
* [[XSLT]]

For additional macro formats, especially binary formats, see [[Executables#Macros or automated scripting]].

See also [[Web#Scripts/Applets/Plug-Ins/Frameworks/APIs/Templating]].

See [[Wikipedia:Category:Template engines]] for another list of template systems.

== Other/Miscellaneous ==
* [[Nomyx language]]
* [[Programmable calculators]]

== See also ==
* [[Development]]
* [[Executables]]
* [[Interactive Fiction]] engines often use specialized programming languages for game development.
* [[Resources]]
* [[Source code]]

== External links ==
===Resources===
* A comprehensive list of over 2000 programming languages and a small sample programs for each of them is available [http://www.99-bottles-of-beer.net/ here]
* [http://rosettacode.org/ Rosetta Code] attempts to present solutions to the same task in different programming languages.
* [http://storify.com/carlzimmer/coding-for-middle-school-girls?utm_content=storify-pingback&utm_source=t.co&utm_campaign=&awesm=sfy.co_s2LP&utm_medium=sfy.co-twitter Coding for middle-school girls] (tips on introducing them to programming)
* [http://langpop.corger.nl/ Programming language popularity chart (based on Github and StackOverflow activity)]
* [http://hivelogic.com/articles/top-10-programming-fonts Top 10 programming fonts]
* [http://www.integralwebsolutions.co.za/Blog/EntryId/901/What-s-The-Most-Popular-Programming-Language.aspx What’s The Most Popular Programming Language?]
* [http://lifehacker.com/which-programming-language-should-i-learn-first-1477153665 Which programming language should I learn first?]
* [http://exple.tive.org/blarg/2013/10/22/citation-needed/ Why array indices start at zero; historical info]
* [http://www.codecademy.com/ Code Academy: learn to code interactively online]
* [http://howto.cnet.com/8301-11310_39-57615356-285/best-free-sites-for-learning-how-to-write-code/ Best free sites for learning how to write code]

=== Commentary ===
* [http://boingboing.net/2013/02/27/what-most-schools-should-reall.html Why you should learn to program]
* [http://mentalfloss.com/article/53160/meet-refrigerator-ladies-who-programmed-eniac Meet the 'Refrigerator Ladies' Who Programmed the ENIAC]
* [http://devblog.avdi.org/2014/01/31/the-moderately-enthusiastic-programmer/ The Moderately Enthusiastic Programmer]
* [http://techcrunch.com/2013/10/10/my-experience-as-a-fourth-grade-hacker/ My Experience As A Fourth Grade Hacker]
* [https://medium.com/learning-to-code/565fc9dcb329 Things I Wish Someone Had Told Me When I Was Learning How to Code]
* [http://michaelochurch.wordpress.com/2012/01/15/the-problem-with-programming-language/ A problem with the term, programming “language”]
* [http://animalnewyork.com/2014/artists-notebook-ramsey-nasser/ Discussion of creating programming languages in Arabic]
* [http://www.viva64.com/en/b/0260/ The Last Line Effect]
* [http://bost.ocks.org/mike/algorithms/ Visualizing algorithms]
* [http://www.playthepast.org/?p=4982 Excavating Code: An Archaeological Record of Software Development]
* [https://medium.com/towards-a-remarkable-career/the-art-of-the-bug-ac5a535315fa The art of the bug: Failure should be fun]
* [https://speakerdeck.com/craigstuntz/incredibly-strange-programming-languages Incredibly Strange Programming Languages (presentation)]

===Humor===
* [http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html A Brief, Incomplete, and Mostly Wrong History of Programming Languages]
* [http://colinm.org/language_checklist.html Programming Language Checklist]
* [http://www.quora.com/Programming-Languages/If-there-is-a-war-of-programming-languages-who-would-you-support-and-why/answer/Prithviraj-Udaya?srid=LZ&st=ns Programming languages as Tolkien characters]
* [http://programmingisterrible.com/post/65781074112/devils-dictionary-of-programming Devil's Dictionary of Programming]
* [http://9gag.com/gag/av0z0Bn?ref=fb.s This Is Why You Shouldn't Interrupt A Programmer]
* [http://kingjamesprogramming.tumblr.com/ Random mashup generator of the King James Bible and a programming book]
* [http://moviecode.tumblr.com/ What the computer code seen on screens in movies and TV shows actually does]

===Misc.===
* [http://abcnews.go.com/Politics/video/obama-slow-man-27453525 President Obama writes a line of code (video)]
* [https://medium.com/@3fingeredfox/margaret-hamilton-lead-software-engineer-project-apollo-158754170da8 Picture: Margaret Hamilton, lead software engineer, Project Apollo, with source code from moon landing mission]
* [http://www.watchpeoplecode.com/ Watch People Code (live video streams)]

URL

2026-03-06T19:02:54Z

Dan Tobias: /* Example */

{{FormatInfo
|subcat=Web
|released=1990
|wikidata={{wikidata|Q42253}}, {{wikidata|Q61694}}, {{wikidata|Q424583}}
}}

A '''URL''' (Uniform Resource Locator) is an address of a resource as used on the World Wide Web, and is one of Tim Berners Lee's original three pillars of the Web along with [[HTTP]] and [[HTML]]. Technically speaking, a URL is just one category of such addresses, a subset of URI (Uniform Resource Identifier) and parallel to URN (Uniform Resource Name), but such distinctions aren't always consistently maintained even by technical people, and URL has entered the popular language in a way those other terms have not.

Over time, the precise definitions of the various terms for Web-related addresses have changed and been argued extensively about by technical people, and some more have been added: an IRI (Internationalized Resource Identifier) is like a URI, but extended to allow non-[[ASCII]] characters so that languages other than English can be supported. However, the newest HTML 5 standards drafts choose to take a more pragmatic approach of just using "URL" to refer to anything that a browser is expected to resolve as an address, as one of many "willful violations" of earlier tech specs they did there. (The "techie" equivalent of social conservatives may consider this to be "defining deviancy down" and hence an "abomination".)

Use of URLs (and URIs, etc.) is not limited to the Web, as there are a number of other technical usages such as in defining namespaces for file formats (e.g., [[XML]]), and in identifying even non-Web-accessible objects for the purpose of expressing taxonomic relations. In less-technical usage, URLs turn up in all sorts of places like TV commercials, billboards, and on the side of vans, but often with the protocol portion left off when [[HTTP]] (or its secure variety, HTTPS, which eventually became the most commonly used protocol) is used. These days most browsers don't even show the "https://" part in the address bar, though it's still officially part of the URL.

== Types of identifiers ==

* '''URI''': The official "parent term" for URLs, URNs, and other such identifiers, but limited to [[ASCII]] characters, with anything else needing to be specially encoded. Even within the ASCII range, some characters such as the space are prohibited, reserved, or designated to be used only for specific syntactic purposes, with percent encoding necessary for all other uses.

* '''IRI''': The internationalized version of URIs, with more liberal rules about what characters in the entire [[Unicode]] range may be included. This allows text in non-English languages to be included without messy encoding, though various transfer protocols may still require the entire string to be encoded on transmission to produce an ASCII-based URI. This is really just a different representation of a URI; any IRI may be represented as a URI, with [[percent-encoding]] UTF-8 sequences if it contains non-ASCII characters.

* '''URL''': Technically only the subset of URIs that are "locators", able to be used to retrieve resources because they designate a specific address for them, but in practice the distinction is very fuzzy and usually ignored. Some newer standards such as HTML 5.0 simply follow common non-techie usage and use URL to refer to the whole universe of Web-style addresses (encompassing URIs and IRIs, and anything else a browser can accept as an address even if it fails to comply with any of the standards).

* '''URN''': Uniform Resource Name. Another type of URI which is supposed to provide a stable permanent identifier for a resource which does not include a specific (and changeable) address for it. To resolve a URN, one needs a resolver such as a server or website that stores a table of current locations of items with URNs. Currently the standards call for all URNs to begin with the 'urn:' scheme identifier, and the next item after this is a URN namespace, followed by another colon and the namespace-specific information. Some common naming schemes have been adopted as URNs, such as [[ISBN]]s (International Standard Book Number), which have the format "urn:isbn:1-234567-890". Unfortunately, browsers haven't been quick to implement URN resolvers as standard features, though add-ons can be installed to do it. URNs can also be used to refer to a [[UUID]], and are also used to refer to hashes in [[magnet URI]]s.

== Standard syntax ==

URLs/URIs/etc. always start with a scheme (protocol). (At least, ''absolute'' URLs do; there are also ''relative'' URLs that leave off parts at the beginning because they are construed as being relative to the current URL they are accessed from.) The most common was traditionally [[HTTP]], but more recently the encrypted variant HTTPS became more common; there are many other schemes too, although they are less common. The scheme part ends with a colon (:).

After this, the rest of the URL is scheme-dependent; there are a number of different syntaxes used in different types of URLs. A common syntax, expected by the standards to be used in all schemes with hierarchical path structures, follows the scheme part with a double slash (//) which introduces a host or authority portion (usually a [[domain name]]), which is then followed by another slash and then the full path being addressed, which uses forward slashes to separate hierarchical levels (which may, but needn't, correspond to subdirectories in a [[filesystem]]).

There's a common misconception that URLs always have a double slash after the colon, sometimes causing developers of new schemes to put this in their syntax where the standards don't call for it; it is only supposed to be used if the following element is some sort of "authority" (most commonly the address to connect to) by which a following path is to be interpreted. There are a number of schemes with no such authority, and hence no double slash; for insstance "mailto:".

== data: URLs ==

One scheme, '''data:''', is actually a file format in its own right, since it encodes the entire contents of a file within the URL instead of referencing an external resource as other schemes do.

* [[Wikipedia:Data URI scheme|Wikipedia article on data: URIs]]
* RFC 2397
* [http://dataurl.net/#about Data URL maker]

== Example ==

https://archive.org/upload/?description=I%20finally%20got%20it.%20However%2C%20an%20update%20made%20the%20Home%20Screen%20look%20like%20Jadoo%205%20and%20not%20like%20the%20new%20Home%20Screen%20they%20put%20in.&subject=Jadoo%2CJadooTV%2CJadoo7%2CJadoo%207%2CAndroid%2CAPK%2CAndroid%20Pie%2CAndroid%209%2CAndroid%209.0%2CAndroid%20TV%2CFarsi%2CHindi&creator=JadooTV&date=2021&collection=open_source_software

== See also ==

* [[Magnet URI]]
* [[URL encoding]]

== Official documents ==

* RFC 1738 (early absolute URL standard)
* RFC 1808 (early relative URL standard)
* RFC 2396 (early URI syntax standard)
* RFC 3986 (later URI syntax standard)
* RFC 3987 (IRI standard)
* RFC 4395 (info on registering new URI schemes)
* [http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/ W3C clarification of URIs, URLs, and URNs (2001)]
* [http://www.w3.org/TR/2012/WD-html51-20121217/infrastructure.html#urls HTML 5.1 draft section on URLs] (which intentionally disregards the distinctions in the other documents above)

== Proposed documents ==
* [http://tools.ietf.org/html/draft-kerwin-file-scheme-09 Internet draft for File scheme]

== Official sites ==

* [http://www.w3.org/Addressing/ W3C: Naming and Addressing] (old)
* [http://www.w3.org/standards/webarch/identifiers W3C: Identifiers] (new)
* [http://www.iana.org/assignments/uri-schemes.html IANA list of registered URI schemes]
* [http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml IANA list of URN namespaces]

== Other links ==

* [https://webtips.dan.info/url.html Dan's Web Tips: URLs]
* [http://blog.welldesignedurls.org/ Well Designed URLs Blog]
* [https://www.w3.org/Provider/Style/URI.html Cool URIs don't change (Tim Berners-Lee)]
* [http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx File URIs in Windows]
* [https://offset.skew.org/wiki/URI/File_scheme File URI scheme update project wiki]
* [https://github.com/AGLDWG/TR/wiki/URI-Guidelines-for-publishing-linked-datasets-on-data.gov.au-v0.1 URI Guidelines for publishing Linked Datasets on data.gov.au v0.1]
* [https://www.w3.org/community/blog/2014/09/11/proposed-group-uri-specification-community-group/ Proposed Group: URI Specification Community Group]
* [http://ben.balter.com/2014/10/07/expose-process-through-urls/ If you liked it then you should have put a URL on it]
* [http://blog.webrecorder.io/2015/02/beyond-robust-links-case-for-robust.html Beyond Robust Links: The case for robust urls and an Archival Url standard]
* [https://corner.squareup.com/2015/05/okhttp-2-4.html OkHttp’s New URL Class]
* [https://eager.io/blog/the-history-of-the-url-domain-and-protocol/ History of the URL: Domain, Protocol, and Port]

[[Category:Naming and numbering systems]]

URL

2026-03-06T19:01:46Z

Dan Tobias: /* Standard syntax */

{{FormatInfo
|subcat=Web
|released=1990
|wikidata={{wikidata|Q42253}}, {{wikidata|Q61694}}, {{wikidata|Q424583}}
}}

A '''URL''' (Uniform Resource Locator) is an address of a resource as used on the World Wide Web, and is one of Tim Berners Lee's original three pillars of the Web along with [[HTTP]] and [[HTML]]. Technically speaking, a URL is just one category of such addresses, a subset of URI (Uniform Resource Identifier) and parallel to URN (Uniform Resource Name), but such distinctions aren't always consistently maintained even by technical people, and URL has entered the popular language in a way those other terms have not.

Over time, the precise definitions of the various terms for Web-related addresses have changed and been argued extensively about by technical people, and some more have been added: an IRI (Internationalized Resource Identifier) is like a URI, but extended to allow non-[[ASCII]] characters so that languages other than English can be supported. However, the newest HTML 5 standards drafts choose to take a more pragmatic approach of just using "URL" to refer to anything that a browser is expected to resolve as an address, as one of many "willful violations" of earlier tech specs they did there. (The "techie" equivalent of social conservatives may consider this to be "defining deviancy down" and hence an "abomination".)

Use of URLs (and URIs, etc.) is not limited to the Web, as there are a number of other technical usages such as in defining namespaces for file formats (e.g., [[XML]]), and in identifying even non-Web-accessible objects for the purpose of expressing taxonomic relations. In less-technical usage, URLs turn up in all sorts of places like TV commercials, billboards, and on the side of vans, but often with the protocol portion left off when [[HTTP]] (or its secure variety, HTTPS, which eventually became the most commonly used protocol) is used. These days most browsers don't even show the "https://" part in the address bar, though it's still officially part of the URL.

== Types of identifiers ==

* '''URI''': The official "parent term" for URLs, URNs, and other such identifiers, but limited to [[ASCII]] characters, with anything else needing to be specially encoded. Even within the ASCII range, some characters such as the space are prohibited, reserved, or designated to be used only for specific syntactic purposes, with percent encoding necessary for all other uses.

* '''IRI''': The internationalized version of URIs, with more liberal rules about what characters in the entire [[Unicode]] range may be included. This allows text in non-English languages to be included without messy encoding, though various transfer protocols may still require the entire string to be encoded on transmission to produce an ASCII-based URI. This is really just a different representation of a URI; any IRI may be represented as a URI, with [[percent-encoding]] UTF-8 sequences if it contains non-ASCII characters.

* '''URL''': Technically only the subset of URIs that are "locators", able to be used to retrieve resources because they designate a specific address for them, but in practice the distinction is very fuzzy and usually ignored. Some newer standards such as HTML 5.0 simply follow common non-techie usage and use URL to refer to the whole universe of Web-style addresses (encompassing URIs and IRIs, and anything else a browser can accept as an address even if it fails to comply with any of the standards).

* '''URN''': Uniform Resource Name. Another type of URI which is supposed to provide a stable permanent identifier for a resource which does not include a specific (and changeable) address for it. To resolve a URN, one needs a resolver such as a server or website that stores a table of current locations of items with URNs. Currently the standards call for all URNs to begin with the 'urn:' scheme identifier, and the next item after this is a URN namespace, followed by another colon and the namespace-specific information. Some common naming schemes have been adopted as URNs, such as [[ISBN]]s (International Standard Book Number), which have the format "urn:isbn:1-234567-890". Unfortunately, browsers haven't been quick to implement URN resolvers as standard features, though add-ons can be installed to do it. URNs can also be used to refer to a [[UUID]], and are also used to refer to hashes in [[magnet URI]]s.

== Standard syntax ==

URLs/URIs/etc. always start with a scheme (protocol). (At least, ''absolute'' URLs do; there are also ''relative'' URLs that leave off parts at the beginning because they are construed as being relative to the current URL they are accessed from.) The most common was traditionally [[HTTP]], but more recently the encrypted variant HTTPS became more common; there are many other schemes too, although they are less common. The scheme part ends with a colon (:).

After this, the rest of the URL is scheme-dependent; there are a number of different syntaxes used in different types of URLs. A common syntax, expected by the standards to be used in all schemes with hierarchical path structures, follows the scheme part with a double slash (//) which introduces a host or authority portion (usually a [[domain name]]), which is then followed by another slash and then the full path being addressed, which uses forward slashes to separate hierarchical levels (which may, but needn't, correspond to subdirectories in a [[filesystem]]).

There's a common misconception that URLs always have a double slash after the colon, sometimes causing developers of new schemes to put this in their syntax where the standards don't call for it; it is only supposed to be used if the following element is some sort of "authority" (most commonly the address to connect to) by which a following path is to be interpreted. There are a number of schemes with no such authority, and hence no double slash; for insstance "mailto:".

== data: URLs ==

One scheme, '''data:''', is actually a file format in its own right, since it encodes the entire contents of a file within the URL instead of referencing an external resource as other schemes do.

* [[Wikipedia:Data URI scheme|Wikipedia article on data: URIs]]
* RFC 2397
* [http://dataurl.net/#about Data URL maker]

== Example ==

http://archive.org/upload/?description=I%20finally%20got%20it.%20However%2C%20an%20update%20made%20the%20Home%20Screen%20look%20like%20Jadoo%205%20and%20not%20like%20the%20new%20Home%20Screen%20they%20put%20in.&subject=Jadoo%2CJadooTV%2CJadoo7%2CJadoo%207%2CAndroid%2CAPK%2CAndroid%20Pie%2CAndroid%209%2CAndroid%209.0%2CAndroid%20TV%2CFarsi%2CHindi&creator=JadooTV&date=2021&collection=open_source_software
== See also ==

* [[Magnet URI]]
* [[URL encoding]]

== Official documents ==

* RFC 1738 (early absolute URL standard)
* RFC 1808 (early relative URL standard)
* RFC 2396 (early URI syntax standard)
* RFC 3986 (later URI syntax standard)
* RFC 3987 (IRI standard)
* RFC 4395 (info on registering new URI schemes)
* [http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/ W3C clarification of URIs, URLs, and URNs (2001)]
* [http://www.w3.org/TR/2012/WD-html51-20121217/infrastructure.html#urls HTML 5.1 draft section on URLs] (which intentionally disregards the distinctions in the other documents above)

== Proposed documents ==
* [http://tools.ietf.org/html/draft-kerwin-file-scheme-09 Internet draft for File scheme]

== Official sites ==

* [http://www.w3.org/Addressing/ W3C: Naming and Addressing] (old)
* [http://www.w3.org/standards/webarch/identifiers W3C: Identifiers] (new)
* [http://www.iana.org/assignments/uri-schemes.html IANA list of registered URI schemes]
* [http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml IANA list of URN namespaces]

== Other links ==

* [https://webtips.dan.info/url.html Dan's Web Tips: URLs]
* [http://blog.welldesignedurls.org/ Well Designed URLs Blog]
* [https://www.w3.org/Provider/Style/URI.html Cool URIs don't change (Tim Berners-Lee)]
* [http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx File URIs in Windows]
* [https://offset.skew.org/wiki/URI/File_scheme File URI scheme update project wiki]
* [https://github.com/AGLDWG/TR/wiki/URI-Guidelines-for-publishing-linked-datasets-on-data.gov.au-v0.1 URI Guidelines for publishing Linked Datasets on data.gov.au v0.1]
* [https://www.w3.org/community/blog/2014/09/11/proposed-group-uri-specification-community-group/ Proposed Group: URI Specification Community Group]
* [http://ben.balter.com/2014/10/07/expose-process-through-urls/ If you liked it then you should have put a URL on it]
* [http://blog.webrecorder.io/2015/02/beyond-robust-links-case-for-robust.html Beyond Robust Links: The case for robust urls and an Archival Url standard]
* [https://corner.squareup.com/2015/05/okhttp-2-4.html OkHttp’s New URL Class]
* [https://eager.io/blog/the-history-of-the-url-domain-and-protocol/ History of the URL: Domain, Protocol, and Port]

[[Category:Naming and numbering systems]]

URL

2026-03-06T19:00:38Z

Dan Tobias: /* Types of identifiers */

{{FormatInfo
|subcat=Web
|released=1990
|wikidata={{wikidata|Q42253}}, {{wikidata|Q61694}}, {{wikidata|Q424583}}
}}

A '''URL''' (Uniform Resource Locator) is an address of a resource as used on the World Wide Web, and is one of Tim Berners Lee's original three pillars of the Web along with [[HTTP]] and [[HTML]]. Technically speaking, a URL is just one category of such addresses, a subset of URI (Uniform Resource Identifier) and parallel to URN (Uniform Resource Name), but such distinctions aren't always consistently maintained even by technical people, and URL has entered the popular language in a way those other terms have not.

Over time, the precise definitions of the various terms for Web-related addresses have changed and been argued extensively about by technical people, and some more have been added: an IRI (Internationalized Resource Identifier) is like a URI, but extended to allow non-[[ASCII]] characters so that languages other than English can be supported. However, the newest HTML 5 standards drafts choose to take a more pragmatic approach of just using "URL" to refer to anything that a browser is expected to resolve as an address, as one of many "willful violations" of earlier tech specs they did there. (The "techie" equivalent of social conservatives may consider this to be "defining deviancy down" and hence an "abomination".)

Use of URLs (and URIs, etc.) is not limited to the Web, as there are a number of other technical usages such as in defining namespaces for file formats (e.g., [[XML]]), and in identifying even non-Web-accessible objects for the purpose of expressing taxonomic relations. In less-technical usage, URLs turn up in all sorts of places like TV commercials, billboards, and on the side of vans, but often with the protocol portion left off when [[HTTP]] (or its secure variety, HTTPS, which eventually became the most commonly used protocol) is used. These days most browsers don't even show the "https://" part in the address bar, though it's still officially part of the URL.

== Types of identifiers ==

* '''URI''': The official "parent term" for URLs, URNs, and other such identifiers, but limited to [[ASCII]] characters, with anything else needing to be specially encoded. Even within the ASCII range, some characters such as the space are prohibited, reserved, or designated to be used only for specific syntactic purposes, with percent encoding necessary for all other uses.

* '''IRI''': The internationalized version of URIs, with more liberal rules about what characters in the entire [[Unicode]] range may be included. This allows text in non-English languages to be included without messy encoding, though various transfer protocols may still require the entire string to be encoded on transmission to produce an ASCII-based URI. This is really just a different representation of a URI; any IRI may be represented as a URI, with [[percent-encoding]] UTF-8 sequences if it contains non-ASCII characters.

* '''URL''': Technically only the subset of URIs that are "locators", able to be used to retrieve resources because they designate a specific address for them, but in practice the distinction is very fuzzy and usually ignored. Some newer standards such as HTML 5.0 simply follow common non-techie usage and use URL to refer to the whole universe of Web-style addresses (encompassing URIs and IRIs, and anything else a browser can accept as an address even if it fails to comply with any of the standards).

* '''URN''': Uniform Resource Name. Another type of URI which is supposed to provide a stable permanent identifier for a resource which does not include a specific (and changeable) address for it. To resolve a URN, one needs a resolver such as a server or website that stores a table of current locations of items with URNs. Currently the standards call for all URNs to begin with the 'urn:' scheme identifier, and the next item after this is a URN namespace, followed by another colon and the namespace-specific information. Some common naming schemes have been adopted as URNs, such as [[ISBN]]s (International Standard Book Number), which have the format "urn:isbn:1-234567-890". Unfortunately, browsers haven't been quick to implement URN resolvers as standard features, though add-ons can be installed to do it. URNs can also be used to refer to a [[UUID]], and are also used to refer to hashes in [[magnet URI]]s.

== Standard syntax ==

URLs/URIs/etc. always start with a scheme (protocol). (At least, ''absolute'' URLs do; there are also ''relative'' URLs that leave off parts at the beginning because they are construed as being relative to the current URL they are accessed from.) The most common is traditionally [[HTTP]], though these days the encrypted variant HTTPS is increasingly common; there are many other schemes too, although they are less common. The scheme part ends with a colon (:).

After this, the rest of the URL is scheme-dependent; there are a number of different syntaxes used in different types of URLs. A common syntax, expected by the standards to be used in all schemes with hierarchical path structures, follows the scheme part with a double slash (//) which introduces a host or authority portion (usually a [[domain name]]), which is then followed by another slash and then the full path being addressed, which uses forward slashes to separate hierarchical levels (which may, but needn't, correspond to subdirectories in a [[filesystem]]).

There's a common misconception that URLs always have a double slash after the colon, sometimes causing developers of new schemes to put this in their syntax where the standards don't call for it; it is only supposed to be used if the following element is some sort of "authority" (most commonly the address to connect to) by which a following path is to be interpreted. There are a number of schemes with no such authority, and hence no double slash; for insstance "mailto:".

== data: URLs ==

One scheme, '''data:''', is actually a file format in its own right, since it encodes the entire contents of a file within the URL instead of referencing an external resource as other schemes do.

* [[Wikipedia:Data URI scheme|Wikipedia article on data: URIs]]
* RFC 2397
* [http://dataurl.net/#about Data URL maker]

== Example ==

http://archive.org/upload/?description=I%20finally%20got%20it.%20However%2C%20an%20update%20made%20the%20Home%20Screen%20look%20like%20Jadoo%205%20and%20not%20like%20the%20new%20Home%20Screen%20they%20put%20in.&subject=Jadoo%2CJadooTV%2CJadoo7%2CJadoo%207%2CAndroid%2CAPK%2CAndroid%20Pie%2CAndroid%209%2CAndroid%209.0%2CAndroid%20TV%2CFarsi%2CHindi&creator=JadooTV&date=2021&collection=open_source_software
== See also ==

* [[Magnet URI]]
* [[URL encoding]]

== Official documents ==

* RFC 1738 (early absolute URL standard)
* RFC 1808 (early relative URL standard)
* RFC 2396 (early URI syntax standard)
* RFC 3986 (later URI syntax standard)
* RFC 3987 (IRI standard)
* RFC 4395 (info on registering new URI schemes)
* [http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/ W3C clarification of URIs, URLs, and URNs (2001)]
* [http://www.w3.org/TR/2012/WD-html51-20121217/infrastructure.html#urls HTML 5.1 draft section on URLs] (which intentionally disregards the distinctions in the other documents above)

== Proposed documents ==
* [http://tools.ietf.org/html/draft-kerwin-file-scheme-09 Internet draft for File scheme]

== Official sites ==

* [http://www.w3.org/Addressing/ W3C: Naming and Addressing] (old)
* [http://www.w3.org/standards/webarch/identifiers W3C: Identifiers] (new)
* [http://www.iana.org/assignments/uri-schemes.html IANA list of registered URI schemes]
* [http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml IANA list of URN namespaces]

== Other links ==

* [https://webtips.dan.info/url.html Dan's Web Tips: URLs]
* [http://blog.welldesignedurls.org/ Well Designed URLs Blog]
* [https://www.w3.org/Provider/Style/URI.html Cool URIs don't change (Tim Berners-Lee)]
* [http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx File URIs in Windows]
* [https://offset.skew.org/wiki/URI/File_scheme File URI scheme update project wiki]
* [https://github.com/AGLDWG/TR/wiki/URI-Guidelines-for-publishing-linked-datasets-on-data.gov.au-v0.1 URI Guidelines for publishing Linked Datasets on data.gov.au v0.1]
* [https://www.w3.org/community/blog/2014/09/11/proposed-group-uri-specification-community-group/ Proposed Group: URI Specification Community Group]
* [http://ben.balter.com/2014/10/07/expose-process-through-urls/ If you liked it then you should have put a URL on it]
* [http://blog.webrecorder.io/2015/02/beyond-robust-links-case-for-robust.html Beyond Robust Links: The case for robust urls and an Archival Url standard]
* [https://corner.squareup.com/2015/05/okhttp-2-4.html OkHttp’s New URL Class]
* [https://eager.io/blog/the-history-of-the-url-domain-and-protocol/ History of the URL: Domain, Protocol, and Port]

[[Category:Naming and numbering systems]]

URL

2026-03-06T18:57:15Z

Dan Tobias:

{{FormatInfo
|subcat=Web
|released=1990
|wikidata={{wikidata|Q42253}}, {{wikidata|Q61694}}, {{wikidata|Q424583}}
}}

A '''URL''' (Uniform Resource Locator) is an address of a resource as used on the World Wide Web, and is one of Tim Berners Lee's original three pillars of the Web along with [[HTTP]] and [[HTML]]. Technically speaking, a URL is just one category of such addresses, a subset of URI (Uniform Resource Identifier) and parallel to URN (Uniform Resource Name), but such distinctions aren't always consistently maintained even by technical people, and URL has entered the popular language in a way those other terms have not.

Over time, the precise definitions of the various terms for Web-related addresses have changed and been argued extensively about by technical people, and some more have been added: an IRI (Internationalized Resource Identifier) is like a URI, but extended to allow non-[[ASCII]] characters so that languages other than English can be supported. However, the newest HTML 5 standards drafts choose to take a more pragmatic approach of just using "URL" to refer to anything that a browser is expected to resolve as an address, as one of many "willful violations" of earlier tech specs they did there. (The "techie" equivalent of social conservatives may consider this to be "defining deviancy down" and hence an "abomination".)

Use of URLs (and URIs, etc.) is not limited to the Web, as there are a number of other technical usages such as in defining namespaces for file formats (e.g., [[XML]]), and in identifying even non-Web-accessible objects for the purpose of expressing taxonomic relations. In less-technical usage, URLs turn up in all sorts of places like TV commercials, billboards, and on the side of vans, but often with the protocol portion left off when [[HTTP]] (or its secure variety, HTTPS, which eventually became the most commonly used protocol) is used. These days most browsers don't even show the "https://" part in the address bar, though it's still officially part of the URL.

== Types of identifiers ==

* '''URI''': The official "parent term" for URLs, URNs, and other such identifiers, but limited to [[ASCII]] characters, with anything else needing to be specially encoded. Even within the ASCII range, some characters such as the space are prohibited, reserved, or designated to be used only for specific syntactic purposes, with percent encoding necessary for all other uses.

* '''IRI''': The internationalized version of URIs, with more liberal rules about what characters in the entire [[Unicode]] range may be included. This allows text in non-English languages to be included without messy encoding, though various transfer protocols may still require the entire string to be encoded on transmission to produce an ASCII-based URI. This is really just a different representation of a URI; any IRI may be represented as a URI, with [[percent-encoding]] UTF-8 sequences if it contains non-ASCII characters.

* '''URL''': Technically only the subset of URIs that are "locators", able to be used to retrieve resources because they designate a specific address for them, but in practice the distinction is very fuzzy and usually ignored. Some newer standards such as HTML 5.0 simply follow common non-techie usage and use URL to refer to the whole universe of Web-style addresses (encompassing URIs and IRIs, and anything else a browser can accept as an address even if it fails to comply with any of the standards).

* '''URN''': Uniform Resource Name. Another type of URI which is supposed to provide a stable permanent identifier for a resource which does not include a specific (and changeable) address for it. To resolve a URN, one needs a resolver such as a server or website that stores a table of current locations of items with URNs. Currently the standards call for all URNs to begin with the 'urn:' scheme identifier, and the next item after this is a URN namespace, followed by another colon and the namespace-specific information. Some common naming schemes have been adopted as URNs, such as [[ISBN]]s (International Standard Book Number), which have the format "urn:isbn:1-234567-890". Unfortunately, browsers haven't been quick to implement URN resolvers as standard features, though add-ons can be installed to do it. URNs can also be used to refer to a [[UUID]]. URNs are also used to refer to hashes in [[magnet URI]]s.

== Standard syntax ==

URLs/URIs/etc. always start with a scheme (protocol). (At least, ''absolute'' URLs do; there are also ''relative'' URLs that leave off parts at the beginning because they are construed as being relative to the current URL they are accessed from.) The most common is traditionally [[HTTP]], though these days the encrypted variant HTTPS is increasingly common; there are many other schemes too, although they are less common. The scheme part ends with a colon (:).

After this, the rest of the URL is scheme-dependent; there are a number of different syntaxes used in different types of URLs. A common syntax, expected by the standards to be used in all schemes with hierarchical path structures, follows the scheme part with a double slash (//) which introduces a host or authority portion (usually a [[domain name]]), which is then followed by another slash and then the full path being addressed, which uses forward slashes to separate hierarchical levels (which may, but needn't, correspond to subdirectories in a [[filesystem]]).

There's a common misconception that URLs always have a double slash after the colon, sometimes causing developers of new schemes to put this in their syntax where the standards don't call for it; it is only supposed to be used if the following element is some sort of "authority" (most commonly the address to connect to) by which a following path is to be interpreted. There are a number of schemes with no such authority, and hence no double slash; for insstance "mailto:".

== data: URLs ==

One scheme, '''data:''', is actually a file format in its own right, since it encodes the entire contents of a file within the URL instead of referencing an external resource as other schemes do.

* [[Wikipedia:Data URI scheme|Wikipedia article on data: URIs]]
* RFC 2397
* [http://dataurl.net/#about Data URL maker]

== Example ==

http://archive.org/upload/?description=I%20finally%20got%20it.%20However%2C%20an%20update%20made%20the%20Home%20Screen%20look%20like%20Jadoo%205%20and%20not%20like%20the%20new%20Home%20Screen%20they%20put%20in.&subject=Jadoo%2CJadooTV%2CJadoo7%2CJadoo%207%2CAndroid%2CAPK%2CAndroid%20Pie%2CAndroid%209%2CAndroid%209.0%2CAndroid%20TV%2CFarsi%2CHindi&creator=JadooTV&date=2021&collection=open_source_software
== See also ==

* [[Magnet URI]]
* [[URL encoding]]

== Official documents ==

* RFC 1738 (early absolute URL standard)
* RFC 1808 (early relative URL standard)
* RFC 2396 (early URI syntax standard)
* RFC 3986 (later URI syntax standard)
* RFC 3987 (IRI standard)
* RFC 4395 (info on registering new URI schemes)
* [http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/ W3C clarification of URIs, URLs, and URNs (2001)]
* [http://www.w3.org/TR/2012/WD-html51-20121217/infrastructure.html#urls HTML 5.1 draft section on URLs] (which intentionally disregards the distinctions in the other documents above)

== Proposed documents ==
* [http://tools.ietf.org/html/draft-kerwin-file-scheme-09 Internet draft for File scheme]

== Official sites ==

* [http://www.w3.org/Addressing/ W3C: Naming and Addressing] (old)
* [http://www.w3.org/standards/webarch/identifiers W3C: Identifiers] (new)
* [http://www.iana.org/assignments/uri-schemes.html IANA list of registered URI schemes]
* [http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml IANA list of URN namespaces]

== Other links ==

* [https://webtips.dan.info/url.html Dan's Web Tips: URLs]
* [http://blog.welldesignedurls.org/ Well Designed URLs Blog]
* [https://www.w3.org/Provider/Style/URI.html Cool URIs don't change (Tim Berners-Lee)]
* [http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx File URIs in Windows]
* [https://offset.skew.org/wiki/URI/File_scheme File URI scheme update project wiki]
* [https://github.com/AGLDWG/TR/wiki/URI-Guidelines-for-publishing-linked-datasets-on-data.gov.au-v0.1 URI Guidelines for publishing Linked Datasets on data.gov.au v0.1]
* [https://www.w3.org/community/blog/2014/09/11/proposed-group-uri-specification-community-group/ Proposed Group: URI Specification Community Group]
* [http://ben.balter.com/2014/10/07/expose-process-through-urls/ If you liked it then you should have put a URL on it]
* [http://blog.webrecorder.io/2015/02/beyond-robust-links-case-for-robust.html Beyond Robust Links: The case for robust urls and an Archival Url standard]
* [https://corner.squareup.com/2015/05/okhttp-2-4.html OkHttp’s New URL Class]
* [https://eager.io/blog/the-history-of-the-url-domain-and-protocol/ History of the URL: Domain, Protocol, and Port]

[[Category:Naming and numbering systems]]

AI and Machine Learning

2026-03-04T18:25:55Z

Dan Tobias: /* General */

{{FormatInfo
|formattype=electronic
|thiscat=AI and Machine Learning
|image=Dall-e_3_(jan_%2724)_artificial_intelligence_icon.png
|caption=DALL-E 3 Generated Image
}}
See also [[Scientific Data formats]] and [[Serialization]]

== General ==
* [[AIML]]
* [[CoreML]]
* [[Deep Learning Container]] (.dlc)
* [[GGML]]
* [[HDF]] (Hierarchical Data Format, originally from NCSA, now maintained by The HDF Group)
** [[HDF4]]
** [[HDF5]]
* [[Keras]] (.keras)
* [[llms.txt]]
* [[MLeap]]
* [[NPY and NPZ (NumPy)|NumPy]]
* [[Pickle]] (.pkl)
* [[Protocol Buffers]]
* [[PyTorch]] (.pt, .pth)
* [[TensorFlow]] (.pb)
** [[TFLite]]
* [[TOON]] [https://toonformat.dev/]

== Links ==
* [https://github.com/trailofbits/ml-file-formats File formats used in ML/AI systems]

Web

2026-03-04T18:21:15Z

Dan Tobias: /* Miscellaneous */

{{FormatInfo
|formattype=electronic
|thiscat=Web
|released=1990
|image=Web browser.png
}}
Formats connected with the World Wide Web, though most of them overlap into other categories; basically everything that can be put in a file format of any sort can be put on the Web, and a multiplicity of types of [[document]]s, [[graphics]], [[Audio and Music|audio]], [[video]], [[markup]], [[Programming Languages|programming languages]], and more, are used there. The Web is a variety of [[hypermedia]], by far the most successful one.

== Blogging and web hosting platforms ==

* [[Blogger]]
* [[Posterous]]
* [[Xanga]]

== Cloud platforms ==

* [[Amazon Web Services]] (AWS)
** [[Amazon Resource Name]] (ARN)
* [[Google Cloud]]
* [[Heroku]]
* [[IBM Cloud]]
* [[Microsoft Azure Cloud]]

== Content management systems ==

* [[Drupal]]
* [[WordPress]]

== Development software ==

* [[Dreamweaver site settings file]] (.ste)
* [[Homestead SiteBuilder]] (.hc, .xpf)
* [[Master Album Maker]] (.mmp)
* [[Actual Drawing]] (.adf)

== Feeds, syndication, and metadata ==

* [[Atom]] (syndication format)
* [[h-entry]] (Microformats, was part of HAtom until split and renamed in microformats2)
* [[h-feed]] (Microformats, was part of HAtom until split and renamed in microformats2)
* [[hListing]] (Microformats; product/service listings)
* [[hMedia]] (Microformats; image/video/audio metadata)
* [[hNews]] (Microformats; news articles)
* [[h-resume]] (Microformats; resumes/CVs)
* [[h-review]] (Microformats; ratings/reviews)
* [[opencomic]] (syndication of webcomics)
* [[OPML]]
* [[RDF]]
** [[RDFa]] (linked data in HTML)
** [[TTL]] [https://en.wikipedia.org/wiki/Turtle_(syntax) Turtle]
* [[RSS]]

== Markup, documents and data ==

* [[3DMLW]] (3D Markup Language for Web)
* [[Accelerated Mobile Pages]] (AMP)
* [[BBCode]]
* [[Cascading Style Sheets]] (CSS)
** [[Sass]] (pre-processor for CSS)
* [[Compressed Markup Language]] (CML, PQA; used in PalmOS)
* [[HTML|HTML/XHTML]]
* [[Markdeep]]
* [[Markdown]]
* [[MHTML]]
* [[Wiki markup]]
* [[WML]]
* [[WOFF]]

== Program/system-specific files (browser/server/OS/etc) ==

=== General ===
* [[Web browser files]] (bookmarks, cookies, configurations, etc.)
* [[Web server files]] (server configuration, etc.)

=== Specific ===
* [[Internet Shortcut]] (Windows)
* [[Webloc]] (Mac OS X)

== Protocols and parameters ==

* [[Common Gateway Interface]] (CGI)
* [[DNS]]
* [[Domain name]]
** [[Top-level domain]]
* [[Gopher]]
* [[HTTP]]
** [[HPACK (HTTP)]]
* [[HTTPS]]
* [[IP address]]
* [[IPV6]]
* [[JSON API]]
* [[Linked Data Platform]]
* [[MIME types]]
* [[QUIC]]
* [[SOAP]]
* [[TCP/IP]]
* [[Tor]]
* [[URL]]s (and URIs, URNs, etc.)
** [[URL encoding]]
* [[WAP]]
* [[WebDAV]]

== Scripts/Applets/Plug-Ins/Frameworks/APIs/Templating ==

* [[Active Server Pages]] (ASP)
* [[ActiveX]]
* [[Audio Data API (Mozilla)]]
* [[BrowserFS]]
* [[ECMAScript]]
* [[Java]]
* [[JavaScript]]
* [[JavaServer Pages]] (JSP)
* [[Liquid]] (.liquid)
* [[MediaStream Processing API]]
* [[.Net Framework]]
* [[node.js]]
* [[NPAPI]]
* [[Open Web App Manifest]] (.webapp)
* [[PHP]]
* [[React]]
* [[Server Side Includes]]
* [[Shockwave (Director)]]
* [[Silverlight]]
* [[SWF]] (Flash)
* [[VBScript]]
* [[Web Audio API]]
* [[WMLScript]]

== Site dumps, multi-file packaging, and offline reading ==

* [[ARC (Internet Archive)]]
* [[HAR]] (HTTP Archive)
* [[MAFF]] (Mozilla Archive Format)
* [[Package (Web)]]
* [[PackageForTheWeb]]
* [[Portable Web Publications]]
* [[WARC]]
* [[Webarchive (Safari)]]
* [[XOWA]]
* [[Zeno]]
* [[ZIM]]

== Miscellaneous ==

* [[Adobe Cross Domain Policy File]] (crossdomain.xml)
* [[Ads.txt]]
* [[Canonical Link Relation]] (rel="canonical")
* [[carbon.txt]]
* [[Content Security Policy]]
* [[DWF]] - AutoDesk's Design Web Format; AutoCAD & Revit can publish to this format; similar in concept to PDF files; AutoDesk Design Review is the reader
* [[Favicon]]
* [[Form URL encoding]]
* [[Galen]] (framework for testing responsive sites)
* [[JSON-LD]] (JSON for linked data)
* [[llms.txt]]
* [[Mark of the Web]]
* [[Multipart/Form-Data]]
* [[Open Graph protocol]]
* [[OpenSearch Description]]
* [[P3P]] (Platform for Privacy Preferences)
* [[Percent-encoding]]
* [[rel-author]] (Microformats; link to author homepage)
* [[rel-home]] (Microformats; link to site homepage)
* [[rel-license]] (Microformats; link to site license)
* [[rel-nofollow]] (Microformats; gets robots to ignore link)
* [[rel-payment]] (Microformats; link to payment method)
* [[rel-tag]] (Microformats)
* [[Robots Exclusion Standard]] (robots.txt)
* [[Security.txt]]
* [[Sitemap]]
* [[URL shorteners]]
* [[Web Annotation Protocol]]
* [[Web-safe colors]]

== See also ==

See also [[E-Mail, newsgroups, and forums]] (a number of web-based messaging/social-networking things are there)

== External links ==

=== History ===
* [http://blogs.palmbeachpost.com/superfun/2013/12/29/watch-arthur-c-clarke-in-1974-predict-computers-and-the-internet-today/ Arthur C. Clarke predicts computers and the Internet in 1974]
* [http://lists.w3.org/Archives/Public/www-talk/1992JanFeb/0000.html Tim Berners-Lee discusses Web protocols/formats in Jan 1992]
* [http://mentalfloss.com/article/49676/what-internet-looked-1995 What the Internet looked like in 1995]
* [https://archive.org/details/The_Internet_-_a_step_by_step_guide_on_video_VHS_ABC_1996 1996 Internet Step-By-Step Guide video]
* [http://theweek.com/article/index/248229/7-highlights-from-this-amazing-1997-kids-guide-to-the-internet 1997 "Kids' Guide to the Internet" video]
* [http://web.archive.org/web/19980610100009/www.redherring.com/mag/issue55/economics.html#?hn 1998: prognosticator predicts "By 2005 or so, it will become clear that the Internet's impact on the economy has been no greater than the fax machine's"]
* [http://thiswasfirst.com/ First posts on famous websites]
* [http://www.wired.com/underwire/2013/04/websites-stuck-in-time/ Internet Archaeology: Behold the Most Hilarious Abandoned Websites]

=== Privacy and security ===
* [http://boingboing.net/2013/08/18/paranoid-browsing-anti-profil.html Paranoid Browsing plug-in]
* [http://justdelete.me/ Justdelete.me: Delete your account on lots of web services]
* [http://www.newscientist.com/article/mg22029444.900-throw-off-the-spooks-by-disguising-your-web-traffic.html Throw off the spooks by disguising your web traffic]
* [https://disconnect.me/ Disconnect: visualize and block invisible websites that track you]
* [https://www.howsmyssl.com/ How's My SSL?] (tests the security of your browser)
* [http://csi.websense.com/ Check URL for stuff Websense thinks is malicious or might be subject to filtering for some reason]
* [http://www.theshovel.com.au/2014/08/06/brandi-laws-only-for-people-using-world-wide-web/ Brandis Reassures Australians: Data Retention Laws Only For People Using World Wide Web]

=== Commentary ===

* [http://boingboing.net/2013/05/09/howto-search-the-web-like-the.html How to search the Web like the NSA]
* [http://www.washingtonpost.com/opinions/robert-samuelson-of-internet-threats-and-cyberattacks/2013/06/30/df7bd42e-e1a9-11e2-a11e-c2ea876a8f30_story.html If I could, I would repeal the Internet]
* [http://www.wired.com/wiredenterprise/2013/08/indie-web/ Meet the Hackers Who Want to Jailbreak the Internet]
* [http://www.w3.org/QA/2013/05/perspectives_on_encrypted_medi.html W3C statement about adding DRM/content protection to web standards]
* [http://www.wired.com/beyond_the_beyond/2009/03/what-bruce-ster/ What Bruce Sterling Actually Said About Web 2.0 at Webstock 09]
* [https://www.usenix.org/system/files/1403_02-08_mickens.pdf To Wash It All Away]
* [http://britishlibrary.typepad.co.uk/webarchive/2014/10/what-is-still-on-the-web-after-10-years-of-archiving-.html What is still on the web after 10 years of archiving?]
* [http://ndsr.nycdigital.org/symmetrical-web-archiving-with-webrecorder-a-browser-based-tool-for-digital-social-memory-an-interview-with-ilya-kreymer/ Symmetrical web archiving]

=== Tools and utilities ===

* [http://netpreserve.org/web-archiving/tools-and-software Web archiving tools and software]
* [http://activehistory.ca/2014/07/two-tools-for-the-web-savvy-historian-memento-and-webcite/ Three Tools for the Web-Savvy Historian: Memento, Zotero, and WebCite]
* [http://ws-dl.blogspot.com/2014/07/2014-07-14-archival-acid-test.html Archival Acid Test] (tests whether web archivers preserve functionality)
* [https://github.com/lintool/warcbase warcbase: A web archive browser built on HBase]
* [http://www.ianww.com/ad-detector/ Ad Detector: flags sponsored content]
* [https://github.com/Netflix/sketchy Sketchy: takes screenshots and scrapes text from web pages]
* [http://ianmilligan.ca/2014/08/27/using-imageplot-to-explore-web-archived-images/ Using ImagePlot to Explore Web Archived Images]
* [https://modern.ie/en-us/screenshots BrowserStack screenshot automation]
* [http://mementoweb.org/ Memento "time travel" extension for Chrome]
** [http://blog.bibsonomy.org/2014/09/feature-of-week-bibsonomy-and-memento_9.html?m=1 BibSonomy and Memento]
** RFC 7089 - proposed HTTP protocol extension for date-time negotiation
** [http://timetravel.mementoweb.org/guide/api/ Time travel API documentation]
* [http://hypothes.is/ The Web, Annotated]
* [https://webrecorder.io/ WebRecorder: create archival copies of sites you browse]
* [http://ws-dl.blogspot.com/2014/11/2014-11-14-carbon-dating-web-version-20.html Carbon dating the Web]
* [http://yacy.net/en/index.html Web Search by the people, for the people]
* [http://builtwith.com/ Builtwith: shows what tools are behind a site]
* [http://frontendhq.com/pinger Ping me when a standard is supported by 90% of browsers]
* [https://owl.english.purdue.edu/owl/resource/558/07/ Resources to Search the Invisible Web]
* [http://dev.modern.ie/tools/vms/windows/ Download virtual machines running various versions of MSIE]
* [http://codepen.io/ CodePen: in-browser HTML/CSS/JS editor with instant results]
* [https://github.com/ikreymer/netcapsule Netcapsule: Browse old websites in emulated old browsers]
* [http://deslide.clusterfake.net/ Deslide: Display those web slideshows on one page]
* [http://oldweb.today/ oldweb.today: View old web pages in emulations of old browsers]
* [https://github.com/helgeho/ArchiveSpark ArchiveSpark: Apache Spark framework that facilitates access to Web Archives]
* [https://hyperdev.com/ HyperDev: developer playground for building web apps] ([http://www.joelonsoftware.com/items/2016/05/30.html More info])

=== Other ===
* [https://webmaker.org/standard Mozilla's Web Literacy Standard]
* [http://mentalfloss.com/article/31932/chasing-cicada-exploring-darkest-corridors-internet Chasing the Cicada: Exploring the Darkest Corridors of the Internet]
* [http://blogs.loc.gov/digitalpreservation/2011/11/the-average-lifespan-of-a-webpage/ The average lifespan of a webpage (2011)]
* [http://www.informationr.net/ir/9-2/paper174.html?_ga=1.52567341.481372218.1392651717 A longitudinal study of Web pages continued: a consideration of document persistence (2004)]
* [http://www.theguardian.com/commentisfree/2013/nov/14/conservatives-website-purge-history-tory-party-speeches-internet The Conservatives' website purge has destroyed history]
* [https://github.com/alphagov/frontend Front end of gov.uk site, downloadable from Github]
* [http://downworthy.snipe.net/ Downworthy: A browser plugin to turn hyperbolic viral headlines into what they really mean]
* [http://www.techrepublic.com/article/flex-the-power-of-curl-for-web-dev-testing-and-data-transfers/ Flex the power of cURL for web dev testing and data transfers]
* [http://www.cs.odu.edu/~aalsum/projects/mcurl.html mcurl: Command line memento client to retrieve old versions of web pages from archives]
* [http://virtuallyfun.superglobalmegacorp.com/?p=3866 Surfing modern web with ancient browsers]
* [http://www.webat25.org/ Web at 25]
* [http://www.re-cycledair.com/restoring-a-14-year-old-website Restoring a 14 year old website]
* [http://blog.archive.org/2013/10/24/web-archive-404-handler-for-webmasters/ Internet Archive 404 Not Found Handler]
* [http://netpreserve.org/collection-development-policies Web archiving policies of various archives and national libraries]
* [http://xldb.di.fc.ul.pt/xldb/publications/Costa:InformationSearchIn:2014_document.pdf Information Search in Web Archives (academic thesis)]
* [https://medium.com/making-instapaper/bookmarklets-are-dead-d470d4bbb626 Bookmarklets are dead... we just don't know it yet]
* [https://webkit.org/blog/6682/improving-color-on-the-web/ Improving color on the web]

[[Category:Hypermedia]]
[[Category:Websites and online services]]

Llms.txt

2026-03-04T18:20:22Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|subcat=Web
|extensions={{ext|txt}}
|wikidata={{wikidata|Q133958690}}
|released=2024
}}
{{DISPLAYTITLE:llms.txt}}

'''llms.txt''' is a proposed document standard by [https://jeremy.fast.ai/ Jeremy Howard] for enabling LLMs to make use of a website at inference time.

'''llms.txt''' is based on [[Markdown]] meaning it is human and machine readable. It adopts a precise structure enabling "fixed processing methods".

== Usage ==

The file is intended to be placed at the root of a website, similarly to other standard site-informational files such as [[Robots Exclusion Standard|robots.txt]]. Optionally it may also be placed in subdirectories for information specific to that directory.

== Proposed structure ==

The structure is proposed as follows:

* An H1 with the name of the project or site. This is the only required section
* A blockquote with a short summary of the project, containing key information necessary for understanding the rest of the file
* Zero or more markdown sections (e.g. paragraphs, lists, etc) of any type except headings, containing more detailed information about the project and how to interpret the provided files
* Zero or more markdown sections delimited by H2 headers, containing “file lists” of URLs where further detail is available
:* Each “file list” is a markdown list, containing a required markdown hyperlink [name](url), then optionally a : and notes about the file.

== Example ==

An example might look as follows (from the documentation):

<pre>
# Title

> Optional description goes here

Optional details go here

## Section name

- [Link title](https://link_url): Optional link details

## Optional

- [Link title](https://link_url)
</pre>

== References ==

* [https://llmstxt.org/ llms.txt homepage]

[[Category:AI and Machine Learning]]
[[Category:File formats with a distinctive filename]]

Llms.txt

2026-03-04T18:19:47Z

Dan Tobias:

Llms.txt

2026-03-04T18:17:22Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|subcat=Web
|extensions={{ext|txt}}
|wikidata={{wikidata|Q133958690}}
}}
{{DISPLAYTITLE:llms.txt}}

'''llms.txt''' is a proposed document standard by [https://jeremy.fast.ai/ Jeremy Howard] for enabling LLMs to make use of a website at inference time.

'''llms.txt''' is based on [[Markdown]] meaning it is human and machine readable. It adopts a precise structure enabling "fixed processing methods".

== Usage ==

The file is intended to be placed at the root of a website, similarly to other standard site-informational files such as [[robots.txt]]. Optionally it may also be placed in subdirectories for information specific to that directory.

== Proposed structure ==

The structure is proposed as follows:

* An H1 with the name of the project or site. This is the only required section
* A blockquote with a short summary of the project, containing key information necessary for understanding the rest of the file
* Zero or more markdown sections (e.g. paragraphs, lists, etc) of any type except headings, containing more detailed information about the project and how to interpret the provided files
* Zero or more markdown sections delimited by H2 headers, containing “file lists” of URLs where further detail is available
:* Each “file list” is a markdown list, containing a required markdown hyperlink [name](url), then optionally a : and notes about the file.

== Example ==

An example might look as follows (from the documentation):

<pre>
# Title

> Optional description goes here

Optional details go here

## Section name

- [Link title](https://link_url): Optional link details

## Optional

- [Link title](https://link_url)
</pre>

== References ==

* [https://llmstxt.org/ llms.txt homepage]

[[Category:AI and Machine Learning]]
[[Category:File formats with a distinctive filename]]
[[Category:Web]]

Compression

2026-03-02T03:50:03Z

Dan Tobias: /* Specific file formats/programs */

{{FormatInfo
|formattype=electronic
|thiscat=Compression
|image=Vise.png
}}

== Stream compression formats ==

A stream format takes a stream of bytes, and outputs a different, hopefully smaller, stream of bytes. These compression formats are often used internally in other data structures to compress data, as well as in network protocols, such as http. Used stand-alone, a stream compression format does not offer archiving capability, however in the UNIX doctrine, an archiver like [[tar]] or the more archaic variant [[shar]] can be combined with an archive format to produce a proper compressed archive.

* [[gzip]] (.gz)
* [[bzip2]] (.bz2)
* [[LZ4]]
* [[LZMA Alone|LZMA_Alone]] (.lzma)
* [[pack (Unix)]] (.z)
* [[XZ]] (.xz)
* [[Zstandard]] (.zstd)
** [[Zstandard dictionary]]

== Compression algorithms and compressed data formats ==

(excluding formats usually used as file formats)

* [[Arithmetic coding]]
* [[Brotli]]
* [[Burrows–Wheeler transform]]
* [[DEFLATE]]
* [[DivANS]]
* [[EXEPACK2]]
* [[FastLZ]]
* [[Fractal compression]]
* [[HPACK (HTTP)|HPACK]] (used to compress HTTP headers)
* [[Huffman coding]]
** [[Adaptive Huffman coding]]
** [[Canonical Huffman code]]
* [[InstaCompOne]]
* [[Lempel–Ziv–Stac]] (LZS)
* [[LZ77]]
* [[LZ77 with Huffman coding]]
* [[LZ78]]
* [[LZFSE]]
* [[LZHAM]]
* [[LZMA]]
* [[LZMA2]]
* [[LZMW]]
* [[LZO]] (Lempel–Ziv–Oberhumer)
* [[LZRW]]
* [[LZSS]] (Lempel–Ziv–Storer–Szymanski)
* [[LZW]]
* [[LZX]]
** [[LZX Delta]]
* [[MSZIP]]
* [[PKWARE DCL Implode]]
* [[PPMd]]
* [[Prediction by partial matching]] (PPM)
* [[Run-length encoding]]
** [[PackBits]]
** [[RLE90]]
* [[Shannon–Fano coding]]
* [[Snappy]] (Google-created compression also used by Apple in iWork formats)
* [[zlib]]

=== Graphics compression ===
See [[Graphics#Compression]] for compression formats used primarily with graphics.

== Specific file formats/programs ==

(multi-file compressors are in [[Archiving]])

* [[9CDR]] (Amiga FileImploder Clone)
* [[ABC (Advanced Blocksorting Compressor)]]
* [[ABComp]] (.abp)
* [[Aldus LZW]]
* [[Aldus PKZP]]
* [[BARF]] (.x, .x??)
* [[BGZF]]
* [[BWTC32Key]] (.B3K)
* [[bzip]] (.bz)
* [[BZip3]] (.bz3)
* [[CAZIP]]
* [[ChiefLZ]] (.LZZ)
* [[compact (Gene Olson)]] (.W)
* [[compact (Unix)]] (.C)
* [[compress (Unix)]] (.Z)
* [[CMP (NEW-DOS)]]
* [[CrLZH]] (.?y?)
* [[CRN]] (.crn) - compressed text files used for PC-Write manual
* [[Crunch]] (.?z?)
* [[Crunch-Mania]]
* [[DACT]]
* [[DitPack]]
* [[DUPA]] (Amiga FileImploder Clone)
* [[EBZ|EBZip]] (.ebz)
* [[EDI Install archive]]
* [[EDI Install packed file]]
* [[EDI LZSSLib]]
* [[EmmaCompress]]
* [[Error Code Modeler]] (.ecm)
* [[File Imploder]] (Amiga) (.imp)
* [[FlySpeed st/exp]]
* [[Freeze/Melt]] (Unix) (.F)
* [[Hammer (compression)|Hammer]]
* [[HAP]] (v2.x)
* [[ICE (Michael Lamanuzzi)|ICE]] (.ice, by Michael Lamanuzzi)
* [[Inflate]] (.infl) - parody format that actually increases size
* [[InstallIt!]]
* [[JAM (W. Jiang)]]
* [[The JAM Packer|JAM Packer, The]]
* [[JCalG1]] (.jc, Commodore Amiga)
* [[Kboom11]]
* [[Logitech Compress]]
* [[lrzip]] (.lrz)
* [[LZ5 and Lizard]]
* [[LZARI]]
* [[LZHUF]]
* [[Lzip]] (.lz)
* [[lzop]] (.lzo)
* [[LZS221]]
* [[LZSS (Haruhiko Okumura)]]
* [[LZWCOM]]
* [[LzwPak]]
* [[Microsoft KWAJ installation compression]]
* [[Microsoft SZ installation compression]]
* [[Mozilla LZ4]] (.jsonlz4)
* [[MS-DOS installation compression]] (.??_)
* [[MULTIKIT COMPRESS]]
* [[NetWare Packed File]]
* [[NOAH]]
* [[Nova Compress]]
* [[NPack]]
* [[NRV (Not Really Vanished)]]
* [[Oodle Data Compression]]
* [[PGNPack]]
* [[PowerPacker]] (.pp)
* [[PPMZ]]
* [[PPMZ2]]
* [[Pro-Pack]]
* [[PUT and GET (Scott Jennings)]]
* [[Quasijarus Strong Compression]]
* [[RAC]]
* [[Reduq]]
* [[RKUC]]
* [[rzip]] (.rz)
* [[S2]] (.s2, .snappy)
* [[SCO compress LZH]]
* [[SEMONE]] (.one)
* [[sfArk]]
* [[SFDN Packer]]
* [[SFPack]]
* [[SHARC]] (density)
* [[Softdisk Text Compressor]] (.ctx)
* [[Splint]]
* [[SQ2]]
* [[Squash (RISC OS)|Squash]] - single file compression on RISC OS
* [[Squeeze|Squeeze/SQ]] (.?q?)
* [[SQUEEZE (AJP Systems)]]
* [[squeeze (Daniel Bernstein)]] (.MW)
* [[Squish (Mike Albert)]]
* [[Sunzip]] (.sz)
* [[TERSE]]
* [[Top4]]
* [[TTCOMP]]
* [[TTW]]
* [[tzip]]
* [[Tzip (Text ZIP)]]
* [[UHBC]]
* [[WWPACK]]
* [[XPK]]
* [[Yay0]]
* [[Yaz0]]
* [[zchunk]]
* [[Zoo filter format]]
* [[Zoo Z format]]
* [[ZSQ (LZW compression)]]

== Transparent file compression ==
(A mostly-obsolete technique in which a background process hooks into the OS and decompresses files transparently when they are read. ''Compression'' might be done manually. The line between this and ''Disk compression'' can be blurry.)

* [[AFX (Atari ST)]]
* [[CFS (Computer Concepts Compression)]]
* [[DIET (compression)|DIET]]
* [[Diet Disk]]
* [[DiskDoubler]]
* [[Pack-Ice]]
* [[SLIM (Dominic Herity)|SLIM]]
* [[Turbo Packer]]
* [[XPACK]]

== Disk compression ==
(Transparent disk compression software and the like, excluding filesystem formats.)

* [[DoubleDisk]]
* [[DoubleSpace and DriveSpace]]
* [[JAM (disk compression)]]
* [[Stacker]]
* [[SuperStor]]

For filesystem formats that feature compression, see [[Filesystem]] (especially [[Filesystem#Compressed filesystems]]).

== Executable compression ==

See [[Executable compression]].

== See also ==

* [[Compression and archiving software]]
* [[Compression research]]
* [[Archiving]] (for formats that place multiple files together in one file, with or without compression)
* [[Graphics#Compression|Graphics]] (for image-specific compression)
* [[Video]] (for video-specific compression)
* [[Audio and Music]] (for audio-specific compression)

== Links ==
* [http://boingboing.net/2014/03/04/data-compression-with-playing.html Data-compression with playing cards]
* [https://web.archive.org/web/20201108101659/https://bestofquora.wordpress.com/2014/06/14/what-is-the-most-compressed-file-ever/ What is the most compressed file ever?]
* [https://ethw.org/History_of_Lossless_Data_Compression_Algorithms History of Lossless Data Compression Algorithms]
* [https://www.mattmahoney.net/dc/dce.html Data Compression Explained - Matt Mahoney]

Just Solve the File Format Problem:Community portal

2026-02-22T18:30:16Z

Dan Tobias: /* Removing copyrighted images */

: ''please add your signature by typing <nowiki>~~~~</nowiki> if you add or reply

== Open issues ==

Below is a list of "issues" which would ordinarily be in a ticketing system of some kind, but are here on the Wiki instead, because that's how we roll. As things are resolved, they will be moved to the Discussion page. If there's an appeal or an issue, the conversation can continue there - this page will be for open issues.

Use of case in URLS / links. I went through all the electronic format types pages, and tried to normalise all the pages where I could (there was a mix of link structures - I've tried to get them all (apart from animation - I've been at it all day!) so they are [[file extension]] - [[file type name]].
I notice that we have a mix of upper and lower case file extension through out. This means we may have 2 links which should point to the same URL (e.g. [[mix]] and [[MIX]]) is this a known issue with the current layout? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 01:32, 20 November 2012 (UTC)
:Since you're linking both the extension and the name, does that mean that there are supposed to be separate articles for each? I don't know if there's really a need for "mainspace" articles by extension, since there are already categories for that purpose; you can browse them through [[:Category:File formats by extension]]. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 02:12, 20 November 2012 (UTC)
::I just copied the most common model that I found on the formats pages. The problem is, if you don't homogenize the method, the linking/crosslinking doesn't work properly. All instances of .doc (for example) should point to the same resource page / disambiguation page. If someone has linked to only format in one place (e.g. [[MS Word]] (.doc)), and someone else the extension (MS Word - [[doc]]), we can't makes sure they point to the same place. The problem occurs because format names and extensions are used interchangeably. You raise an interesting question about the relationship between the ext and the format name. I would argue they are not equal (1:1), nor (1:many) / (many:1) so it makes sense to protect both aspects as definable things - the extension because that's whats most commonly searched for and referred to by users and 'format name' because its more accurate. How is the [[:Category:File formats by extension]] populated? --[[User:JaygattusoNLNZ|JaygattusoNLNZ]] ([[User talk:JaygattusoNLNZ|talk]]) 18:31, 20 November 2012 (UTC)
:::The categories are inserted when you use the ext template in the infobox. My preference is to have articles by actual format name and use multiple navigation aids (menus, cats, etc.) to get to them. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:38, 21 November 2012 (UTC)

== Article naming convention ==

As mentioned above, there's some dispute over whether to name articles after the full name of a format or its file extension. If using full names, you then get into issues of whether to use the full technical name or a shorter thing that's more popularly used, and in some cases that's even the same as the extension (GIF, for instance). And you also get into tricky issues of capitalization: all-caps like an acronym, all-lowercase like filenames are often done (though this is OS-dependent; some, like MS-DOS, use all-uppercase), or mixed case (proper names capitalized)? And then there's the disambiguation issue of how to name articles on different things that have the same name, which happens sometimes even with long official names, but even more often with short acronyms and file extensions. But there's also yet another issue of which things get separate articles and which are combined, like formats that have had many different versions, etc.

Currently you have things like [[CI]] and [[CT]], recently-created articles that represent two different file types within the data of one type of music tracker. The spec document they link to is the same one, which documents all the file types used in that tracker. Unless there's going to be really a lot to say about each of the specific file types, my own preference would be to have one article called [[CyberTracker]] that discusses all the formats used by the program in question, with subheaders within the article for the different file types, and all the extensions listed in the infobox (and hence in associated categories). If any other indices by extension are built up, they'd also have entries for both CI and CT. For instance, when I documented [[Softdisk Family Tree]], I covered all the various file formats in one article, though there are several versions and multiple files for each. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:39, 21 November 2012 (UTC)
: I realise I'm as guilty of this as anyone, having used both forms at some point (e.g. [[Surprise! Adlib Tracker v2.0]] and [[CI]]). Indeed, the two articles - [[CI]] and [[CT]] - you refer to were created by me. I guess in general I would favour using a descriptive page name rather than simply the file extension - that seems to be something that's being taken care of by infoboxes and categories.

:On the issue of what gets a separate page and what doesn't, I guess that just comes down to individual discretion. There will be instances where a format has undergone a number of minor revisions over time or has a number of minor variants (e.g. the variant forms of Chaos Music Composer's [[CMC]]) where it would make sense to keep them all to a single page, while a major revision would necessitate a multi-page approach (e.g. the shift with Capella from the binary [[CAP]] to the XML-based [[CapXML]] format).

:However, I'm not sure I agree with [[CI]] and [[CT]] having a single [[CyberTracker]] page. While both link to the same spec document and both are used by the same program, they are different formats serving different purposes. I think in general we should try and distinguish between program and file format - [[S3M]] doesn't belong on the [[ScreamTracker]] page, although each should link to the other. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 14:04, 21 November 2012 (UTC)

:Since the purpose of the wiki is to document file formats, I think it's good that as many formats as possible are listed in the category pages and that you can browse these pages for format extensions. Sometimes it might be better to link multiple extension to the same article (e.g. a specific application), but not always. I think it is difficult to come up with a strict rule for this (but maybe recommendations and, even better, good examples). --[[User:PN|PN]] ([[User talk:PN|talk]]) 15:08, 21 November 2012 (UTC)

::It's a judgment call, certainly. It depends on how the files are typically encountered, distributed, used, etc., and how they're thought of by people who use them; if a bunch of file types related to a particular program are usually found together as part of a larger data set, they most likely belong together in one article (with subsections to describe the function of the particular files), but if they're distinct entities with their own particular treatment (like separate areas of file trading sites for enthusiasts) they should have separate articles, though more descriptive names like "CyberTracker instrument file" might be better than a cryptic and likely ambiguous CI. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:46, 21 November 2012 (UTC)
::And then, somebody has also used a robot to create pages in a separate namespace devoted to file extensions, like [[Ext:cin]]. That's yet another navigational system for getting to information by extension, though those pages oddly don't actually have direct links to the normal pages here about those file formats. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 15:56, 21 November 2012 (UTC)
::: Yes, that was me with Bender the bot. Still experimenting with it and working on creating a list of all pages in relation to extensions. [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 15:22, 22 November 2012 (UTC)
::What I'd like to avoid is the messy format somebody did to a few index pages like [[Compression]], where each line has separately hyperlinked format names and extensions (not always in a consistent order) where often one or the other is a redlink, or one redirects to the other, or one is just a disambiguation page, making a somewhat confusing hodgepodge. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:22, 21 November 2012 (UTC)
:::I've started rearranging the Compression page to be a little less messy. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:56, 22 November 2012 (UTC)

== So now what? ==
The official month of this project is now over... what are the plans for the site now? It's made a good start at documenting file formats, but has a good long way to go yet. (A project like this can never possibly be "finished", since there are always more file formats coming out of the woodwork, both new ones that are introduced, and old ones that are discovered.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 05:10, 1 December 2012 (UTC)
: This is an awesome project and I will stay committed to it. Of course this first month is just a start. Let's roll people! [[User:Maurice.de.rooij|Maurice.de.rooij]] ([[User talk:Maurice.de.rooij|talk]]) 23:22, 3 December 2012 (UTC)

== Anybody else still around? ==
Everybody else seems to have vanished around the middle of December... I'm the only one editing here lately. I hate to put more effort into improving a ghost town... anyone else even reading this? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 23:16, 2 January 2013 (UTC)

: I will be editing more once I get back to work - still don't have a home internet connection and working from the local library computers / girlfriend's netbook over public wi-fi is a pain. It would be nice to see more contributions from others - you can see how much work is left to do on the music section alone, and I've really only been creating stub entries for most things. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:51, 3 January 2013 (UTC)

:Well, I still stop by on occasion, and I've vowed to use the site as my first stop when I come across a file format I don't recognize, but I never made any substantial additions, so I'm not sure if that gives you any useful information. (My edits were mostly technical or editorial.) [[User:Gphemsley|GPHemsley]] ([[User talk:Gphemsley|talk]]) 00:18, 13 January 2013 (UTC)

:I'll be editing from time-to-time. Currently a bit snowed under with other work, but planning to do more later in the year. Would also like to review the InfoBox(es) at some point, to ensure the information on this site can be reliably linked up to other information sources. [[User:AndyJackson|AndyJackson]] ([[User talk:AndyJackson|talk]]) 12:10, 18 January 2013 (UTC)

:I'm here. Like Andy, my workload is quite high, but I'll be popping in and out. --[[User:Rhetoric X|Rhetoric X]] ([[User talk:Rhetoric X|talk]]) 12:31, 18 January 2013 (UTC)

:I dip in and out when I want a challenge (or can stomach the frustration.) [[User:Foxtrot|Foxtrot]] ([[User talk:Foxtrot|talk]]) 11:47, 11 January 2023 (UTC)

:Hi there! I sometimes add a word here or there. I must say this Wiki is pretty good now. Popular formats are nicely described and niche formats are just niche formats so it's sometimes hard to add anything about them. I think that maybe it would be helpful to start adding images to posts. An image explaining format details or a screenshot of an image editor may be a nice addition. What about algorithms in pseudo-code? --[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 0:28, 7 September 2018 (UTC)

::A description of file formats and pseudo-codes would be helpful (although you do not necessarily need a picture). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 05:19, 5 May 2019 (UTC)

== Spam ==

I see the spammers have found the site, as I worried would happen; I run a wiki myself ([http://mpedia.dan.info/ MPedia], about things related to Mensa) and have to constantly play whack-a-mole with them; even adding such annoyances (for legitimate users) as a captcha and e-mail confirmation seem to only slightly slow the spammers down. I don't know the solution. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:59, 18 January 2013 (UTC)

:...but "learn-to-read-Korean-in-15-minutes" is a legitimate addition, going to a comic strip explaining the [[Hangul]] writing system, which is in fact a legitimate article here since "file formats" is interpreted expansively to include human written languages. That link ''sounds'' a bit spammy, but if it was from a spammer, it would go to some page selling a dodgy language-learning tool, not a free-to-read resource! (It can start to get tricky distinguishing spam from legitimate stuff when you've got such a wide range of topics here to begin with! Once there's a huge flood of spam to get rid of, there's some danger of legitimate users getting caught in the net too.) [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:03, 18 January 2013 (UTC)

::Yes, it's incumbent on me to make sure we can have people sign up, and be a part of it, without getting spammers. We'll keep exploring. At least bots can't take us on.... I think.... --[[User:Jason Scott|Jason Scott]] ([[User talk:Jason Scott|talk]]) 19:28, 18 January 2013 (UTC)

:::If you've got some tips about how to configure MediaWiki to have open signups but not get the flood of spambots, let me know; that would help me with my own wiki. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:56, 22 January 2013 (UTC)

== Orphaned / Blank Pages ==

I've been making an attempt to clear up some of the orphaned pages, but there are a few I'm not sure of - maybe Dan or someone could sort them out?

* [[Emulation]]
* [[FAQ:File Format]]
* [[File format extensions list]] (seems to be used for the "ext:" pages but hasn't been updated)
* [[Library]]
* [[Original Plan]]
* [[RAD Game Tools]] (should probably have the individual formats moved to appropriate sections)
* [[Statistica]] (clearly belongs in Scientific Data formats, but I'm not sure where)

I've also come across a few pages that should probably be deleted - either because they've been blanked at some point (I know I did this to a few pages) or because they contain data duplicated elsewhere.

* [[AA]]
* [[Compressed executable (.com)]]
* [[SAP]]
* [[Barnes & Noble Fixed-layout Format]]

[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 10:41, 22 January 2013 (UTC)

:OK, I deleted those last three; I'll look at the others. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 12:58, 22 January 2013 (UTC)
:I put Statistica under "Mathematics" in the science category. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 22 January 2013 (UTC)

Hi Dan, got another one for you - I merged the info from [[ODS files created by Microsoft Office 2007 SP2]] into the main [[OpenDocument Spreadsheet]] page. [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 13:59, 25 February 2013 (UTC)

Added Barnes & Noble to the list (made a bit of a mess and forgot about the rename feature) [[User:Johanvanderknijff|Johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 19:05, 21 April 2016 (UTC)

== Permissions for user pages ==

Is there any way we can get permission to delete sub-pages of our own user pages? I've been using mine to draft articles bit by bit, rather than release half-finished articles into the wild, and it would be nice to be able to remove the drafts once complete [[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 12:43, 3 October 2013 (UTC)

:I'm not sure, but as an admin I can delete anything you ask. It might also be possible to use the Move function to move it directly into the intended place. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:45, 3 October 2013 (UTC)

== cd.textfiles.com ==
All the files on http://cd.textfiles.com/ disappeared a few days ago, breaking about a million links on this wiki. Does anyone have any information about that? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 18:48, 25 January 2015 (UTC)

:As I recall from Jason's Twitter feed, he had some server problems, with most of his sites going down at least temporary, and most of them eventually coming back up, but maybe that one had a harder crash. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:50, 25 January 2015 (UTC)

== Broken image in footer ==
The "Creative Commons 0" image at the bottom of every page (https://www.mediawiki.org/w/skins/common/images/cc-0.png) is broken. Can that be fixed? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:06, 10 July 2015 (UTC)
:Still broken 5 years later... Is this place even maintained? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 23:23, 12 March 2021 (UTC)
::Ok so it appears it should probably be [https://licensebuttons.net/l/zero/1.0/88x31.png this image], it matches the 88x31px that the HTML claims the image would be if it was there. Who maintains this site so it can be fixed? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 00:01, 13 March 2021 (UTC)
:::I guess that would be Jason Scott. I'm an admin, but if I have any ability to edit that part of the site I have no idea how. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:31, 13 March 2021 (UTC)

== Wikipedia links ==
At least in my geographical area, Wikipedia has been redirecting "http:" links to "https:". So, all of the <nowiki>[[Wikipedia:...]]</nowiki> links in this wiki are getting redirected. Could/should we change these links to use "https:" directly?

The magic "RFC" links like RFC 822 could also use https:, though the http: links still work. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:10, 10 July 2015 (UTC)

== Google Code ==
We still have around 50 articles that link to Google Code. My understanding is that the next phase of Google Code's shutdown process will happen on 2016-01-25 (two weeks from today). It would be good to update as many of these as possible before then.
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=http%3A%2F%2Fcode.google.com&namespace= links to http://code.google.com]
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fcode.google.com&namespace= links to https://code.google.com]
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:05, 11 January 2016 (UTC)

== Cleanup of top-level categories ==
(Call for objections.) I want to do some cleanup of the [[:Category:Top Level Categories|top-level categories]], and make sure there's at least one category for virtually every article. (See [[Special:UncategorizedPages]].) My plans:
* A new "Meta" category, for articles about the File Formats Wiki (e.g. [[FAQ]], [[Original Plan]], [[Statement of Project]], [[Main Page]], ...).
* Rename the [[:Category:Geek humor|Geek humor]] category to "Humor"
* Remove the [[:Category:Computer facts|Computer facts]] category
* A new "Information" category, for relevant informative articles ([[Ontology]], [[Patents]], ...) that don't have a more suitable top-level category.
* Maybe someday: A category named "Devices", or "Hardware", or even "Things". Most computers and [[Networked devices]] just aren't formats, IMHO. (But I'm not going to delete the infobox from all the "Networked devices" articles. If we can't figure out a way to have infoboxes for nonformats, then I'll leave them be.)
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 15:56, 1 June 2017 (UTC)

[[Category:Meta]]

== Love It! ==
Hi there, kudos to all you guys who helped create this valuable resource. Wikipedia is such a snob when it comes to detailed technical documentation so this wiki is a lifesaver. I added a few things to:

* [[SWF#Software]]
* [[FLA#Software]]
* [[BSON#Libraries]]

Thanks again!

PS: Can the "thumbs up" icon be changed to something better? Do you want me to design a possible logo?

[[User:Hgupta|Hgupta]] ([[User talk:Hgupta|talk]]) 05:42, 17 August 2017 (UTC)

:Nice work! As for the thumb icon, you'd have to ask Jason Scott, the owner of this site (and the one who put the thumb up). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 13:02, 17 August 2017 (UTC)

:I support the idea of changing the logo. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:08, 18 August 2017 (UTC)

== What time is it? ==
I'm making this edit at 17:10 UTC, but the timestamp is: [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 17:25, 2 May 2018 (UTC)
:"Does anybody really know what time it is; does anybody really care?" -- Chicago
[posted at 01:20 UTC; let's see when it thinks it is] [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 01:36, 3 May 2018 (UTC)

== Type / Creator codes ==

Curious what everyone's thoughts are on collecting Type/Creator Codes for Macintosh formats. There seems to be a few attempts at doing this around the webs. Is there a way here to gather them all into one area of the wiki? --[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 17:46, 4 May 2019 (UTC)

* [[Wikipedia:Type_code|Type Code : Wikipedia]]
* [[Wikipedia:Creator_code|Creator Code : Wikipedia]]
* [http://www.lacikam.co.il/tcdb/ TCDBx unmaintained]
* [https://vintageapple.org/macprogramming/pdf/The_Programmers_Apple_Mac_Sourcebook_1989.pdf The Programmers Apple Mac Sourcebook]
* [https://www.macdisk.com/macsigen.php Mac Signatures]

:Maybe do it similar to how file extensions are handled, as an item in the infobox that links to a category? [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 19:09, 4 May 2019 (UTC)

::An article for Mac type/creator codes has been on my to-do list for a while, so we could at least do that, and see if there's any interest in listing lots of codes there. Should it be one article, or two? FormatInfo already has a "type code" param that is supposed to be for the Mac code. Maybe we are supposed to make a "Type Code" template to go along with it, so we can do like "<nowiki>|type code={{Type Code|XXXX}}</nowiki>". [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:07, 4 May 2019 (UTC)

:::If they were listed in a single article as opposed to a series of categories, I don't see what there would be for a template would do. In that case, the text on the left side of the infobox could link to the list page (although this might be ugly). (It would be convenient if there was something between the complexity of the MediaWiki category system and a list page, but I don't think anything like that exists in a plain Mediawiki installation.) [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:30, 4 May 2019 (UTC)

::Even if they went into the infobox, the category system could potentially be left out out, as is currently done with FOURCCs and MIMETypes (the latter links to an external database, but whether anything is there is based on luck more than anything else, as there are so many unregistered mimetypes). These can still be found with the wiki's search feature. [[User:Effect2|Effect2]] ([[User talk:Effect2|talk]]) 21:13, 4 May 2019 (UTC)

:::And there's also the Creator Code, as noted above; that refers to what program created the file, so there might be several associated with one file type code (and several file type codes associated with one creator). Perhaps there needs to be a section of the article listing all the code values associated with a given format and/or program (depending on what's covered by the article). [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 21:44, 4 May 2019 (UTC)

::I like the idea of at least a uniform template for using codes within format descriptions. Since most of the files from the early macintosh days don't have an extension, unless they were cross platform and the Windows extension is used, then the only way to identify the file is from its Type/Creator code. I don't think Apple ever released the full registry, but some estimates are well over 50,000 entries.--[[User:Thorsted|Thorsted]] ([[User talk:Thorsted|talk]]) 03:24, 5 May 2019 (UTC)

== Reverse engineering formats ==
I am trying to reverse engineer some formats. Sometimes successfully, sometimes not. My most recent attempt is:
* http://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)

Maybe we can do this together instead of everyone here focusing on different things? Also is there a better way to discuss things than writing here?
[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 01:39, 9 May 2019 (UTC)

:You should set up a NNTP for reverse engineering file formats discussions (if there isn't already the appropriaate newsgroup). (I had done some of my own reverse engineering file formats too, but I have not set up a NNTP to discuss them. I do have a NNTP server, so you can suggest newsgroups there if wanted, I suppose) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:26, 23 August 2021 (UTC)

== CAPTCHA ==

AT is no longer on EFnet: https://archiveteam.org/index.php?title=Archiveteam:IRC#Special_ArchiveTeam_IRC_rules [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC)

: This is a pretty serious problem. Are there any plans to fix it? -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:22, 12 November 2020 (UTC)

:: <del>Seems like it has been fixed, by removing the CAPTCHA altogether.</del> [2021-12-30 edit: I spoke too soon; still 'efnet'.] Let's all keep a keen eye out for spamdalism. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 03:33, 23 November 2020 (UTC)

== [[special:interwiki]] ==
don't see it at [[special:specialpages]]? [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 02:57, 8 November 2020 (UTC)

: Perhaps the [https://www.mediawiki.org/wiki/Extension:Interwiki Interwiki extension] is not installed? — [[User:Rjt|rjt]] ([[User talk:Rjt|talk]]) 15:16, 30 December 2023 (UTC)

== List of my idea what maybe should be added on ==
My idea of what things I think that probably should be added on (when someone has the information of it to add):
* TRON character encoding
* TRON Application Databus
* BANCStar
* C67 (music)
(I might add a few others later if I will remember some more later, too) --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 09:30, 31 July 2021 (UTC)

==Hello==
I’ve joined and made a few edits. Starting with the Linux page by modification of the attribution of Linux to iOS, which is BSD.
Mad a few tweaks to HLP by creating a page for the source file.
As a retro tech enthusiast I think I could help a bit on some of the older files. Especially tape and disk formats; then, and their modern emulation files. As well as format info.
You can take a look at the original writeup I did here [http://wiki.digital-digest.com/index.php?title=History_of_AV]. Thought it has errors and is considerably lacking many formats.

==SSL and SEO==
SSL has been a factor in web site indexing for a while https://security.googleblog.com/2014/08/https-as-ranking-signal_6.html. Anecdotally I am seeing this more profoundly with personal websites. I wonder if Just Solved can be upgraded to HTTPS sometime in the near future. This should help SEO rankings which benefits us all as it attracts more users. It also protects us using the site too. [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 07:34, 3 January 2023 (UTC)

:You'd have to ask Jason about this server-level stuff. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 16:16, 3 January 2023 (UTC)

:Please do not make TLS mandatory. However, optional TLS is a good idea. --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:13, 5 January 2023 (UTC)

:NB. SSL is listed with further rationale in the TODO: http://fileformats.archiveteam.org/wiki/JustSolve:To_Do [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 09:49, 11 June 2024 (UTC)

== Mediawiki version ==

What are the plans to upgrade this site? Wikimedia is currently at 1.38, Just Solved File Formats is 1.19 with it's dependencies MySQL and PHP somewhat far behind current standards too. [[User:Ross-spencer|Ross-spencer]] ([[User talk:Ross-spencer|talk]]) 07:34, 3 January 2023 (UTC)

: Over the past six weeks, I've sent a few emails to Jason Scott asking how we could get some maintenance for this site. Although he has replied, with some indication that he might be willing to help, I haven't been able to figure out the right thing to say to make that actually happen. At this point, I'm not optimistic that my emails will be sufficient. -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 14:48, 25 February 2023 (UTC)

:: [[special:version#Installed_software]] is where MW stores the version, for anyone wondering. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 05:08, 3 January 2025 (UTC)

== About this community portal ==

Hi there! I'm a new editor here <sup>^^</sup> I would like to know a bit more on the status of the project.

Also, I've noticed that both this page and its associated [[{{TALKPAGENAME}}|talk page]] are being used as the community portal. I think we should choose just one of them, consolidate all the discussion there, and redirect the unused page to the one we decide to keep.

For reference, Inkipedia uses the [https://splatoonwiki.org/wiki/Inkipedia_talk:Ink_Pump talk page] as the central community space, with the project page redirecting to it, which works well since the talk page includes an "Add topic" button for easy participation. [[User:It's moon|It's moon]] ([[User talk:It's moon|talk]]) 04:18, 23 May 2025 (UTC)

== File information template ==

On another topic, would y'all be interested in having a template to add to file pages so we can provide license, source and author info? I created [https://deadmau5.miraheze.org/wiki/Template:File this template] on another wiki I edit. [[User:It's moon|It's moon]] ([[User talk:It's moon|talk]]) 04:18, 23 May 2025 (UTC)

== CAPTCHA issue ==

The other day I made some edits to the [[Quattro_Pro]] page. I was able to save most of them, but after another edit that inserted a "references" tag I end with a CAPTCHA: "Your edit includes new external links. To help protect against automated spam, please answer the question that appears below", with the "question" being "Write wiki@textfiles.com to ask for an account". This is a bit puzzling as I already have an account and I'm seeing this while logged in! Does anyone know why this happens (or better, have a fix)? Thanks!

[[User:Johanvanderknijff|Johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 11:55, 3 June 2025 (UTC)

:Try inputting the password that was provided via email, when creating your account. [[User:Anonymoususer852|Anonymoususer852]] ([[User talk:Anonymoususer852|talk]]) 21:45, 30 July 2025 (UTC)

:: What about when I never received verification email and I still can't make any constructive edits due to it? [[User:265 993 303|265 993 303]] ([[User talk:265 993 303|talk]]) 07:50, 22 February 2026 (UTC)

== Removing copyrighted images ==

There are some images on the wiki that are likely copyrighted, and thus are not suitable for the wiki's CC0 license. In particular:
* [[:File:Boyfriend.gif]], [[:File:Girlfriend.png]] (art assets from the game Friday Night Funkin; see [https://web.archive.org/web/20250511162953/https://en.wikipedia.org/wiki/File:Boyfriend-2.png discussion of copyright situation at Wikipedia])
* [[:File:Arcade-gaming-1361761483gDu.jpg]] (the author might have uploaded this to the internet as "public domain", but the focus of the image is a screenshot of the copyrighted Sega game ''Rambo'')
Is there a standard way to request their deletion? [[User:Havoc Crow|Havoc Crow]] ([[User talk:Havoc Crow|talk]]) 06:10, 28 June 2025 (UTC)
:If nothing else, there should be contact information at [[Talk:Main Page]].

Since none of these images are currently in use on any page, and the copyright status has been brought into question, I have deleted them. [[User:Dan Tobias|Dan Tobias]] ([[User talk:Dan Tobias|talk]]) 18:30, 22 February 2026 (UTC)

== IRC links are invalid on Main page ==
<s>[[Main_Page]] contains potentially obsoleted IRC server and channel. These should be pointed to Hackint IRC network with the same channel name; #justsolve. I don't have permissions to edit that page, or create talk page for that.</s>

<s>[[User:Anonymoususer852|Anonymoususer852]] ([[User talk:Anonymoususer852|talk]]) 18:35, 2 August 2025 (UTC)</s>

This is already noted on [[JustSolve:To_Do]], under "Admin side". --[[User:Anonymoususer852|Anonymoususer852]] ([[User talk:Anonymoususer852|talk]]) 18:47, 2 August 2025 (UTC)

Game data files

2026-02-22T18:27:30Z

Dan Tobias: Put new image since old one was removed for copyright issues.

{{FormatInfo
|formattype=electronic
|thiscat=Game data files
|image=Arcade-game-boy.png
}}

==Overview==
Many popular games use proprietary file formats to store their assets. These include custom image, sound and video formats and custom archive formats. There is no way that all of these can be enumerated here in some way or another. And as long as the games can still be run by an [[Emulation_Software|Emulator]] it's not that much of a deal. However, a lot of work has been put into deciphering, decrypting and hacking these files, and that work should be preserved.

See also: [[Interactive Fiction]] for data formats related to text adventure games, [[Puzzles]] for puzzle-game files, and [[Saved Games]] for data saved by games to store a player's game status.

==References==
* [http://wiki.xentax.com Xentax Wiki]
* [http://rewiki.awiki.org ReWiki]
* [http://aluigi.altervista.org/quickbms.htm QuickBMS], a tool suite to describe archives in an abstract BASIC-like language, and lots of scripts for even more games

==General Game Formats==

This section details formats such as [[Interplay ACM]] and [[Unreal Music Format]] which are used in a number of games.

=== Archiving / Compression ===
* [[CFL]]
* [[Electronic Arts LIB Game Archive]]
* [[FAR (The Sims)]]
* [[HMM Packfile]] (.PAK)
* [[Remedy Archive System]]
* [[Unity package file]]

===Audio / Music===
(see also [[Audio and Music]])

* [[BAKA]] (PCM 16 bit)
* beatmania / IIDX simulation
** [[BMS]]
* [[BH2PCM]] (extracted from [[Doom WAD]] by eXtendable WAD Editor)
* [[BNSF]] (IS14)
* Commodore Amiga
** [[AC1D-DC1A Packer]]
** [[AMOS Music Bank]]
** [[Channel Players]]
** [[Digital Illusions]]
** [[Game Music Creator]]
** [[Jason Page]]
* Electronic Arts
** [[Electronic Arts MUS]]
* [[Epic Megagames MASI]]
* id Software
** [[Doom MUS]]
** [[id Software Music Format]]
* [[Interplay ACM]]
* [[Inverse Frequency Sound format]]
* [[Ken's Adlib Music]]
* [[Sierra AGI]]
* [[Sierra SCI]]
* [[Westwood Studios ADL]]
* [[Westwood Studios AUD]]
* [[Xbox IMA ADPCM]]
* Nintendo GameCube / Wii
** [[Nintendo GameCube / Wii AST]]
** [[Nintendo GameCube / Wii BRSTM]]

=== Game programming languages ===

* [[Blitz3D]]
** [[Blitz3D Model]]

(see also [[Programming Languages]])

=== Other ===

* Allegro (game programming library)
** [[Allegro packfile]]

* Atari
** [[STOS memory bank]] (.mbk)

* Bitsboard
** [[Bitsboard board]]

* Blizzard Entertainment
** [[BLP]]
** [[MDX (Blizzard)|MDX]]
** [[MoPaQ]]

* Build Engine
** [[ART (Build Engine ART)]]
** [[DAT (Build Engine Palette)]]
** [[GRP (Build Engine Group Archive)]]

* [[D3TV]]
* [[DIV Games Studio]]

* Electronic Arts
** [[Electronic Arts CMV]]
** [[Electronic Arts INF]]
** [[Electronic Arts MAD]]‎
** [[Electronic Arts MOV]]
** [[Electronic Arts MPC‎]]
** [[Electronic Arts TGV]]
** [[Electronic Arts WVE]]

* Free Hero Mesh
** [[Free Hero Mesh class definition file]] (.class)
** [[Free Hero Mesh class resource file]] (.xclass)
** [[Free Hero Mesh level file]] (.level)
** [[Free Hero Mesh solution file]] (.solution)
** [[Free Hero Mesh code page file]]
** [[Free Hero Mesh composite puzzle set]]

* Hero Mesh
** [[Hero Mesh puzzle set]] (.mb)

* id Software
** [[BSP]] (map format used in Quake)
** [[Doom WAD]]
** [[Quake PAK]]
** [[Quake PK3]] (actually [[ZIP]])
** [[Quake WAD]]

* Infinity Engine
** [[BAM]]

* [[MegaZeux]]

* NetImmerse / Gamebryo Engine
** [[KF]]
** [[NIF]]

* Nintendo GameCube
** [[Nintendo GameCube Opening.bnr]]

* Nintendo GameCube / Wii
** [[DOL (Nintendo)]]
** [[RARC]]
** [[Yaz0]]

* Nintendo Wii
** [[BootMii NAND Dump]]
** [[BRFNT]]
** [[Mii Data]]
** [[Nintendo Wii BRLAN]]
** [[Nintendo Wii BRLYT]]
** [[Nintendo Wii BRRES]]
** [[Nintendo Wii Content.bin]]
** [[Nintendo Wii Data.bin]]
** [[Nintendo Wii Opening.bnr]]
** [[Nintendo Wii PAC]]
** [[Nintendo Wii PCS]]
** [[Nintendo Wii REL]]
** [[Nintendo Wii Savegame]]
** [[Nintendo Wii SEL]]
** [[Nintendo Wii Ticket]]
** [[Nintendo Wii TPL]]
** [[Nintendo Wii U8]]
** [[Nintendo Wii Update.inf]]
** [[Nintendo Wii VFF]]
** [[Title metadata]]
** [[Virtual Console CCF]]
** [[WAD (Wii)]]
** [[WiiConnect24 file]]

* [[OHRRPGCE]]

* [[Outerra engine]] (.otx) (used in Anteworld game)

* Raven Software game engine
** [[GLA]] - Ghoul animation (.gla)
** [[GLM]] - Ghoul mesh (.glm)

* [[RES (Gromada)]]

* Sokoban
** [[Softdisk Publishing UDF files]] (used for Softdisk's version of Sokoban)
** [[SOK (Sokoban)]]
** [[Sokoban XML]]

* Terminal Reality [https://github.com/jopadan/termpod/wiki/Terminal-Reality]
** [[POD1]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-1-Format-Reference] (no CRC)
** [[POD2]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-2-Format-Reference] (CRC=[[CRC-32#CRC-32/MPEG-2|CRC-32/MPEG-2]])
** [[POD3]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-3-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD4]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-4-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD5]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-5-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD6]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-6-Format-Reference] (no CRC)
** [[EPD]] (.epd) [https://github.com/jopadan/termpod/wiki/Epd-Format-Reference] (CRC=CRC-32/MPEG-2)

* Tiled
** [[Tiled JSON]]
** [[Tiled TMX]]
** [[Tiled TSX]]

* Torque 3D game engine
** [[DTS]] (.dts)

* Valve Source Engine
** [[Valve Model Format]] (.mdl) [https://developer.valvesoftware.com/wiki/MDL Source Code]
** [[Valve Collision Model]] (.phy)
** [[Valve Map Format]] (.vmf)
** [[Valve Material Type]] (.vmt)
** [[Valve Vertex Data]] (.vvd)
** [[Valve Texture Format]] (.vtf)

* Xtremeworlds
** [[Xtremeworlds PWX]]
** [[Xtremeworlds map]]

* [[ZZT]]
** [[ZXT/ZAX]]

* [[ZZ Zero]]

==Individual Game Formats==

This section details formats which are specific to a single game (or perhaps a game series), such as [[God of Thunder Music Format]].
* 7 Days to Die
** [[TTS Prefab]] (.tts)
** [[7DTD Map File]] (.map)
* Age of Empires
** [[Data Resource File]] (.drs)
** [[Age of Empires Graphics File]] (.slp)
* Age of Mythology
** [[BAR (Age of Mythology)]] (.bar archive)
* Alter Ego (1986)
** [[Alter Ego Vignette Script format]]
* Arma
** [[Arma PBO]] (.pbo)
* Barony
** [[Barony Voxel]] (.vox)
* Blur
** [[BAF]] (Blur ADPCM)
* BVE, OpenBVE, Boso View Express (railroad simulator)
** [[BVE object formats]]
** [[BVE route formats]]
** [[BVE train.dat file]]
* Carnivores
** [[CAR (Carnivores)]] (.car)
* Cartooners
** [[Cartooners actor file]] (.act)
** [[Electronic Arts INF‎]] (.inf)
** [[Electronic Arts MOV]] (.mov)
** [[Electronic Arts MUS]] (.mus)
* Chasm: The Rift
** [[CAR (Chasm: The Rift)]]
* Cities Skylines
** [[Cities Skylines CRP]] (.crp)
* Commander Keen 1
** [[Commander Keen 1 Level format]] (.ck1)
* Core Wars
** [[RBJ (Redcode oBJect)]] (.rbj)
* Crystal Caves
** [[Crystal Caves Sound format]] (.snd)
* Dance With Intensity
** [[Dance With Intensity simfile]] (.dwi)
* Dangerous Dave
** [[Dangerous Dave level format]]
** [[Dangerous Dave tileset format]]
** (also uses [[Inverse Frequency Sound format]])
* Dark Reign
** [[FTG (Dark Reign)]]
** [[PAL (Dark Reign)]]
* Dofus
** [[Dofus localization]]
* Donkey Konga 2
** [[Donkey Konga 2 DSP]]
* Doom
** [[Doom cheat code encryption]]
** [[Doom MUS]] (.mus)
** [[Doom WAD]] (.wad)
** [[Doom DWD]] (.dwd)
** [[DeHackEd patch]] (used by the Doom modding community)
* DTX Mania
** [[DTX Mania simfile]]
* Duke Nukem
** [[ART (Duke Nukem 3D)]]
** [[DAT (Duke Nukem 3D)]]
** [[Duke Nukem level format]]
** [[Duke Nukem graphics format]]
** [[GRP (Duke Nukem 3D)]]
* Fallout
** [[Fallout character description]] (.gcd)
* Friday Night Funkin
** [[Friday Night Funkin mod]]
* Garry's Mod
** [[Garry's Mod Addon]] (.gma)
* God of Thunder
** [[DAT (God of Thunder)]]
** [[God of Thunder Music Format]]
* Grand Theft Auto
** [[RAGE Package Format]] (.rpf)
** [[RenderWare binary stream file]] (.dff)
* In the Groove
** [[In the Groove PCK]] (.pck)
* Jack Nicklaus Golf & Course Design: Signature Edition
** [[JNSE golf course]]
* Kick It Up
** [[Kick It Up simfile]] (.ksf)
* Lego Island
** [[Lego Island World Database]] (.wdb)
* Magic & Mayhem
** [[Magic & Mayhem sprites file]]
* Mario Kart Wii
** [[Wii BTI]]
* Mario Paint
** [[Mario Paint Composer]]
** [[SHI]]
** [[SHO]]
* Mass Effect
** [[AFC]] (AFX audio file; Mass Effect 2)
* MegaZeux
** [[MegaZeux Property List]]
* Minecraft
** [[Minecraft Alpha level format]]
** [[Minecraft Anvil format]]
** [[Minecraft Bedrock Edition level format]]
** [[Minecraft chunk format]]
** [[Minecraft classic level format]]
** [[Minecraft classic server protocol]]
** [[Minecraft generated structures format]]
** [[Minecraft Indev level format]]
** [[Minecraft Java Edition level format]]
** [[Minecraft loot table]]
** [[Minecraft map item format]]
** [[Minecraft model]]
** [[Minecraft NBT format]]
** [[Minecraft player format]]
** [[Minecraft raids.dat format]]
** [[Minecraft Region format]]
** [[Minecraft server_level.dat]]
** [[Minecraft server list format]]
** [[Minecraft structure block file format]]
** [[Minecraft scoreboard format]]
** [[Minecraft sounds.json]]
** [[Minecraft villages.dat format]]
** [[Schematic file format]]
* Mortal Kombat 4
** [[Mortal Kombat 4 filesys.dat]]
* Pokémon
** [[Pokémon Mystery Dungeon]]
** [[Pokémon ROM]]
** [[RMC]]
* Quake
** [[MD2]] - Quake 2 model format (.md2)
** [[MD3]] - Quake 3 model format (.md3)
** [[MD4 (Quake)|MD4]] - Quake MD4 model format (used in later Quake 3 versions) (.md4)
* Rise of the Triad
** [[Rise of the Triad level format]]
** (also uses [[Doom WAD]])
* RobotWar
** [[RobotWar|RobotWar programming language]]
* Sims, The
** [[CFP]] (Compressed Floating Point)
** [[CMX/BCF]]
** [[FAR (The Sims)]]
** [[IFF (The Sims)]] (.iff, .flr, .wll, .spf, .stx)
** [[SKN/BMF]]
* StarCraft
** [[StarCraft group file]] (.grp)
* StepMania
** [[StepMania simfile]] (.sm)
** [[StepMania 5 simfile]] (.ssc)
** [[StepMania AMX simfile]] (.sma)
* Stronghold
**[[Stronghold GM1]] (.gm1)
**[[TGX Graphics]] (.tgx)
* Supaplex
** [[Supaplex Level format]] (.dat)
* Super Mario Galaxy
** [[Super Mario Galaxy savefile]]
* Super Paper Mario
** [[BRSTMPSM]] (music data)
* Total War
** [[Total War ESF]] (.esf)
* Vinyl Goddess From Mars
** [[Vinyl Goddess From Mars Instrument Format]]
** [[Vinyl Goddess From Mars Music Format]]
* Warcraft
** [[Warcraft II PUD]] (.pud) (custom maps)
* Wiggle Planet
** [[Wiglet]]
* Wii Fit / Wii Fit Plus
** [[Wii Fit BMG]]

== Game hints ==
* [[UHS]]

== Board/card games ==
* [[Magic Set Editor]]
** [[Magic Set Editor card set]] (.mse-set)
** [[Magic Set Editor export template]] (.mse-export-template)
** [[Magic Set Editor game definition]] (.mse-game)
** [[Magic Set Editor include package]] (.mse-include)
** [[Magic Set Editor installer]] (???)
** [[Magic Set Editor style sheet]] (.mse-style)
** [[Magic Set Editor symbol font]] (.mse-symbol-font)
* [[REKO Cardset]]
* [[TeXnicard]]
** [[TeXnicard card database]]
** [[TeXnicard template]]
* [[Wiz Solitaire]]

== Uncategorized ==

* [[RBPACK]]

== External links ==

* [http://www.osti.gov/accomplishments/videogame.html Possibly the first video game, in 1958]
* [https://archive.org/details/Nintendo_Ultra64_Programming_Manual Nintendo Ultra64 Programming Manual]
* [http://ukvac.com/forum/topic335921.html Sega Pengo: bug found in maze generating algorithm]
* [http://www.stavros.io/posts/winning-candy-crush/ How to 'hack' Candy Crush]
* [http://www.glitchthegame.com/public-domain-game-art/ Glitch game files, released into the public domain]
* [https://github.com/jmechner/Prince-of-Persia-Apple-II Prince of Persia source code (Apple II)]
* [http://sourceforge.net/projects/dice/ DICE: emulator of early discrete-circuit video games]
* [http://www.polygon.com/2014/4/22/5640114/maze-invaders-atari-arcade-source-code-strong-museum-icheg Museum acquires 'virtually complete' source code from Atari's arcade heyday]
* [https://archive.org/details/pdp1_spacewar Spacewar! for the PDP-1 (1962)] (with in-browser emulation)
* [http://tcrf.net/Category:Games_with_hidden_developer_messages Games with hidden developer messages]
* [http://www.loc.gov/preservation/resources/rfs/softgame.html Library of Congress Recommended Format Specifications: Software/Gaming]
* [https://github.com/keendreams/keen Keen Dreams Source Code (open-source release)]

File:Arcade-game-boy.png

2026-02-22T18:26:13Z

Dan Tobias: Public domain: Source https://www.publicdomainpictures.net/en/view-image.php?image=299366&picture=arcade-game-boy License: CC0 Public Domain Dawn Hudson has released this “Arcade Game Boy” image under Public Domain license. It means that you can ...

Public domain: Source https://www.publicdomainpictures.net/en/view-image.php?image=299366&picture=arcade-game-boy

License: CC0 Public Domain

Dawn Hudson has released this “Arcade Game Boy” image under Public Domain license. It means that you can use and modify it for your personal and commercial projects. If you intend to use an image you find here for commercial use, please be aware that some photos do require a model or a property release. Pictures featuring products should be used with care.

Category:File formats with extension .lit

2026-02-22T18:06:55Z

Dan Tobias: Created page with "L"

[[Category:File formats by extension|L]]

BWTC32Key

2026-01-23T23:13:17Z

Dan Tobias:

{{FormatInfo
| formattype = electronic
| subcat = Transfer Encodings
| tpm = Encryption
| developed by = stgiga
| maintained by = stgiga
| spec availability = Free
| error resilience = Yes
| patent license = Unencumbered
| reference impl = https://stgiga.github.io/bwtc32key
| extensions = {{ext|b3k}}
| released = 2019
| magic = 0xFEFF4D00, "bwtc", "nomo", "dfsm", "fenw", 0x4D01
| compression = Always Lossless
| extended from = bzip
| spec = https://github.com/stgiga/bwtc32key
| endianness = Big-Endian
| mimetypes = {{mimetype|application/prs.bwtc32key}}
| wikidata = {{wikidata|Q105859280}}
| }}
'''BWTC32Key''' is a single-file [[compression]] tool and format with optional [[encryption]], that also is text-armored, and also initially defined the 8.3-safe "*.B3K" file extension that was first used by the format.

== Discussion ==
The code is based upon specific [[JavaScript]] implementations of Base32768, [[AES]], [[SHA-256]], and a spiritual successor to the original [[bzip]] format. The code is based upon JS code that runs in pure JS with no dependencies and is housed in the [[HTML]] frontend as a single monolithic program.

The output of the encoder is a text string. .B3K files are always [[UTF-16]] Big-endian text documents bearing the Byte Order Mark that contain said string. That string is a version of Base32768 which uses [[Hangul]] Syllable blocks and Han ideographs to allow font support while keeping size down in bytes. Also, the string is essentially a Korean message but in a different style. The file starts with a header of 0xFEFF4D00 and ends with a trailer of 0x4D01. The file CAN be concatenated, but to reverse that, one must use a text editor to extract the portion you need, due to the way the original program currently works.

All of the code is stream and chunk compatible, and this includes the AES256 implementation which uses the Counter mode. The password field as of 2023 accepts [[UTF-8]] and has never had a length limit. Also, the encryption can be blanked out, allowing the format to be used in things that encryption wouldn't be useful in, such as an image compression format, essentially leaving the encryption feature unused when the password field is left blank or at default.

The format was written in pure [[JavaScript]] and is purely FOSS. The format was written by the author starting at age 15 (the earliest POSSIBLE estimate COULD very well be AROUND 14) and was definitely finished by the time they turned 17. This does show in the code. The compression and encryption functionality of this program coincidentally harks back to the Classic Mac OS days of [[PackIt]], which featured similar sequential concatenation and compression of multiple files and forks into the archive as well as encryption, all far more primitive and inefficient than BWTC32Key.

The Base32768 final step is essentially the antithesis of the original [[BinHex]], because instead of using an algorithm that doubles the binary input size via base 16, the Base32768 step makes the AES256-CTR encrypted BWTC archive (with standard US [[ASCII]] magic number "bwtc" in the Base32768-decoded decrypted compressed BWTC archive, which uses another US-ASCII magic number of "nomo" for the NoModel step of the process, before a DefSum step with yet another US-ASCII magic number of "dfsm" (assuming a compression level of five or lower), followed by the Fenwick Tree-based range coder step that has one more US-ASCII magic number of "fenw", (if the compression level is higher than 5. The five-or-lower is called "Fast mode" in the code.) (All 8-bit and 7-bit US-ASCII variants of these ASCII magic numbers are allowed.) all of which must each be present in their respective steps during each of their respective spots in the decompression steps of the decompression process, which is done last after the AES256-CTR decryption and the Base32768 decoding have completed, which all must successfully happen correctly with everything in the right places and sequences in order for the program to work, which is why all of these magic numbers exist. All of them are used to make the program safer from data corruption and other errors that may occur at any point during the execution of the program.)
compression only 16/15 of the original compressed size prior to the inherently padding-free AES and Base32768 steps, assuming that the UTF-16BE with BOM output is the encoding to be fed into the output text file, which uses the ".B3K" extension instead of the .txt extension that is normally used for standard plain text documents. It should be noted that since the BWTC compressor is very simple compared to even the original bzip, and that the 256-bit [[AES]] variety used uses the counter mode which needs no padding at all, the BWTC32Key format is very slim and subtle in every possible way.

As a text based format that closely resembles human text, it can be used where text is exclusively required (in most cases), while also being similar in spirit to authentic human scripts, which allows it to be injected into written works as if it were a Korean section of actual human writing, with no humanly-distinguishable traces at all. Also, due to it being stream compatible, broadcasting it can be done as a means of sending data through live channels as a stream of data one could opt into. Another feature it has is that it will never decode corrupt input, without computing anything. Meaning, it will fail if the magic number of the BWTC archive ("bwtc") (or the other magic numbers) isn't present in the compressed data due to corruption or the wrong key, or if the Base32768 text itself has junk thrown in or isn't properly formed or decodable. And if the corruption corrupts the Base32768 text data itself, or even the UTF16BE (with BOM) encoded Base32768 text itself, it will also fail in either case. This ensures that corrupted files will not be created by the decoder or your system, which can help stop damage to your system if something like a firmware blob or an executable was affected. This format does not care about file information of any kind. Hence, this is why it can be used as a chunk or stream format in cases where file info isn't needed. This is only possible because of the encryption feature being optional to apply to the input, thus allowing data (such as uncompressed image data, typeface data, soundbank data, and open streams) that would be pointless and unwise to encrypt to be able to be used with this format. As mentioned before, live input streams are allowed, and real time data input is as well. And in other implementations, multiple files could be encoded and then concatenated, optionally with different keys per file, all with the right logic.

The format is well suited to tarred input because tar files are a text-like block and stream based format that has many null bytes, all of which make the tar format very similar to the rest of the entire BWTC32Key format itself. Thus, it is a match made in heaven, and that means that it is a good idea to use tarred input for that very same reason.

The Korean text output does not interfere with actual Korean because Zhuyin (also known as Bopomofo) and Hangul Jamo can be used to replace the Han ideographs (Hanja), and Korean syllable blocks (Hangul) respectively in a message running alongside the data. Thus, it does not render Korean communication impossible when using it, which allows for use in textual messages as if it were native text but with the extra feature of not locking out anyone's language from being spoken there. This means one can seamlessly put this in something like a written work in txt format. This is superficially similar to using [[PGP]] on part of a written work in regards to how the headers and text encoding work. BWTC32Key is its own animal entirely though, and the details may require accurate emulation to ensure that nothing messes up in ports/etc. Coincidentally, the letter "K" in the ".B3K" file extension can be interpreted as a reference to the format using Korean-esque text as its output, which is similar in meaning to the format's intentional usage of UTF16BE in order to alphabetically match up the "BE" part of UTF16BE to the "B3" part of the ".B3K" file extension. On systems with all-caps filenames, the ".B3K" file extension has the extra bonus feature of properly acronyming the full name of the format according to most rules for capitalized acronym casing. Also it can do camel case if required but mostly to avoid bugs. Also the .B3K extension being an unclaimed 8.3-safe file extension was quite lucky and useful given how it's friendly to older hardware if ported to something like C.

Some things to note: In 2022, support for the program generating and reading its own files without needing the user to manually paste the string was added (this also made it so that the files are done correctly. UTF-8 harms the compression savings, and 0xEFBBBFE4B480 is, due to being UTF-8, indicative of wrongful UTF-8 transcoding. The first bytes of .B3K files should be 0xFEFF4D00, not THAT. The ending bytes should be 0x4D01. Basically, reading .B3K files that aren't in compliance with a header of 0xFEFF4D00 and a trailer of 0x4D01 is allowed, but never generate anything that is not that. That being said, because Unicode itself using Big-endian goes against many processor architectures in modern use, this fact isn't intended to be an immovable directive. Basically, the preferred encoding is UTF-16BE.

Also, the program's assumed "application/octet-stream" MIME type from other sources may have fit more in the past, but the canonical and IANA-compliant MIME type that ISN'T generic is "application/prs.bwtc32key", but it is not intended to be implemented in a way breaking existing code using "application/octet-stream". Furthermore, if one is surmising said "application/octet-stream" MIME type, the place it shows up in the code's reference implementation is in the "MIME type" box, which is actually supposed to be the MIME type of a decoded file, not an encoded one. Since the format stores only the data of a file, when decoding it, the user specifies the file name, extension, and MIME type to "download" after decoding. If one wants multiple files, attributes, names, and dates, TAR beforehand is advised. Basically, the developer never gave the program a MIME type until years later, and it's in the prs/personal range for best IANA compliance but if that wasn't a factor there would be no "prs." and it may not be "application" as the family of formats it is under, rather, something like "text/" due to the format being text-based (and by extension not technically binary especially given the number base being 32768 instead of 2). Oh and the developer hasn't contacted the IANA yet due to not wanting to reveal their real name for multiple significant reasons. At least the program is distinct enough and is in the "personal" range of types to keep on the good side of the IANA as best as possible in light of the circumstances.

As for downloading a .B3K with the button in the reference implementation, the code involved downloads whatever is in the output string box as a UTF-16BE text document, and the relevant code assigns a MIME type of "text/plain". Samsung Internet on Android gives a ".B3K.txt" as the file downloaded, but nothing else does. That said, because ANYTHING put into the box gets saved, you don't need a text editor to encrypt text. All you need is to put your text in the box, change the extension in the "B3K filename" box to .txt or the extension of a text-based format of your choice, and download. Then, upload THAT with your desired key. The decoding of files doesn't care what you upload to be put in the box. That code reads whatever you feed it as UTF-16BE. So, after decryption, you can upload the output file into the .B3K uploader, and the text/etc will appear. So, the program can operate as a textual cipher. So trying to make the extension on such a Samsung case be .B3K would actually reduce functionality, albeit unintended functionality, which the program has a LOT of. One of the best ones is password generation and storage, in conjunction with other cryptographic and additional uses, of which there are many.)

Also, in 2022, the Compression Level was allowed to be set by the user rather than hard-coded at 9. It can be made to go higher, which can net extra savings if you are clever. Also, one should test to see whether the output successfully decompresses on a chosen overdriven level. Secondly, it supports going below one, which is helpful if speed is a priority over anything else. Basically, you can go lower than 0.5. The way the compression level in this and in the BZip-family archivers work is that they multiply the level times 100,000 to get the block size. So one can use non-integral numbers if the program lets you, and the developer of BWTC32Key sees no need to restrict to integers between 1 and 9. Also, that year, a fix was found for the reference implementation having problems on newer macOS versions, namely due to their stripping of the Byte Order Mark. Basically, the program was made to behave fine in such a situation.

Additionally, in 2023, fixes were made that don't break compatibility, and one of the side bonuses of the fix was Unicode support in the password box.

In 2024 the SHA-256 got a security fix and the program got some extra UI features involving copy and paste.

So, in the span of several years since the 2019 version, various limitations of the program were lifted thanks to further development.

== Links ==
* The author's format implementation is at [https://stgiga.github.io/bwtc32key/ Github Implementation]
* The github repository is at [https://github.com/stgiga/bwtc32key The Repo]

[[Category:Compression]]
[[Category:Encryption]]

PCX

2026-01-13T15:34:27Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|subcat=Graphics
|extensions={{ext|pcx}}, {{ext|pcc}}
|mimetypes={{mimetype|image/vnd.zbrush.pcx}}, {{mimetype|image/x-pcx}}
|pronom={{PRONOM|fmt/86}}, {{PRONOM|fmt/87}}, {{PRONOM|fmt/88}}, {{PRONOM|fmt/89}}, {{PRONOM|fmt/90}}
|kaitai struct=pcx
|wikidata={{wikidata|Q535473}}
|released=~1984
}}
'''PCX''' is the native image format of the DOS-based program ''PC Paintbrush'' from ZSoft Corporation.

== Discussion ==
PCX was for a time (especially the late 1980s) a very popular image format among users of IBM PC compatibles and the PC/MS-DOS operating system. Much clip art was distributed in this format. However, it was tied closely to platform-specific attributes such as the particular graphic modes available in early PCs, and later lost ground to more platform-independent graphic formats like [[GIF]], [[JPEG]], and [[PNG]].

PC Paintbrush was licensed to Microsoft, and it evolved into the Paint/Paintbrush application included with Windows. The versions for Windows 3.0 through Windows 95 support PCX format. There was also a product named ''Microsoft Paintbrush 2.0''.

It's not clear what PCX stands for, if anything. Some non-authoritative sources claim "PiCture eXchange", others "Personal Computer eXchange".

== Format details ==
A PCX file consists of a 128-byte fixed header (48 bytes of which may be used for a palette), followed by the pixel data, followed in some cases by a 769-byte palette segment.

A number of different PCX specifications can be found on the internet, but unfortunately, they tend to be incomplete, and ambiguous about certain details. Part of this may be the fault of the PCX format. PC Paintbrush itself reportedly may interpret the same file differently, depending on the version of the software, and the graphics mode being used.

The variety of a given PCX file is determined primarily by the combination of the ''bits per pixel per plane'' field at offset 3, and the ''number of planes'' field at offset 65. The following varieties of PCX seem to be common and well-supported:
* bits=1, planes=1: Bi-level, black and white (other colors may be possible, but are not well-supported)
* bits=1, planes=4, version≠3: 16-color, using the palette contained in the header
* bits=8, planes=1: 256-color, using the palette at the end of the file
* bits=8, planes=3: 24-bit truecolor

Unfortunately, there are many other varieties that are not necessarily so portable.

=== Compression ===
The PCX specifications require that all PCX image data be compressed with a form of [[run-length encoding]], indicated by the ''encoding'' field having the value 1. However, modern graphics software often supports uncompressed PCX, in which the ''encoding'' field is 0. You can use [[ImageMagick]] to create such files, if you explicitly disable compression.

=== Transparency ===
We haven't located any PCX specification that mentions transparency, yet some modern graphics software supports 32-bit RGBA format (bits=8, planes=4). [[ImageMagick]] will readily create such files.

The Wikipedia article also suggests a 16-bit RGBA format (bits=4, planes=4).

=== Resolution ===
The PCX header has X- and Y-"resolution" fields (at offset 12), which you might think would help to display PCX images at the correct aspect ratio. Unfortunately, these fields are not reliable. If not set to zero, they might contain any of the following:
* The dots per inch
* The pixel dimensions of the target screen mode
* The pixel dimensions of the image itself
* An obsolete copy of one of the above things.

Some PCX encoders use a separate field, at offset 70, for the pixel dimensions of the target screen mode. However, some PCX files have other data or garbage there.

== Identification ==
The first byte of a PCX file is <code>0x0a</code>. The second byte (the version number) is 0, 2, 3, 4, or 5. The third byte (the ''encoding'') is 1 or (rarely) 0.

== See also ==
* [[DCX]]
* [[Word for DOS screen capture]]
* [[PCX Library]]
* [[MIF (MAXpaint)]]
* [[BMG (Bert's Coloring Programs)]]
* [[VGAPaint 386 PCX Self-Extracting Picture]]

== Specifications ==
* [https://www.fileformat.info/format/pcx/spec/a10e75307b3a4cc49c3bbe6db4c41fa2/view.htm ZSoft Technical Reference Manual, Revision 5]
* [https://www.martinreddy.net/gfx/2d/PCX.txt ZSoft Technical Reference Manual]
** [http://www.textfiles.com/programming/FORMATS/pcx.txt PCX excerpt from the above document]
* [http://www.textfiles.com/programming/FORMATS/pix_fmt.txt Picture format docs (of a number of formats including PCX)]
* [https://moddingwiki.shikadi.net/wiki/PCX_Format PCX Format], from the DOS Game Modding Wiki
* [https://www.drdobbs.com/pcx-graphics/184402396 Dr. Dobb's: PCX Graphics]
* [https://www.fysnet.net/pcxfile.htm PCX graphics files explained]

== Metaformat files ==

* {{Synalysis|pcx}}

== Software ==
* [[ImageMagick]]
* [[Konvertor]]
* [[Netpbm]]: ppmtopcx, pcxtoppm
* [https://www.irfanview.com/ IrfanView] (may require PlugIns package)
* [[XnView]]
* [[FFmpeg]]
* {{Deark}}
* [http://snisurset.net/code/abydos/ abydos]
* [http://toastytech.com/guis/win1x2x.html Applications for Windows 1.x and 2.x] ("For historical preservation")
** [http://toastytech.com/guis/PC%20Paintbrush%20for%20Windows%201.05%20(3.5).zip {PC Paintbrush for Windows} v1.05] (for Windows 1.x and 2.x)
** [http://toastytech.com/guis/pbrushwin122.zip {PC Paintbrush Plus for Windows} v1.22] (for Windows 2.x)
* [https://archive.org/details/art-bonus-pack PCXHDR.EXE tool for viewing PCX headers]

== Sample files ==
* https://samples.ffmpeg.org/image-samples/pcx/
* {{CdTextfilesURL|clipart1996/}} ...
* https://samples.ffmpeg.org/image-samples/pcx/cga/ - Examples of (bits=2, planes=1)
* {{CdTextfilesURL|hof91/icondemo/animals.pcx}} - Example of (bits=1, planes=3, version=3)
* {{CdTextfilesURL|hof91/icondemo/shuttle1.pcx}} - Example of (bits=1, planes=4, version=3)
* [https://archive.org/details/IM_5_96] → WIN/HOME/ITDEMO.ZIP (most .PCX files) - Example of (bits=4, planes=1)
* {{DexvertSamples|image/pcx}}

== Links ==
* {{EGFF|pcx|PCX File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
* [[Wikipedia:PCX|Wikipedia: PCX]]
* [[Wikipedia:PC Paintbrush|Wikipedia: PC Paintbrush]]
* [[Wikipedia:Microsoft Paint|Wikipedia: Microsoft Paint]]
* [https://danielslegacycomputercollections.com/ssg-dos-pc-paintbrush-310.html PC Paintbrush 3.10], from Daniel's Legacy Computer Collections
* [https://danielslegacycomputercollections.com/ssg-dos-microsoft-paintbrush-20.html Microsoft Paintbrush 2.0], from Daniel's Legacy Computer Collections
* [https://www.betaarchive.com/forum/viewtopic.php?t=29671 BetaArchive forum post about PC Paintbrush and PCX]
* [https://archive.org/details/bitsavers_mindsetPCP_4931746 PC Paintbrush manual]
* [http://www.theohupkens.nl/English/PCX.htm The PCX File Format: Very Old and Somewhat Gray]

[[Category:Microsoft]]

Programming Languages

2026-01-07T16:45:56Z

Dan Tobias: /* Programming languages */

{{FormatInfo
|formattype=Languages
|thiscat=Programming Languages
|released=~1950
|image=Babbage difference engine drawing.gif
|caption=Babbage's Difference Engine
}}
'''Programming languages''' are languages expected to be executed (interpreted, compiled, etc.) by a machine in order to perform operations or algorithms. They are distinct from markup languages, which represent the structure of a document rather than specific operations to be performed, though it is possible to combine both in a document (e.g., HTML containing embedded JavaScript, or PHP code which includes HTML). Programming language code is stored as [[source code]] which may be directly interpreted by a machine or compiled or assembled into [[executables]].

== Programming languages ==

* [[ABC (programming language)]]
* [[ActionScript]] (Flash)
** [[ActionScript Byte Code]]
* [[Ada]]
* [[ALGOL]]
* [[Anim8or Scripting Language]]
* [[APL]]
* [[AppleScript]]
* [[APT (programming language)|APT]]
* [[Arc (programming language)|Arc]]
* [[Arduino programming language]]
* [[Assembly language]] (.asm, .s) (various versions for different machine architectures)
* [[Aussie++]]
* [[Austral]]
* [[AutoHotkey]]
* [[AutoLISP]]
* [[AWK]]
* [[B]]
* [[BASIC]] (Beginner's All Purpose Symbolic Instruction Code) (.bas) -- See also [[Tokenized BASIC]]
* [[Batch file]] (DOS, Windows, OS/2)
* [[BCPL]]
* [[BLISS]]
* [[Blitz BASIC]]
** [[Blitz3D]]
* [[BlooP, FlooP, and GlooP]]
* [[Bourne shell script]] (.sh)
* [[Brainfuck]]
* [[Breder]]
* [[C]] (.c, .cc, .h)
* [[C Sharp|C#]] (.cs)
* [[C shell script]]
* [[C++]] (.cpp, .cxx)
* [[C+=]]
* [[CakeML]]
* [[CEEMAC]]
* [[CFEngine]]
* [[CHIP-8]]
* [[ChordQL]]
* [[Clipper (programming language)]]
* [[Clojure]]
** [[ClojureScript]]
* [[COBOL]] (COmmon Business-Oriented Language)
* [[CoffeeScript]]
* [[ColdFusion]]
* [[COMAL]]
* [[COMIT]]
* [[COW]]
* [[Coq]]
* [[CORC]] (Cornell Computing Language)
* [[CPL]]
* [[Crystal]]
* [[CUPL]] (Cornell University Programming Language)
* [[Cython (Pyrex)]]
* [[D]]
* [[Dart]] (was Dash)
* [[Dern]]
* [[dBase programming language]]
* [[DogeScript]]
* [[Dylan]]
* [[Elixir]]
* [[Elm]]
* [[Erlang]]
* [[Expect]]
* [[Extended Batch Language]] (EBL)
* [[F Sharp|F#]]
* [[Fantom]]
* [[Fish shell]] (*.fish)
* [[Flare]]
* [[Flow]]
* [[Forth]]
* [[FORTRAN]] (FORmula TRANslation)
* [[FoxPro programming language]]
* [[Free Pascal]]
* [[Fusion (programming language)|Fusion]] (.fu, .ci)
* [[GAMS]] (.gms)
* [[GDL Script]] - scripting language used in ARCHICAD (.gdl)
* [[Gherkin]]/Cucumber
* [[Go]]
* [[Graphics Programming Language]] (GPL) (mid-level language on TI computers)
* [[Groovy]]
* [[HamsterSpeak]]
* [[Haskell]]
* [[Haxe]]
* [[High Level Shading Language]] (HLSL)
* [[Hoon]]
* [[Hopscotch]]
* [[HyperTalk]]
* [[IDL]]
* [[INTERCAL]]
* [[Ioke]]
* [[Java]] (.j, .jav, .java)
* [[JavaScript]] (JScript, [[ECMAScript]]) (.js)
** [[Node.js]]
** [[React]]
** [[TypeScript]]
* [[JCL]] (Job Control Language; used on IBM mainframes)
* [[JOSS]]
* [[JSONata]] [http://jsonata.org/]
* [[JSX]]
* [[Julia]]
* [[Kotlin]]
* [[LISP]]
* [[LiveScript]]
* [[Logo]]
* [[LOLCODE]]
* [[Lollipop]]
* [[Lua]]
* [[Lurk]]
* [[Machine language]] (various versions for different machine architectures)
* [[MATLAB script file]] (.m)
* [[MDL (programming language)|MDL]] (.mud)
* [[Microcode]]
* [[mIRC scripting language]]
* [[ML]]
* [[MUMPS]] (Massachusetts General Hospital Utility Multi-Programming System)
* [[Music Macro Language]] (.mmi)
* [[Nim]]
* [[Nock]]
* [[NetLogo]]
* [[Object Pascal]] (including Delphi)
* [[Objective-C]] (.m, .h) (used in Mac and iOS development)
* [[OCaml]]
* [[OpenGL Shading Language]] (GLSL)
* [[P (Microsoft programming language)|P]] (Microsoft)
* [[Pascal]] (.pas)
* [[Pawn]]
* [[Perl]] (.pl, .pm)
* [[PHP]] (.php)
* [[Piet]]
* [[PikaScript]]
* [[PILOT]]
* [[Pixie (programming language)|Pixie]]
* [[Pixilang]] (.pixi)
* [[PL/I]]
* [[PLASMA]]
* [[PostScript]]
* [[PowerShell]]
* [[Processing]]
* [[Programmable Command Language]] (PCL), for TOPS-20
* [[Prolog]]
* [[Pyramid]]
* [[Python]] (.py, .pyc, .pyo, .pyd)
* [[QML]]
* [[Q Sharp|Q#]]
* [[Quorum]]
* [[R]]
* [[Racket]]
* [[Raku]]
* [[Rant]]
* [[Ratfor]]
* [[Redcode]]
* [[RenderWare object]] (.rwx)
* [[RobotWar]]
* [[RPG]]/RPGLE/RPG IV/RPG ILE (.rpgle, .sqlrpgle)
* [[Ruby]]
* [[Rust]]
* [[S]]
* [[SAIL]]
* [[Scala]]
* [[Scheme]]
* [[SCODL]]
* [[Scratch]]
* [[Server Side Includes]]
* [[Shen]]
* [[Sikuli]]
* [[Skip]]
* [[Smalltalk]]
* [[SNOBOL]]
* [[Solidity]]
* [[Squiggle]]
* [[Squirrel]]
* [[Standard ML]]
* [[StarLogo]]
* [[Swift]] (Apple) (.swift)
* [[Swift (parallel scripting)]]
* [[SYSDOOM]]
* [[Tabloid (programming language)|Tabloid]]
* [[Tcl]]
* [[TECO]]
* [[TRAC programming language]]
* [[TUTOR]]
* [[TypeScript]]
* [[Verilog]]
* [[vim script]]
* [[Visual Basic]]
* [[VBScript]]
* [[Vue.js]] component files
* [[WaveGL]]
* [[WebAssembly]]
* [[Wenyan]] (文言)
* [[Windows Script File]]
* [[WMLScript]]
* [[Wolfram Language]]
* [[Wuffs]]
* [[ZAP]]
* [[Z-code]]
* [[ZIL]]

== Logical assertion languages ==
* [[SNARK]]

== Query languages ==
* [[Fauna Query Language]] (FQL)
* [[PRQL]]
* [[SPARQL]]
* [[SQL]]

== Templates, macros, preprocessors, etc. ==
* [[Cascading Style Sheets|CSS]]
* [[doT]]
* [[DSSSL]]
* [[Jinja]]
* [[Jsonnet]] [https://jsonnet.org/]
* [[Liquid]] (.liquid)
* [[M4]] (.m4)
* [[Pug]]
* [[Smarty]]
* [[XSL]]
* [[XSLT]]

For additional macro formats, especially binary formats, see [[Executables#Macros or automated scripting]].

See also [[Web#Scripts/Applets/Plug-Ins/Frameworks/APIs/Templating]].

See [[Wikipedia:Category:Template engines]] for another list of template systems.

== Other/Miscellaneous ==
* [[Nomyx language]]
* [[Programmable calculators]]

== See also ==
* [[Development]]
* [[Executables]]
* [[Interactive Fiction]] engines often use specialized programming languages for game development.
* [[Resources]]
* [[Source code]]

== External links ==
===Resources===
* A comprehensive list of over 2000 programming languages and a small sample programs for each of them is available [http://www.99-bottles-of-beer.net/ here]
* [http://rosettacode.org/ Rosetta Code] attempts to present solutions to the same task in different programming languages.
* [http://storify.com/carlzimmer/coding-for-middle-school-girls?utm_content=storify-pingback&utm_source=t.co&utm_campaign=&awesm=sfy.co_s2LP&utm_medium=sfy.co-twitter Coding for middle-school girls] (tips on introducing them to programming)
* [http://langpop.corger.nl/ Programming language popularity chart (based on Github and StackOverflow activity)]
* [http://hivelogic.com/articles/top-10-programming-fonts Top 10 programming fonts]
* [http://www.integralwebsolutions.co.za/Blog/EntryId/901/What-s-The-Most-Popular-Programming-Language.aspx What’s The Most Popular Programming Language?]
* [http://lifehacker.com/which-programming-language-should-i-learn-first-1477153665 Which programming language should I learn first?]
* [http://exple.tive.org/blarg/2013/10/22/citation-needed/ Why array indices start at zero; historical info]
* [http://www.codecademy.com/ Code Academy: learn to code interactively online]
* [http://howto.cnet.com/8301-11310_39-57615356-285/best-free-sites-for-learning-how-to-write-code/ Best free sites for learning how to write code]

=== Commentary ===
* [http://boingboing.net/2013/02/27/what-most-schools-should-reall.html Why you should learn to program]
* [http://mentalfloss.com/article/53160/meet-refrigerator-ladies-who-programmed-eniac Meet the 'Refrigerator Ladies' Who Programmed the ENIAC]
* [http://devblog.avdi.org/2014/01/31/the-moderately-enthusiastic-programmer/ The Moderately Enthusiastic Programmer]
* [http://techcrunch.com/2013/10/10/my-experience-as-a-fourth-grade-hacker/ My Experience As A Fourth Grade Hacker]
* [https://medium.com/learning-to-code/565fc9dcb329 Things I Wish Someone Had Told Me When I Was Learning How to Code]
* [http://michaelochurch.wordpress.com/2012/01/15/the-problem-with-programming-language/ A problem with the term, programming “language”]
* [http://animalnewyork.com/2014/artists-notebook-ramsey-nasser/ Discussion of creating programming languages in Arabic]
* [http://www.viva64.com/en/b/0260/ The Last Line Effect]
* [http://bost.ocks.org/mike/algorithms/ Visualizing algorithms]
* [http://www.playthepast.org/?p=4982 Excavating Code: An Archaeological Record of Software Development]
* [https://medium.com/towards-a-remarkable-career/the-art-of-the-bug-ac5a535315fa The art of the bug: Failure should be fun]
* [https://speakerdeck.com/craigstuntz/incredibly-strange-programming-languages Incredibly Strange Programming Languages (presentation)]

===Humor===
* [http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html A Brief, Incomplete, and Mostly Wrong History of Programming Languages]
* [http://colinm.org/language_checklist.html Programming Language Checklist]
* [http://www.quora.com/Programming-Languages/If-there-is-a-war-of-programming-languages-who-would-you-support-and-why/answer/Prithviraj-Udaya?srid=LZ&st=ns Programming languages as Tolkien characters]
* [http://programmingisterrible.com/post/65781074112/devils-dictionary-of-programming Devil's Dictionary of Programming]
* [http://9gag.com/gag/av0z0Bn?ref=fb.s This Is Why You Shouldn't Interrupt A Programmer]
* [http://kingjamesprogramming.tumblr.com/ Random mashup generator of the King James Bible and a programming book]
* [http://moviecode.tumblr.com/ What the computer code seen on screens in movies and TV shows actually does]

===Misc.===
* [http://abcnews.go.com/Politics/video/obama-slow-man-27453525 President Obama writes a line of code (video)]
* [https://medium.com/@3fingeredfox/margaret-hamilton-lead-software-engineer-project-apollo-158754170da8 Picture: Margaret Hamilton, lead software engineer, Project Apollo, with source code from moon landing mission]
* [http://www.watchpeoplecode.com/ Watch People Code (live video streams)]

Archiving

2026-01-07T16:41:00Z

Dan Tobias: /* Uncategorized */

{{FormatInfo
|formattype=electronic
|thiscat=Archiving
|image=Magazine-files.jpg
}}
(Lossless, for generic data + file archives)

== Archiving only ==
(many files => 1 file, no compression attempted)

* [[AR]] file format (.a, .lib) -- Unix Archiver (ar) format as used by various compilers/linkers
* [[ARC (Internet Archive)]] (.arc)
* [[BagIt]]
** [[Mailbag]]
* [[BAR (Age of Mythology)]]
* [[bar]] (SunOS 4)
* [[CAR (CarComp)]]
* [[cpio]] (.cpio)
* [[DPK]]
* [[FAR (The Sims)]] (.far)
* [[Flash (Micro TECH Systems)]] (.flh)
* [[GRP (Build Engine Group Archive)]] (.grp)
* [[Hamster archive]]
* [[HMM Packfile]]
* [[HRX]]
* [[LBR]] (.lbr)
* [[LBR (Commodore)]] (.lbr)
* [[Lynx archive]] (Commodore) (.lnx)
* [[Mozilla Archive]] (.mar)
* [[Packaged Activity]] (.apk)
* [[PACKFILE (Brad Smith)]]
* [[pax]]
* [[QFC]]
* [[Quake PAK]]
* [[SAVF]]
* [[SeqBox]] (.sbx)
* [[siva]] (.siva)
* [[Tape Archive]] (.tar)
* [[TPAC (Tim Gordon)]]
* [[VIV]] (.viv, .big; used in Electronic Arts games)
* [[Webarchive (Safari)]]
* [[XMIT]]

=== Text-based ===
* [[HRA]]
* [[HRX]]

== Compression + archiving ==
(Multiple files => 1 file, makes it smaller. See [[Compression]] for formats that compress single files/streams, and [[Disk Image Formats]] for formats that capture the low-level structure of a disk)

* [[4Q]] (.4q)
* [[777]]
* [[7z]] (.7z)
* [[ACB (compressed archive)|ACB]]
* [[ACE]] (.ace)
* [[afio]]
* [[Ai Archiver]] (.ai)
* [[AIN]] (.ain)
* [[AKT]]
* [[ALZ]] (.alz) (ALZip)
* [[AMG (compressed archive)|AMG]] (AMGC)
* [[ar (Haruhiko Okumura)]]
* [[Apple Archive]] (.aar)[https://developer.apple.com/documentation/applearchive]
* [[Apple Encrypted Archive]] (.aea)[https://developer.apple.com/documentation/applearchive#3761312]
* [[AR7]]
* [[ARC (compression format)|ARC]] (PC/MS-DOS) (.arc)
* [[ARC (Commodore)]] (.arc)
* [[ARC (FreeArc)]] (.arc)
* [[ARC (Internet Archive)]] (gzipped form: .arc.gz)
* [[ArcFS]] (RISC OS) (.arc)
* [[ArcMac]]
* [[ARG]]
* [[ARHANGEL]]
* [[ARI (compressed archive)|ARI]]
* [[ARJ]]
* [[ARJZ]]
* [[ARQ]]
* [[ARX]]
* [[ASD Archiver]]
* [[Astrotite]] (.afa)
* [[B1]]
* [[B6Z]] (.b6z)
* [[BGA Archive]] (.bza, .gza)
* [[BIX]]
* [[BlakHole]] (.bh)
* [[BLINK]] (.bli)
* [[BOA Constrictor Archiver]]
* [[BRU]] - (RSX-11M backup)
* [[BSArc and BSA]]
* [[BTSPK]]
* [[Cabinet]] (.cab)
* [[CAR (SAP)|CAR]] (a SAP archive format; also see [[SAR]])
* [[CAR (MylesHi!)]]
* [[CAZIPXP]] (.caz)
* [[CFL]] (Compressed file library) (.cfl)
* [[ChArc]] (.chz)
* [[ChiefLZ]] (LZA)
* [[CMZ (archive format)|CMZ]]
* [[CODEC (Telvox)]]
* [[Compact File Set]] (.cfs)
* [[Compact Pro]] (.cpt)
* [[Compressia]] (.car)
* [[The Compressor (John Lauro)|Compressor, The (John Lauro)]]
* [[CP Shrink]] (.cpz)
* [[CRUSH]]
* [[Disk Archiver]] (.dar)
* [[DGCA]] (.dgc)
* [[Diamond]]
* [[Doom WAD]] (.wad)
* [[DRY]]
* [[DWC]] (.dwc)
* [[Dzip]] (.dz)
* [[Eazel]] (.eaz)
* [[EGG (ALZip)]] (.egg)
* [[ELI 5750]]
* [[ERI (compressed archive)|ERI]]
* [[ESP (compressed archive)|ESP]]
* [[Fold (J. Turin)]]
* [[FOXSQZ]]
* [[Freeze!]]
* [[GCA]] (.gca)
* [[Genus Graphics Library]]
* [[GFSA]] (.fa)
* [[Greenleaf ArchiveLib]]
* [[HA]] (.ha)
* [[HAP]]
* [[HIT (compressed archive)|HIT]]
* [[HKI]] (WinHKI) (.hki)
* [[HPACK (compressed archive)|HPACK]] (.hpk)
* [[HUF (CP/M)]]
* [[Hyper archive]] (.hyp)
* [[ICE (ICEOWS)]] (.ice)
* [[IMP]] (.imp)
* [[JAR (ARJ Software)]] (.j)
* [[JARCS]] (.jar)
* [[JRchive]] (.jrc)
* [[KGB Archiver]] (.kgb)
* [[Konqueror web archive]] (.war)
* [[LArc]] (.lzs)
* [[LHA]] (.lzh, .lha)
* [[LHARK]]
* [[LHice]]
* [[LIMIT]] (.lim)
* [[LZX]] (.lzx)
* [[MAFF]] (Mozilla web archive; uses ZIP for compression)
* [[MAr (Melting-Pot)]]
* [[MDCD]] (.md)
* [[Micrognosis Compression Archiver]] (MAR)
* [[MPC (Marco Czudej)]] (.mp3)
* [[MSXiE]] (.xie)
* [[MZP]]
* [[NaShrinK]] (.nsk)
* [[Now Compress]]
* [[NuFX]] / ShrinkIt (.shk)
* [[OOP]]
* [[oPAQue]]
* [[PA (PowerArchiver)]]
* [[packARC]] (.pja)
* [[Packdir]] (RISC OS)
* [[PACKER (ImagiSOFT)‎]] (The Finishing Touch)
* [[PackIt]] (.pit)
* [[PAK]] (.pak) - various formats
* [[PAK (ARC extension)]]
* [[PAKLEO]]
* [[PAQ]] (.pa6, .pa7, .pa8, others)
* [[PAQJ]] (.qar)
* [[PC-Shrink]] (.shr)
* [[PCX Library]] (.pcl)
* [[PEA]] (PeaZIP) (.pea)
* [[PerfectCompress]] (.uca)
* [[PIM]] (.pim)
* [[PKARC/PKPAK]]
* [[PLA]] (ARCHICAD Archive) (.pla)
* [[PMA]] (.pma)
* [[PPMd]]
* [[Pretty Simple Archiver]] (.psa)
* [[PUT]] (MicroFox) (.put)
* [[Quadruple D Archiver]] (.qda)
* [[Quantum compressed archive]] (.q)
* [[QuARK]] (.ark)
* [[RAR]] (.rar)
* [[RARC (Nintendo)]]
* [[RAX (compressed archive)|RAX]]
* [[RK]] (WinRK)
* [[RKIVE]] (.rkv)
* [[S7z]] (.s7z)
* [[SAR]] (a SAP archive format; also see [[CAR (SAP)|CAR]])
* [[SAR (Streamline Design)]]
* [[SARJ]] (.srj)
* [[SBX (SpinnerBaker Software)]] (.sb)
* [[Scifer]] (.sen, .ba, .xml)
* [[SKY (compressed archive)|SKY]]
* [[Slim!]]
* [[SOF (Spectrum Software)]] (RESOF)
* [[Softlib]] (Softdisk Publishing) (.slb)
* [[Spark]] (.spk)
* [[SQLite Archive]] (SQLAR)
* [[Squash ARH|Squash]] (.arh)
* [[Squeeze It]] (.sqz)
* [[SQWEZ]] 2.x (.sqz)
* [[SQX]] (.sqx)
* [[StuffIt]] (.sit)
* [[StuffIt X]] (.sitx)
* [[SuperPack]] (.spa)
* [[TBAFS]] (RISC OS)
* [[Tome]]
* [[TPK (compressed archive)|TPK]]
* [[TSComp]]
* [[UFA]]
* [[UHARC]] (.uha)
* [[UltraCompressor II]] (.uc, .uc0, .uc2, .ucn, .ur2, .ue2)
* [[VEM]] (Sony Virtual Expander)
* [[WARC]] (.warc, .warc.gz)
** [[WACZ]] (packaged warc)
* [[X (X1)]] (.x)
* [[xar (Extensible Archive)]] (.xar)
* [[Xidie archive]] (.zxc)
* [[XP3]] (.xp3) - used in [[KiriKiri Adventure Game System]]
* [[xpa32]] (.xpa)
* [[XPACK archive]] (.xpa)
* [[YAC]] (.yc)
* [[Yamazaki zipper archive]] (.yz1) - used in DeepFreezer
* [[ZAR (Zip-Archiv)]]
* [[Zet]]
* [[ZIP]] (.zip)
* [[Zipx]] (.zipx)
* [[Zoo]] (.zoo)
* [[ZPack (LeadRDRK)]]
* ZPack [Lite] (.zpk) - See [[Z/Install]]
* [[ZPAQ]]
* [[Zzip]] (.zz)

== Diff files ==
(containing only the parts of a file that have changed, so they can be applied to an existing file to update it; used for update distribution and incremental backups)

* [[ACB (compressed archive)|ACB]]
* [[binpatch (Jaap Korthals Altes)]]
* [[BinPatch (Kay Hayen)]]
* [[bsdiff]]
* [[Courgette]]
* [[diff]]
* [[dirpatch]]
* [[FidoNet nodediff]]
* [[FXPF]]
* [[GDIFF]]
* [[IPS (binary patch format)]]
* [[JSON Patch]]
* [[LDArc and LDIFF]] (.lzd)
* [[rename helper]]
* [[RTPatch]]
* [[SmartVersion]] (.svf)
* [[Unified diff]]
* [[UPS (binary patch format)]]
* [[VCDIFF]]

See also [[Wikipedia:Data differencing]].

== Versioning files ==
(contains multiple versions of files, often just saving the differences to save space)

(often a filesystem-level capability, such as ZFS and Btrfs snapshots and Windows Shadow Copy)

* [[Autodesk Vault]]
* [[SmartVersion]] (.svf)

See also [[Development#Revision_control_systems_.2F_code_repositories|Revision control systems / code repositories]]

== Encrypted or cryptographically signed archives ==
* [[DataSAFE]] (.saf, .lbx)
* [[SDN (SDN Project)]]
* [[XIP]]
* [[ZED]]

== File splitting ==
(1 file => multiple files. Most file splitting utilities just produce raw file fragments, and don't have a native file format. But some use a container format, and some create a separate "control" file for metadata.)

* [[AS/ZC (Zip Chunker)]]
* [[AUTOCHOP]]
* [[LambChop]]
* [[SLICE (Ziff Communications)]]
* [[SPLIT (M. Dingacci)]]

Also, the two sorts of [[Horcrux]], [[Horcrux (jesseduffield)]] and [[Horcrux (kndyry)]], are split-and-encrypted files.

== Filesystem backup and restoration ==
Formats designed for backing up disks, usually specifically targeted at particular [[filesystem]]s (but backing it up in the form of file structures, not raw sector images like [[Disk Image Formats]]).
* [[BACKUP (MS-DOS)]]
* [[Partimage]]
* [[ufsdump]]
* [[Unix dump]]
* [[Windows Imaging Format]] (.wim, .swm)

See also [[Backup]].

== Fake archiving ==
Beware of these; they purport to be archivers but aren't really; you might lose any data you entrust to them. Could be somebody's idea of humor or malware.
* [[OWS (fake compressed archive)]]
* [[WIC (fake compressed archive)]]

== Institutional archiving ==
* [[ARK]] (identifier for archived documents)
* [[Archive eXchange Format]] (.axf)
* [[OAIS]] (Open Archival Information System, an organization that does archiving)
* [[Planets Core Registry]]
* [[PRONOM]]
** [[PUID]]
* [[SIRF]] (Self-Contained Information Retention Format)
* [[Submission Information Package]]
* [[UPF]] (Universal Preservation Format)

== Metadata formats ==
* [[Archive Team hostname file]]
* [[CDX]] (associated with web archives)
* [[DFDL]] (Data Format Description Language) - a file format for describing file formats
* [[FilmConservationMetadata]]
* [[Internet Archive metadata]]
* [[mtree]]
* [[Portland Common Data Model]]
* [[TOSEC Naming Convention]]
* [[Web Archive Metadata File]] (metadata for [[WARC]])

(see also [[Metadata]], [[Bibliographic data]])

== Program/App/Applet/Installer specialized archive formats ==
* [[Adobe Air]]
* [[APK]] (Android app)
** [[XAPK]]
*** [[OBB]]
* [[Bundle file (Linux)]]
* [[Bundle file (OS X)]]
* [[Cabal]]
* [[Cakewalk Bundle (BUN)]]
* [[Cakewalk Bundle (CWB)]]
* [[Cross-Platform Installer Module]]
* [[deb]] (Debian package)
* [[EA archive]]
* [[Eschalon Setup archive]] (.arv)
* [[FIZ]]
* [[Garc archive]] (.gar)
* [[IPS archive|Image Packaging System (IPS) archive]] (.p5p)
* [[IPS manifest|Image Packaging System (IPS) manifest]] (.p5m)
* [[Inno Setup self-extracting archive]]
* [[Installer VISE]]
* [[InstallShield]]
** [[InstallShield archive (IBT)]]
** [[InstallShield CAB]]
** [[InstallShield installer archive]]
** [[InstallShield PKG]]
** [[InstallShield Self-Extracting EXE]]
** [[InstallShield Z]]
* [[IPA]] (.ipa) => iOS app in archived form; actually in zip format
* [[IPSW]] (.ipsw) Apple OS restore format [https://en.wikipedia.org/wiki/IPSW 1]
* [[IRIX software distribution format]] (.idb, etc.)
* [[Jar]] (.j, .jar) (Java) => this is just a renamed zip file with some mandatory files
* [[Lead Technologies archive]]
* [[LIF (Knowledge Dynamics)]]
* [[MDA (Micrografx)]]
* [[Meta-Package File]] (.mpkg) (Mac OS X)
* [[Microsoft Update Standalone Package]]
* [[MRNZ]]
* [[NSIS]] (Nullsoft Scriptable Install System)
* [[Olive]] (executable virtual-machine archive of software)
* [[OS/2 PACK archive]]
* [[OS/2 PACK2 archive]] (FTCOMP)
* [[Packaged Activity]] (Microsoft Train Simulator)
* [[Package File (OS X)]] (.pkg)
* [[PackageForTheWeb]]
* [[PC-Install]] (20/20 Software) - See also [[PC-Shrink]].
* [[QIP (Quarterdeck)]]
* [[RED (Knowledge Dynamics)]]
* [[RPM]] (formerly known as RedHat Package Manager, nowadays RPM Package Manager)<ref>[[wikipedia:RPM_Package_Manager|RPM Package Manager - Wikipedia]]</ref>
* [[Setup Factory]] (Indigo Rose Software)
* [[SIS]] (Symbian)
* [[Snap]]
* Sweet Home 3D
** [[Sweet Home 3D Furniture Library]]
** [[Sweet Home 3D Plug-in]]
** [[Sweet Home 3D Texture Library]]
* [[SWG]] (SWAG)
* [[Unity package file]]
* [[WAD (Wii)]]
* [[Windows Installer]] (.msi, .msp)
* [[Wise installer package]]
* [[XAR (Executable Archive)]]
* [[XP3]] (KiriKiri Adventure Game System)
* [[Z/Install]]
* [[ZSoft ZPK2]]
* [[Zune HD Application File]] (.zcp)

== Self-extracting archives ==
(in addition, some of the other archivers are able to produce executable files for some platform which include the archived data and a program to extract them, and generally have the file extension normal for executables, such as .exe for DOS/Windows. In many cases, if you rename the extension to the appropriate one for the archive type involved, e.g., '''.zip''', the file will open in the appropriate archiver, which is handy for extracting them on systems not compatible with the original executable.)
* [[ARS]]
* [[COMPACK]] / BUILDSFX
* [[LHA/LHarc self-extracting archive]]
* [[makeself]] [https://github.com/megastep/makeself]
* [[NETSEND]]
* [[PMsfx]]
* [[SCRNCH]] (in "write mode")
* [[SDA]] (Self Dissolving Archive)
* [[SEA (StuffIt)]] (StuffIt Self-Extracting Archive)
* [[Self-extracting ZIP]]
* [[SFX]] (Self-Extracting Archive)
* [[shar]] (Shell Archive, in Unix-like systems)
* [[SQWEZ]]

== Software ==
Refer to [[Compression and archiving software]].

== Transfer formats ==
(encapsulate a system-specific file structure to make it compatible with foreign systems, file transfer protocols, etc.)
* [[AppleDouble]]
* [[AppleSingle]]
* [[Bento]] (1990s Apple cross-platform compound content format)
* [[Binary II]] (.bny) (for Apple II series) (often [[squeeze]]d as .bqy)
* [[BinHex]] (.hqx)
* [[GEOS Convert]] (.cvt)
* [[MacBinary]]
* [[MAR Utility]]
* [[oric-dsk-manager exported file]]
* [[TI variable file]]

For low-level transfer encodings, see [[Transfer Encodings]].

== Uncategorized ==
* [[Cache Directory Tagging Standard]]
* [[Content Addressable Archive]] (CAR)
* [[SMART Notebook]]

== See also ==
* [[Backup]]
* [[Compression]]
* [[Disk Image Formats]]
* [[Executable envelopes#Executable libraries]]

== Links ==
* [http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html Torture-testing Backup and Archive Programs: Things You Ought to Know But Probably Would Rather Not]
* [http://www.ietf.org/mail-archive/web/apps-discuss/current/msg13094.html Discussion of proposed top-level MIME type for 'archive']
* [http://blogs.loc.gov/digitalpreservation/2014/02/what-do-you-mean-by-archive-genres-of-usage-for-digital-preservers/ What Do you Mean by Archive? Genres of Usage for Digital Preservers]

== References ==
<references/>

Category:File formats with extension .notebook

2026-01-07T16:39:53Z

Dan Tobias: Created page with "N"

[[Category:File formats by extension|N]]

Category:Remedy Entertainment

2025-11-22T05:02:04Z

Dan Tobias: Created page with "Category:Companies and organizations"

[[Category:Companies and organizations]]

Punched card

2025-10-09T20:42:17Z

Dan Tobias: Add headers

{{FormatInfo
|formattype=physical
|thiscat=Punched card
|released=1801
}}

'''Punched cards''', or punchcards, were for many years the major method of providing input to computers. Programs in [[FORTRAN]] or [[COBOL]] or [[RPG]] were punched onto decks of cards (one card per program line) on keypunch machines and handed in to be run in batch-processing mode on the computer, which was too massive and expensive to be made available to individuals other than through the mediation of system operators who eventually handed back the output in printed form. Often the function of the programs was to churn through large amounts of data to do number-crunching or other operations on it; this data might also be provided on punchcards (though [[magnetic tape]] and paper [[punched tape]] were also used). Punchcards could also be found in all sorts of other places, including in the cards you sent back with bill payments (which bore the infamous exhortation, "Do not fold, spindle, or mutilate").

While punchcards are most associated with the "big-iron" mainframe computers of the 1950s through 1970s, they have a 200-year history of use for many applications, from the [[Jacquard Loom]] of 1801 to the "hanging chads" of the 2000 US presidential [[Votomatic card|election]]. In between they were proposed for use in Babbage's never-finished Analytic Engine and used by Hollerith for data-tabulation for the 1890 US Census.

It is possible to read most standard punch cards with a scanner and DataMuseum.dk has developed such a program in python3, aptly named "Florida2000". The source code can be found under the Datamuseum-DK account on github.

== Digital preservation formats ==

A survey (2025-10-01) looking for standarized file-formats, for the digital preservation of punched card contents comes up empty.

The SIMH emulator software implements four different file-formats of which one is translating ("Standard Ascii"), one is limited to only certain kinds of punched cards ("BCD Format"), leaving "Binary Card format" and "CBN Format".

A survey of the contents of BitSavers (2025-10-01) finds 8 artifacts in CBN format and 2600+ in "Binary Card format".

The description of the "Binary Card format" in the Open-SIMH source code (2025-10-01) is somewhat confused:

Binary Card format:
Each record 160 characters.
First characters 6789----
Second character 21012345
111
Top 4 bits of second character are 0.
It is unlikely that any other format could
look like this.

The line "Top 4 bits of second character are 0." is wrong, and should correctly read "The bottom bits of every second character is 0."

== Card types ==

* [[Aperture card]]
* [[Hollerith card]]
* [[IBM card]] (original 80-column version)
** [[IBM stub card]]
** [[IBM 96-column card]]
* [[Jacquard Loom]]
* [[Korsakov card]]
* [[Mark Sense card]]
* [[UNIVAC 90-column card]]
* [[Votomatic card]] (used in election ballots)

== Resources ==

* [http://homepage.cs.uiowa.edu/~jones/cards/ The Douglas W. Jones Punched Card Page]
* [http://www.quadibloc.com/comp/cardint.htm The Punched Card]: shows details of a number of card formats and character encoding schemes
* [http://www.masswerk.at/google60/ Google60]: Cute web app showing how Google's interface might have been in the 1960s, complete with simulated keypunch
* [http://www.wired.com/wired/archive/7.03/punchcards.html The little secret that haunts corporate America ... A technology that won't go away.]
* [http://what-if.xkcd.com/63/ If all digital data were stored on punch cards, how big would Google's data warehouse be?]

Bsdiff

2025-09-30T00:51:40Z

Dan Tobias:

{{FormatInfo
|subcat=Archiving
|pronom={{PRONOM|fmt/439}}
|wikidata={{wikidata|Q58367808}}
|released=2003
}}

'''Bsdiff''' is an open-source utility for generating diffs of binary files which can be distributed as patches or updates without having to send the entire set of binary data each time the package is updated. While one might think the need for such things is reduced with the much-improved bandwidth of modern times, software has also increased in size (the "bloatware" phenomenon), so the need for tools like this continues. Supposedly bsdiff generates more compact diff files than the high-priced proprietary [[RTPatch]] system.

bsdiff uses a technique called [https://en.wikipedia.org/wiki/Delta_encoding delta encoding] to encode the differences between two binary objects.

[[bzip2]] is used for compression.

There have been some forks and variant versions of bsdiff, and slightly-divergent forms are used for some platforms and software systems; for instance, there is an adapted version used for Mozilla updates (which, in turn, get put into [[Mozilla Archive]] files).

== Code and downloads ==

* [http://www.daemonology.net/bsdiff/ BSDIFF page with link to download]
* [https://github.com/mendsley/bsdiff An 2012 fork of bsdiff]
* [https://github.com/gabstv/go-bsdiff Golang implementation of bsdiff based on Percival's original]

== Links and references ==

* [http://www.pokorra.de/coding/bsdiff.html bsdiff for Windows]
* [http://cx-bsdiff.sourceforge.net/ bsdiff Python extension]
* [http://openplanetsfoundation.org/system/files/bsdiff-4.0-documentation-colin-percival-bsd-licensed.pdf BSDIFF format information]
* [http://www.daemonology.net/papers/bsdiff.pdf Paper on algorithm used]
* [http://www.daemonology.net/papers/thesis.pdf Doctoral thesis by author describing more sophisticated algorithm]
* [http://damaestro.us/blog/bsdiff-very-interesting-binary-diff Blog discussion]
* [https://openpreservation.org/blogs/bsdiff-technological-solutions-reversible-pre-conditioning-complex-binary-objects/ BSDIFF: Technological Solutions for Reversible Pre-conditioning of Complex Binary Objects]
* [https://exponentialdecay.co.uk/blog/bsdiff-as-a-tool-for-digital-preservation/ Revisiting bsdiff as a tool for digital preservation]

Text Encoding Initiative

2025-07-29T02:57:57Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|subcat=Markup
}}

The '''Text Encoding Initiative''' (TEI) is a consortium to develop standards for digitally-represented texts, begun in 1994. Their standards and guidelines are used widely in the humanities and social sciences, as well as by libraries and museums.

== Software ==
* "[https://github.com/odict/freedict freedict]", converter of dictionary files to [[ODict]]

== External links ==

* [http://www.tei-c.org/index.var Text Encoding Initiative website ]
* [[Wikipedia:Text Encoding Initiative]]

[[Category:XML based file formats]]

Diagramming and flowcharting

2025-07-29T02:41:46Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|thiscat=Diagramming and flowcharting
|image=Flowchart-311347 640.png
}}

Formats for making charts and diagrams.

* [[ABC FlowCharter]] (later iGrafx FlowCharter)
* [[Chartist (Novagraph)]]
* [[ConceptDraw]]
** [[ConceptDraw Document]]
** [[ConceptDraw XML]]
** [[ConceptDraw Mindmap]]
* [[Corel Flow]]
* [[DataDiagrammingML]]
* [[Dia]]
* [[Diagram Designer]]
* [[DOT (graph description language)]]
* [[Flow Charting]]
* [[GEXF]] (Graph Exchange XML Format)
* [[MyDraw]]
* [[OmniGraffle]]
* [[OrgPlus]] (.opx)
* [[PlantUML]]
* [[RFFlow]]
* [[SmartDraw]]
* [[Timeline Maker]] (.tlm, .tlmp)
* [[UML]]
* [[Visio]]

== See also ==
* [[Graphics]]
* [[Mind maps, Topic maps, etc.]]
* [[Scientific Data formats]]
* [[Flowchart]]

Category:Novagraph

2025-07-29T02:33:56Z

Dan Tobias: Created page with "Category:Companies and organizations"

[[Category:Companies and organizations]]

Game data files

2025-06-26T00:47:52Z

Dan Tobias: /* Individual Game Formats */

{{FormatInfo
|formattype=electronic
|thiscat=Game data files
|image=Arcade-gaming-1361761483gDu.jpg
}}

==Overview==
Many popular games use proprietary file formats to store their assets. These include custom image, sound and video formats and custom archive formats. There is no way that all of these can be enumerated here in some way or another. And as long as the games can still be run by an [[Emulation_Software|Emulator]] it's not that much of a deal. However, a lot of work has been put into deciphering, decrypting and hacking these files, and that work should be preserved.

See also: [[Interactive Fiction]] for data formats related to text adventure games, [[Puzzles]] for puzzle-game files, and [[Saved Games]] for data saved by games to store a player's game status.

==References==
* [http://wiki.xentax.com Xentax Wiki]
* [http://rewiki.awiki.org ReWiki]
* [http://aluigi.altervista.org/quickbms.htm QuickBMS], a tool suite to describe archives in an abstract BASIC-like language, and lots of scripts for even more games

==General Game Formats==

This section details formats such as [[Interplay ACM]] and [[Unreal Music Format]] which are used in a number of games.

=== Archiving / Compression ===
* [[CFL]]
* [[FAR (The Sims)]]
* [[HMM Packfile]] (.PAK)
* [[Unity package file]]

===Audio / Music===
(see also [[Audio and Music]])

* [[BAKA]] (PCM 16 bit)
* beatmania / IIDX simulation
** [[BMS]]
* [[BH2PCM]] (extracted from [[Doom WAD]] by eXtendable WAD Editor)
* [[BNSF]] (IS14)
* Commodore Amiga
** [[AC1D-DC1A Packer]]
** [[AMOS Music Bank]]
** [[Channel Players]]
** [[Digital Illusions]]
** [[Game Music Creator]]
** [[Jason Page]]
* Electronic Arts
** [[Electronic Arts MUS]]
* [[Epic Megagames MASI]]
* id Software
** [[Doom MUS]]
** [[id Software Music Format]]
* [[Interplay ACM]]
* [[Inverse Frequency Sound format]]
* [[Ken's Adlib Music]]
* [[Sierra AGI]]
* [[Sierra SCI]]
* [[Westwood Studios ADL]]
* [[Westwood Studios AUD]]
* [[Xbox IMA ADPCM]]
* Nintendo GameCube / Wii
** [[Nintendo GameCube / Wii AST]]
** [[Nintendo GameCube / Wii BRSTM]]

=== Game programming languages ===

* [[Blitz3D]]
** [[Blitz3D Model]]

(see also [[Programming Languages]])

=== Other ===

* Allegro (game programming library)
** [[Allegro packfile]]

* Atari
** [[STOS memory bank]] (.mbk)

* Bitsboard
** [[Bitsboard board]]

* Blizzard Entertainment
** [[BLP]]
** [[MDX (Blizzard)|MDX]]
** [[MoPaQ]]

* Build Engine
** [[ART (Build Engine ART)]]
** [[DAT (Build Engine Palette)]]
** [[GRP (Build Engine Group Archive)]]

* [[D3TV]]
* [[DIV Games Studio]]

* Electronic Arts
** [[Electronic Arts CMV]]
** [[Electronic Arts INF]]
** [[Electronic Arts MAD]]‎
** [[Electronic Arts MOV]]
** [[Electronic Arts MPC‎]]
** [[Electronic Arts TGV]]
** [[Electronic Arts WVE]]

* Free Hero Mesh
** [[Free Hero Mesh class definition file]] (.class)
** [[Free Hero Mesh class resource file]] (.xclass)
** [[Free Hero Mesh level file]] (.level)
** [[Free Hero Mesh solution file]] (.solution)
** [[Free Hero Mesh code page file]]
** [[Free Hero Mesh composite puzzle set]]

* Hero Mesh
** [[Hero Mesh puzzle set]] (.mb)

* id Software
** [[BSP]] (map format used in Quake)
** [[Doom WAD]]
** [[Quake PAK]]
** [[Quake PK3]] (actually [[ZIP]])
** [[Quake WAD]]

* Infinity Engine
** [[BAM]]

* [[MegaZeux]]

* NetImmerse / Gamebryo Engine
** [[KF]]
** [[NIF]]

* Nintendo GameCube
** [[Nintendo GameCube Opening.bnr]]

* Nintendo GameCube / Wii
** [[DOL (Nintendo)]]
** [[RARC]]
** [[Yaz0]]

* Nintendo Wii
** [[BootMii NAND Dump]]
** [[BRFNT]]
** [[Mii Data]]
** [[Nintendo Wii BRLAN]]
** [[Nintendo Wii BRLYT]]
** [[Nintendo Wii BRRES]]
** [[Nintendo Wii Content.bin]]
** [[Nintendo Wii Data.bin]]
** [[Nintendo Wii Opening.bnr]]
** [[Nintendo Wii PAC]]
** [[Nintendo Wii PCS]]
** [[Nintendo Wii REL]]
** [[Nintendo Wii Savegame]]
** [[Nintendo Wii SEL]]
** [[Nintendo Wii Ticket]]
** [[Nintendo Wii TPL]]
** [[Nintendo Wii U8]]
** [[Nintendo Wii Update.inf]]
** [[Nintendo Wii VFF]]
** [[Title metadata]]
** [[Virtual Console CCF]]
** [[WAD (Wii)]]
** [[WiiConnect24 file]]

* [[OHRRPGCE]]

* [[Outerra engine]] (.otx) (used in Anteworld game)

* Raven Software game engine
** [[GLA]] - Ghoul animation (.gla)
** [[GLM]] - Ghoul mesh (.glm)

* Sokoban
** [[Softdisk Publishing UDF files]] (used for Softdisk's version of Sokoban)
** [[SOK (Sokoban)]]
** [[Sokoban XML]]

* Terminal Reality [https://github.com/jopadan/termpod/wiki/Terminal-Reality]
** [[POD1]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-1-Format-Reference] (no CRC)
** [[POD2]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-2-Format-Reference] (CRC=[[CRC-32#CRC-32/MPEG-2|CRC-32/MPEG-2]])
** [[POD3]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-3-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD4]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-4-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD5]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-5-Format-Reference] (CRC=CRC-32/MPEG-2)
** [[POD6]] (.pod) [https://github.com/jopadan/termpod/wiki/Pod-6-Format-Reference] (no CRC)
** [[EPD]] (.epd) [https://github.com/jopadan/termpod/wiki/Epd-Format-Reference] (CRC=CRC-32/MPEG-2)

* Tiled
** [[Tiled JSON]]
** [[Tiled TMX]]
** [[Tiled TSX]]

* Torque 3D game engine
** [[DTS]] (.dts)

* Valve Source Engine
** [[Valve Model Format]] (.mdl) [https://developer.valvesoftware.com/wiki/MDL Source Code]
** [[Valve Collision Model]] (.phy)
** [[Valve Map Format]] (.vmf)
** [[Valve Material Type]] (.vmt)
** [[Valve Vertex Data]] (.vvd)
** [[Valve Texture Format]] (.vtf)

* Xtremeworlds
** [[Xtremeworlds PWX]]
** [[Xtremeworlds map]]

* [[ZZT]]
** [[ZXT/ZAX]]

* [[ZZ Zero]]

==Individual Game Formats==

This section details formats which are specific to a single game (or perhaps a game series), such as [[God of Thunder Music Format]].
* 7 Days to Die
** [[TTS Prefab]] (.tts)
** [[7DTD Map File]] (.map)
* Age of Empires
** [[Data Resource File]] (.drs)
** [[Age of Empires Graphics File]] (.slp)
* Age of Mythology
** [[BAR (Age of Mythology)]] (.bar archive)
* Alter Ego (1986)
** [[Alter Ego Vignette Script format]]
* Arma
** [[Arma PBO]] (.pbo)
* Barony
** [[Barony Voxel]] (.vox)
* Blur
** [[BAF]] (Blur ADPCM)
* BVE, OpenBVE, Boso View Express (railroad simulator)
** [[BVE object formats]]
** [[BVE route formats]]
** [[BVE train.dat file]]
* Carnivores
** [[CAR (Carnivores)]] (.car)
* Cartooners
** [[Cartooners actor file]] (.act)
** [[Electronic Arts INF‎]] (.inf)
** [[Electronic Arts MOV]] (.mov)
** [[Electronic Arts MUS]] (.mus)
* Chasm: The Rift
** [[CAR (Chasm: The Rift)]]
* Cities Skylines
** [[Cities Skylines CRP]] (.crp)
* Commander Keen 1
** [[Commander Keen 1 Level format]] (.ck1)
* Core Wars
** [[RBJ (Redcode oBJect)]] (.rbj)
* Crystal Caves
** [[Crystal Caves Sound format]] (.snd)
* Dance With Intensity
** [[Dance With Intensity simfile]] (.dwi)
* Dangerous Dave
** [[Dangerous Dave level format]]
** [[Dangerous Dave tileset format]]
** (also uses [[Inverse Frequency Sound format]])
* Dark Reign
** [[FTG (Dark Reign)]]
** [[PAL (Dark Reign)]]
* Dofus
** [[Dofus localization]]
* Donkey Konga 2
** [[Donkey Konga 2 DSP]]
* Doom
** [[Doom cheat code encryption]]
** [[Doom MUS]] (.mus)
** [[Doom WAD]] (.wad)
* DTX Mania
** [[DTX Mania simfile]]
* Duke Nukem
** [[ART (Duke Nukem 3D)]]
** [[DAT (Duke Nukem 3D)]]
** [[Duke Nukem level format]]
** [[Duke Nukem graphics format]]
** [[GRP (Duke Nukem 3D)]]
* Fallout
** [[Fallout character description]] (.gcd)
* Friday Night Funkin
** [[Friday Night Funkin mod]]
* Garry's Mod
** [[Garry's Mod Addon]] (.gma)
* God of Thunder
** [[DAT (God of Thunder)]]
** [[God of Thunder Music Format]]
* Grand Theft Auto
** [[RAGE Package Format]] (.rpf)
** [[RenderWare binary stream file]] (.dff)
* In the Groove
** [[In the Groove PCK]] (.pck)
* Jack Nicklaus Golf & Course Design: Signature Edition
** [[JNSE golf course]]
* Kick It Up
** [[Kick It Up simfile]] (.ksf)
* Lego Island
** [[Lego Island World Database]] (.wdb)
* Magic & Mayhem
** [[Magic & Mayhem sprites file]]
* Mario Kart Wii
** [[Wii BTI]]
* Mario Paint
** [[Mario Paint Composer]]
** [[SHI]]
** [[SHO]]
* Mass Effect
** [[AFC]] (AFX audio file; Mass Effect 2)
* MegaZeux
** [[MegaZeux Property List]]
* Minecraft
** [[Minecraft Alpha level format]]
** [[Minecraft Anvil format]]
** [[Minecraft Bedrock Edition level format]]
** [[Minecraft chunk format]]
** [[Minecraft classic level format]]
** [[Minecraft classic server protocol]]
** [[Minecraft generated structures format]]
** [[Minecraft Indev level format]]
** [[Minecraft Java Edition level format]]
** [[Minecraft loot table]]
** [[Minecraft map item format]]
** [[Minecraft model]]
** [[Minecraft NBT format]]
** [[Minecraft player format]]
** [[Minecraft raids.dat format]]
** [[Minecraft Region format]]
** [[Minecraft server_level.dat]]
** [[Minecraft server list format]]
** [[Minecraft structure block file format]]
** [[Minecraft scoreboard format]]
** [[Minecraft sounds.json]]
** [[Minecraft villages.dat format]]
** [[Schematic file format]]
* Mortal Kombat 4
** [[Mortal Kombat 4 filesys.dat]]
* Pokémon
** [[Pokémon Mystery Dungeon]]
** [[Pokémon ROM]]
** [[RMC]]
* Quake
** [[MD2]] - Quake 2 model format (.md2)
** [[MD3]] - Quake 3 model format (.md3)
** [[MD4 (Quake)|MD4]] - Quake MD4 model format (used in later Quake 3 versions) (.md4)
* Rise of the Triad
** [[Rise of the Triad level format]]
** (also uses [[Doom WAD]])
* RobotWar
** [[RobotWar|RobotWar programming language]]
* Sims, The
** [[CFP]] (Compressed Floating Point)
** [[CMX/BCF]]
** [[FAR (The Sims)]]
** [[IFF (The Sims)]] (.iff, .flr, .wll, .spf, .stx)
** [[SKN/BMF]]
* StarCraft
** [[StarCraft group file]] (.grp)
* StepMania
** [[StepMania simfile]] (.sm)
** [[StepMania 5 simfile]] (.ssc)
** [[StepMania AMX simfile]] (.sma)
* Stronghold
**[[Stronghold GM1]] (.gm1)
**[[TGX Graphics]] (.tgx)
* Supaplex
** [[Supaplex Level format]] (.dat)
* Super Mario Galaxy
** [[Super Mario Galaxy savefile]]
* Super Paper Mario
** [[BRSTMPSM]] (music data)
* Total War
** [[Total War ESF]] (.esf)
* Vinyl Goddess From Mars
** [[Vinyl Goddess From Mars Instrument Format]]
** [[Vinyl Goddess From Mars Music Format]]
* Warcraft
** [[Warcraft II PUD]] (.pud) (custom maps)
* Wiggle Planet
** [[Wiglet]]
* Wii Fit / Wii Fit Plus
** [[Wii Fit BMG]]

== Game hints ==
* [[UHS]]

== Board/card games ==
* [[Magic Set Editor]]
** [[Magic Set Editor card set]] (.mse-set)
** [[Magic Set Editor export template]] (.mse-export-template)
** [[Magic Set Editor game definition]] (.mse-game)
** [[Magic Set Editor include package]] (.mse-include)
** [[Magic Set Editor installer]] (???)
** [[Magic Set Editor style sheet]] (.mse-style)
** [[Magic Set Editor symbol font]] (.mse-symbol-font)
* [[REKO Cardset]]
* [[TeXnicard]]
** [[TeXnicard card database]]
** [[TeXnicard template]]
* [[Wiz Solitaire]]

== Uncategorized ==

* [[RBPACK]]

== External links ==

* [http://www.osti.gov/accomplishments/videogame.html Possibly the first video game, in 1958]
* [https://archive.org/details/Nintendo_Ultra64_Programming_Manual Nintendo Ultra64 Programming Manual]
* [http://ukvac.com/forum/topic335921.html Sega Pengo: bug found in maze generating algorithm]
* [http://www.stavros.io/posts/winning-candy-crush/ How to 'hack' Candy Crush]
* [http://www.glitchthegame.com/public-domain-game-art/ Glitch game files, released into the public domain]
* [https://github.com/jmechner/Prince-of-Persia-Apple-II Prince of Persia source code (Apple II)]
* [http://sourceforge.net/projects/dice/ DICE: emulator of early discrete-circuit video games]
* [http://www.polygon.com/2014/4/22/5640114/maze-invaders-atari-arcade-source-code-strong-museum-icheg Museum acquires 'virtually complete' source code from Atari's arcade heyday]
* [https://archive.org/details/pdp1_spacewar Spacewar! for the PDP-1 (1962)] (with in-browser emulation)
* [http://tcrf.net/Category:Games_with_hidden_developer_messages Games with hidden developer messages]
* [http://www.loc.gov/preservation/resources/rfs/softgame.html Library of Congress Recommended Format Specifications: Software/Gaming]
* [https://github.com/keendreams/keen Keen Dreams Source Code (open-source release)]

CAR (Carnivores)

2025-06-26T00:45:04Z

Dan Tobias:

{{FormatInfo
|subcat=3D and CAD/CAM Models
|extensions={{ext|car}}
}}
'''CAR''' format is used in the Carnivores game series to store 3D objects.

== Links ==

* https://carnivores.fandom.com/wiki/CAR
* https://github.com/carnivores-cpe/c3dit
* https://www.tapatalk.com/groups/the_carnivores_saga/carnivores-1-2-and-ice-age-car-files-t2309.html

[[Category:Game data files]]

CAR (Chasm: The Rift)

2025-06-26T00:42:22Z

Dan Tobias:

{{FormatInfo
|subcat=3D and CAD/CAM Models
}}
'''CAR''' format is used in the Chasm: The Rift game to store 3D objects such as the player and monsters.

== Links ==

* https://moddingwiki.shikadi.net/wiki/CAR_Format
* https://github.com/jopadan/AwesomeChasm?tab=readme-ov-file#models

[[Category:Game data files]]

Lottie

2025-05-04T03:10:08Z

Dan Tobias:

{{FormatInfo
|formattype=electronic
|subcat=Animation
|extensions={{ext|json}}
}}
[[Lottie]] is a modern animated file format, using [[JSON]].

== Software ==

* [https://lottiefiles.com/ lottiefiles.com]
* [https://app.lottiefiles.com/ app.lottiefiles.com]
* [https://github.com/Samsung/rlottie rlottie]
* [http://snisurset.net/code/abydos/ abydos]

== Sample files ==

Sample files can be downloaded from [https://lottiefiles.com/ lottiefiles.com] and created and downloaded in [https://app.lottiefiles.com/ app.lottiefiles.com].

Samples are also available at dexvert: {{DexvertSamples|image/lottie}}

Category:File formats with extension .song

2025-05-03T23:41:29Z

Dan Tobias: Created page with "S"

[[Category:File formats by extension|S]]

Library

2025-03-10T20:31:38Z

Dan Tobias:

A collection of articles related to the File Format problem, this project, or education about the type of endeavor this sort of project entails. For more information, see pages under the [[:Category:Information|Information category]].

* [http://unsustainableideas.wordpress.com/2012/10/22/open-letter-ms-obsolete-formats/ Open letter to Microsoft on specs for obsolete file formats] by Chris Rusbridge.
** [http://unsustainableideas.wordpress.com/2012/11/26/response-open-letter-obsolete-ms-formats/ Reply from Microsoft]
** [http://unsustainableideas.wordpress.com/2012/11/28/more-from-microsoft/ 2nd reply from Microsoft]
* [http://unsustainableideas.wordpress.com/2012/10/15/ppt-4-adventure-learning/ The PowerPoint 4.0 adventure: what did I learn?] by Chris Rusbridge.
* [http://blog.dshr.org/2012/10/cleaning-up-formats-through-time-mess.html Cleaning up the "Formats through Time" mess] by David Rosenthal.
* [http://blog.dshr.org/2014/04/what-could-possibly-go-wrong.html What Could Possibly Go Wrong?] by David Rosenthal
* [http://infotrope.net/2012/11/30/importing-data-is-hard/ Importing data is hard] by Skud
* [http://journal.code4lib.org/articles/8029 The Format Registry Problem] by Gary McGath
* [http://filesthatlast.com/ Files that Last: Digital Preservation for Everygeek] by Gary McGath
* [http://archive.org/details/XFRSTN_FAQ XFER STN FAQ] by New Museum of Contemporary Art (info on their project to preserve artists' multimedia from archaic formats)
* [http://blogs.loc.gov/digitalpreservation/2013/08/solving-problems-and-saving-bits-an-interview-with-jason-scott/ Solving Problems and Saving Bits: An Interview with Jason Scott] by Jefferson Bailey, for the Library of Congress blog
* [http://www.ribbonfarm.com/2013/10/11/the-mother-of-all-disruptions/ The Mother of All Disruptions] by Venkat (what he calls "soft technology" corresponds pretty well with what's called "file format" here)
* [http://rbriggs87.wordpress.com/2013/09/20/disappearing-digital-world/ Disappearing Digital World] by Rebecca E. “Becky” Briggs
* [https://www.gov.uk/government/news/process-starts-to-select-open-standards-for-government-documents Process starts to select open standards for government documents (UK)]
* [http://vimeo.com/album/2651464/video/81873487 Jason Scott speech at DISH 2013] (video)
* [http://exponentialdecay.co.uk/blog/genesis-of-a-file-format/ Genesis of a file format] by Ross Spencer
* [http://www.theguardian.com/technology/2014/jan/16/digital-failures-software Digital failures are inevitable, but we need them to be graceful] by Cory Doctorow
* [http://fsfe.org/activities/os/minimalisticstandards.html The minimal principle: because being an open standard is not enough.] by Bernhard Reiter
* [http://bjoern.brembs.net/2014/03/what-is-the-difference-between-text-data-and-code/ What is the difference between text, data and code?] by Björn Brembs
* [http://famicoman.com/2014/05/20/philosophy-of-data-organization/ Philosophy of Data Organization] by Famicoman
* [http://arstechnica.com/gadgets/2014/06/saving-old-software-from-extinction-in-the-age-of-cloud-computing/ Saving old software from extinction in the age of cloud computing] by Ron Amadeo
* [http://qanda.digipres.org//38/what-is-a-file-format?show=44 What is a file format?] (Discussion)
* [http://news.bbc.co.uk/2/hi/6265976.stm Warning of data ticking time bomb] (BBC News, 2007)
* [http://contentsmagazine.com/articles/dark-archives/ Dark Archives] by Tim Maly
* [http://files.d-nb.de/nestor/materialien/nestor_mat_15-eng.pdf Nestor guidelines for preservation planning]
* [https://themanual.org/read/issues/4/paul-ford/article On File Formats, Very Briefly] by Paul Ford
* [http://britishlibrary.typepad.co.uk/webarchive/2012/08/analysing-file-formats-in-web-archives.html Analysing File Formats in Web Archives] in UK Web Archive Blog
* [https://fstoppers.com/education/trouble-tech-or-why-you-should-print-your-photos-else-risk-losing-them-forever-59454 The Trouble With Tech or Why You Should Print Your Photos Else Risk Losing Them Forever]
* [http://nautil.us/blog/will-you-be-able-to-read-this-article-in-1000-years Will You Be Able to Read this Article in 1,000 Years?]
* [http://www.dpconline.org/advice/preservationhandbook Digital Preservation Handbook]
* [http://archive.ifla.org/IV/ifla63/63kuny1.pdf A Digital Dark Ages? Challenges in the Preservation of Electronic Information], by Terry Kuny (1997)
* [https://www.avpreserve.com/blog/what-is-the-chemistry-of-digital-preservation/ What is the chemistry of digital preservation?], by Bertram Lyons (2016)
* [http://www.kdk.fi/images/tiedostot/NDL-File-Formats-v1.4-en.pdf National Digital Library of Finland file format guide]
* [http://preservica.com/blog/how-not-to-build-a-digital-archive-lessons-from-the-dark-side-of-the-force/ How Not to Build a Digital Archive: Lessons from the Dark Side of the Force]
* [http://motherboard.vice.com/read/the-disk-formats-of-star-wars-rogue-one-spoilers From Tape Drives to Memory Orbs, the Data Formats of Star Wars Suck (Spoilers)]
* [http://homes.ukoln.ac.uk/~lismd/preservation.html Preservation of electronic information: a bibliography] (1997)
* [https://scholarworks.umt.edu/cgi/viewcontent.cgi?article=1033&context=ml_pubs A Brief History of Digital Preservation] by Erin Baucom (2019)
* [https://prolost.com/blog/fileformats Held Prisoner by File Formats] by Stu Maschwitz (2014)

[[Category:Information]]

SOPS

2025-02-26T17:02:09Z

Dan Tobias: Link YAML and JSON

{{FormatInfo
|formattype=electronic
|subcat=Encryption
|extensions={{ext|yaml}}
{{ext|json}}
|mimetypes={{mimetype|application/json}}
{{mimetype|application/yaml}}
|pronom=
|wikidata=
|released=2016
}}

'''SOPS'' ('''Secrets OPerationS''') is a structured format for managing secret keys. It belongs to the SOPS application ('''Simple and flexible tool for managing secrets''') and allows users to create encrypted key-value pairs for managing secrets. The utility is potentially helpful for development teams managing keys across projects. The primary formats that SOPS supports are <code>[[JSON]]</code> and <code>[[YAML]]</code>.

== About ==

SOPS is initialized within your default editor using a key, e.g. PGP key. You can then proceed to create a data structure as you chose, the idea being, the keys in your structure will be encoded in plain-text once saved, and your values, again, once saved, will be encrypted. Similarly, decryption requires your keys to decode the SOPS structure back into the original data structure you began with.

== Configuration and examples ==

=== Test install ===

An example from the SOPS README shows how to test the utility using its example pgp key:

<pre>
git clone https://github.com/getsops/sops.git
cd sops
cd cmd
go mod tidy
go build
gpg --import pgp/sops_functional_tests_key.asc
</pre>

=== Example YAML ===

Given the above, you can then elect to edit a YAML file:

<pre>
./sops edit example.yaml
</pre>

SOPS will bring up a default object, although this can be deleted and you can encode any structure.

<pre>
hello: Welcome to SOPS! Edit this file as you please!!
example_key: example_value
# Example comment
example_array:
- example_value1
- example_value2
example_number: 1234.56789
example_booleans:
- true
- false

</pre>

When this file is saved, values are wrapped with semantic information to help decoding, and a <code>'sops'</code> key created containing decode and encryption specific information.

<pre>
hello: ENC[AES256_GCM,data:uHToaQKhNuSRfJLfVPmBBAYzwDcA7OQ/gyd8AZqPtdAszHk4SevC6xA34x55tXU=,iv:M/ni78KR8us2zBf4myH+8QsivUyudM8DSKGdx0j7ltc=,tag:zECH/1665g+ebSu5HL0ppw==,type:str]
example_key: ENC[AES256_GCM,data:MjFv3ewfpq1Sq+3WJg==,iv:NT/Yb3XawHuX/ypbzm9WPRLIar11Fq5uF0vJJtLgphY=,tag:wzlXdbtQBqmUpNcO3GQkng==,type:str]
#ENC[AES256_GCM,data:HlTEj04aNP48sytIFPQhaQ==,iv:CWuWsTk7TmfFAyYUkwW/8xAv2XxY/bwwfCrayo5cCmE=,tag:CEpvfAM6PTZQHxhPv4f0ag==,type:comment]
example_array:
- ENC[AES256_GCM,data:4KxwWTHxEf3LDPx7UFc=,iv:l6caTOPmKxQFK+uREVzgezu2LbCyTEHTMu5bIJdm8+A=,tag:pjsY69yWWvbbGyqtAsPaUQ==,type:str]
- ENC[AES256_GCM,data:vaTUurETsaYDJ6B1A5g=,iv:2UxiUDn6jWFyaZO8micUf/n98ELHLQYWzG74gpCVpy4=,tag:4NB/X0spcKHhbnOmYtZPZQ==,type:str]
example_number: ENC[AES256_GCM,data:816+HcmStO0rpQ==,iv:VLXvtL9uLeylWLzvmXG/kKnxgzE8QuSmWqPGH6su4Fg=,tag:xxCmwfupJWjiO7jf4toHcA==,type:float]
example_booleans:
- ENC[AES256_GCM,data:vtkQiA==,iv:cxbZA3eecGy4XfF6rO2kI4ime9d7gKTqSPSz39tm9Fo=,tag:V71+rHj44N1tiu7uJlHiHg==,type:bool]
- ENC[AES256_GCM,data:Cmv7aVs=,iv:FuyQn7wJrsPXRcloqtOq+PxNvY5DrCRISwGlUsVnmRQ=,tag:cJzDzUJavUbbcBapzQNh1g==,type:bool]
sops:
kms: []
gcp_kms: []
azure_kv: []
hc_vault: []
age: []
lastmodified: "2025-02-26T15:24:03Z"
mac: ENC[AES256_GCM,data:iOigwJNFsPFZ2+hERTWE38izLH7QjiM/I+dxZLpEO8u0dkep/xh1BgtLHJMVspUisq4zI0XOwq4+ZTwpIOpC6yzaLt20X/2cLtWy5ZGlm3Vgo3iT0N7cbggKtXoSZ1XdzY9YP1bQl7grS8bnXYYeIKo5uJO517/nxydtaRYgJc0=,iv:rkE8ti+ZPTZnVlr8Aro32SfT9Lo3XDjUCOvbRqk5OHw=,tag:u5A+2ce1Ojmd6vnYHKm28Q==,type:str]
pgp:
- created_at: "2025-02-26T15:24:00Z"
enc: |-
-----BEGIN PGP MESSAGE-----

hQEMAyUpShfNkFB/AQf/c7gcIWuhhsSfP9rd/ZAicTmh7+SM0GJhMR28snWBD/Sc
sxYqZm+utqJW14Woi/XQUKrC7sanNguUNkCk6SKPKAWnQ+CjzaUlISbDyQwgKpQn
eqr2q/5sFxWpFtzQpryK7lQzhIMbKhIKZh1xliLsL4Knkm2I7FO+KDBfVvJ9lwcR
4dBhXQdZySH4YNDT6Z7zK9o4cXswKa7OgoVHPVtqEHaDc2sA6GKBmrio3A9x5BAX
xbf1r6FfT/XPFP1AlmV1Ixiu80lurfp39SuDfoHU7uVthrK7Oo9A7nd/Uu9zdS5O
7aPrbcSRtTN6ntglm3X/sU6oxgehVaTxipnW79XNntJeAXkFWLo5WMVCaIwXyenM
uCfxeGd+fxL2k1miZC+7cXDorv5FfpAAQGURh3KbujHQ0n+ZriqW0wzYgweMSbFT
skINiavro2+ocZXNrVZWWkexy2P8evcMWPVbVQ5HGw==
=KkKj
-----END PGP MESSAGE-----
fp: FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4
- created_at: "2025-02-26T15:24:00Z"
enc: |-
-----BEGIN PGP MESSAGE-----

hIwDXFUltYFwV4MBA/92mfagks7hCLfAGCuT2yFinvIheHTTfQn/sRHMkU4YsDDs
79fFtpAQRhiEe+2dcHP9QY4vNzk6G8yHnvSrpjkLlBz15F//2DTgPQGK0hutNo4n
PMx+a99RSlvy2GJ/nSS2dBHJBj3JOt6iDk+eVzYQjDo4zjf+qeFm2m4QMkXqNNJe
AY9AJ23ifr0tyhrlGbVd4KNcJmJLg6Vz3nxvG8r7TSLt91bTMUOi6owLkTFl+Tij
X63YSoEauQzc/tSRKJfNFi5No173krsqXFQLyt2LrSPakZ0xgDGwU+fn2KCnmw==
=Bj+H
-----END PGP MESSAGE-----
fp: D7229043384BCC60326C6FB9D8720D957C3D3074
unencrypted_suffix: _unencrypted
version: 3.9.4

</pre>

=== Example JSON ===

Alternatively, you can elect to edit a JSON file:

<pre>
./sops edit example.json
</pre>

SOPS will bring up a default object, although this can be deleted and you can encode any structure.

<pre>
{
"hello": "Welcome to SOPS! Edit this file as you please!!",
"example_key": "example_value",
"example_array": [
"example_value1",
"example_value2"
],
"example_number": 1234.56789,
"example_booleans": [
true,
false
]
}

</pre>

When this file is saved, values are wrapped with semantic information to help decoding, and a <code>'sops'</code> key created containing decode and encryption specific information.

<pre>
{
"hello": "ENC[AES256_GCM,data:5t8seVgX/GxsD6muvKOnVgPjNk8yoX/Gbp3xCt0KuOH0yENKC0I6zyWUBgE0jIE=,iv:iPM4TVZ0GlQMZgEUWbGS+SHNVD0JF8uqT/X+VOij/dw=,tag:8Hnl4Giec2IcriApyc/CLA==,type:str]",
"example_key": "ENC[AES256_GCM,data:LRMvnB36y2AvtrSbFw==,iv:kQ0LE2msZc50QHJhT+V84XbSiUA4yiynztJ/WvOVnFk=,tag:3hP8QJLPWezJ0lqiy7B+Vw==,type:str]",
"example_array": [
"ENC[AES256_GCM,data:rENwn4lVjLQmb06OZo8=,iv:lI6HEkYkOmNavvMczUpc1QdE6sf4oZionB0EAk5o5TM=,tag:Niew51lQ87+JUMJQ0+Qpjw==,type:str]",
"ENC[AES256_GCM,data:cxogL0GVCcgMA7D0bRY=,iv:zblA1Uo6FwYDkRj2RQ/Rv26lGY+Kcqy1IeDHyeJy/JQ=,tag:Pr9BIh1fG5cTKaZLJXuEGw==,type:str]"
],
"example_number": "ENC[AES256_GCM,data:6l6Ez2VJm9AAsw==,iv:24bAR3EGZ+WHK0/4T+hB7/SLeVQ/8m3PsB5k6rYO0qY=,tag:ZVeEwIV0u4Mh48hf5kgjJg==,type:float]",
"example_booleans": [
"ENC[AES256_GCM,data:sla9Gw==,iv:iMuyEFbO4GF5UkSiJY7eJeMd8TtCFtyHpzi0kbQMV60=,tag:nRUuew9bfSXLuZ4sKZr0Pg==,type:bool]",
"ENC[AES256_GCM,data:LmA/l6U=,iv:M5QXLpIRMgH/RpJ6qlU+VtPytJUCT1RdE4FPsQ/WGyc=,tag:9nkIJHA9EQ+PMQVUUgyMSg==,type:bool]"
],
"sops": {
"kms": null,
"gcp_kms": null,
"azure_kv": null,
"hc_vault": null,
"age": null,
"lastmodified": "2025-02-26T15:43:02Z",
"mac": "ENC[AES256_GCM,data:0LWYLJbAbflAzS9URkFFAUzMtZCpqd8KnLQWYQLPJv5x8d9K9zNRh3meRX3PembwtZcr64IoVAJY3ft8Ttt6Dmww+UIhFQAvo8nmbDp3QVwUXzLgpFIodhNyUjSOm3Dj9ZVRXy5emHyd5Ai1ocQ7aUvN/Tj03Cb8DAw9Bf3Z+OU=,iv:S7edialcrk6AHV4UTedYXxVQpz342gpObFypzDdW3X4=,tag:CCpqLgKtnp1sqlgCVUrxnA==,type:str]",
"pgp": [
{
"created_at": "2025-02-26T15:42:52Z",
"enc": "-----BEGIN PGP MESSAGE-----\n\nhQEMAyUpShfNkFB/AQf/XGtcWkKvKJX2Q5gky+ewG+BjIok6Ruw0Q5oebuawTgh0\nxHWN6miY/YSoq4jmz47u5QRYiPxfQ6kmeHYjbrkDJwkqev3dQ9e9X+Auk38W+EiT\nyDYxP9uML+d2GdG9irrHkeeMqZs7NPbohS2AQpT5NgA19PQB2PvwscMRZtOCjnEb\nTJcVZYkHQgXlLHJ6AdmNqneIwca6dN5x6pDnfys8oErK9bl5bsDAzm8LzOzIKHkf\nLKWRNyXkE2VBLjaTU431k7zXvG7F1BcA3BuaLhJaAPEkjg8wSy2H0Mx1fcTNoqfI\ncezuL+BUgNR0C2JVAzqgiP/92FADXl9NJpHCG+JzJdJcAdY8JIXqYcmJZqQYu82+\nNwykwnrdu6r/RWkDk0P+/u6GKVz6KCkAn5p9e45zs/z1fv1KfQMCM58w6fTEIdDW\n0sChyjEmxZq8wuu6c3xKxyCihVvL6SgIaY483zM=\n=794N\n-----END PGP MESSAGE-----",
"fp": "FBC7B9E2A4F9289AC0C1D4843D16CEE4A27381B4"
},
{
"created_at": "2025-02-26T15:42:52Z",
"enc": "-----BEGIN PGP MESSAGE-----\n\nhIwDXFUltYFwV4MBA/wJkpY5y4wGupEEJKOwomPtCFDTCgn7ug3KFFMAbHm3lz6M\nd+a2CPr3jSEpyjE1VbLAWnxFpfoDTNzqOdWmCbwRkNCjV3ih9Y0SLVL0al/STz1T\nLQw99VN3IRMbTO9wbQ/OpyS+rodP4W/EmzHR5DQCqNH+8A/koWsjc1Fz/zIqC9Jc\nAQh0P381qCx5lbow8JaBmYZ9BE2qDmRC2uw0W8LYNP7sWAVxSXfwTqNV3YEtomnf\nQGGPnRKnGq3HrTgCKE9pAypYcCSariQEDV2aM6v8C5cfocVY6tco16qG2bg=\n=VpnI\n-----END PGP MESSAGE-----",
"fp": "D7229043384BCC60326C6FB9D8720D957C3D3074"
}
],
"unencrypted_suffix": "_unencrypted",
"version": "3.9.4"
}
}

</pre>

== Identification ==

It should be possible to create a signature from the SOPS data structure, looking for the <code>'sops'</code> key and some of the values encoded within there, e.g <code>'lastmodified'</code> and <code>'mac'</code> are two important values for the format. Additional details here, and understanding of the format will benefit signature research.

== Links and references ==

* [https://getsops.io/ SOPS website]
* [https://github.com/getsops/sops SOPS on GitHub]
* [https://www.youtube.com/watch?v=V2PRhxphH2w Introduction tutorial on YouTube]

IBM Displaywriter

2025-02-24T21:50:18Z

Dan Tobias:

IBM 6580 DisplayWriter

A microcomputer for textprocessing which could also be used as terminal to "real" IBM computers.

8" floppy disks for storage, and the character set is some kind of extended EBCDIC or possibly EBCDIC with switchable code pages.

Bitsavers have many documents, but I found non describing the filesystem.

I had reason to reverse engineer a single such floppy, and got far enough to be able to compare the texts on another preservation copy, so all the hard stuff (tab-settings, etc. etc.) are still outstanding.

My code is now part of the "AutoArchaeologist" software tool

[[Category:Word Processor]]
[[Category:IBM]]

Category:File formats with extension .cfz

2025-01-24T17:36:36Z

Dan Tobias: Created page with "C"

[[Category:File formats by extension|C]]

Squiggle

2025-01-04T19:31:23Z

Dan Tobias: /* Links */

{{FormatInfo
|formattype=Languages
|subcat=Programming Languages
}}
'''Squiggle''' is a specialized programming language designed for displaying probability distributions. It can be used for making "Fermi estimates", such as in a test example of estimating the number of piano tuners in New York City by multiplying various estimated ranges such as the total population, fraction who have pianos, and number of pianos a tuner can service.

The output of Squiggle is a graph of the distribution defined by the ranges and calculations given.

== Links ==
* [https://www.squiggle-language.com/ Official site]
* [https://forum.effectivealtruism.org/posts/TsaRbCotCaWpcrt8F/squiggle-why-and-how-to-use-it Squiggle: How and Why to Use It]
* [https://www.lesswrong.com/posts/7worWgggeHL3Eb7wq/introducing-squiggle-ai Introducing Squiggle AI]