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

Nitrogen Fingers Paint

2021-03-14T13:22:58Z

GoodClover: P stands for "Paint"

{{FormatInfo
| name = Nitrogen Fingers Paint
| formattype = electronic
| subcat = Graphics
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[Nitrogen Fingers Paint]] (NFP) is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a [[wikipedia:hexadecimal|hex]] character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 real pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md CraftOS-Standards] (Poorly documented)

[[Category:ComputerCraft]]
[[Category:File formats named after chemical elements]]

Talk:NFP

2021-03-14T13:20:49Z

GoodClover: GoodClover moved page Talk:NFP to Talk:Nitrogen Fingers Paint: P stands for "Paint".

#REDIRECT [[Talk:Nitrogen Fingers Paint]]

Talk:Nitrogen Fingers Paint

2021-03-14T13:20:49Z

GoodClover: GoodClover moved page Talk:NFP to Talk:Nitrogen Fingers Paint: P stands for "Paint".

I'll finish this tomorrow [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 02:38, 13 March 2021 (UTC)

Whilst [[NFT]] stands for "Nitrogen Fingers Text" I can't find info on what the P in NFP stands for. The [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md "standard"] (if you can really call it that, it's missing alot of details) Just calls it "Paintutils Image". [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 16:50, 13 March 2021 (UTC)

NFP

2021-03-14T13:20:49Z

GoodClover: GoodClover moved page NFP to Nitrogen Fingers Paint: P stands for "Paint".

#REDIRECT [[Nitrogen Fingers Paint]]

Nitrogen Fingers Paint

2021-03-14T13:20:48Z

GoodClover: GoodClover moved page NFP to Nitrogen Fingers Paint: P stands for "Paint".

{{FormatInfo
| name = NFP
| formattype = electronic
| subcat = Graphics
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a [[wikipedia:hexadecimal|hex]] character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 real pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md CraftOS-Standards] (Poorly documented)

[[Category:ComputerCraft]]

User:GoodClover

2021-03-13T17:25:34Z

GoodClover:

Hi, I'm '''Oliver'''. :)

I'm probably going to make/work on:
* [[ComputerCraft]]/[[:Category:ComputerCraft]] ([https://computercraft.cc/ http://computercraft.cc])
* [[NFP]] - CC's default very-super-simple-as-it-gets plain text image format. Don't know what it stands for :P
* [[NFT]] - More of a coloured text format than an image format, but it is mainly used to create images.
* [[ComputerCraft Video]]/[[CCV]] - A CC video format. ([http://www.computercraft.info/forums2/index.php?/topic/23399-video-player-watch-rick-roll-in-computercraft/ from this])

This site is really nice, but unfortunately seems to be fairly unmaintained - and has fallen into a state of disrepair (as in the Wiki itself, not it's content).
Would be nice if it got freshened a bit and some stuff was updated.

Nitrogen Fingers Text

2021-03-13T17:20:32Z

GoodClover: Not an extension, I misunderstood.

{{FormatInfo
| name = Nitrogen Fingers Text
| formattype = electronic
| extensions = {{ext|nft}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/modules/main/cc/image/nft.lua <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s nft image Implementation (lua)]
| error resilience = None
}}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/modules/main/cc/image/nft.lua ComputerCraft:Tweaked's CraftOS nft image Implementation (lua)]
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/6-nft.md CraftOS-Standards]

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T17:20:04Z

GoodClover:

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a [[wikipedia:hexadecimal|hex]] character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 real pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md CraftOS-Standards] (Poorly documented)

[[Category:ComputerCraft]]

User:GoodClover

2021-03-13T17:09:50Z

GoodClover:

Hi, I'm '''Oliver'''. :)

I'm probably going to make/work on:
* [[ComputerCraft]]/[[:Category:ComputerCraft]] ([https://computercraft.cc/ http://computercraft.cc])
* [[NFP]] - CC's default very-super-simple-as-it-gets plain text image format. Don't know what it stands for :P
* [[NFT]] - Extension of NFP, it's more of a coloured text than an image format, but it is mainly used to create images.
* [[ComputerCraft Video]]/[[CCV]] - A CC video format. ([http://www.computercraft.info/forums2/index.php?/topic/23399-video-player-watch-rick-roll-in-computercraft/ from this])

This site is really nice, but unfortunately seems to be fairly unmaintained - and has fallen into a state of disrepair (as in the Wiki itself, not it's content).
Would be nice if it got freshened a bit and some stuff was updated.

Talk:Nitrogen Fingers Paint

2021-03-13T16:52:33Z

GoodClover:

Talk:Nitrogen Fingers Paint

2021-03-13T16:50:50Z

GoodClover:

I'll finish this tomorrow [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 02:38, 13 March 2021 (UTC)

Whilst [[NFT]] stands for "Nitrogen Fingers Text" I can't find info on what the P in NFP stands for. The "standard" (if you can really call it that) Just calls it "Paintutils Image". [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 16:50, 13 March 2021 (UTC)

User:GoodClover

2021-03-13T16:49:33Z

GoodClover:

Hi, I'm '''Oliver'''. :)

I'm probably going to make/work on:
* [[CompputerCraft]]/[[:Category:ComputerCraft]] ([https://computercraft.cc/ http://computercraft.cc])
* [[NFP]] - CC's default very-super-simple-as-it-gets plain text image format. Don't know what it stands for :P
* [[NFT]] - Extension of NFP, it's more of a coloured text than an image format, but it is mainly used to create images.
* [[ComputerCraft Video]]/[[CCV]] - A CC video format. ([http://www.computercraft.info/forums2/index.php?/topic/23399-video-player-watch-rick-roll-in-computercraft/ from this])

This site is really nice, but unfortunately seems to be fairly unmaintained - and has fallen into a state of disrepair (as in the Wiki itself, not it's content).
Would be nice if it got freshened a bit and some stuff was updated.

Template:FormatInfo

2021-03-13T16:48:11Z

GoodClover: Extended To

<table class="infobox formatinfo" border="0" style="float: right; border: 1px solid #666666; max-width: 25%; overflow: hidden; background-color:{{#switch: {{{formattype}}}
|electronic=#F8E0F7
|physical=#F6E3CE
|organic=#CEF6CE
|Languages=#CEE3F6
|#F8E0F7
}};
padding: 0.25em; margin: 0.25em 1em;">
<tr>
<th colspan="2">[[File Formats|File Format]]<includeonly>[[Category:File Formats]]</includeonly></th>
</tr>
{{FormatInfo/row|Name|{{{name|{{PAGENAME}}}}}{{DEFAULTSORT:{{{name|{{PAGENAME}}}}}}}}}
{{FormatInfo/row
| Ontology
|
<ul><li>
{{#switch: {{{formattype}}}
|electronic=[[Electronic File Formats]]<includeonly>[[Category:Electronic File Formats]]</includeonly>
|physical=[[Physical File Formats]]<includeonly>[[Category:Physical File Formats]]</includeonly>
|organic=[[Organic File Formats]]<includeonly>[[Category:Organic File Formats]]</includeonly>
|[[{{{formattype|Electronic File Formats}}}]]<includeonly>[[Category:{{{formattype|Electronic File Formats}}}]]</includeonly>
}}
<ul><li>
{{#if:{{{subcat|}}}
|[[{{{subcat}}}]]<includeonly>[[Category:{{{subcat}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat2|}}}
|[[{{{subcat2}}}]]<includeonly>[[Category:{{{subcat2}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat3|}}}
|[[{{{subcat3}}}]]<includeonly>[[Category:{{{subcat3}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat4|}}}
|[[{{{subcat4}}}]]<includeonly>[[Category:{{{subcat4}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat5|}}}
|[[{{{subcat5}}}]]<includeonly>[[Category:{{{subcat5}}}]]</includeonly>
<ul><li>
{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
</li></ul>
}}{{#if:{{{extensions|{{{extension|}}}}}}|
{{FormatInfo/row|[[Filename extension|Extension(s)]]|{{{extensions|{{{extension}}}}}}}}
}}{{#if:{{{mimetypes|{{{mimetype|}}}}}}|
{{FormatInfo/row|[[MIME types|MIME Type(s)]]|{{{mimetypes|{{{mimetype}}}}}}}}
}}{{#if:{{{locfdd|}}}|
{{FormatInfo/row|LoCFDD|{{{locfdd}}}}}
}}{{#if:{{{fourccs|}}}|
{{FormatInfo/row|[[FourCC]]|{{{fourccs}}}}}
}}{{#if:{{{pronom|}}}|
{{FormatInfo/row|[[PRONOM]]|{{{pronom}}}}}
}}{{#if:{{{type code|}}}|
{{FormatInfo/row|[[Macintosh type/creator code|Type Code]]|{{{type code}}}}}
}}{{#if:{{{uniform type|}}}|
{{FormatInfo/row|[[Uniform Type Identifier|UTI]]|{{{uniform type}}}}}
}}{{#if:{{{wikidata|}}}|
{{FormatInfo/row|[[Wikidata identifier|Wikidata ID]]|{{{wikidata}}}}}
}}{{#if:{{{compression|}}}|
{{FormatInfo/row|[[Compression]]|{{{compression}}}}}
}}{{#if:{{{extended from|}}}|
{{FormatInfo/row|Extended From|[[{{{extended from}}}]]}}
}}{{#if:{{{extended to|}}}|
{{FormatInfo/row|Extended To|[[{{{extended to}}}]]}}
}}{{#if:{{{magic|}}}|
{{FormatInfo/row|[[Magic]] Bytes|{{{magic}}}}}
}}{{#if:{{{kaitai struct|}}}|
{{FormatInfo/row|[[Kaitai Struct|Kaitai Struct Spec]]|[http://formats.kaitai.io/{{{kaitai struct}}}/index.html {{{kaitai struct}}}.ksy]}}
}}{{#if:{{{spec|}}}|
{{FormatInfo/row|Spec|{{{spec}}}}}
}}{{#if:{{{spec availability|}}}|
{{FormatInfo/row|Spec Availability|{{{spec availability}}}}}
}}{{#if:{{{reference impl|}}}|
{{FormatInfo/row|Reference Implementation|{{{reference impl}}}}}
}}{{#if:{{{conforms to|}}}|
{{FormatInfo/row|Conforms To|{{{conforms to}}}}}
}}{{#if:{{{charset|}}}|
{{FormatInfo/row|[[IANA character set name|IANA charset]]|[http://www.iana.org/assignments/charset-reg/{{{charset}}} {{{charset}}}]}}
}}{{#if:{{{charsetaliases|}}}|
{{FormatInfo/row|IANA aliases|{{{charsetaliases}}}}}
}}{{#if:{{{mibenum|}}}|
{{FormatInfo/row|IANA MIBenum|{{{mibenum}}}}}
}}{{#if:{{{codepage|}}}|
{{FormatInfo/row|Code Page|{{{codepage}}}}}
}}{{#if:{{{cfstringencoding|}}}|
{{FormatInfo/row|CFStringEncoding|{{{cfstringencoding}}}}}
}}{{#if:{{{nsstringencoding|}}}|
{{FormatInfo/row|NSStringEncoding|{{{nsstringencoding}}}}}
}}{{#if:{{{endianness|}}}|
{{FormatInfo/row|[[Endianness]]|{{{endianness}}}}}
}}{{#if:{{{tpm|}}}|
{{FormatInfo/row|TPM|{{{tpm}}}}}
}}{{#if:{{{error resilience|}}}|
{{FormatInfo/row|Error Resilience|{{{error resilience}}}}}
}}{{#if:{{{patent license|}}}|
{{FormatInfo/row|Patent License|{{{patent license}}}}}
}}{{#if:{{{developed by|}}}|
{{FormatInfo/row|Developed By|{{{developed by}}}}}
}}{{#if:{{{maintained by|}}}|
{{FormatInfo/row|Maintained By|{{{maintained by}}}}}
}}{{#if:{{{released|}}}|
{{FormatInfo/row|Released|{{{released}}}}}
}}
{{#if:{{{image|}}}|
<tr><td align="center" colspan="2">
[[Image:{{{image}}}|200px|{{{caption}}}]]
</td></tr>
}}
{{#if:{{{caption|}}}|
<tr><td align="center" colspan="2">
{{{caption}}}
</td></tr>
}}
</table>
<includeonly>{{#if:{{{formattype|}}}||[[Category:FormatInfo without formattype]]}}{{#if:{{{subcat|}}}||[[Category:FormatInfo without subcat]]}}{{#ifeq:{{{formattype|electronic}}}|electronic|{{#if:{{{extensions|}}}||[[Category:FormatInfo without extensions]]}}{{#if:{{{mimetypes|}}}||[[Category:FormatInfo without mimetypes]]}}|}}</includeonly><noinclude>
== Usage ==
<pre>
{{FormatInfo
| name =
| formattype =
| subcat =
| subcat2 =
| subcat3 =
| subcat4 =
| subcat5 =
| thiscat =
| extensions =
| mimetypes =
| locfdd =
| fourccs =
| pronom =
| type code =
| uniform type =
| wikidata =
| compression =
| extended from =
| extended to =
| magic =
| kaitai struct =
| spec =
| spec availability=
| reference impl =
| conforms to =
| charset =
| charsetaliases =
| codepage =
| mibenum =
| cfstringencoding =
| nsstringencoding =
| endianness =
| tpm =
| error resilience =
| patent license =
| developed by =
| maintained by =
| released =
| image =
| caption =
}}
</pre>

===Parameters===
;name: '''(optional)''' The name of the file format. ''Default: <nowiki>{{PAGENAME}}</nowiki>''
;formattype: '''(optional)''' The [[File Formats|type]] of the file format. Choose 'electronic', 'physical', or 'organic', or specify your own. ''Default: electronic''
;subcat: '''(optional)''' The subcategory of the file format.
;subcat2: '''(optional)''' An additional subcategory of the file format.
;subcat3: '''(optional)''' An additional subcategory of the file format.
;subcat4: '''(optional)''' An additional subcategory of the file format.
;subcat5: '''(optional)''' An additional subcategory of the file format.
;thiscat: '''(optional)''' Special parameter for indicating ontology of a non-terminal subcategory page.
;extensions: '''(optional)''' The format's known filename extensions. Use [[Template:ext|<nowiki>{{ext}}</nowiki>]], or [[Template:Noext|<nowiki>{{Noext}}</nowiki>]] if it is known to be extensionless.
;mimetypes: '''(optional)''' The MIME type of the format. Use [[Template:mimetype|<nowiki>{{mimetype}}</nowiki>]].
;locfdd: '''(optional)''' Identifier for this format from the Library of Congress Sustainability of Digital Formats, e.g. "fdd000314". Use [[Template:LoCFDD|<nowiki>{{LoCFDD}}</nowiki>]].
;fourccs: '''(optional)''' FourCC code
;pronom: '''(optional)''' The [[Sources/PRONOM|PRONOM]] ID of the format, e.g. "fmt/45". Use [[Template:PRONOM|<nowiki>{{PRONOM}}</nowiki>]].
;type code: '''(optional)''' The Type Code of the file, used by Mac OS Classic. Use [[Template:Type Code|<nowiki>{{Type Code}}</nowiki>]].
;uniform type: '''(optional)''' The Uniform Type Identifier (UTI), used by Mac OS X and iOS. Use [[Template:UTI|<nowiki>{{UTI}}</nowiki>]].
;wikidata: '''(optional)''' Wikidata title ID. Use [[Template:wikidata|<nowiki>{{wikidata}}</nowiki>]].
;compression: Types of compression. Whether Lossy, Lossless, or Both, and whether Optional or Always compressed. i.e. JPEG is Always Lossy.
;extended from: Any formats this one was based upon.
;extended to: Any formats that have been derived from this one.
;magic: A sequence of byte values that can be used to identify the file contents, usually located close to the start of the file.
;kaitai struct: '''(optional)''' An identifier of a format at [http://formats.kaitai.io Kaitai Struct] project, e.g. "ico" would result in a link to http://formats.kaitai.io/ico/index.html generated.
;spec: URL of the format specification.
;spec availability: Type of availability the specification, e.g. commercial, free.
;reference impl: Link to page about the reference implementation of this format, if any.
;conforms to: '''(optional)''' The UTI of the parent format in the conformance hierarchy.
;charset: '''(optional)''' For character encodings: IANA charset parameter value.
;charsetaliases: '''(optional)''' For character encodings: Variant IANA charset parameter values.
;codepage: '''(optional)''' For character encodings: Code page number (IBM/MS).
;mibenum: '''(optional)''' For character encodings: IANA MIBenum.
;cfstringencoding: '''(optional)''' For character encodings: CFStringEncoding.
;nsstringencoding: '''(optional)''' For character encodings: NSStringEncoding.
;endianness: Big-endian or Little-endian byte ordering.
;tpm: Technical Protection Mechanisms supported by the format, e.g. encryption.
;error resilience: Is this format able to detect damage or recover from damage to the bitstream.
;patent license: Unknown, Disputed, Encumbered, (F)RAND, Royalty-Free, Unencumbered.
;developed by: Who developed the format.
;maintained by: Who now maintains the format.
;released: '''(optional)''' The date the format was publicly released.
;image: '''(optional)''' Illustration to show in infobox.
;caption: '''(optional)''' Caption for image

===Potential Parameters===
This is a list of parameters that could be included in this template.

;mime & mime aliases: Split mimetypes into primary type and known aliases.
;version: The version of the format, e.g. "1.4" for PDF 1.4
;previous version: Link to page about the previous version of this format.
;next version: Link to page about the next version of this format.
;back compat: Whether this version is backwards compatible with the previous version.
;wikipedia: Name of the Wikipedia page that describes this format, e.g. "JPEG 2000" will be rendered as [[Wikipedia:JPEG 2000|JPEG 2000]]
;container for: A list of formats this format can contain.
;contained by: A list of formats that may contain this format.
;embeddable metadata: Kinds of metadata that can be embedded in this format.
;dependencies: External resources that files in this format may depend upon, e.g. fonts, or even hardware.
;namespace: The namespace-uri that defines the file format if it is XML-based.

==Examples==

[[Category:File Formats| ]]
</noinclude>

Nitrogen Fingers Paint

2021-03-13T16:45:49Z

GoodClover:

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
| extended to = NFT
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

[[NFT]] is an extension of [[NFP]] which allows for characters and character colours to be saved, it is less of an image format and more of a text file with character foreground and background colours.

== Format ==

An NFP file consists of a text file containing a [[wikipedia:hexadecimal|hex]] character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 real pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md CraftOS-Standards] (Poorly documented)

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T16:39:57Z

GoodClover:

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

[[NFT]] is an extension of [[NFP]] which allows for characters and character colours to be saved, it is less of an image format and more of a text file with character foreground and background colours.

== Format ==

An NFP file consists of a text file containing a [[wikipedia:hexadecimal|hex]] character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 real pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/4-paint.md CraftOS-Standards] (Poorly documented)

[[Category:ComputerCraft]]

NFT

2021-03-13T16:39:36Z

GoodClover: Redirected page to Nitrogen Fingers Text

#REDIRECT [[Nitrogen Fingers Text]]

Nitrogen Fingers Text

2021-03-13T16:37:46Z

GoodClover: Created page with "{{FormatInfo | name = Nitrogen Fingers Text | formattype = electronic | extensions = {{ext|nft}} | compression = None | reference impl = [https:..."

{{FormatInfo
| name = Nitrogen Fingers Text
| formattype = electronic
| extensions = {{ext|nft}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/modules/main/cc/image/nft.lua <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s nft image Implementation (lua)]
| error resilience = None
| extended from = NFP
}}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/modules/main/cc/image/nft.lua ComputerCraft:Tweaked's CraftOS nft image Implementation (lua)]
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)
* [https://github.com/oeed/CraftOS-Standards/blob/master/standards/6-nft.md CraftOS-Standards]

[[Category:ComputerCraft]]

Category:ComputerCraft

2021-03-13T16:31:35Z

GoodClover:

This page is for formats originally created for use with [https://computercraft.cc ComputerCraft] programs and it's default CraftOS system.

If you want to test/use some of this stuff, without installing Minecraft and the ComputerCraft mod, you can use [https://emux.cc/ CCEmuX]—a Java ComputerCraft emulator that runs on desktop.

Some file formats have documentation as a "standard" over at the [https://github.com/oeed/CraftOS-Standards CraftOS-Standards GitHub], however it is fairly poor in quality.

[[Category:Computer platforms]]
[[Category:Minecraft]]

Nitrogen Fingers Paint

2021-03-13T16:29:30Z

GoodClover: /* External links */

Nitrogen Fingers Paint

2021-03-13T16:16:28Z

GoodClover:

Nitrogen Fingers Paint

2021-03-13T16:00:24Z

GoodClover: Pixel aspect ratio / Character Mode

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a hex character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to a space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

=== Pixel aspect ratio ===

CraftOS's <code>paintutils</code> library (and therefore <code>paint</code>) uses character mode for displaying images, meaning one image "pixel" is a character cell.
Character cells are at a 2:3 aspect ratio, 12×18 "real" pixels in size.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T14:27:02Z

GoodClover: /* Format */ spelling

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a hex character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treated as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T14:25:41Z

GoodClover: /* Format */

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a hex character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treaded as a transparent pixel, it is recommended that a space be used.
CraftOS's <code>paint</code> program automatically converts all transparent pixels to space when saved.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T14:24:17Z

GoodClover: Colours

{{FormatInfo
| name = NFP
| formattype = electronic
| extensions = {{ext|nfp}}
| compression = None
| reference impl = [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 <abbr title="ComputerCraft:Tweaked CraftOS">CC:T</abbr>'s paintutils (lua)]
| error resilience = None
}}

[[NFP]]{{fix|Stands for?}} is a simple [[text]] file format used by [https://computercraft.cc ComputerCraft] to store images.

CraftOS's <code>paint</code> program allows for easy editing of these files with a GUI.

== Format ==

An NFP file consists of a text file containing a hex character for each pixel.

Each pixel's character must be in the range <abbr title="0123456789abcdef"><code>0-f</code></abbr> and be lowercase,
any other characters (including capital <abbr title="ABCDEF"><code>A-F</code></abbr>) are treated as fully transparent pixels.

The newline (<code>\n</code>) character moves to the beginning of the next row.{{fix|End file with newline or not?}}
Due to the nature of this, it is possible to have rows of different length and therefore means that nonsquare images can be created.

Whilst any unrecognised character is treaded as a transparent pixel, it is recommended that a space be used.

=== Colours ===

To calculate a colour for a given value do <code>2x</code> and then treat it as a 24-bit RGB value (8 bits for each of red, green and blue).

It is recommended that a lookup table be generated for performance.

== Example ==

{|
|+<code>house.nfp</code>
|+''[[File:NFP_transparent.png]] represents a transparent pixel.''
|-
! NFP !! PNG !! PNG (nonsquare)
|-
|<code><pre>
c␤
eeeeec␤
eeeeeee␤
eeeeeeeee␤
ccccccc␤
c33cc5c␤
ccccc5c␤
fffffffffff␤
</pre></code>
''<code></code>
|| [[File:NFP_house.png]]
|| [[File:NFP_house_nonsquare.png]]
|}

== External links ==

* [https://github.com/SquidDev-CC/CC-Tweaked/blob/66e42e0817484702d3be7ab880e60246097f7ecb/src/main/resources/data/computercraft/lua/rom/apis/paintutils.lua#L50 ComputerCraft:Tweaked's CraftOS paintutils Implementation (lua)]
*: ''Note:'' Lua lists start at 1 so <code>2x-1</code> is used when generating the lookup table.
* [https://tweaked.cc/module/colors.html ComputerCraft:Tweaked Wiki's Colour table] (Paint/Blit column)

[[Category:ComputerCraft]]

Nitrogen Fingers Paint

2021-03-13T14:11:49Z

GoodClover: /* Example */

File:NFP transparent.png

2021-03-13T14:09:54Z

GoodClover:

Nitrogen Fingers Paint

2021-03-13T14:06:04Z

GoodClover: Format

Category:ComputerCraft

2021-03-13T13:00:20Z

GoodClover:

Category:ComputerCraft

2021-03-13T12:50:49Z

GoodClover:

[[Category:Computer platforms]]
[[Category:Minecraft]]

Nitrogen Fingers Paint

2021-03-13T02:40:23Z

GoodClover: Category

Talk:Nitrogen Fingers Paint

2021-03-13T02:38:34Z

GoodClover: Created page with "I'll finish this tomorrow ~~~~"

I'll finish this tomorrow [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 02:38, 13 March 2021 (UTC)

Nitrogen Fingers Paint

2021-03-13T02:37:00Z

GoodClover:

Nitrogen Fingers Paint

2021-03-13T02:33:32Z

GoodClover:

Nitrogen Fingers Paint

2021-03-13T02:31:09Z

GoodClover: Created page with "{{FormatInfo | name = NFP | formattype = electronic | extensions = {{ext|nfp}} | compression = None | reference impl = [https://github.com/Squid..."

File:NFP house nonsquare.png

2021-03-13T02:24:44Z

GoodClover: PNG version of the nonsquare example for NFP

PNG version of the nonsquare example for [[NFP]]

File:NFP house.png

2021-03-13T02:16:17Z

GoodClover: PNG version of the example for NFP

PNG version of the example for [[NFP]]

Template:FormatInfo

2021-03-13T01:55:06Z

GoodClover: /* Parameters */ Correct wrong spelling - "error resilience" is used in the template

<table class="infobox formatinfo" border="0" style="float: right; border: 1px solid #666666; max-width: 25%; overflow: hidden; background-color:{{#switch: {{{formattype}}}
|electronic=#F8E0F7
|physical=#F6E3CE
|organic=#CEF6CE
|Languages=#CEE3F6
|#F8E0F7
}};
padding: 0.25em; margin: 0.25em 1em;">
<tr>
<th colspan="2">[[File Formats|File Format]]<includeonly>[[Category:File Formats]]</includeonly></th>
</tr>
{{FormatInfo/row|Name|{{{name|{{PAGENAME}}}}}{{DEFAULTSORT:{{{name|{{PAGENAME}}}}}}}}}
{{FormatInfo/row
| Ontology
|
<ul><li>
{{#switch: {{{formattype}}}
|electronic=[[Electronic File Formats]]<includeonly>[[Category:Electronic File Formats]]</includeonly>
|physical=[[Physical File Formats]]<includeonly>[[Category:Physical File Formats]]</includeonly>
|organic=[[Organic File Formats]]<includeonly>[[Category:Organic File Formats]]</includeonly>
|[[{{{formattype|Electronic File Formats}}}]]<includeonly>[[Category:{{{formattype|Electronic File Formats}}}]]</includeonly>
}}
<ul><li>
{{#if:{{{subcat|}}}
|[[{{{subcat}}}]]<includeonly>[[Category:{{{subcat}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat2|}}}
|[[{{{subcat2}}}]]<includeonly>[[Category:{{{subcat2}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat3|}}}
|[[{{{subcat3}}}]]<includeonly>[[Category:{{{subcat3}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat4|}}}
|[[{{{subcat4}}}]]<includeonly>[[Category:{{{subcat4}}}]]</includeonly>
<ul><li>
{{#if:{{{subcat5|}}}
|[[{{{subcat5}}}]]<includeonly>[[Category:{{{subcat5}}}]]</includeonly>
<ul><li>
{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
|{{#if:{{{thiscat|}}}|[[{{{thiscat}}}]]<includeonly>[[Category:{{{thiscat}}}| ]]</includeonly>|[[{{{name|{{PAGENAME}}}}}]]}}
}}
</li></ul>
</li></ul>
}}{{#if:{{{extensions|{{{extension|}}}}}}|
{{FormatInfo/row|[[Filename extension|Extension(s)]]|{{{extensions|{{{extension}}}}}}}}
}}{{#if:{{{mimetypes|{{{mimetype|}}}}}}|
{{FormatInfo/row|[[MIME types|MIME Type(s)]]|{{{mimetypes|{{{mimetype}}}}}}}}
}}{{#if:{{{locfdd|}}}|
{{FormatInfo/row|LoCFDD|{{{locfdd}}}}}
}}{{#if:{{{fourccs|}}}|
{{FormatInfo/row|[[FourCC]]|{{{fourccs}}}}}
}}{{#if:{{{pronom|}}}|
{{FormatInfo/row|[[PRONOM]]|{{{pronom}}}}}
}}{{#if:{{{type code|}}}|
{{FormatInfo/row|[[Macintosh type/creator code|Type Code]]|{{{type code}}}}}
}}{{#if:{{{uniform type|}}}|
{{FormatInfo/row|[[Uniform Type Identifier|UTI]]|{{{uniform type}}}}}
}}{{#if:{{{wikidata|}}}|
{{FormatInfo/row|[[Wikidata identifier|Wikidata ID]]|{{{wikidata}}}}}
}}{{#if:{{{compression|}}}|
{{FormatInfo/row|[[Compression]]|{{{compression}}}}}
}}{{#if:{{{extended from|}}}|
{{FormatInfo/row|Extended From|[[{{{extended from}}}]]}}
}}{{#if:{{{magic|}}}|
{{FormatInfo/row|[[Magic]] Bytes|{{{magic}}}}}
}}{{#if:{{{kaitai struct|}}}|
{{FormatInfo/row|[[Kaitai Struct|Kaitai Struct Spec]]|[http://formats.kaitai.io/{{{kaitai struct}}}/index.html {{{kaitai struct}}}.ksy]}}
}}{{#if:{{{spec|}}}|
{{FormatInfo/row|Spec|{{{spec}}}}}
}}{{#if:{{{spec availability|}}}|
{{FormatInfo/row|Spec Availability|{{{spec availability}}}}}
}}{{#if:{{{reference impl|}}}|
{{FormatInfo/row|Reference Implementation|{{{reference impl}}}}}
}}{{#if:{{{conforms to|}}}|
{{FormatInfo/row|Conforms To|{{{conforms to}}}}}
}}{{#if:{{{charset|}}}|
{{FormatInfo/row|[[IANA character set name|IANA charset]]|[http://www.iana.org/assignments/charset-reg/{{{charset}}} {{{charset}}}]}}
}}{{#if:{{{charsetaliases|}}}|
{{FormatInfo/row|IANA aliases|{{{charsetaliases}}}}}
}}{{#if:{{{mibenum|}}}|
{{FormatInfo/row|IANA MIBenum|{{{mibenum}}}}}
}}{{#if:{{{codepage|}}}|
{{FormatInfo/row|Code Page|{{{codepage}}}}}
}}{{#if:{{{cfstringencoding|}}}|
{{FormatInfo/row|CFStringEncoding|{{{cfstringencoding}}}}}
}}{{#if:{{{nsstringencoding|}}}|
{{FormatInfo/row|NSStringEncoding|{{{nsstringencoding}}}}}
}}{{#if:{{{endianness|}}}|
{{FormatInfo/row|[[Endianness]]|{{{endianness}}}}}
}}{{#if:{{{tpm|}}}|
{{FormatInfo/row|TPM|{{{tpm}}}}}
}}{{#if:{{{error resilience|}}}|
{{FormatInfo/row|Error Resilience|{{{error resilience}}}}}
}}{{#if:{{{patent license|}}}|
{{FormatInfo/row|Patent License|{{{patent license}}}}}
}}{{#if:{{{developed by|}}}|
{{FormatInfo/row|Developed By|{{{developed by}}}}}
}}{{#if:{{{maintained by|}}}|
{{FormatInfo/row|Maintained By|{{{maintained by}}}}}
}}{{#if:{{{released|}}}|
{{FormatInfo/row|Released|{{{released}}}}}
}}
{{#if:{{{image|}}}|
<tr><td align="center" colspan="2">
[[Image:{{{image}}}|200px|{{{caption}}}]]
</td></tr>
}}
{{#if:{{{caption|}}}|
<tr><td align="center" colspan="2">
{{{caption}}}
</td></tr>
}}
</table>
<includeonly>{{#if:{{{formattype|}}}||[[Category:FormatInfo without formattype]]}}{{#if:{{{subcat|}}}||[[Category:FormatInfo without subcat]]}}{{#ifeq:{{{formattype|electronic}}}|electronic|{{#if:{{{extensions|}}}||[[Category:FormatInfo without extensions]]}}{{#if:{{{mimetypes|}}}||[[Category:FormatInfo without mimetypes]]}}|}}</includeonly><noinclude>
== Usage ==
<pre>
{{FormatInfo
| name =
| formattype =
| subcat =
| subcat2 =
| subcat3 =
| subcat4 =
| subcat5 =
| thiscat =
| extensions =
| mimetypes =
| locfdd =
| fourccs =
| pronom =
| type code =
| uniform type =
| wikidata =
| compression =
| extended from =
| magic =
| kaitai struct =
| spec =
| spec availability=
| reference impl =
| conforms to =
| charset =
| charsetaliases =
| codepage =
| mibenum =
| cfstringencoding =
| nsstringencoding =
| endianness =
| tpm =
| error resilience =
| patent license =
| developed by =
| maintained by =
| released =
| image =
| caption =
}}
</pre>

===Parameters===
;name: '''(optional)''' The name of the file format. ''Default: <nowiki>{{PAGENAME}}</nowiki>''
;formattype: '''(optional)''' The [[File Formats|type]] of the file format. Choose 'electronic', 'physical', or 'organic', or specify your own. ''Default: electronic''
;subcat: '''(optional)''' The subcategory of the file format.
;subcat2: '''(optional)''' An additional subcategory of the file format.
;subcat3: '''(optional)''' An additional subcategory of the file format.
;subcat4: '''(optional)''' An additional subcategory of the file format.
;subcat5: '''(optional)''' An additional subcategory of the file format.
;thiscat: '''(optional)''' Special parameter for indicating ontology of a non-terminal subcategory page.
;extensions: '''(optional)''' The format's known filename extensions. Use [[Template:ext|<nowiki>{{ext}}</nowiki>]], or [[Template:Noext|<nowiki>{{Noext}}</nowiki>]] if it is known to be extensionless.
;mimetypes: '''(optional)''' The MIME type of the format. Use [[Template:mimetype|<nowiki>{{mimetype}}</nowiki>]].
;locfdd: '''(optional)''' Identifier for this format from the Library of Congress Sustainability of Digital Formats, e.g. "fdd000314". Use [[Template:LoCFDD|<nowiki>{{LoCFDD}}</nowiki>]].
;fourccs: '''(optional)''' FourCC code
;pronom: '''(optional)''' The [[Sources/PRONOM|PRONOM]] ID of the format, e.g. "fmt/45". Use [[Template:PRONOM|<nowiki>{{PRONOM}}</nowiki>]].
;type code: '''(optional)''' The Type Code of the file, used by Mac OS Classic. Use [[Template:Type Code|<nowiki>{{Type Code}}</nowiki>]].
;uniform type: '''(optional)''' The Uniform Type Identifier (UTI), used by Mac OS X and iOS. Use [[Template:UTI|<nowiki>{{UTI}}</nowiki>]].
;wikidata: '''(optional)''' Wikidata title ID. Use [[Template:wikidata|<nowiki>{{wikidata}}</nowiki>]].
;compression: Types of compression. Whether Lossy, Lossless, or Both, and whether Optional or Always compressed. i.e. JPEG is Always Lossy.
;extended from: Any formats this one was based upon.
;magic: A sequence of byte values that can be used to identify the file contents, usually located close to the start of the file.
;kaitai struct: '''(optional)''' An identifier of a format at [http://formats.kaitai.io Kaitai Struct] project, e.g. "ico" would result in a link to http://formats.kaitai.io/ico/index.html generated.
;spec: URL of the format specification.
;spec availability: Type of availability the specification, e.g. commercial, free.
;reference impl: Link to page about the reference implementation of this format, if any.
;conforms to: '''(optional)''' The UTI of the parent format in the conformance hierarchy.
;charset: '''(optional)''' For character encodings: IANA charset parameter value.
;charsetaliases: '''(optional)''' For character encodings: Variant IANA charset parameter values.
;codepage: '''(optional)''' For character encodings: Code page number (IBM/MS).
;mibenum: '''(optional)''' For character encodings: IANA MIBenum.
;cfstringencoding: '''(optional)''' For character encodings: CFStringEncoding.
;nsstringencoding: '''(optional)''' For character encodings: NSStringEncoding.
;endianness: Big-endian or Little-endian byte ordering.
;tpm: Technical Protection Mechanisms supported by the format, e.g. encryption.
;error resilience: Is this format able to detect damage or recover from damage to the bitstream.
;patent license: Unknown, Disputed, Encumbered, (F)RAND, Royalty-Free, Unencumbered.
;developed by: Who developed the format.
;maintained by: Who now maintains the format.
;released: '''(optional)''' The date the format was publicly released.
;image: '''(optional)''' Illustration to show in infobox.
;caption: '''(optional)''' Caption for image

===Potential Parameters===
This is a list of parameters that could be included in this template.

;mime & mime aliases: Split mimetypes into primary type and known aliases.
;version: The version of the format, e.g. "1.4" for PDF 1.4
;previous version: Link to page about the previous version of this format.
;next version: Link to page about the next version of this format.
;back compat: Whether this version is backwards compatible with the previous version.
;wikipedia: Name of the Wikipedia page that describes this format, e.g. "JPEG 2000" will be rendered as [[Wikipedia:JPEG 2000|JPEG 2000]]
;container for: A list of formats this format can contain.
;contained by: A list of formats that may contain this format.
;extended to: Any formats that have been derived from this one.
;embeddable metadata: Kinds of metadata that can be embedded in this format.
;dependencies: External resources that files in this format may depend upon, e.g. fonts, or even hardware.
;namespace: The namespace-uri that defines the file format if it is XML-based.

==Examples==

[[Category:File Formats| ]]
</noinclude>

Template:Fix

2021-03-13T01:28:43Z

GoodClover: Usage

[[[{{{link|:Template:Fix}}}|{{{1|unspecified fix wanted}}}]]]<noinclude>
== Usage ==

<code><nowiki>{{fix|</nowiki>''Message''<nowiki>|link=</nowiki>''link''<nowiki>}}</nowiki></code>

;Message: What needs fixing?
;link: '''(optional)''' Page to link to, don't add <code>[[ ]]</code>. Defaults to linking here.

</noinclude>

Template:Fix

2021-03-13T01:18:32Z

GoodClover: Rather than defaulting to Cleanup link back to the template page.

Template:Fix

2021-03-13T01:12:53Z

GoodClover: Create a basic fix template

[[[{{{link|Cleanup}}}|{{{1|unspecified fix wanted}}}]]]<noinclude>
</noinclude>

User:GoodClover

2021-03-13T00:23:31Z

GoodClover:

Hi, I'm '''Oliver'''. :)

I'm probably going to make/work on:
* [[CompputerCraft]]/[[:Category:ComputerCraft]] ([https://computercraft.cc/ http://computercraft.cc])
* [[NFP]] - CC's default very-super-simple-as-it-gets plain text image format. Don't know what it stands for :P
* [[ComputerCraft Video]]/[[CCV]] - A CC video format. ([http://www.computercraft.info/forums2/index.php?/topic/23399-video-player-watch-rick-roll-in-computercraft/ from this])

This site is really nice, but unfortunately seems to be fairly unmaintained - and has fallen into a state of disrepair (as in the Wiki itself, not it's content).
Would be nice if it got freshened a bit and some stuff was updated.

User:GoodClover

2021-03-13T00:21:30Z

GoodClover:

Hi, I'm '''Oliver'''. :)

I'm probably going to make/work on:
* [[CompputerCraft]]/[[:Category:ComputerCraft]] ([https://computercraft.cc/ http://computercraft.cc])
* [[NFT]] - CC's default very-super-simple-as-it-gets plain text image format. Don't know what it stands for :P
* [[ComputerCraft Video]]/[[CCV]] - A CC video format. ([http://www.computercraft.info/forums2/index.php?/topic/23399-video-player-watch-rick-roll-in-computercraft/ from this])

This site is really nice, but unfortunately seems to be fairly unmaintained - and has fallen into a state of disrepair (as in the Wiki itself, not it's content).
Would be nice if it got freshened a bit and some stuff was updated.

User:GoodClover

2021-03-13T00:20:46Z

GoodClover:

User:GoodClover

2021-03-13T00:20:26Z

GoodClover: Created page with "Hi, I'm '''Oliver'''. :) I'm probably going to make/work on: * CompputerCraft/:Category:ComputerCraft ([https://computercraft.cc/ http://computercraft.cc]) * NFT ..."

Portable Network Graphics

2021-03-13T00:03:34Z

GoodClover: Redirected page to PNG

#REDIRECT [[PNG]]

Just Solve the File Format Problem:Community portal

2021-03-13T00:01:26Z

GoodClover: /* Broken image in footer */

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

== Open issues ==

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

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

== Article naming convention ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Spam ==

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

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

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

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

== Orphaned / Blank Pages ==

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

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

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

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

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

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

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

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

== Permissions for user pages ==

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

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

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

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

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

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

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

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

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

[[Category:Meta]]

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

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

Thanks again!

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

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

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

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

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

== Type / Creator codes ==

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

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

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

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

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

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

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

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

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

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

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

:This is a pretty serious problem. Are there any plans to fix it? -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:22, 12 November 2020 (UTC)
::Seems like it has been fixed, by removing the CAPTCHA altogether. Let's all keep a keen eye out for spamdalism. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 03:33, 23 November 2020 (UTC)

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

Just Solve the File Format Problem:General disclaimer

2021-03-12T23:42:50Z

GoodClover:

* Nobody who contributes here can ensure beyond a reasonable doubt that you will be able to use or convert to/from a given format.
* We just document the mess, [https://www.youtube.com/watch?v=eFTLKWw542g we didn't make it] (except those of us who did; you know who you are).
* Documentation is always incomplete and the real world changes quickly, and that goes double for file formats.
* If your favourite piece of knowledge about an obscure format is missing, it is because you didn't add it yet.
* Keep backups!

[[Category:Meta]]

Just Solve the File Format Problem:Community portal

2021-03-12T23:23:55Z

GoodClover: /* Broken image in footer */

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

== Open issues ==

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

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

== Article naming convention ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Spam ==

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

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

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

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

== Orphaned / Blank Pages ==

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

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

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

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

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

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

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

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

== Permissions for user pages ==

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

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

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

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

== Broken image in footer ==
The "Creative Commons 0" image at the bottom of every page (https://www.mediawiki.org/w/skins/common/images/cc-0.png) is broken. Can that be fixed? [[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 00:06, 10 July 2015 (UTC)
:Still broken 5 years later... Is this place even maintained? [[User:GoodClover|GoodClover]] ([[User talk:GoodClover|talk]]) 23:23, 12 March 2021 (UTC)

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

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

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

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

[[Category:Meta]]

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

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

Thanks again!

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

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

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

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

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

== Type / Creator codes ==

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

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

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

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

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

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

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

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

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

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

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

:This is a pretty serious problem. Are there any plans to fix it? -[[User:Jsummers|Jsummers]] ([[User talk:Jsummers|talk]]) 16:22, 12 November 2020 (UTC)
::Seems like it has been fixed, by removing the CAPTCHA altogether. Let's all keep a keen eye out for spamdalism. [[User:Arlo James Barnes|Arlo James Barnes]] ([[User talk:Arlo James Barnes|talk]]) 03:33, 23 November 2020 (UTC)

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