http://fileformats.archiveteam.org/api.php?action=feedcontributions&user=Tekkno&feedformat=atomJust Solve the File Format Problem - User contributions [en]2024-03-29T09:40:10ZUser contributionsMediaWiki 1.19.2http://fileformats.archiveteam.org/wiki/BlakHoleBlakHole2022-10-23T09:45:21Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|subcat=Archiving<br />
|extensions={{ext|bh}}<br />
}}<br />
<br />
'''BlakHole''' is a fairly obscure archiving format supported by a handful of multi-format archiving programs. Similar to some other formats such as [[ZIP]] and [[ARJ]], BlakHole puts multiple files together in one compressed file. It's a proprietary format from the ZipTV Compression Components - a library for Delphi.<br />
<br />
== Programs supporting this format ==<br />
* [http://www.powerarchiver.com/ PowerArchiver]<br />
* [http://downloads.info/windows/utilities/compression/ls-archiver.html LS Archiver]<br />
* [https://www.izarc.org/ IZArc]<br />
<br />
== Sample files ==<br />
* [https://www.dan.info/sampledata/test.bh test.bh]</div>Tekknohttp://fileformats.archiveteam.org/wiki/IThmbIThmb2019-09-20T15:26:05Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|name=iThmb<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|ithmb}}<br />
}}<br />
{{DISPLAYTITLE:iThmb}}<br />
<br />
'''iThmb''' is a format used in iOS to store thumbnail versions of images (such as in the photo library). Pictures are converted to this format when imported into devices such as iPhones and iPads, and are intended and optimized for viewing on those devices and nowhere else, but users sometimes seek a means of exporting them to other systems if they have pictures on an iOS device and no longer have other copies of them elsewhere.<br />
Older ITHMB files were uncompressed and used YUV colorspace. Newer ones use JPEG compression.<br />
<br />
== Software ==<br />
* [http://www.ithmbconverter.com/ iThmb converter]<br />
* [[Konvertor]]<br />
* [http://www.ultrafileopener.com/formats/ithmb/index2.php?utm_expid=44280878-30 Ultra File Opener]<br />
* [http://apps.microsoft.com/windows/en-us/app/compuclever-ithmb-viewer/6e58b482-8b6e-4fbb-9485-2ba746cbcd7d CompuClever iThmb Viewer]<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
* [https://tomseditor.com/convert/ Online Converter]<br />
<br />
== Sample files ==<br />
* Many iThmb files can be found by searching the web for [https://www.google.com/search?q=%22index+of%22+ipod+photo+cache "index of" ipod photo cache].<br />
<br />
== Links ==<br />
* [https://discussions.apple.com/thread/2640386?start=0&tstart=0 Discussion on converting iThmb files]<br />
* [http://www.ithmbconverter.com/en/help/welcome-to-ithmb-converter/what-is-ithmb-format/ What is iThmb format]<br />
* [http://forums.ilounge.com/ipod-classic-legacy-ipods/110066-hacking-ithmb-file-format.html Hacking iThmb file format]<br />
<br />
[[Category:IOS]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/EncryptionEncryption2019-05-23T01:13:27Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|thiscat=Encryption<br />
|image=Detective in spyglass.png<br />
}}<br />
== Ciphers ==<br />
* [[AES]]<br />
* [[Blowfish]]<br />
* [[DES]]<br />
* [[RC4]]<br />
* [[Triple DES]]<br />
<br />
== Cryptographic hash functions ==<br />
* [[BLAKE]]<br />
* [[BLAKE2]]<br />
* [[MD4]]<br />
* [[MD5]]<br />
* [[RIPEMD]]<br />
* [[RIPEMD-160]]<br />
* [[SHA-1]]<br />
* [[SHA-2]]<br />
* [[SHA-3]]<br />
For non-cryptographic hash functions, see [[Error detection and correction]].<br />
<br />
== Password hashes ==<br />
* [[Argon2]]<br />
* [[bcrypt]]<br />
* [[passwd#crypt|crypt]]<br />
* [[PBKDF2]]<br />
* [[scrypt]]<br />
<br />
See also [[passwd#Password field]].<br />
<br />
== Formats and protocols ==<br />
* [[Cryptoloop]]<br />
* [[DissidentX]]<br />
* [[dm-crypt]]<br />
* [[Javascript Object Signing and Encryption]] (JOSE)<br />
* [[JSON Web Encryption]] (JWE)<br />
* [[Loop-AES]]<br />
* [[LUKS]]<br />
* [[MCrypt]] (.nc)<br />
* [[OpenSSL salted format]]<br />
* [[PGP]]<br />
** [[PGP public key]]<br />
* [[Silent Circle Instant Messaging Protocol]]<br />
* [[SSL]]<br />
* [[TrueCrypt]]<br />
<br />
== Digital rights management (DRM) ==<br />
Main article: [[Digital Rights Management]]<br />
<br />
* [[Content Scramble System]] (used on DVDs)<br />
<br />
== Blockchain-related systems ==<br />
(see also [[Currency]], where most such systems, including [[Bitcoin]], are documented; however, applications of blockchain technology beyond currency use are now appearing)<br />
* [[Tezos]]<br />
<br />
== Miscellaneous ==<br />
* [[Cryptolocker]]<br />
* [[Exclusive Or]]<br />
* [[Mono]]<br />
* [[OpenSSL]]<br />
* [[ROT13]]<br />
* [[Steganography]]<br />
<br />
== See also ==<br />
See also [[Security]] for information on digital certificates and electronic signing. Various other formats, including [[compression]], [[archiving]], and [[filesystem]] formats, may support encryption as a built-in feature or through plug-ins.<br />
<br />
== External links ==<br />
<br />
=== Security techniques ===<br />
* [http://boingboing.net/2013/02/22/secure-documents.html One way to keep your documents secure...]<br />
* [https://mashable.com/2013/06/28/encryption-apps/ Is It the Dawn of the Encryption App?]<br />
* [http://news.cnet.com/8301-13578_3-57602246-38/amid-nsa-uproar-encryption-standards-body-defends-process/ Amid NSA uproar, encryption-standards body defends process]<br />
* [http://blogs.fsfe.org/greve/?p=634 STEED: project to create nonproprietary encryption]<br />
* [https://www.schneier.com/blog/archives/2013/10/defending_again_1.html Defending Against Crypto Backdoors]<br />
* [http://www.darkmail.info/ Dark Mail Alliance] - developing end-to-end encryption for e-mail<br />
* [http://www.flossmanuals.org/news/floss-manuals-content-being-used-cryptoparties FLOSS Manuals content being used in CryptoParties]<br />
* [http://www.wired.com/wiredscience/2014/02/cryptography-breakthrough/all/ Cryptography Breakthrough Could Make Software Unhackable]<br />
* [http://boingboing.net/2014/06/09/time-capsule-crypto-to-help-jo.html Time-capsule crypto to help journalists protect their sources]<br />
<br />
=== Code breaking, bugs, and back doors ===<br />
* [http://www.schneier.com/blog/archives/2012/12/breaking_hard-d.html Breaking Hard-Disk Encryption]<br />
* [http://blog.whitehatsec.com/cracking-aes-256-dmgs-and-epic-self-pwnage/ Password Cracking AES-256 DMGs and Epic Self-Pwnage]<br />
* [http://www.wired.com/wiredscience/2013/06/quantum-cryptography-hack/ Laws of Physics Say Quantum Cryptography Is Unhackable. It’s Not]<br />
* [http://news.netcraft.com/archives/2013/06/25/ssl-intercepted-today-decrypted-tomorrow.html SSL: Intercepted today, decrypted tomorrow]<br />
* [http://boingboing.net/2013/09/05/report-nsa-slices-through-mos.html Report: NSA slices through most 'net encryption, according to 'Bullrun' documents leaked by Snowden]<br />
* [http://arstechnica.com/security/2014/03/critical-crypto-bug-leaves-linux-hundreds-of-apps-open-to-eavesdropping/ Critical crypto bug leaves Linux, hundreds of apps open to eavesdropping]<br />
* [http://www.macworld.com/article/2055640/researchers-challenge-apples-claim-of-unbreakable-imessage-encryption.html Researchers challenge Apple's claim of unbreakable iMessage encryption]<br />
* [http://boingboing.net/2013/12/20/nsa-had-secret-deal-on-back-do.html NSA had secret deal on back-doored crypto with security firm RSA, Snowden docs reveal]<br />
* [http://op-co.de/blog/posts/android_ssl_downgrade/ Why Android SSL was downgraded from AES256-SHA to RC4-MD5 in late 2010]<br />
* [http://security.stackexchange.com/questions/70719/ssl3-poodle-vulnerability SSL3 “POODLE” Vulnerability]<br />
<br />
=== Unsolved codes/ciphers ===<br />
* [http://mobile.reuters.com/article/idUSBRE8AM0E520121123?irpc=932 70-year old code uncracked]<br />
* [http://boingboing.net/2014/03/25/mysterious-coded-messages-at-u.html Mysterious coded messages at university library]<br />
* [http://www.wired.com/dangerroom/2012/12/codes/?pid=1708&viewall=true 7 Codes You’ll Never Ever Break]<br />
* [http://www.nbcnews.com/science/worlds-most-mysterious-manuscript-has-genuine-message-6C10444898 World's most mysterious manuscript has genuine message]<br />
<br />
=== Tools, Utilities, and Software ===<br />
* [http://coptr.digipres.org/Category:Encryption_Detection Encryption Detection: COPTR]<br />
* [https://libfte.org/ LibFTE: A toolkit for constructing practical, format-abiding encryption schemes.]<br />
* [https://keybase.io/ Keybase: look up public keys connected with social-media usernames]<br />
* [http://ziin.pl/en/easy_hash Easy Hash: free program which can calculate over 180 hash functions and checksums]<br />
<br />
=== Miscellaneous ===<br />
* [http://cryptofloricon.com/ Cryptofloricon: send a message with flowers] (not a ''secret'' one, though, since the decryption key is on the website!)<br />
* [https://www.schneier.com/crypto-gram-9810.html#cipherdesign Memo to the Amateur Cipher Designer]<br />
* [http://www.theonion.com/articles/fasttalking-computer-hacker-just-has-to-break-thro,32000/ Fast-Talking Computer Hacker Just Has To Break Through Encryption Shield Before Uploading Nano-Virus (The Onion)]<br />
* [http://io9.com/check-out-the-cipher-from-an-assassination-attempt-on-q-1567478070 Check Out the Cipher from an Assassination Attempt on Queen Elizabeth]<br />
* [http://regmedia.co.uk/2014/05/16/0955_peter_gutmann.pdf Crypto Won’t Save You Either]<br />
* [http://codegolf.stackexchange.com/questions/32024/i-am-passive-aggressive-and-want-to-insult-my-boss-without-him-finding-out?stw=2 Programming-contest entries to hide a nasty message in note to boss]<br />
* [http://motherboard.vice.com/read/the-secret-codes-that-cartels-use-to-send-orders-from-prison?trk_source=recommended The Secret Codes That Cartel Bosses Use to Send Handwritten Orders from Prison]<br />
* [https://github.com/lclevy/firepwd/blob/master/mozilla_pbe.pdf Mozilla Password Based Encryption]</div>Tekknohttp://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)DGI (Digi-Pic)2019-05-09T13:12:33Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|dgi}}<br />
|released=≤1986<br />
}}<br />
'''DGI''' is a raster graphics format apparently associated with something called ''Digi-Pic''.<br />
<br />
Images are 640x400. File size is 64 008 Bytes. File size and presence of colors suggest 2 bpp. Image is stored in 8 planes. Each plane is 640x100 mono. 8 planes * 640*100 = 64 000 Bytes. The 8 extra bytes are located at offset 32000 (but why?).<br />
<br />
DGIMAC.EXE converts .DGI images into monochrome by ignoring every second bit of image. TURBODGI.ZIP displays image in 3 colors (gray, black, red).<br />
<br />
== Software ==<br />
* [http://cd.textfiles.com/carousel344/003/TURBODGI.ZIP TURBODGI.ZIP]: ''Turbo DiGI Vision Display Utility'', a viewer for MS-DOS by Basi Angulo<br />
* [http://cd.textfiles.com/carousel344/015/CGADGI.ZIP CGADGI.ZIP]: Viewer for MS-DOS<br />
* [http://cd.textfiles.com/carousel344/003/CONV125.ZIP CONV125.ZIP] → DGIMAC.EXE: MS-DOS utility to convert DGI to [[MacPaint]] format<br />
<br />
== Sample files ==<br />
* [http://cd.textfiles.com/carousel344/026/TIPS.ZIP TIPS.ZIP] → TIPS.DGI (image is NSFW)</div>Tekknohttp://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)DGI (Digi-Pic)2019-05-09T13:11:32Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|dgi}}<br />
|released=≤1986<br />
}}<br />
'''DGI''' is a raster graphics format apparently associated with something called ''Digi-Pic''.<br />
<br />
Images are 640x400. File size is 64 008 Bytes. File size and presence of colors suggest 2 bpp. Image is stored in 8 planes. Each plane is 640x100 mono. 8 planes * 640*100 = 64 000 Bytes. The 8 extra bytes are located at offset 32000 (but why?).<br />
<br />
DGIMAC.EXE converts .DGI images into monochrome by ignoring every second bit of image. TURBODGI.ZIP displays image in 3 colors (gray, black, red).<br />
<br />
== Software ==<br />
* [http://cd.textfiles.com/carousel344/003/TURBODGI.ZIP TURBODGI.ZIP]: ''Turbo DiGI Vision Display Utility'', a viewer for MS-DOS by Basi Angulo<br />
* [http://cd.textfiles.com/carousel344/015/CGADGI.ZIP CGADGI.ZIP]: Viewer for MS-DOS<br />
* [http://cd.textfiles.com/carousel344/003/CONV125.ZIP CONV125.ZIP] → DGIMAC.EXE: MS-DOS utility to convert DGI to [[MacPaint]] format<br />
<br />
== Sample files ==<br />
* [http://cd.textfiles.com/carousel344/026/TIPS.ZIP TIPS.ZIP] → TIPS.DGI (may be NSFW)</div>Tekknohttp://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)DGI (Digi-Pic)2019-05-09T01:59:39Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|dgi}}<br />
|released=≤1986<br />
}}<br />
'''DGI''' is a raster graphics format apparently associated with something called ''Digi-Pic''.<br />
<br />
Images are 640x400. File size is 64 008 Bytes. File size and presence of colors suggest 2 bpp. Image is stored in 8 planes. Each plane is 640x100 mono. 8 planes * 640*100 = 64 000 Bytes. So there are 8 extra bytes (but why?).<br />
<br />
== Software ==<br />
* [http://cd.textfiles.com/carousel344/003/TURBODGI.ZIP TURBODGI.ZIP]: ''Turbo DiGI Vision Display Utility'', a viewer for MS-DOS by Basi Angulo<br />
* [http://cd.textfiles.com/carousel344/015/CGADGI.ZIP CGADGI.ZIP]: Viewer for MS-DOS<br />
* [http://cd.textfiles.com/carousel344/003/CONV125.ZIP CONV125.ZIP] → DGIMAC.EXE: MS-DOS utility to convert DGI to [[MacPaint]] format<br />
<br />
== Sample files ==<br />
* [http://cd.textfiles.com/carousel344/026/TIPS.ZIP TIPS.ZIP] → TIPS.DGI (may be NSFW)</div>Tekknohttp://fileformats.archiveteam.org/wiki/Just_Solve_the_File_Format_Problem:Community_portalJust Solve the File Format Problem:Community portal2019-05-09T01:39:57Z<p>Tekkno: /* Reverse engineering formats */</p>
<hr />
<div>: ''please add your signature by typing <nowiki>~~~~</nowiki> if you add or reply<br />
<br />
== Open issues ==<br />
<br />
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.<br />
<br />
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]]. <br />
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)<br />
: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)<br />
::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)<br />
:::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)<br />
<br />
== Article naming convention ==<br />
<br />
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.<br />
<br />
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)<br />
: 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.<br />
<br />
: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).<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
::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)<br />
::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)<br />
::: 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)<br />
::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)<br />
:::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)<br />
<br />
== So now what? ==<br />
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)<br />
: 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)<br />
<br />
== Anybody else still around? ==<br />
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)<br />
<br />
: 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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
== Spam ==<br />
<br />
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)<br />
<br />
:...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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
== Orphaned / Blank Pages ==<br />
<br />
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?<br />
<br />
* [[Emulation]]<br />
* [[FAQ:File Format]]<br />
* [[File format extensions list]] (seems to be used for the "ext:" pages but hasn't been updated)<br />
* [[Library]]<br />
* [[Original Plan]]<br />
* [[RAD Game Tools]] (should probably have the individual formats moved to appropriate sections)<br />
* [[Statistica]] (clearly belongs in Scientific Data formats, but I'm not sure where)<br />
<br />
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.<br />
<br />
* [[AA]]<br />
* [[Compressed executable (.com)]]<br />
* [[SAP]]<br />
* [[Barnes & Noble Fixed-layout Format]]<br />
<br />
[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 10:41, 22 January 2013 (UTC)<br />
<br />
: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)<br />
: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)<br />
<br />
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)<br />
<br />
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)<br />
<br />
== Permissions for user pages ==<br />
<br />
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)<br />
<br />
: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)<br />
<br />
== cd.textfiles.com ==<br />
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)<br />
<br />
: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)<br />
<br />
== Broken image in footer ==<br />
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)<br />
<br />
== Wikipedia links ==<br />
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?<br />
<br />
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)<br />
<br />
== Google Code ==<br />
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.<br />
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=http%3A%2F%2Fcode.google.com&namespace= links to http://code.google.com]<br />
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fcode.google.com&namespace= links to https://code.google.com]<br />
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:05, 11 January 2016 (UTC)<br />
<br />
== Cleanup of top-level categories ==<br />
(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:<br />
* A new "Meta" category, for articles about the File Formats Wiki (e.g. [[FAQ]], [[Original Plan]], [[Statement of Project]], [[Main Page]], ...).<br />
* Rename the [[:Category:Geek humor|Geek humor]] category to "Humor"<br />
* Remove the [[:Category:Computer facts|Computer facts]] category<br />
* A new "Information" category, for relevant informative articles ([[Ontology]], [[Patents]], ...) that don't have a more suitable top-level category.<br />
* 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.)<br />
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 15:56, 1 June 2017 (UTC)<br />
<br />
[[Category:Meta]]<br />
<br />
== Love It! ==<br />
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:<br />
<br />
* [[SWF#Software]]<br />
* [[FLA#Software]]<br />
* [[BSON#Libraries]]<br />
<br />
Thanks again!<br />
<br />
PS: Can the "thumbs up" icon be changed to something better? Do you want me to design a possible logo?<br />
<br />
[[User:Hgupta|Hgupta]] ([[User talk:Hgupta|talk]]) 05:42, 17 August 2017 (UTC)<br />
<br />
: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)<br />
<br />
:I support the idea of changing the logo. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:08, 18 August 2017 (UTC)<br />
<br />
== What time is it? ==<br />
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)<br />
:"Does anybody really know what time it is; does anybody really care?" -- Chicago<br />
[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)<br />
<br />
== Type / Creator codes ==<br />
<br />
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)<br />
<br />
* [[Wikipedia:Type_code|Type Code : Wikipedia]] <br />
* [[Wikipedia:Creator_code|Creator Code : Wikipedia]] <br />
* [http://www.lacikam.co.il/tcdb/ TCDBx unmaintained]<br />
* [https://vintageapple.org/macprogramming/pdf/The_Programmers_Apple_Mac_Sourcebook_1989.pdf The Programmers Apple Mac Sourcebook]<br />
* [https://www.macdisk.com/macsigen.php Mac Signatures]<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::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)<br />
<br />
== Reverse engineering formats ==<br />
I am trying to reverse engineer some formats. Sometimes successfully, sometimes not. My most recent attempt is:<br />
* http://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)<br />
<br />
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?<br />
[[User:Tekkno|Tekkno]] ([[User talk:Tekkno|talk]]) 01:39, 9 May 2019 (UTC)</div>Tekknohttp://fileformats.archiveteam.org/wiki/Just_Solve_the_File_Format_Problem:Community_portalJust Solve the File Format Problem:Community portal2019-05-09T01:38:35Z<p>Tekkno: </p>
<hr />
<div>: ''please add your signature by typing <nowiki>~~~~</nowiki> if you add or reply<br />
<br />
== Open issues ==<br />
<br />
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.<br />
<br />
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]]. <br />
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)<br />
: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)<br />
::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)<br />
:::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)<br />
<br />
== Article naming convention ==<br />
<br />
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.<br />
<br />
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)<br />
: 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.<br />
<br />
: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).<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
::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)<br />
::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)<br />
::: 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)<br />
::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)<br />
:::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)<br />
<br />
== So now what? ==<br />
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)<br />
: 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)<br />
<br />
== Anybody else still around? ==<br />
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)<br />
<br />
: 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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
== Spam ==<br />
<br />
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)<br />
<br />
:...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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
== Orphaned / Blank Pages ==<br />
<br />
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?<br />
<br />
* [[Emulation]]<br />
* [[FAQ:File Format]]<br />
* [[File format extensions list]] (seems to be used for the "ext:" pages but hasn't been updated)<br />
* [[Library]]<br />
* [[Original Plan]]<br />
* [[RAD Game Tools]] (should probably have the individual formats moved to appropriate sections)<br />
* [[Statistica]] (clearly belongs in Scientific Data formats, but I'm not sure where)<br />
<br />
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.<br />
<br />
* [[AA]]<br />
* [[Compressed executable (.com)]]<br />
* [[SAP]]<br />
* [[Barnes & Noble Fixed-layout Format]]<br />
<br />
[[User:Halftheisland|Halftheisland]] ([[User talk:Halftheisland|talk]]) 10:41, 22 January 2013 (UTC)<br />
<br />
: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)<br />
: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)<br />
<br />
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)<br />
<br />
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)<br />
<br />
== Permissions for user pages ==<br />
<br />
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)<br />
<br />
: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)<br />
<br />
== cd.textfiles.com ==<br />
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)<br />
<br />
: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)<br />
<br />
== Broken image in footer ==<br />
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)<br />
<br />
== Wikipedia links ==<br />
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?<br />
<br />
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)<br />
<br />
== Google Code ==<br />
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.<br />
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=http%3A%2F%2Fcode.google.com&namespace= links to http://code.google.com]<br />
* [http://fileformats.archiveteam.org/index.php?title=Special%3ALinkSearch&target=https%3A%2F%2Fcode.google.com&namespace= links to https://code.google.com]<br />
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 21:05, 11 January 2016 (UTC)<br />
<br />
== Cleanup of top-level categories ==<br />
(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:<br />
* A new "Meta" category, for articles about the File Formats Wiki (e.g. [[FAQ]], [[Original Plan]], [[Statement of Project]], [[Main Page]], ...).<br />
* Rename the [[:Category:Geek humor|Geek humor]] category to "Humor"<br />
* Remove the [[:Category:Computer facts|Computer facts]] category<br />
* A new "Information" category, for relevant informative articles ([[Ontology]], [[Patents]], ...) that don't have a more suitable top-level category.<br />
* 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.)<br />
[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 15:56, 1 June 2017 (UTC)<br />
<br />
[[Category:Meta]]<br />
<br />
== Love It! ==<br />
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:<br />
<br />
* [[SWF#Software]]<br />
* [[FLA#Software]]<br />
* [[BSON#Libraries]]<br />
<br />
Thanks again!<br />
<br />
PS: Can the "thumbs up" icon be changed to something better? Do you want me to design a possible logo?<br />
<br />
[[User:Hgupta|Hgupta]] ([[User talk:Hgupta|talk]]) 05:42, 17 August 2017 (UTC)<br />
<br />
: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)<br />
<br />
:I support the idea of changing the logo. [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:08, 18 August 2017 (UTC)<br />
<br />
== What time is it? ==<br />
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)<br />
:"Does anybody really know what time it is; does anybody really care?" -- Chicago<br />
[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)<br />
<br />
== Type / Creator codes ==<br />
<br />
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)<br />
<br />
* [[Wikipedia:Type_code|Type Code : Wikipedia]] <br />
* [[Wikipedia:Creator_code|Creator Code : Wikipedia]] <br />
* [http://www.lacikam.co.il/tcdb/ TCDBx unmaintained]<br />
* [https://vintageapple.org/macprogramming/pdf/The_Programmers_Apple_Mac_Sourcebook_1989.pdf The Programmers Apple Mac Sourcebook]<br />
* [https://www.macdisk.com/macsigen.php Mac Signatures]<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::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)<br />
<br />
== Reverse engineering formats ==<br />
I am trying to reverse engineer some formats. Sometimes successfully, sometimes not. My most recent attempt is:<br />
* http://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)<br />
<br />
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?<br />
[[User:Tekkno|Tekkno]] 01:38,, 9 May 2019 (UTC)</div>Tekknohttp://fileformats.archiveteam.org/wiki/DGI_(Digi-Pic)DGI (Digi-Pic)2019-05-09T01:30:41Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|dgi}}<br />
|released=≤1986<br />
}}<br />
'''DGI''' is a raster graphics format apparently associated with something called ''Digi-Pic''.<br />
<br />
Images are 640x400. File size is 64 008 Bytes. File size and presence of colors suggest 2 bpp. Image is stored in 8 planes. Each plane is 320x200 mono. First 2 planes create top left corner of the image.<br />
Next 2 planes create top right corner of the image. And so on. 8 planes * 320*200 = 64 000 Bytes. So there are 8 extra bytes (but why?).<br />
<br />
== Software ==<br />
* [http://cd.textfiles.com/carousel344/003/TURBODGI.ZIP TURBODGI.ZIP]: ''Turbo DiGI Vision Display Utility'', a viewer for MS-DOS by Basi Angulo<br />
* [http://cd.textfiles.com/carousel344/015/CGADGI.ZIP CGADGI.ZIP]: Viewer for MS-DOS<br />
* [http://cd.textfiles.com/carousel344/003/CONV125.ZIP CONV125.ZIP] → DGIMAC.EXE: MS-DOS utility to convert DGI to [[MacPaint]] format<br />
<br />
== Sample files ==<br />
* [http://cd.textfiles.com/carousel344/026/TIPS.ZIP TIPS.ZIP] → TIPS.DGI (may be NSFW)</div>Tekknohttp://fileformats.archiveteam.org/wiki/Doodle!_(C64)Doodle! (C64)2019-05-08T00:17:07Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Commodore graphics formats<br />
|extensions={{ext|dd}}, {{ext|jj}}<br />
|released=~1985<br />
}}<br />
'''Doodle!''' is a raster image format associated with the ''Doodle!'' drawing program for Commodore 64 computers. It is not related to the Atari [[Doodle (Atari)|Doodle]] format.<br />
<br />
There is an uncompressed and a compressed version of the format. On platforms that use filename extensions, uncompressed files use extension '''.dd''', and compressed files use extension '''.jj'''.<br />
<br />
== Identification ==<br />
Uncompressed files begin with {{magic|00 1C}}, or possibly {{magic|00 5C}}. Some sources say they are 9218 bytes in size, while others imply that sizes of 9026 and 9346 are also possible.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[RECOIL]]<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://recoil.sourceforge.net/examples.zip → *.dd, *.JJ<br />
* [ftp://8bitfiles.net/archives/genie-commodore-file-library/HiResGraphics/DOODLEPIC1.ARC DOODLEPIC1.ARC], [ftp://8bitfiles.net/archives/genie-commodore-file-library/HiResGraphics/DOODLEPIC2.ARC DOODLEPIC2.ARC]<br />
* http://whatis.rest7.com/how-to-open-dd-file<br />
<br />
== Links ==<br />
* [http://www.c64-wiki.com/index.php/Doodle Doodle], from the C64-Wiki</div>Tekknohttp://fileformats.archiveteam.org/wiki/Doodle_(Atari)Doodle (Atari)2019-05-08T00:11:56Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Atari graphics formats<br />
|extensions={{ext|doo}}<br />
}}<br />
:''See [[Doodle]] for other formats with that name.''<br />
<br />
'''Doodle''' is a raster image format used on Atari ST computers. It is apparently the native format of a paint program named ''Dr. Doodle''.<br />
<br />
== Format details ==<br />
Files are exactly 32000 bytes in size, and are essentially just a dump of video memory.<br />
<br />
Doodle is supposed to be a high resolution (640×400) bi-level format, but in practice some '''.doo''' files contain a medium resolution (640×200) or low resolution (320×200) image instead. It is not possible to determine the resolution just by looking at the file, and presumably only high resolution format is portable.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[RECOIL]] (Supports only HiRes images)<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
=== High res ===<br />
* [http://samples.libav.org/image-samples/atarist/doodle/ELMRSESN.DOO ELMRSESN.DOO]<br />
* [http://cd.textfiles.com/atarilibrary/atari_cd09/VOLLVERS/LICENSE/PR_PRESS/CLIPS/DLS_11.DOO DLS_11.DOO], [http://cd.textfiles.com/atarilibrary/atari_cd09/VOLLVERS/LICENSE/PR_PRESS/CLIPS/DLS_12.DOO DLS_12.DOO]<br />
<br />
=== Medium res ===<br />
* [http://samples.libav.org/image-samples/atarist/doodle/MEDRES.DOO MEDRES.DOO]<br />
* [http://cd.textfiles.com/crawlycrypt2/utility/disk/diskedit/diskedit.doo diskedit.doo]<br />
<br />
=== Low res ===<br />
* [http://samples.libav.org/image-samples/atarist/doodle/MAGICMTN.DOO MAGICMTN.DOO]<br />
* [http://samples.libav.org/image-samples/atarist/doodle/MEDUSABL.DOO MEDUSABL.DOO]<br />
* [http://cd.textfiles.com/crawlycrypt2/games/joust/joust.doo joust.doo]<br />
<br />
== Links ==<br />
* [http://wiki.multimedia.cx/index.php?title=Doodle MultimediaWiki article]<br />
* {{AtariForumWiki|ST_Picture_Formats|ST Picture Formats}}</div>Tekknohttp://fileformats.archiveteam.org/wiki/DeskMate_PaintDeskMate Paint2019-05-07T23:44:45Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|pnt}}<br />
|released=1986<br />
}}<br />
Tandy '''DeskMate''' is a discontinued line of software consisting of an operating environment, and associated productivity software. Some versions of it include a bitmap graphics editor named '''Paint''', which has a native '''.PNT''' file format.<br />
<br />
The DeskMate versions named ''Personal DeskMate'' and ''Personal DeskMate 2'' definitely used this format. It is not clear whether ''Professional DeskMate'' did. It is not clear whether there are versions for the Tandy Color Computer that did. As of ''DeskMate 3.00'', Paint was no longer inclded, and instead there was a vector graphics editor named [[DeskMate Draw|Draw]].<br />
<br />
Images can be compressed or not and use at most 16 colors per pixel.<br />
<br />
== Identification ==<br />
Files begin with bytes {{magic|13 50 4e 54}}.<br />
<br />
== Software ==<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* [http://www.oldskool.org/guides/tvdog/deskmate.html DeskMate Programs and Related Files] → [ftp://ftp.oldskool.org/pub/tvdog/tandy1000/deskmate/deskp.zip deskp.zip]<br />
<br />
== Links ==<br />
* [ftp://ftp.oldskool.org/pub/tvdog/tandy1000/deskmate/pdm2man.zip Personal Deskmate manual]<br />
* [ftp://ftp.oldskool.org/pub/tvdog/tandy1000/deskmate/pdmman.zip Personal Deskmate 2 manual]<br />
* [http://toastytech.com/guis/pdm3.html Timeline of MS-DOS-based DeskMate versions]<br />
* [[Wikipedia: DeskMate]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/DEGAS_imageDEGAS image2019-05-07T19:04:34Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Atari graphics formats<br />
|extensions={{ext|pi1}}, {{ext|pi2}}, {{ext|pi3}}, {{ext|pc1}}, {{ext|pc2}}, {{ext|pc3}}<br />
}}<br />
'''DEGAS image''' refers to a family of raster graphics formats associated with the ''DEGAS'' (or ''D.E.G.A.S.'', for ''Design & Entertainment Graphic Arts System'') and ''DEGAS Elite'' paint programs for Atari ST.<br />
<br />
The compressed formats use [[PackBits]] compression.<br />
<br />
== Formats ==<br />
There are nine main DEGAS image formats:<br />
{| class="wikitable"<br />
! Format<br />
! Resolution<br />
! Ext.<br />
! Signature<br />
! File size<br />
|-<br />
|DEGAS low res. || 320×200, 16 colors || .PI1 || {{magic|00 00}} || 32034<br />
|-<br />
|DEGAS medium res. || 640×200, 4 colors || .PI2 || {{magic|00 01}} || 32034<br />
|-<br />
|DEGAS high res. || 640×400, 2 colors || .PI3 || {{magic|00 02}} || 32034<br />
|-<br />
|DEGAS Elite low res. || 320×200, 16 colors || .PI1 || {{magic|00 00}} || 32066<br />
|-<br />
|DEGAS Elite medium res. || 640×200, 4 colors || .PI2 || {{magic|00 01}} || 32066<br />
|-<br />
|DEGAS Elite high res. || 640×400, 2 colors || .PI3 || {{magic|00 02}} || 32066<br />
|-<br />
|DEGAS Elite low res. compressed || 320×200, 16 colors || .PC1 || {{magic|80 00}} || (varies)<br />
|-<br />
|DEGAS Elite medium res. compressed || 640×200, 4 colors || .PC2 || {{magic|80 01}} || (varies)<br />
|-<br />
|DEGAS Elite high res. compressed || 640×400, 2 colors || .PC3 || {{magic|80 02}} || (varies)<br />
|}<br />
<br />
For formats with extensions '''.PI4''' through '''.PI9''', see [[Extended DEGAS image]].<br />
<br />
== Related formats ==<br />
Other DEGAS formats:<br />
* [[DEGAS Elite icon]] (.ICN)<br />
* DEGAS Elite block (.BL1, .BL2, .BL3): These files are in [[ILBM]] format, with an unusual file extension. ([http://cd.textfiles.com/806atari/401-500/438/DEGELITE/BLOCKS/ examples])<br />
* DEGAS Elite brush (.BRU) ([http://cd.textfiles.com/806atari/401-500/438/DEGELITE/BRUSHES/ examples])<br />
* DEGAS Elite fill pattern (.FIL, .FI1, .FI2) ([http://cd.textfiles.com/806atari/401-500/438/DEGELITE/FILLS/ examples])<br />
* [[Extended DEGAS image]] (.PI4, .PI5, .PI6, .PI7, .PI8, .PI9)<br />
<br />
See also:<br />
* [[Atari ST color palette]]<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[RECOIL]]<br />
* [[Netpbm]]: pi1toppm, pi3topbm, pc1toppm<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/suzybatari2/degas/<br />
* http://cd.textfiles.com/geminiatari/FILES/EMAG/ (see the [http://cd.textfiles.com/geminiatari/FILES/EMAG/00_LIST.TXT index])<br />
* http://samples.libav.org/image-samples/atarist/degas/<br />
* [http://www.page6.org/st_lib/st_lib.htm ST Library] →<br />
** [http://www.page6.org/st_lib/standard/st0005.php ST5] (PI1, PI2)<br />
** [http://www.page6.org/st_lib/standard/st0370.php ST370] (PC1)<br />
** [http://www.page6.org/st_lib/standard/st1049.php ST1049] (PI1)<br />
** [http://www.page6.org/st_lib/clipart/cl053.php CL053] through [http://www.page6.org/st_lib/clipart/cl070.php CL070] (PI3)<br />
** [http://www.page6.org/st_lib/clipart/cl071.php CL071] (PI3, PC3)<br />
* http://whatis.rest7.com/how-to-open-pi1-file (Sample Degas Pi1 images)<br />
* http://whatis.rest7.com/how-to-open-pi2-file (Sample Degas Pi2 images)<br />
* http://whatis.rest7.com/how-to-open-pi3-file (Sample Degas Pi3 images)<br />
<br />
== Resources ==<br />
* {{AtariForumWiki|ST_Picture_Formats|ST Picture Formats}}<br />
* [http://wiki.multimedia.cx/index.php?title=Degas MultimediaWiki article]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Dr._Halo_CUTDr. Halo CUT2019-05-07T18:33:41Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|cut}}, {{ext|pal}}, {{ext|pic}}<br />
|pronom={{PRONOM|x-fmt/316}}, {{PRONOM|fmt/1186}}<br />
}}<br />
'''Dr. Halo''' was a line of raster image editing software for MS-DOS. It has a well-known device-independent '''.CUT''' image format, which uses [[Run-length encoding|RLE compression]] (in a way which is similar to, but not the same as, [[PackBits]]). CUT files are sometimes accompanied by '''.PAL''' palette files.<br />
<br />
There is also a device-dependent '''.PIC''' image format. We have not located any details about PIC format.<br />
<br />
== Format details ==<br />
All CUT images have exactly 8 bits per pixel, but all 8 bits might not be used. It is common for the only color codes used by an image to be 0 and 1.<br />
<br />
It is not clear what to do if no palette file is present. Interpreting the image as grayscale, with black=0, seems to be standard practice. But different viewers use different logic for guessing the code that should be interpreted as white.<br />
<br />
== Software ==<br />
* [[ImageMagick]] (format named "CUT"; read only)<br />
* [[Konvertor]] (read only)<br />
* [[XnView]] (read only)<br />
* [[Farbfeld Utilities]] (read/write)<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
* Dr. Halo (read/write)<br />
** [https://archive.org/details/Dr.HaloIII3.0KyeOEM Dr. Halo III] - Floppy disk images from archive.org<br />
** [https://archive.org/details/Dr.HaloPlus3.00QTronixOEMGerman Dr. Halo Plus 3.00 (German)] - Floppy disk images from archive.org<br />
** Possibly relevant: [http://cd.textfiles.com/rbbsv3n1/dull/drhalo.unp drhalo.unp]<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/fantaziasampler/CLIPART/CUT/<br />
* http://cd.textfiles.com/gameempire/SOFT/NEW/PRO7/<br />
* http://cd.textfiles.com/librisbritannia/GRAPHICS/CLIPDRHA/ ...<br />
** [http://cd.textfiles.com/librisbritannia/GRAPHICS/CLIPDRHA/1169.ZIP 1169.ZIP] - PIC format<br />
<br />
== Links ==<br />
* {{EGFF|drhalo|Dr. Halo File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [http://www.textfiles.com/programming/FORMATS/pix_fmt.txt Picture format docs (of a number of formats including this one)]<br />
<br />
[[Category:Multi-file formats]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/CUT_(Amstrad)CUT (Amstrad)2019-05-07T17:00:43Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|cut}}<br />
}}<br />
'''CUT''' is a raster image format, apparently associated with [[CP/M]] and/or Amstrad computers.<br />
<br />
It is not related to [[Dr. Halo]]'s CUT format.<br />
<br />
== Specifications ==<br />
* [http://www.chiark.greenend.org.uk/~jacobn/cpm/mdaspec.html#cut The CUT image format]<br />
<br />
== Sample files ==<br />
* [http://www.classiccmp.org/cpmarchives/cpm/mirrors/ftp.demon.com/pub/cpm/mdaspec.com mdaspec.com] ([[PMA]] format) → diagram.cut<br />
* http://whatis.rest7.com/how-to-open-cut-file (Atari logo)<br />
<br />
== Software ==<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
* [[XnView]]<br />
<br />
[[Category:Amstrad]]<br />
[[Category:CP/M]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/COKE_(Atari_Falcon)COKE (Atari Falcon)2019-05-07T16:39:14Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Atari graphics formats<br />
|extensions={{ext|tg1}}<br />
}}<br />
'''COKE format''' is a simple uncompressed raster image format associated with Atari Falcon computers.<br />
<br />
== Identification ==<br />
Files begin with ASCII "{{magic|COKE format.}}".<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/atarilibrary/atari_cd07/DEMOS/XPERIENC/ → *.TG1<br />
<br />
== Specifications ==<br />
* {{AtariForumWiki|COKE_file_format|COKE file format}}, from the Atari Forum Wiki<br />
<br />
== Software ==<br />
* [[RECOIL]]<br />
* [[Tom's Viewer]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Cisco_IP_Phone_imageCisco IP Phone image2019-05-07T16:22:38Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|cip}}<br />
}}<br />
'''Cisco IP Phone image''' is an uncompressed raster image file format for bi-level and 4-tone grayscale images. It is a text format, based on [[XML]].<br />
<br />
The file can contain additional data describing how to present the image on a Cisco IP Phone.<br />
<br />
== Identification ==<br />
Files begin with a "<code>CiscoIPPhoneImage</code>" XML element.<br />
<br />
== Specifications ==<br />
* Cisco Unified IP Phone Services Application Development Notes: [http://developer.cisco.com/web/ipps/home IPPS Developer Center] → Documentation...<br />
* [http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/all_models/xsi/8_0_1/xmlobjects.html#wp1033528 Developer notes for Release 3.3(2)] (old version)<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[ImageMagick]] (format named "CIP"; write-only)<br />
* [[Tom's Viewer]]<br />
* [http://search.cpan.org/~mrpalmer/Cisco-IPPhone-0.05/IPPhone.pm Cisco/IPPhone Perl module]<br />
<br />
[[Category:XML based file formats]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/BRender_PIXBRender PIX2019-05-07T16:15:09Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|pix}}<br />
}}<br />
'''BRender PIX''' is a raster image format associated with the ''BRender'' 3D graphics engine from Argonaut Games.<br />
<br />
== Identification ==<br />
PIX files begin with (hex) bytes <code>00 00 00 12 00 00 00 08 00 00 00 02 00 00 00 02</code>.<br />
<br />
== Software ==<br />
* [[FFmpeg]]<br />
* [[Konvertor]]<br />
* [[XnView]] (Claims to support BRender PIX, but we could not confirm.)<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/cdaction/cdaction20b/IWAR/BRENDER/DAT/<br />
<br />
== Links ==<br />
* [http://web.archive.org/web/19970524151531/http://www.argonaut.com/brender/index.html 1997 archive of BRender web site]<br />
* [[Wikipedia:Argonaut Games|Wikipedia: Argonaut Games]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Bob_ray_tracer_bitmapBob ray tracer bitmap2019-05-07T16:07:51Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|bob}}<br />
|released=1992<br />
}}<br />
'''Bob ray tracer bitmap''' refers to the raster image format used for output by the ''Bob'' ray tracer software. See [[Bob ray tracer scene description]] for more information about Bob.<br />
<br />
== Format ==<br />
The format appears to be a simple uncompressed paletted image format. A file begins with 4 bytes for the dimensions, then 768 bytes for the palette. The rest of the file is the image pixels.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://www.fileformat.info/format/vividbob/sample/index.htm → MARBLES.BOB<br />
<br />
== See also ==<br />
* [[Bob ray tracer scene description]]<br />
* [[Vivid scene description]]<br />
<br />
== Links ==<br />
* [http://www.fileformat.info/resource/book/1558512470/index.htm Photorealism and Ray Tracing in C] - book by Christopher D. Watkins, Stephen B. Coy, Mark Finlay<br />
* {{EGFF|vividbob|Vivid and Bob File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]] - Related information, but doesn't mention this format directly</div>Tekknohttp://fileformats.archiveteam.org/wiki/BioRad_confocal_imageBioRad confocal image2019-05-07T16:06:28Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Health and Medicine<br />
|extensions={{ext|pic}}<br />
}}<br />
A '''BioRad confocal image''' is an image from a type of microscope used in health and research imaging applications, which uses a stepper motor to collect a series of images of a three-dimensional object which can be used in both 2-D and 3-D imaging.<br />
<br />
== Identification ==<br />
Bytes <code>0x39 0x30</code> appear at offset 54.<br />
<br />
== File format info ==<br />
* [http://lists.umn.edu/cgi-bin/wa?A2=ind9704&L=confocalmicroscopy&P=963 A message discussing the file format]<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: bioradtopgm<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
== File conversion and manipulation info ==<br />
* [http://depts.washington.edu/rubelab/protocols/ObjectImage&Confocal.html Using Object-Image with Confocal Microscope Images]<br />
* [http://rsb.info.nih.gov/nih-image/more-docs/confocals.html NIH docs on manipulating confocal images]<br />
* [http://lists.umn.edu/cgi-bin/wa?A2=ind9601&L=confocalmicroscopy&P=12824 Converting TIFF to PIC file]<br />
<br />
== Other links ==<br />
* [http://depts.washington.edu/keck/intro.htm Why use a confocal microscope?]<br />
* [http://www.biotechniques.com/multimedia/archive/00003/BTN_A_000112798_O_3722a.pdf Over the rainbow: 25 years of confocal imaging]<br />
* [http://www.mrc-lmb.cam.ac.uk/rlw/text/tutorials/fluorescence_microscopy/Radiance2100Brochure.pdf Brochure on BioRad Radiance systems]<br />
* [http://isu.technion.ac.il/ISU/Templates/showpage.asp?DBID=1&LNGID=1&TMID=84&FID=575&PID=1014 Confocal Bio-Rad MRC 1024]<br />
* [http://www.uq.edu.au/sbms/calm/documents/MRC_600.pdf Start-up directions: BioRad MRC 600]<br />
* [http://www.microscopyu.com/articles/confocal/threecolorconfocal.html Methods and Applications of Three-Color Imaging for Laser Scanning Confocal Microscopy]<br />
<br />
[[Category:Graphics]]<br />
[[Category:3D and CAD/CAM Models]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/AVS_X_imageAVS X image2019-05-07T14:57:49Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|x}}, {{ext|avs}}, {{ext|mbfavs}}<br />
}}<br />
'''AVS X image''' (or '''Stardent AVS X image''') is a simple raster image file format. It stores uncompressed RGBA images. AVS undoubtedly stands for ''Application Visualization System''.<br />
<br />
== Format ==<br />
Files have an 8-byte header containing the width and height, followed by the pixel data.<br />
<br />
== Software ==<br />
* [[ImageMagick]] (format named "AVS")<br />
* [[Konvertor]]<br />
* [[Netpbm]] (starting with version 10.50): pamtoavs, avstopam<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* [http://paulbourke.net/dataformats/avs_x/ AVS Image Format] → [http://paulbourke.net/dataformats/avs_x/mandrill.x.gz mandrill.x.gz] ''[Ed. note: This file may be bogus.]''<br />
<br />
== Links ==<br />
* [http://paulbourke.net/dataformats/avs_x/ AVS Image Format]<br />
<br />
== Editors' notes ==<br />
The coding of the alpha samples is unknown to us. In the mandrill.x.gz sample file, the alpha samples are all 0, implying that 0 means ''opaque''. But the applications we've looked at all think that 0 means ''transparent''.<br />
<br />
There might be some information buried in [http://bitsavers.informatik.uni-stuttgart.de/pdf/stardent/ these documents].</div>Tekknohttp://fileformats.archiveteam.org/wiki/ART_(PFS:_First_Publisher)ART (PFS: First Publisher)2019-05-07T14:55:26Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|art}}<br />
}}<br />
:''See [[ART]] for other formats with that name.''<br />
<br />
'''PFS: 1st Publisher Clip Art Format''' ('''ART''') is an uncompressed bi-level image file format.<br />
<br />
== Format details ==<br />
''[Partial decoding, based on open source software, and analysis of ART files.]''<br />
<br />
Multi-byte integers are little-endian.<br />
<br />
{| class="wikitable"<br />
! Offset !! Length !! Field !! Details<br />
|-<br />
|0 || 2 || || Unknown. Observed to be 0.<br />
|-<br />
|2 || 2 || width || Image width in pixels<br />
|-<br />
|4 || 2 || || Unknown. Observed to be 0.<br />
|-<br />
|6 || 2 || height || Image height in pixels<br />
|-<br />
|8 || || image_data || Pixels are in left-to-right, top-to-bottom order. 8 pixels per byte, most significant bit first, black is 0. Rows are padded to the next 2-byte boundary.<br />
|}<br />
<br />
== Software ==<br />
* [[ImageMagick]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/fantaziasampler/CLIPART/ART/<br />
* http://cd.textfiles.com/swinnund/disk3/CLIPART/ → 1STPUB3.EXE, ARTFILE?.EXE, ART_FPUB.EXE ([[Self-extracting ZIP]] format)</div>Tekknohttp://fileformats.archiveteam.org/wiki/Apple_volume_label_imageApple volume label image2019-05-07T14:47:20Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
}}<br />
'''Apple volume label image''' is a raster image format apparently associated with the MacOS boot loader.<br />
<br />
It is a 16-color grayscale format. The height of the image must be exactly 12 pixels. Images are not compressed.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: ppmtoapplevol (write-only)<br />
* [http://refit.sourceforge.net/ rEFIt] → vollabel.py<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://kanotix.acritox.com/files/mac/label.vollabel<br />
<br />
== Links ==<br />
* [http://refit.sourceforge.net/info/vollabel.html rEFIt document about volume labels]<br />
<br />
[[Category:Macintosh]]<br />
[[Category:Booting]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Abekas_YUVAbekas YUV2019-05-07T14:35:48Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|yuv}}<br />
}}<br />
'''Abekas YUV''' is a raster image file format. Images use the [[YUV]] color space, and are subsampled.<br />
<br />
It is a ''[[Raw bitmap|raw]]'' format, storing only the bitmap. It cannot be decoded unless you know, or can figure out, the image dimensions.<br />
<br />
Note that there are other YUV image formats that also use the .yuv extension. The Diskus YUV format is apparently the same as the Abekas one, using only raw data for the three color layers and no headers. Apparently "qcif format" is one label for a family of YUV formats, but the format of a particular file can vary in the size of each of the layers and whether they are interlaced or progressive. Quantel raw uncompressed YCbCr (QNT) is another format label.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: ppmtoyuv, yuvtoppm <br />
* [http://www.sunrayimage.com/yuvtools.html YUVTools]<br />
<br />
== Sample files ==<br />
* [http://www.sunrayimage.com/examples.html Some example YUV files] (qcif format), 6 frame animations<br />
<br />
== Resources ==<br />
* [http://netpbm.sourceforge.net/doc/ppmtoyuv.html ppmtoyuv manual]<br />
* [http://www.sunrayimage.com/yuvformat.html YUV format discussion]<br />
* [http://www.fourcc.org/yuv.php YUV pixel formats]</div>Tekknohttp://fileformats.archiveteam.org/wiki/AAIAAI2019-05-07T14:29:04Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|aai}}<br />
}}<br />
'''AAI''' is a raster image file format associated with Dune HD media players. It is a simple uncompressed truecolor format, with support for alpha transparency.<br />
<br />
== Format ==<br />
Files have an 8-byte header containing the width and height, followed by the image data.<br />
<br />
== Specifications ==<br />
* [http://dune-hd.com/firmware/misc/AAImageGen-README.txt AAImageGen-README.txt]<br />
<br />
== Sample files ===<br />
* [[Tom's Viewer]] can create .AAI<br />
<br />
== Software ==<br />
* [[ImageMagick]]<br />
* [[Konvertor]]<br />
* [[Tom's Viewer]]<br />
* [http://dune-hd.com/firmware/misc/ Dune Firmware Zone] → AAImageGen.exe<br />
<br />
== Links ==<br />
* [http://dune-hd.com/ Dune HD website]</div>Tekknohttp://fileformats.archiveteam.org/wiki/J6IJ6I2019-04-27T22:01:58Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Cameras and Digital Image Sensors<br />
|extensions={{ext|j6i}}<br />
}}<br />
'''J6I''' is a format used in Ricoh digital cameras, and was once in common use, though not any more. It is one of the many formats for which any attempt at a search for details results mostly in scads of the cookie-cutter sites that sprout up like kudzu to "document" every file format, but are exceedingly short in actually useful information. By putting this page here, we've probably added one more not-so-much-information page to that bunch, but at least it's a wiki so that if you do happen to have a bit more to say, you can edit it yourself to add it and help future information-seekers.<br />
<br />
The format is apparently related to [[JPEG]], but given some proprietary twists.<br />
<br />
J6I files are created by Ricoh RDC-2 and Ricoh RDC-2E. Maybe other models too. Format was in use around 1998. It seems this is just a JPEG with a custom header added before it. The header contains date. The image is saved in weird proportions 1:2. Which means the height needs to be doubled in order to display properly.<br />
It's possible that Arcsoft's Photostudio 2.0 can convert JPEG images into J6I.<br />
Ricoh RDC-2E captures images in resolution 768 x 576.<br />
<br />
[[Konvertor]] supposedly supports it.<br />
[[XnView]] is reported to support it.<br />
<br />
== Software ==<br />
[[Tom's Viewer]]<br />
<br />
[[Category:Graphics]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/IThmbIThmb2019-04-27T21:56:53Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|name=iThmb<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|ithmb}}<br />
}}<br />
{{DISPLAYTITLE:iThmb}}<br />
<br />
'''iThmb''' is a format used in iOS to store thumbnail versions of images (such as in the photo library). Pictures are converted to this format when imported into devices such as iPhones and iPads, and are intended and optimized for viewing on those devices and nowhere else, but users sometimes seek a means of exporting them to other systems if they have pictures on an iOS device and no longer have other copies of them elsewhere.<br />
Older ITHMB files were uncompressed and used YUV colorspace. Newer ones use JPEG compression.<br />
<br />
== Software ==<br />
* [http://www.ithmbconverter.com/ iThmb converter]<br />
* [[Konvertor]]<br />
* [http://www.ultrafileopener.com/formats/ithmb/index2.php?utm_expid=44280878-30 Ultra File Opener]<br />
* [http://apps.microsoft.com/windows/en-us/app/compuclever-ithmb-viewer/6e58b482-8b6e-4fbb-9485-2ba746cbcd7d CompuClever iThmb Viewer]<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* Many iThmb files can be found by searching the web for [https://www.google.com/search?q=%22index+of%22+ipod+photo+cache "index of" ipod photo cache].<br />
<br />
== Links ==<br />
* [https://discussions.apple.com/thread/2640386?start=0&tstart=0 Discussion on converting iThmb files]<br />
* [http://www.ithmbconverter.com/en/help/welcome-to-ithmb-converter/what-is-ithmb-format/ What is iThmb format]<br />
* [http://forums.ilounge.com/ipod-classic-legacy-ipods/110066-hacking-ithmb-file-format.html Hacking iThmb file format]<br />
<br />
[[Category:IOS]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Nokia_Logo_Manager_bitmapNokia Logo Manager bitmap2019-04-27T21:56:06Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|nlm}}<br />
}}<br />
'''Nokia Logo Manager bitmap''' ('''NLM''') is a raster image format associated with Nokia phones and related software. It is also known by other similar names, such as '''Nokia Logo File''' and '''Nokia Phones LogoManager Bitmap'''.<br />
<br />
The file's header has a field indicating that it can store one of several kinds of logo images: "Operator", "Caller", "Startup", or "Picture".<br />
<br />
== Format ==<br />
Files have a 10-byte header.<br />
<br />
== Identification ==<br />
Files begin with the ASCII string "<code>NLM </code>" (<code>4E 4C 4D 20</code>).<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
* [http://www.irfanview.com/ IrfanView]<br />
* [http://wammu.eu/gammu/ Gammu]<br />
<br />
== Sample files ==<br />
* http://www.corsasport.co.uk/phone/corsasport.nlm<br />
* http://www.smsxchange.com/account/whitepaper.pdf - Has a [[Hex encoding|hex-encoded]] sample file<br />
<br />
[[Category:Nokia]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/TI_picture_fileTI picture file2019-04-27T21:55:14Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|73i}}, {{ext|82i}}, {{ext|83i}}, {{ext|8xi}}, {{ext|85i}}, {{ext|86i}}, {{ext|89i}}, {{ext|92i}}, {{ext|9xi}}, {{ext|v2i}}<br />
}}<br />
'''TI picture file''' is a family of bi-level raster image formats used with Texas Instruments calculators. A picture file is a kind of [[TI variable file]] that contains a variable of type "picture".<br />
<br />
There is a version of the format for each model of TI calculator. About three or four of the versions are meaningfully different.<br />
<br />
== Identification ==<br />
All TI files begin with an 8 byte ASCII signature that starts with "<code>**TI</code>" and indicates the version or model, for example "<code>**TI92**</code>" or "<code>**TI83F*</code>".<br />
<br />
Picture files use a filename extension that ends with the letter "i".<br />
<br />
There are also "group" files, whose extension ends with "g". A group file contains multiple variables, one or more of which may be images.<br />
<br />
== Specifications ==<br />
* [http://merthsoft.com/linkguide/ TI Link Protocol Guide] ([http://www.ticalc.org/archives/files/fileinfo/247/24750.html download]) - See [TI* → File Formats] and [TI* → Variable Formats → Pictures]<br />
<br />
== Software ==<br />
* [http://webmail.ticalc.org/archives/files/fileinfo/256/25671.html gp_tipic.tar.gz] - GIMP plugin (for [http://www.gimp.org GIMP]; requires libtifiles from [http://www.ticalc.org/archives/files/fileinfo/374/37479.html tilibs])<br />
* [[Konvertor]]<br />
* [[XnView]] (Supports some .92i files, at least)<br />
* {{Deark}}<br />
* [[Tom's Viewer]]<br />
* [http://imageconverter.rest7.com/ Rest7 Online Image Converter]<br />
<br />
== Sample files ==<br />
* [http://www.ticalc.org/pub/ ticalc.org archives] → [model] → basic → media → images<br />
** Or sometimes [model] → basic → graphics<br />
<br />
[[Category:Texas Instruments]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/PSDPSD2019-04-27T21:54:14Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|psd}}<br />
|mimetypes={{mimetype|image/vnd.adobe.photoshop}}<br />
|pronom={{PRONOM|x-fmt/92}}<br />
|released=≥1990<br />
}}<br />
'''PSD''' is the native layered raster graphics file format of the [[Photoshop|Adobe Photoshop]] program line. The format has gone through multiple versions, each being downwards (but not always upwards) compatible.<br />
<br />
PSD is a partially-documented proprietary format. It is very large and complex. Despite this, decoding the primary image of a PSD file is often fairly simple. If an application claims to support PSD, that could mean just about anything.<br />
<br />
== Format details ==<br />
=== Compression ===<br />
Images are usually compressed with [[PackBits]], or uncompressed. "Zip" compression, which apparently means [[zlib]], is also supported.<br />
<br />
=== Text encoding ===<br />
PSD files often contain both [[Unicode]] and non-Unicode text. It's not clear whether there is a good way to determine the encoding of the non-Unicode text. Some sources claim [[MacRoman]], which is true in many cases, but other encodings have been observed.<br />
<br />
== Identification ==<br />
PSD files begin with bytes <code>'8' 'B' 'P' 'S' 0x00 0x01</code>.<br />
<br />
== See Also ==<br />
* [[PSB]]<br />
* [[PhotoDeluxe]] (PDD)<br />
<br />
See [[Photoshop]] for other related formats.<br />
<br />
== Specifications ==<br />
* [https://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ Adobe Photoshop File Formats Specification] (current version)<br />
** Other versions (from archive.org): [https://web.archive.org/web/20110109163057/http://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2010-07] · [https://web.archive.org/web/20120910224552/http://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2012-06] · [https://web.archive.org/web/20121209170357/http://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2012-12] · [https://web.archive.org/web/20130725152233/http://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2013-06] · [https://web.archive.org/web/20160617040616/https://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2013-10] · [https://web.archive.org/web/20160701113240/https://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2016-06] · [https://web.archive.org/web/20160917163012/http://www.adobe.com/devnet-apps/photoshop/fileformatashtml/ 2016-08]<br />
* [ftp://ftp.buerliag.ch/pub/Documentation/Adobe/Photoshop/ps6ffspecsv2.pdf Photoshop File Formats Specification V6.0 Release 2]<br />
* [ftp://ftp.ora.com/pub/examples/gff/CDROM/GFF/VENDSPEC/ADOBEPHO/PHOTOSDK.PDF PHOTOSDK.PDF] - Adobe Photoshop 3.0.4 SDK<br />
** [ftp://ftp.ora.com/pub/examples/gff/CDROM/GFF/VENDSPEC/ADOBEPHO/ADOBE.TXT ADOBE.TXT] - Photoshop 3.0.4 File Format<br />
* [ftp://ftp.ora.com/pub/examples/gff/CDROM/GFF/VENDSPEC/ADOBEPHO/PHOTOSHP.TXT PHOTOSHP.TXT] - Adobe Photoshop 2.5 File Format<br />
* [https://github.com/layervault/psd.rb/wiki/Anatomy-of-a-PSD-File PSD.rb: Anatomy of a PSD File]<br />
<br />
== Software ==<br />
=== Viewers, editors, and converters ===<br />
* [[Adobe Photoshop]]<br />
* [[ImageMagick]]<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
=== Libraries and tools ===<br />
* [https://github.com/layervault/psd.rb PSD.rb] (Ruby)<br />
* [https://pypi.python.org/pypi/psd-tools/ psd-tools] (Python)<br />
* [https://sourceforge.net/projects/libpsd/ Libpsd] (C)<br />
* [https://github.com/alco/psdump psdump] (C++; uses Libpsd)<br />
<br />
== Sample files ==<br />
* "Free PSD" websites are abundant. Some examples:<br />
** [http://www.psdking.eu/ PsdKing]<br />
** [http://www.psdgraphics.com/ psdGraphics]<br />
** [http://www.freepik.com/free-psd Freepik → PSD]<br />
* [https://github.com/devbrain/tombexcavator/tree/master/data/PSD tombexcavator samples]<br />
<br />
== Links ==<br />
See also [[Photoshop#Links]].<br />
<br />
* [[Wikipedia: Adobe Photoshop#File format]]<br />
* [https://www.adobe.com/products/photoshop.html Adobe Photoshop website]<br />
* {{EGFF|psd|Adobe Photoshop File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [http://git.gnome.org/browse/gimp/tree/plug-ins/file-psd Open-Source PSD import code from GIMP]<br />
<br />
=== Commentary ===<br />
* [http://blogs.adobe.com/jnack/2009/05/some_thoughts_about_the_psd_format.html Some thoughts about the PSD format]<br />
* [https://bitbucket.org/WAHa_06x36/old-xee/src/fe1cec107972603523e67e7be29a83e493f5cac2/XeePhotoshopLoader.m?fileviewer=file-view-default#XeePhotoshopLoader.m-108 Rant about PSD format in comments of a program's source code]<br />
<br />
[[Category:Adobe]]<br />
[[Category:Photoshop]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/DirectDraw_SurfaceDirectDraw Surface2019-04-27T21:52:35Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|dds}}<br />
|released=~1999<br />
|pronom={{PRONOM|fmt/1040}}<br />
}}<br />
:''DDS redirects here. For the tape format, see [[Digital Data Storage]].''<br />
<br />
'''DirectDraw Surface''' ('''DDS''') is an image file format developed by Microsoft. It is associated with DirectX and related APIs. Some video game graphics use this format. Images may be uncompressed, or use one of several compression algorithms.<br />
<br />
== Identification ==<br />
DDS files begin with ASCII characters "<code>DDS </code>" (hex <code>44 44 53 20</code>).<br />
<br />
== Specifications ==<br />
* Microsoft's [http://msdn.microsoft.com/en-us/library/windows/desktop/bb943992%28v=vs.85%29.aspx Reference for DDS]<br />
<br />
== Software ==<br />
* [[ImageMagick]] (read support starting with v6.3.9-2; write support starting with v6.8.6-10)<br />
* [http://code.google.com/p/gimp-dds/ DDS Plugin for GIMP]<br />
* [https://developer.nvidia.com/content/dds-utilities-83111271645 NVIDIA DDS Utilities]<br />
* [http://www.getpaint.net/ Paint.NET]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* [http://code.google.com/p/tombexcavator/source/browse/#svn%2Ftrunk%2Fdata%2FDDS tombexcavator samples]<br />
== Links ==<br />
* [[Wikipedia:DirectDraw Surface|Wikipedia article]]<br />
* [http://msdn.microsoft.com/en-us/library/windows/desktop/bb943990%28v=vs.85%29.aspx Microsoft's DDS page]<br />
<br />
[[Category:Microsoft]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/SGI_(image_file_format)SGI (image file format)2019-04-27T21:52:07Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|sgi}}, {{ext|bw}}, {{ext|rgb}}, {{ext|rgba}}<br />
|pronom={{PRONOM|x-fmt/140}}<br />
}}<br />
'''SGI''' (also known as '''IRIS''', and sometimes called '''RGB''' or '''Irix RGB''') is a raster image file format. The image may be uncompressed, or use [[Run-length encoding|RLE]] compression.<br />
<br />
SGI probably stands for '''Silicon Graphics Image'''.<br />
<br />
== Image types ==<br />
SGI supports the following image types:<br />
* Grayscale, 8 or 16 bits/sample<br />
* RGB, 8 or 16 bits/sample<br />
* RGBA, 8 or 16 bits/sample<br />
* RGB 3-3-2, 8 bits/pixel (obsolete)<br />
* Colormapped (but no palette is stored in the file) (obsolete)<br />
* Colormap (file contains only a palette; no image) (obsolete)<br />
<br />
== Format ==<br />
SGI files start with a 512-byte fixed header, most of which is unused. If the image is uncompressed, the pixel data follows. Compressed images have a scanline table, followed by the compressed pixel data.<br />
<br />
The pixel data is stored from bottom-up, instead of top-down as in most image formats.<br />
<br />
== Identification ==<br />
SGI files begin with bytes <code>01 DA</code>.<br />
<br />
== Specifications ==<br />
* [ftp://ftp.sgi.com/graphics/grafica/sgiimage.html The SGI Image File Format, Version 1.00]<br />
* [ftp://ftp.sgi.com/graphics/SGIIMAGESPEC The SGI Image File Format, Draft version 0.97]<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: pnmtosgi, sgitopnm<br />
* [[ImageMagick]] (format named "SGI")<br />
* [[Tom's Viewer]]<br />
* [http://svn.osgeo.org/grass/grass/branches/releasebranch_5_5/src.contrib/CERL/SGI/libimage/ libimage]<br />
<br />
== Sample files ==<br />
* [http://ftp.funet.fi/index/graphics/packages/volvis/RGB.tar.Z RGB.tar.Z]<br />
<br />
== External links ==<br />
* [[Wikipedia:Silicon Graphics Image|Wikipedia article]]<br />
* {{EGFF|sgiimage|SGI Image File Format File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Poser_Bump_MapPoser Bump Map2019-04-27T21:46:26Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|bum}}<br />
}}<br />
A '''Poser Bump Map''' (BUM) is a file used by a program called Poser for storing bump maps, which are a variety of bitmaps that represent the texture of a rough 3-D surface. BUM files are actually in the same format as Windows [[BMP]] files, and can be opened in most graphic programs if the extension is renamed to .bmp.<br />
<br />
== Links ==<br />
* [http://docs.daz3d.com/doku.php/artzone/pub/tutorials/textures/textures-poser03 Mastering Bump Maps for Poser and Bryce]<br />
* [http://docs.daz3d.com/doku.php/artzone/pub/tutorials/poser/poser-maps02 Bump Maps and File Formats]<br />
* [http://forum.runtimedna.com/showthread.php?10354-Converting-BUM-files-to-jpg Converting BUM files to jpg (forum discussion)]<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
[[Category:3D and CAD/CAM Models]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/XimXim2019-04-27T21:45:38Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|xim}}<br />
|released=~1989<br />
}}<br />
'''Xim''' is a raster image file format associated with the ''Xim'' (X Image Manipulator) toolkit for [[X Window System|X-Windows]], by Philip R. Thompson.<br />
<br />
== Specifications ==<br />
* http://ftp.x.org/pub/X11R4/tape-2/ → contrib/clients/xim/xim.man (refers to definitions in XimHeader.h, also available as xim.h in the [[Netpbm]] distribution)<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: ximtoppm<br />
* [[Tom's Viewer]]<br />
* [[XnView]] (Seems to misleadingly call this format "Ximage" or "X image".)<br />
* Xim: http://ftp.x.org/pub/X11R4/tape-2/ → contrib/clients/xim/<br />
<br />
== Sample files ==<br />
* http://ftp.x.org/pub/X11R4/tape-2/ → contrib/clients/xim/images/*.xim<br />
<br />
[[Category:X Window System]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/InterpaintInterpaint2019-04-27T21:45:07Z<p>Tekkno: Created page with "{{FormatInfo |formattype=electronic |subcat=Graphics |subcat2=Commodore graphics formats |extensions={{ext|iph}}, {{ext|ipt}} }} '''Interpaint''' is a raster image format asso..."</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Commodore graphics formats<br />
|extensions={{ext|iph}}, {{ext|ipt}}<br />
}}<br />
'''Interpaint''' is a raster image format associated with the ''Interpaint'' drawing program for Commodore 64 computers. <br />
<br />
This is an uncompressed format. On platforms that use filename extensions, uncompressed files use extension '''.iph'' or '''.ipt'''.<br />
<br />
== Identification ==<br />
Uncompressed files begin with {{magic|00 40}}. Size is always 9002 bytes.<br />
<br />
== Software ==<br />
* [[RECOIL]]<br />
* [[Tom's Viewer]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Commodore_graphics_formatsCommodore graphics formats2019-04-27T21:44:26Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|thiscat=Commodore graphics formats<br />
}}<br />
This is a list of graphics formats used on the Commodore 64 and other 8-bit Commodore computers.<br />
<br />
The Commodore 64 did not really use file extensions, but standard extensions seem to have evolved for most of the formats.<br />
<br />
== Graphic modes ==<br />
* [[Multicolor]]<br />
<br />
== Formats ==<br />
* Advanced Art Studio (.ocp, .art, .pic)<br />
* AFLI-editor v2.0 (Topaz Beerlin) (.afl)<br />
* Amica Paint (.ami)<br />
* [[Art Studio]] (.aas, .art)<br />
* [[BFLI]] (Big FLI) (bfl, .bfli)<br />
* Blazing Paddles (.pi)<br />
* CDU-Paint (.cdu)<br />
* Cheese (.che)<br />
* Create with Garfield (.cwg)<br />
* Dolphin Ed (.dol)<br />
* [[Doodle! (C64)]] (.dd, .jj)<br />
* Drazlace (.drl, .dlp)<br />
* Drazpaint (.drp, .drz)<br />
* EAFLI edit v1.0 (.eaf)<br />
* ECI Graphic Editor (.eci, .ecp)<br />
* Face Painter (.fpt)<br />
* [[FFLI]] (.ffli)<br />
* [[Flexible Line Interpretation]] (.fli)<br />
* FLI Designer (.fd2)<br />
* FLI Graph 2.2 (Blackmail) (.bml, .fli)<br />
* Flinterlacer v1.0 (.fln)<br />
* FLI-Profi (.fpr)<br />
* Fun Graphics Machine (.fgs)<br />
* [[Funpaint]]; Fun Painter II (fun, .fp2)<br />
* Generic C64 (.vic)<br />
* Generic IFLI RAW (.raw)<br />
* [[geoPaint]]<br />
* Gigacad (.gcd)<br />
* Gigapaint (.gig, .gih)<br />
* [[GoDot]] (.4bt)<br />
* Gunpaint (.gun, .ifl)<br />
* Hi-Eddi (.hed)<br />
* Hi-Pic Creator (.hpc)<br />
* Hires-Bitmap (.hbm, .hir)<br />
* Hires FLI (Crest) (.hfc)<br />
* Hires Interlace (Feniks) (.hlf)<br />
* Hires-Laze (.hil)<br />
* Hires Manager (Cosmos) (.him)<br />
* Image System (.ism, .ish, .ims)<br />
* Interlace Hires Editor (.ihe)<br />
* [[Interpaint]] (.iph, .ipt)<br />
* [[KoalaPainter]] (.koa, .kla, .gg)<br />
* Logo Painter 3/3+ (.lp3)<br />
* Micro Illustrator (.mil)<br />
* Mono Magic (.mon)<br />
* Multi-Lace Editor (.mle)<br />
* P4I<br />
* Paint Magic (.pmg)<br />
* Picasso 64 (.p64)<br />
* [[Printfox bitmap]] (.bs, .pg, .gb)<br />
* Rainbow Painter (.rp)<br />
* Run Paint (.rpm)<br />
* Saracen Paint (.sar)<br />
* SHFLI Editor v1.0 (.shf)<br />
* SHFLI-XL (.shx)<br />
* SHIFLI Editor v1.0 (.shi)<br />
* Truepaint (.mci, .mcp)<br />
* UFLI Editor v1.0 (.ufl)<br />
* UIFLI Editor v1.0 (.ufi, .uf2)<br />
* [[VBM (VDC BitMap)]] (.vbm, .bm)<br />
* Vidcom 64 (.vid)<br />
* [[Wigmore Artist 64]] (.wig, .a64)<br />
* Zoomatic<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[RECOIL]]<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [http://www.haddewig.de/nogames64/ NoGames64] → [http://www.haddewig.de/nogames64/grafix.html Grafix]<br />
<br />
== See also ==<br />
* [[Commodore 64 color palette]]<br />
<br />
== Links ==<br />
* [http://www.editorix.org/congo/html/c64_image_formats__part_i.html C64 Image Formats, Part I]<br />
* [http://www.editorix.org/congo/html/c64_image_formats__part_ii.html C64 Image Formats, Part II]<br />
* [http://www.studiostyle.sk/dmagic/gallery/gfxmodes.htm Description of C64 graphics modes]<br />
* [http://codebase64.org/doku.php?id=base:c64_grafix_files_specs_list_v0.03 C64 Graphics File Format Specs]<br />
* [http://ist.uwaterloo.ca/~schepers/formats/BITMAP.TXT Identification of C64 bitmap files]<br />
<br />
[[Category:Commodore computers]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Commodore_graphics_formatsCommodore graphics formats2019-04-27T21:43:50Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|thiscat=Commodore graphics formats<br />
}}<br />
This is a list of graphics formats used on the Commodore 64 and other 8-bit Commodore computers.<br />
<br />
The Commodore 64 did not really use file extensions, but standard extensions seem to have evolved for most of the formats.<br />
<br />
== Graphic modes ==<br />
* [[Multicolor]]<br />
<br />
== Formats ==<br />
* Advanced Art Studio (.ocp, .art, .pic)<br />
* AFLI-editor v2.0 (Topaz Beerlin) (.afl)<br />
* Amica Paint (.ami)<br />
* [[Art Studio]] (.aas, .art)<br />
* [[BFLI]] (Big FLI) (bfl, .bfli)<br />
* Blazing Paddles (.pi)<br />
* CDU-Paint (.cdu)<br />
* Cheese (.che)<br />
* Create with Garfield (.cwg)<br />
* Dolphin Ed (.dol)<br />
* [[Doodle! (C64)]] (.dd, .jj)<br />
* Drazlace (.drl, .dlp)<br />
* Drazpaint (.drp, .drz)<br />
* EAFLI edit v1.0 (.eaf)<br />
* ECI Graphic Editor (.eci, .ecp)<br />
* Face Painter (.fpt)<br />
* [[FFLI]] (.ffli)<br />
* [[Flexible Line Interpretation]] (.fli)<br />
* FLI Designer (.fd2)<br />
* FLI Graph 2.2 (Blackmail) (.bml, .fli)<br />
* Flinterlacer v1.0 (.fln)<br />
* FLI-Profi (.fpr)<br />
* Fun Graphics Machine (.fgs)<br />
* [[Funpaint]]; Fun Painter II (fun, .fp2)<br />
* Generic C64 (.vic)<br />
* Generic IFLI RAW (.raw)<br />
* [[geoPaint]]<br />
* Gigacad (.gcd)<br />
* Gigapaint (.gig, .gih)<br />
* [[GoDot]] (.4bt)<br />
* Gunpaint (.gun, .ifl)<br />
* Hi-Eddi (.hed)<br />
* Hi-Pic Creator (.hpc)<br />
* Hires-Bitmap (.hbm, .hir)<br />
* Hires FLI (Crest) (.hfc)<br />
* Hires Interlace (Feniks) (.hlf)<br />
* Hires-Laze (.hil)<br />
* Hires Manager (Cosmos) (.him)<br />
* Image System (.ism, .ish, .ims)<br />
* Interlace Hires Editor (.ihe)<br />
* Interpaint (.iph, .ipt)<br />
* [[KoalaPainter]] (.koa, .kla, .gg)<br />
* Logo Painter 3/3+ (.lp3)<br />
* Micro Illustrator (.mil)<br />
* Mono Magic (.mon)<br />
* Multi-Lace Editor (.mle)<br />
* P4I<br />
* Paint Magic (.pmg)<br />
* Picasso 64 (.p64)<br />
* [[Printfox bitmap]] (.bs, .pg, .gb)<br />
* Rainbow Painter (.rp)<br />
* Run Paint (.rpm)<br />
* Saracen Paint (.sar)<br />
* SHFLI Editor v1.0 (.shf)<br />
* SHFLI-XL (.shx)<br />
* SHIFLI Editor v1.0 (.shi)<br />
* Truepaint (.mci, .mcp)<br />
* UFLI Editor v1.0 (.ufl)<br />
* UIFLI Editor v1.0 (.ufi, .uf2)<br />
* [[VBM (VDC BitMap)]] (.vbm, .bm)<br />
* Vidcom 64 (.vid)<br />
* [[Wigmore Artist 64]] (.wig, .a64)<br />
* Zoomatic<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[RECOIL]]<br />
* [[XnView]]<br />
* [[Tom's Editor]]<br />
* [http://www.haddewig.de/nogames64/ NoGames64] → [http://www.haddewig.de/nogames64/grafix.html Grafix]<br />
<br />
== See also ==<br />
* [[Commodore 64 color palette]]<br />
<br />
== Links ==<br />
* [http://www.editorix.org/congo/html/c64_image_formats__part_i.html C64 Image Formats, Part I]<br />
* [http://www.editorix.org/congo/html/c64_image_formats__part_ii.html C64 Image Formats, Part II]<br />
* [http://www.studiostyle.sk/dmagic/gallery/gfxmodes.htm Description of C64 graphics modes]<br />
* [http://codebase64.org/doku.php?id=base:c64_grafix_files_specs_list_v0.03 C64 Graphics File Format Specs]<br />
* [http://ist.uwaterloo.ca/~schepers/formats/BITMAP.TXT Identification of C64 bitmap files]<br />
<br />
[[Category:Commodore computers]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Art_StudioArt Studio2019-04-27T21:43:34Z<p>Tekkno: Created page with "{{FormatInfo |formattype=electronic |subcat=Graphics |subcat2=Commodore graphics formats |extensions={{ext|art}}, {{ext|aas}} }} '''Art Studio''' is a raster image format asso..."</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|subcat2=Commodore graphics formats<br />
|extensions={{ext|art}}, {{ext|aas}}<br />
}}<br />
'''Art Studio''' is a raster image format associated with the ''Art Studio'' drawing program for Commodore 64 computers. <br />
<br />
This is an uncompressed format. On platforms that use filename extensions, uncompressed files use extension '''.art'' or '''.aas'''.<br />
<br />
== Identification ==<br />
Uncompressed files begin with {{magic|00 20}}. Size is always 9003 bytes.<br />
<br />
== Software ==<br />
* [[RECOIL]]<br />
* [[Tom's Viewer]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/XV_thumbnailXV thumbnail2019-04-27T21:39:48Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|p7}}, others<br />
|released=~1993<br />
}}<br />
'''XV thumbnail''', also known as '''XV Visual Schnauzer''' format, is an image file format used by the ''XV'' image viewer for its thumbnail cache. The color format is 8 bits/pixel RGB 3-3-2.<br />
<br />
Thumbnail files are normally written to a subdirectory named ".xvpics", and evidently use the same filename and extension as the full-size image file. The '''.p7''' extension might be used artificially sometimes, if such a file has been moved out of the .xvpics directory, or created by other means.<br />
<br />
== Identification ==<br />
Files begin with ASCII text "<code>P7 332</code>", followed by a newline.<br />
<br />
Note that they could easily be misidentified as [[PAM (Portable Arbitrary Map)|PAM format]].<br />
<br />
== Specifications ==<br />
The format is described in a "THUMBNAIL FILE FORMAT" comment in the xvbrowse.c file from the XV source distribution (v3.10a, at least).<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: pamtoxvmini, xvminitoppm<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
* [http://www.trilon.com/xv/ XV]<br />
<br />
== Links ==<br />
* [http://www.trilon.com/xv/manual/xv-3.10a/visual-schnauzer-1.html Documentation for XV's Visual Schnauzer feature]</div>Tekknohttp://fileformats.archiveteam.org/wiki/YBMYBM2019-04-27T21:39:14Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|bm}}<br />
|released=≤1989<br />
}}<br />
This article describes the uncompressed bi-level image format that is usually called something like '''Bennet Yee's face format''', and sometimes '''YBM'''. It does not seem to have an official name. It is the format used by [[Netpbm]]'s ybmtopbm/pbmtoybm utilities, and is among the formats supported by the Fuzzy Pixmap library (<code>-B</code> option). It originated with utilities named "face" and "xbm", by Bennet Yee.<br />
<br />
== Disambiguation ==<br />
The name "Bennet Yee's face format" has also been used<ref>[http://ftp.andrew.cmu.edu/pub/AUIS/src/atk/image/faces.c faces.c]: Example of FaceSaver being called "Bennet Yee's face format"</ref> when referring to [[FaceSaver]], a completely different format. This may or may not be an error.<br />
<br />
== Format ==<br />
Files have a 6-byte header, followed by the image data.<br />
<br />
== Identifiers ==<br />
The Fuzzy Pixmap library suggests the file extension '''.bm'''.<br />
<br />
== Identification ==<br />
Files begin with <code>0x21 0x21</code> (ASCII "<code>!!</code>").<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: pbmtoybm, ybmtopbm<br />
* [[Tom's Viewer]]<br />
* [http://ibiblio.org/pub/linux/apps/graphics/convert/fbm-1.2.tgz fbm-1.2.tgz] - Fuzzy Pixmap Manipulation Library (see also [[FBM image]])<br />
<br />
== Editors' notes ==<br />
It would be nice to find copies of the "face" and "xbm" utilities. They are referenced in the man pages of old versions of Netpbm<ref>[http://www.manpager.com/linux/man1/pbmtoybm.1.html Old pbmtoybm man page]</ref>, which suggests that they were publicly available.<br />
<br />
== References ==<br />
<references/><br />
<br />
[[Category:CMU]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Sun_RasterSun Raster2019-04-27T21:38:47Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|sun}}, {{ext|ras}}, {{ext|rast}}, {{ext|rs}}, {{ext|sr}}, {{ext|scr}}, {{ext|im1}}, {{ext|im8}}, {{ext|im24}}, {{ext|im32}}<br />
|pronom={{PRONOM|x-fmt/184}}<br />
|released=≤1989<br />
}}<br />
'''Sun Raster''', or '''Sun Rasterfile''', is an image file format associated with Sun operating systems. It supports grayscale, paletted, and full color images. Images may be uncompressed, or use [[Run-length encoding|RLE]] compression.<br />
<br />
== Format details ==<br />
Files have a fixed 32-byte header, followed by an optional color palette, followed by the image data.<br />
<br />
== Identification ==<br />
Files begin with signature bytes {{magic|59 a6 6a 95}}.<br />
<br />
== Specifications ==<br />
* http://www.fileformat.info/format/sunraster/spec/index.htm<br />
* http://www.martinreddy.net/gfx/2d/RAS.txt<br />
* https://hg.java.net/hg/solaris-x11~x-s12-clone/file/b0bfd498768f/open-src/data/rasterfile/sun-src<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[Netpbm]]: pnmtorast, rasttopnm<br />
* [[ImageMagick]] (format named "RAS" or "SUN")<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://samples.libav.org/image-samples/sunrast/<br />
<br />
== Resources ==<br />
* {{EGFF|sunraster|Sun Raster File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [http://wiki.multimedia.cx/index.php?title=Sun_rasterfile MultimediaWiki article]<br />
* [[Wikipedia: Sun Raster]]<br />
<br />
[[Category:Sun]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/MPlayer_bitmap_fontMPlayer bitmap font2019-04-27T21:38:25Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Fonts<br />
|extensions={{ext|raw}}, {{ext|desc}}<br />
}}<br />
'''MPlayer bitmap font''' is a bitmap font format associated with the ''MPlayer'' video player software.<br />
<br />
The bitmaps are stored in a '''.raw''' file, and other font data is in a '''.desc''' file.<br />
<br />
The '''.raw''' file uses a variant of [[HSI Raw]] format.<br />
<br />
== Software ==<br />
* [https://mplayerhq.hu/ MPlayer]<br />
* [[Netpbm]]: pamtompfont (write-only)<br />
* [[XnView]] - Can display the .raw file<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* https://mplayerhq.hu/MPlayer/releases/fonts/<br />
* https://mplayerhq.hu/MPlayer/contrib/fonts/<br />
<br />
== Links ==<br />
* [https://mplayerhq.hu/ MPlayer website]<br />
** [https://mplayerhq.hu/DOCS/HTML/en/fonts-osd.html#bitmap-fonts MPlayer documentation section on bitmap fonts]<br />
* [http://netpbm.sourceforge.net/doc/pamtompfont.html Netpbm's pamtompfont documentation]<br />
* [[Wikipedia: MPlayer]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Photo_CDPhoto CD2019-04-27T21:37:58Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|pcd}}<br />
|pronom={{PRONOM|fmt/211}}<br />
|released=1992<br />
}}<br />
Kodak '''Photo CD''' ('''PCD''') is an image file format that was used by products and services which developed photographs by digitizing them and writing them to a CD.<br />
<br />
Photo CD files combine six different resolution version of the original image into a single compressed file.<br />
<br />
== Identification ==<br />
The ASCII string "<code>PCD_IPI</code>" appears in the file, usually(?) at offset 2048.<br />
<br />
== Converting PCD to other formats ==<br />
PCD files contain multiple resolutions and have other subtitles that tools must be aware of. [http://www.tedfelix.com/PhotoCD/PCDSoftware.html This page] discusses tool support, and recommends [http://pcdtojpeg.sourceforge.net/Home.html pcdtojpeg] over [[ImageMagick]], which had flaws at that time. It seems that later versions of ImageMagick have dealt with the colour blow-out issues.<br />
<br />
Note that, when converting PCD files using ImageMagick, you must manually select the resolution layer you want. e.g.<br />
<br />
<pre><br />
$ convert BlownJohn.pcd[0] BlownJohn-0.png<br />
$ convert BlownJohn.pcd[1] BlownJohn-1.png<br />
$ convert BlownJohn.pcd[2] BlownJohn-2.png<br />
$ convert BlownJohn.pcd[3] BlownJohn-3.png<br />
$ convert BlownJohn.pcd[4] BlownJohn-4.png<br />
$ convert BlownJohn.pcd[5] BlownJohn-5.png<br />
$ convert BlownJohn.pcd[6] BlownJohn-6.png<br />
$ convert BlownJohn.pcd[7] BlownJohn-7.png<br />
$ convert BlownJohn.pcd[8] BlownJohn-8.png<br />
</pre><br />
<br />
However, examining the results, we can see that some of these are the same:<br />
<br />
<pre><br />
$ ls -l BlownJohn-?.png<br />
52322 BlownJohn-0.png<br />
52322 BlownJohn-1.png<br />
191840 BlownJohn-2.png<br />
707221 BlownJohn-3.png<br />
2476659 BlownJohn-4.png<br />
9668328 BlownJohn-5.png<br />
28572165 BlownJohn-6.png<br />
28572165 BlownJohn-7.png<br />
28572165 BlownJohn-8.png<br />
</pre><br />
<br />
i.e. (0,1) are identical, as are (6,7,8), with (1) being the lowest resolution and (6) being the highest. This is consistent with the six resolutions that should be present in the PCD. For the highest resolution, use this:<br />
<br />
<pre><br />
$ convert BlownJohn.pcd[6] BlownJohn.png<br />
</pre><br />
<br />
The [http://fam-tille.de/debian/pcd2html.html pcd2html] tool may also be useful.<br />
<br />
== Sample files ==<br />
* http://cd.textfiles.com/prettywomen/IMAGES/<br />
* http://www.fileformat.info/format/photocd/sample/index.htm<br />
<br />
== Software ==<br />
* [[Tom's Viewer]]<br />
* [[XnView]]<br />
<br />
== External Links ==<br />
* [[Wikipedia:Photo CD|Wikipedia article]]<br />
* [http://www.kodak.com/go/photocd Kodak Photo CD web page]<br />
* {{EGFF|photocd|Kodak Photo CD File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
<br />
[[Category:Optical Discs]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Scitex_CTScitex CT2019-04-27T21:35:57Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|sct}}, {{ext|ct}}, {{ext|ch}}<br />
|pronom={{PRONOM|x-fmt/146}}<br />
|released=~1986<br />
}}<br />
'''Scitex CT''', or '''Scitex Continuous Tone''', is a raster image file format associated with Scitex workstations. It supports CMYK, RGB, and grayscale images.<br />
<br />
Scitex CT is one of a family of formats known as '''Scitex Handshake'''. The others are LW (Linework), BM (Bitmap), PG (Page), and TX (Text).<br />
<br />
== Identification ==<br />
The ASCII characters "<code>CT</code>" appear at offset 0x50.<br />
<br />
== Software ==<br />
* [[ImageMagick]] (format named "SCT")<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* [http://electricmessiah.org/jay/test_rgb.ct test_rgb.ct]<br />
<br />
== Links ==<br />
* [https://web.archive.org/web/20140711150035/http://oreilly.com/www/centers/gff/formats/scitex/ Scitex HandShake Formats] (from archive.org)<br />
* [http://electricmessiah.org/press/the-scitex-ct-file-format/ The Scitex CT File Format]<br />
* [[Wikipedia:Scitex CT|Wikipedia article]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/HP_PaintjetHP Paintjet2019-04-27T01:41:43Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|pjxl}}<br />
}}<br />
The '''HP Paintjet''' line of printers uses a type of bitmap graphics, apparently in conjunction with the [[PCL]] printer command language, which documents some features involving transmission of bitmaps.<br />
<br />
Apparently such bitmaps have been known to be stored in files with a .pjxl extension, but not much is documented online about them; trying to google it mostly yields the rash of SEO-friendly script-generated sites that put up pages on every conceivable file format written in Mad-Lib style: "Are you trying to open a (PJXL) file? You may want to know what a (PJXL) file is. Well, Joe's Grand File Format Documentation Site is the foremost expert in documenting (PJXL) files. A (PJXL) file is a(n) (HP PAINTJET PCL BITMAP GRAPHIC). How do you open a(n) (HP PAINTJET PCL BITMAP GRAPHIC)? Try these file conversion programs: (NONE LISTED). Or your best approach is to click on the file and hope your operating system is configured by default to open something useful. (Praying a lot might help.)" Perhaps it goes on to advertise a commercial file recovery service that ''specializes'' in (PJXL) files... honest!<br />
<br />
All things considered, ''this'' site is admittedly not being all that much more helpful to you in figuring out what to do with those oddball PJXL files you may be struggling with. But it ''does'' link to the [[PCL]] article, which in turn links to some documentation manuals which might possibly help you. If you find some solid information, it would be nice if you'd register an account on this wiki and participate here by writing up what you've found!<br />
<br />
== Software ==<br />
* [[NetPBM]] ppmtopjxl <br />
<br />
[[Category:Hewlett-Packard]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/QRT_Ray_Tracer_bitmapQRT Ray Tracer bitmap2019-04-27T01:33:23Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|raw}}, {{ext|qrt}}, {{ext|dis}}<br />
|released=1989<br />
}}<br />
'''QRT Ray Tracer bitmap''' is the default output format of the ''QRT Ray Tracer'' (also known as ''Quick Ray Tracer'' or ''QRT'') software. It is an uncompressed truecolor raster image format.<br />
<br />
This format is also used by the ''DKBTrace'' (DKB Ray Tracer) software, which uses a default filename of '''data.dis'''.<br />
<br />
== Format ==<br />
Files have a 4-byte header, containing the width and height. Each row has a 2-byte prefix containing the row number.<br />
<br />
== Identifiers ==<br />
The QRT Ray Tracer software uses the '''.raw''' filename extension for this format. Some third-party applications use '''.qrt''', though this conflicts with [[QRT Ray Tracer scene description]] format.<br />
<br />
== See also ==<br />
* [[QRT Ray Tracer scene description]] (.QRT)<br />
* [[DKBTrace scene description]]<br />
<br />
== Software ==<br />
* [http://www.programmersheaven.com/download/14195/download.aspx QRT Ray Tracer source code] (RAYSRC.ZIP)<br />
* [http://cd.textfiles.com/graphics16000/GENERAL/RAYTRACE/DKB/ DKBTrace]<br />
* [[Konvertor]]<br />
* [[Netpbm]]: qrttoppm<br />
* [[XnView]] (format named QRT or DIS)<br />
* [[Tom's Viewer]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/XBMXBM2019-04-26T23:15:57Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|xbm}}, {{ext|bm}}<br />
|mimetypes={{mimetype|image/x-xbitmap}}<br />
|pronom={{PRONOM|x-fmt/207}}, {{PRONOM|x-fmt/299}}<br />
}}<br />
'''XBM''' ('''X BitMap''') is a file format for bi-level raster images, originally associated with the X Window System. It was, and to some extent still is, widely supported by graphics software.<br />
<br />
An XBM file is plain text, and doubles as a fragment of [[C]] programming code. The format is very inefficient in size, but it can be useful as a simple way to embed an image into a C program.<br />
<br />
== See also ==<br />
* [[XPM]]<br />
<br />
== Specifications ==<br />
* [http://www.x.org/releases/X11R7.7/doc/libX11/libX11/libX11.html#Manipulating_Bitmaps Manipulating Bitmaps] section of [http://www.x.org/releases/X11R7.7/doc/libX11/libX11/libX11.html Xlib - C Language X Interface: X Consortium Standard]<br />
<br />
== Software ==<br />
* [[X Window System]]: [http://cgit.freedesktop.org/xorg/lib/libX11/tree/src/RdBitF.c XReadBitmapFile] & [http://cgit.freedesktop.org/xorg/lib/libX11/tree/src/WrBitF.c XWriteBitmapFile] in [http://cgit.freedesktop.org/xorg/lib/libX11 libX11]<br />
* [[Netpbm]]: pbmtoxbm, xbmtopbm<br />
* [[ImageMagick]]<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [http://www.gimp.org GIMP]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://www.fileformat.info/format/xbm/sample/index.htm<br />
* http://ftp.x.org/pub/individual/data/xbitmaps-1.1.1.tar.gz<br />
* http://cd.textfiles.com/blackcrawling/ICONS/<br />
<br />
== Links ==<br />
* {{EGFF|xbm|XBM File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [[Wikipedia:X BitMap|Wikipedia article]]<br />
* [https://twitter.com/angealbertini/status/532652860702326784/photo/1 Image describing XBM format]<br />
<br />
[[Category:X Window System]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/WBMPWBMP2019-04-26T23:13:59Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|wbmp}}<br />
|mimetypes={{mimetype|image/vnd.wap.wbmp}}<br />
|pronom={{PRONOM|fmt/497}}<br />
}}<br />
'''WBMP''' ('''Wireless Bitmap''', or '''WAP Bitmap''') is an image file format associated with WAP (Wireless Application Protocol). It stores uncompressed bi-level raster images.<br />
<br />
== Specifications ==<br />
* [http://www.wapforum.org/what/technical/SPEC-WAESpec-19990524.pdf WAP WAE Specification, Version 1.1]<br />
<br />
== Software ==<br />
* [[Netpbm]]: pbmtowbmp, wbmptopbm<br />
* [[ImageMagick]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
* [http://libgd.bitbucket.org/ LibGD]<br />
<br />
== Links ==<br />
* [[Wikipedia:Wireless Application Protocol Bitmap Format|Wikipedia article]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/WBMPWBMP2019-04-26T23:13:50Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|wbmp}}<br />
|mimetypes={{mimetype|image/vnd.wap.wbmp}}<br />
|pronom={{PRONOM|fmt/497}}<br />
}}<br />
'''WBMP''' ('''Wireless Bitmap''', or '''WAP Bitmap''') is an image file format associated with WAP (Wireless Application Protocol). It stores uncompressed bi-level raster images.<br />
<br />
== Specifications ==<br />
* [http://www.wapforum.org/what/technical/SPEC-WAESpec-19990524.pdf WAP WAE Specification, Version 1.1]<br />
<br />
== Software ==<br />
* [[Netpbm]]: pbmtowbmp, wbmptopbm<br />
* [[ImageMagick]]<br />
* [[XnViewe]]<br />
* [[Tom's Viewer]]<br />
* [http://libgd.bitbucket.org/ LibGD]<br />
<br />
== Links ==<br />
* [[Wikipedia:Wireless Application Protocol Bitmap Format|Wikipedia article]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/Pocket_PC_BitmapPocket PC Bitmap2019-04-26T23:11:37Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|2bp}}<br />
|released=~1996<br />
}}<br />
'''Pocket PC Bitmap''' ('''2BP''') is a bitmap image format used on early Windows CE devices. It is a 4-tone grayscale format.<br />
<br />
Evidently, 2BP is the same as [[BMP|Windows BMP]] v3, except that it has a bit depth of 2. The palette might always contain the grayscale colors {0x00, 0x80, 0xc0, 0xff}.<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Netpbm]]: bmptopnm<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
* http://www.opensource.apple.com/source/zip/zip-6/unzip/unzip/wince/ → *.2bp<br />
<br />
== Links ==<br />
* [http://support.microsoft.com/kb/159279 Microsoft article about converting .2bp to .bmp]<br />
* [http://msdn.microsoft.com/en-us/library/aa452885.aspx BITMAPINFOHEADER (Windows CE 5.0)]<br />
<br />
[[Category:Personal Digital Assistant formats]]<br />
[[Category:Microsoft]]<br />
[[Category:Windows]]</div>Tekknohttp://fileformats.archiveteam.org/wiki/BMPBMP2019-04-26T22:57:09Z<p>Tekkno: </p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|bmp}}, {{ext|rle}}, {{ext|dib}}, others<br />
|mimetypes={{mimetype|image/bmp}}<br />
|locfdd={{LoCFDD|fdd000189}}<br />
|pronom={{PRONOM|fmt/116}}, others<br />
|kaitai struct=bmp<br />
|released=1987<br />
}}<br />
'''BMP''' is a family of raster image file formats primarily used on Microsoft Windows and OS/2 operating systems. The format is sometimes known as '''Device-Independent Bitmap''' ('''DIB'''), since, when loaded into memory using Windows software, the image is held as a DIB structure.<br />
<br />
Though seemingly a simple format, it is complicated by its many different versions, lack of an official specification, lack of any version control process, and ambiguities and contradictions in the documentation.<br />
<br />
Images are usually uncompressed, but [[Run-length encoding|RLE]] compression can be used under some conditions. [[JPEG]], [[PNG]], and [[Modified Huffman|Huffman 1D]] compression are also theoretically possible, but rarely supported.<br />
<br />
== Identifiers ==<br />
No MIME type has been officially registered. Strings found in practice are: image/bmp; image/x-bmp; image/x-ms-bmp<br />
<br />
The usual filename extension is '''.bmp'''. Extensions '''.rle''' (for RLE-compressed images) and '''.dib''' (which usually indicates that the file lacks a ''file header'') are also sometimes seen. Many other extensions have been used by various applications.<br />
<br />
== Identification ==<br />
BMP files start with bytes <code>'B' 'M'</code>.<br />
<br />
That's not a very distinctive signature, but it's hard to give any definite rules beyond that. The bytes at offset 6 to 9 are usually all zero, but a few OS/2 BMP files have nonzero "hotspot coordinates" at that location.<br />
<br />
See also [[VBM (VDC BitMap)]], which has a similar signature.<br />
<br />
== Well-known versions ==<br />
BMP files use a common 14-byte file header, named BITMAPFILEHEADER. Following that is the "Info header", which begins with a 4-byte integer indicating its size. The Info header size (mostly) reveals the version of BMP that the file uses.<br />
<br />
=== Windows BMP v2 ===<br />
* Info header size: 12<br />
* Info header name: BITMAPCOREHEADER<br />
* PRONOM: {{PRONOM|fmt/115}}<br />
<br />
See also OS/2 BMP 1.0, below.<br />
<br />
=== Windows BMP v3 ===<br />
* Info header size: 40<br />
* Info header name: BITMAPINFOHEADER<br />
* PRONOM: {{PRONOM|fmt/116}}, {{PRONOM|fmt/117}}<br />
<br />
This is by far the most widely used version of BMP. It was introduced with Windows 3.x. Windows NT extended it to support 16 and 32 bits/pixel.<br />
<br />
Windows CE also extended it, for example to allow 2 bits/pixel (see [[Pocket PC Bitmap]]), but its extensions were not migrated to the BMP v4 and v5 formats.<br />
<br />
It is apparently possible for OS/2 BMP 2.0 format to masquerade as Windows BMP v3. The upshot is that if the compression type is 3 and the bit depth is 1, or the compression type is 4 and the bit depth is 24, then the file should be treated as OS/2 BMP 2.0.<br />
<br />
=== Windows BMP v4 ===<br />
* Info header size: 108<br />
* Info header name: BITMAPV4HEADER<br />
* PRONOM: {{PRONOM|fmt/118}}<br />
<br />
Introduced with Windows 95. Adds support for transparency and colorimetry.<br />
<br />
=== Windows BMP v5 ===<br />
* Info header size: 124<br />
* Info header name: BITMAPV5HEADER<br />
* PRONOM: {{PRONOM|fmt/119}}<br />
<br />
Introduced with Windows 98. Adds support for [[ICC profile|ICC profiles]].<br />
<br />
== Other versions ==<br />
<br />
=== Windows BMP v1 ===<br />
* PRONOM: {{PRONOM|fmt/114}}<br />
<br />
Also called DDB, this is the bitmap file format used by Windows 1.0. It's not really a BMP format. Refer to [[Windows DDB]].<br />
<br />
=== OS/2 BMP 1.0 ===<br />
:''See also the [[OS/2 BMP|OS/2 BMP disambiguation page]].''<br />
* Info header size: 12<br />
* Info header name: BITMAPCOREHEADER or OS21XBITMAPHEADER<br />
* PRONOM: {{PRONOM|x-fmt/25}} (deprecated), {{PRONOM|fmt/115}}<br />
<br />
For practical purposes, OS/2 BMP 1.0 is identical to Windows BMP v2. But there can be at least one small difference: In OS/2 formats, the "Size" field at offset 2 (variously named "cbSize", "FileSize", or "bfSize") is sometimes set to the size of the headers, instead of the size of the file. For v1, that means it will be 26 (14+12). For v2, it can range from 30 to 78.<br />
<br />
=== OS/2 BMP 2.0 ===<br />
* Info header size: 16–64 (16, 24, 40, 48, and 64 may be most common)<br />
* Info header name: BITMAPCOREHEADER2 or OS22XBITMAPHEADER<br />
* PRONOM: {{PRONOM|x-fmt/270}}<br />
<br />
OS/2 BMP 2.0 defines several file subtypes; here we are describing only the "Bitmap" subtype (files with a signature of "BM"). For other subtypes, see [[OS/2 bitmap family]].<br />
<br />
The header size can be reduced from its full size of 64 bytes. Omitted fields are assumed to have a value of zero.<br />
<br />
The fields in the first 40 bytes of the header are (nearly) identical to those in Windows BMP v3, v4, and v5. The remaining fields are different.<br />
<br />
OS/2 BMP 2.0 supports compression types "Huffman 1D" and "RLE24", unlike any other version of BMP.<br />
<br />
=== BITMAPV2INFOHEADER ===<br />
* Info header size: 52<br />
* Info header name: BITMAPV2INFOHEADER<br />
<br />
Possibly consists of, or includes, a single V2 color on top of a V3 info header; see [https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf], page 38<br />
=== BITMAPV3INFOHEADER ===<br />
* Info header size: 56<br />
* Info header name: BITMAPV3INFOHEADER<br />
<br />
Possibly consists of, or includes, the combination of a V3 header and a single V3 color table entry; see [https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf], page 38<br />
<br />
=== RMMP Color Table-Less v3 DIB ===<br />
Based on the v3 Windows BMP format, but, like other DIBs, lacks file header; unlike other DIBs, this one lacks a color table, as well, even though it has 8 or less bits per pixel (which would usually necessitate one). This DIB type can only be found in [[RIFF Multimedia Movie]] files, and it is possible that the color table is stored somewhere else in the RMPP, as well.<br />
<br />
The best way to read this file is currently to make a color scheme up and add it as a color table with a hex editor, which will change it into the next listed format. Some image software (e.g. Qt's, or whatever it is based one) will try to read these files anyway, using pixel bytes as a color table.<br />
<br />
=== Windows Color Table DIB ===<br />
Essentially the result of stripping the file header from a Windows BMP (of any version) that uses a color table. If the color table has less than 2^bits-per-pixel entries (i.e. if the color table is not completely used), [[ImageMagick]] will fail to decode these.<br />
See [https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf the RIFF standard], p. 36. DIBs are not RIFF files but are nonetheless in the standard.<br />
<br />
=== Windows 24-bit DIB ===<br />
A Windows BMP (of any version) with the file header removed, and 24-bit color (no color table). These DIBs are widely supported.<br />
See [https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf the RIFF standard], p. 36. DIBs are not RIFF files but are nonetheless in the standard.<br />
<br />
=== OS/2 Bitmap Array ===<br />
Sometimes, an [[OS/2 Bitmap Array]] file containing one or more bitmaps is considered to be a kind of BMP file. Such a file begins with an extra 14-byte header, with signature "<code>BA</code>". (But note that deleting this header is not quite enough to get a valid BMP file.)<br />
<br />
== Symbol definitions ==<br />
Here are the definitions, from the Windows SDKs, of some of the symbols used in the BMP documentation.<br />
<br />
All integers use little-endian [[Endianness|byte order]].<br />
<br />
{| class="wikitable"<br />
! Symbol<br />
! Definition<br />
|-<br />
|WORD || unsigned 16-bit integer<br />
|-<br />
|DWORD || unsigned 32-bit integer<br />
|-<br />
|LONG || signed 32-bit integer<br />
|-<br />
|BI_RGB || 0<br />
|-<br />
|BI_RLE8 || 1<br />
|-<br />
|BI_RLE4 || 2<br />
|-<br />
|BI_BITFIELDS || 3<br />
|-<br />
|(Huffman 1D) || 3<br />
|-<br />
|BI_JPEG || 4<br />
|-<br />
|(24-bit RLE) || 4<br />
|-<br />
|BI_PNG || 5<br />
|-<br />
|BI_ALPHABITFIELDS || 6<br />
|-<br />
|BI_SRCPREROTATE || 0x8000 (?)<br />
|-<br />
|LCS_CALIBRATED_RGB || 0<br />
|-<br />
|LCS_sRGB || <code>'sRGB'</code> = 0x73524742<br />
|-<br />
|LCS_WINDOWS_COLOR_SPACE || <code>'Win '</code> = 0x57696e20<br />
|-<br />
|PROFILE_LINKED || <code>'LINK'</code> = 0x4c494e4b<br />
|-<br />
|PROFILE_EMBEDDED || <code>'MBED'</code> = 0x4d424544<br />
|-<br />
|LCS_GM_BUSINESS || 1<br />
|-<br />
|LCS_GM_GRAPHICS || 2<br />
|-<br />
|LCS_GM_IMAGES || 4<br />
|-<br />
|LCS_GM_ABS_COLORIMETRIC || 8<br />
|}<br />
<br />
== Specifications ==<br />
* BMP (as "DeviceIndependentBitmap") is defined in the [http://msdn.microsoft.com/en-us/library/cc215212.aspx Windows Metafile Specification]<br />
* [http://msdn.microsoft.com/en-us/library/dd183374%28v=vs.85%29.aspx BITMAPFILEHEADER]<br />
* [http://msdn.microsoft.com/en-us/library/dd183372%28v=vs.85%29.aspx BITMAPCOREHEADER]<br />
* [http://msdn.microsoft.com/en-us/library/dd183376%28v=vs.85%29.aspx BITMAPINFOHEADER]<br />
* [http://msdn.microsoft.com/en-us/library/aa452885.aspx BITMAPINFOHEADER (Windows CE 5.0)]<br />
* [http://msdn.microsoft.com/en-us/library/dd183380%28v=vs.85%29.aspx BITMAPV4HEADER]<br />
* [http://msdn.microsoft.com/en-us/library/dd183381%28v=vs.85%29.aspx BITMAPV5HEADER]<br />
* [http://www.digicamsoft.com/bmp/bmp.html Another site with format descriptions]<br />
* [http://www.fileformat.info/format/os2bmp/spec/902d5c253f2a43ada39c2b81034f27fd/view.htm OS/2 Presentation Manager Programming Reference Guide, Vol III]<br />
<br />
== Metaformat files ==<br />
<br />
* {{Synalysis|bitmap}}<br />
<br />
== Software ==<br />
BMP is widely supported by graphics software, including web browsers. Software listed here has been arbitrarily selected.<br />
* [[Netpbm]]: bmptopnm, ppmtobmp<br />
* [[ImageMagick]]<br />
* [[XnView]]<br />
* [[Tom's Viewer]]<br />
<br />
== Sample files ==<br />
=== Windows BMP v2 ===<br />
This format is fairly common, but examples of it can be hard to spot amidst all the BMPv3 files.<br />
* [http://samples.libav.org/image-samples/money-2-%28os2%29.bmp money-2-(os2).bmp], [http://samples.libav.org/image-samples/money-16-%28os2%29.bmp money-16-(os2).bmp], [http://samples.libav.org/image-samples/money-256-%28os2%29.bmp money-256-(os2).bmp], [http://samples.libav.org/image-samples/money-24bit-os2.bmp money-24bit-os2.bmp]<br />
* http://cd.textfiles.com/hobbesos29709/disk2/MULTIMED/BMP/ → BMPS*.ZIP, OS2ORBIT.ZIP, REALMERL.BMP<br />
<br />
=== Windows BMP v3 ===<br />
* http://cd.textfiles.com/mmplatinum/IMAGES/BMP/<br />
* http://cd.textfiles.com/monstmedia/WIN/ICONS/<br />
* http://cd.textfiles.com/maxx/tothemaxww/BMPMISC/<br />
<br />
=== OS/2 BMP 2.0 ===<br />
* [http://kimludvigsen.dk/os2/os2/graphx/teamlog2.zip teamlog2.zip] → TEAMcol.bmp, teamcol2.bmp<br />
* [http://samples.libav.org/image-samples/bmp-files/test4os2v2.bmp test4os2v2.bmp]<br />
* [http://cd.textfiles.com/hobbesos29709/disk2/MULTIMED/BMP/CARDBMPS.ZIP CARDBMPS.ZIP] - Most of the files are OS/2 BMP 2.0<br />
* [http://cd.textfiles.com/hobbesos29709/disk1/GAMES/MAKMAN10.ZIP MAKMAN10.ZIP] - Some of the files are files OS/2 BMP 2.0<br />
* [http://cd.textfiles.com/monstmedia/IMAGES/JUR_OS2.BMP JUR_OS2.BMP]<br />
* http://cd.textfiles.com/pier/pier09/cdrom/036/ → os2bmp*.zip<br />
<br />
=== Various ===<br />
* [http://wvnvms.wvnet.edu/vmswww/bmp.html Example BMP images (all Windows v3 except as indicated)]<br />
* [https://archive.org/details/OS2BBS OS/2 BBS Files Archive] → 13-Bitmap.zip - Lots of OS/2 BMP 1.0 & 2.0 files<br />
* [http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html BMP Suite Image List]<br />
<br />
== See also ==<br />
* [[CUR]]<br />
* [[ICO]]<br />
* [[OS/2 bitmap family]]<br />
* [[OS/2 Bitmap Array]]<br />
* [[packPNM]]<br />
* [[Pocket PC Bitmap]]<br />
* [[Poser Bump Map]]<br />
* [[Segmented Hypergraphics]]<br />
* [[Windows DDB]]<br />
* [[Winzle Puzzle]]<br />
<br />
== Resources ==<br />
* [http://whatis.rest7.com/how-to-open-bmp-file Specification of BMP headers]<br />
* [[Wikipedia:BMP file format|Wikipedia: BMP file format]]<br />
* {{EGFF|bmp|Microsoft Windows Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* {{EGFF|os2bmp|OS/2 Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]<br />
* [http://coptr.digipres.org/Bad_Peggy Bad Peggy: scans images for problems]<br />
<br />
[[Category:Microsoft]]<br />
[[Category:Windows]]<br />
[[Category:OS/2]]</div>Tekkno