Template:FormatInfo

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Categories should be includeonly.)
(Name- and category-related changes.)
Line 1: Line 1:
 
<table class="infobox formatinfo" border="0" style="float: right; border: 1px solid #666666; max-width: 15%; background-color: #F8F8F8; padding: 0.25em; margin: 0.25em 1em;">
 
<table class="infobox formatinfo" border="0" style="float: right; border: 1px solid #666666; max-width: 15%; background-color: #F8F8F8; padding: 0.25em; margin: 0.25em 1em;">
{{FormatInfo/row|<includeonly>Name</includeonly>|{{{name|<includeonly>{{PAGENAME}}</includeonly>}}}}}
+
<tr>
 +
<th colspan="2">[[File Formats|File Format]]</th>
 +
</tr>
 +
{{FormatInfo/row|Name|{{{name|{{PAGENAME}}}}}{{DEFAULTSORT:{{{name|{{PAGENAME}}}}}}}}}
 
{{FormatInfo/row
 
{{FormatInfo/row
 
| Ontology
 
| Ontology
Line 15: Line 18:
 
|[[{{{subcat}}}]]<includeonly>[[Category:{{{subcat}}}]]</includeonly>
 
|[[{{{subcat}}}]]<includeonly>[[Category:{{{subcat}}}]]</includeonly>
 
<ul><li>
 
<ul><li>
<includeonly>[[{{PAGENAME}}]]</includeonly>
+
[[{{{name|{{PAGENAME}}}}}]]
 
</li></ul>
 
</li></ul>
|<includeonly>[[{{PAGENAME}}]]</includeonly>
+
|[[{{{name|{{PAGENAME}}}}}]]
 
}}
 
}}
 
</li></ul>
 
</li></ul>
Line 31: Line 34:
 
}}
 
}}
 
</table>
 
</table>
 +
[[Category:File Formats|<noinclude> </noinclude>]]
 
<noinclude>
 
<noinclude>
 
== Usage ==
 
== Usage ==

Revision as of 23:40, 9 November 2012

File Format
Name FormatInfo
Ontology

Contents

Usage

{{FormatInfo
| name                   = 
| extensions             = 
| mimetypes              = 
| pronom                 = 
}}

Parameters

name
The name of the file format (optional - will default to the page name)
extensions
The format's known filename extensions, space separated, including the dot, e.g. ".pdf .fdf"
mimetypes
The MIME type of the format.
pronom
The PRONOM ID of the format, e.g. "fmt/45".

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 JPEG 2000
locfdd
Identifier for this format from the Library of Congress Sustainability of Digital Formats, e.g. "fdd000314" will be rendered as fdd000314.
type code
The Type Code of the file, used by Mac OS Classic.
uniform type
The Uniform Type Identifier (UTI), used by Mac OS X and iOS.
conforms to
The UTI of the parent format in the conformance hierarchy.
magic
A sequence of byte values that can be used to identify the file contents, usually located close to the start of the file.
released
The date the format was publicly released.
container for
A list of formats this format can contain.
contained by
A list of formats that may contain this format.
extended from
Any formats this one was based upon.
extended to
Any formats that have been derived from this one.
spec
URL of the format specification.
spec availability
Type of availability the specification, e.g. commercial, free.
patent license
Unknown, Disputed, Encumbered, (F)RAND, Royalty-Free, Unencumbered.
compression
Types of compression. Whether Lossy, Lossless, or Both, and whether Optional or Always compressed. i.e. JPEG is Always Lossy.
endianness
Big-endian or Little-endian byte ordering.
developed by
Who developed the format.
maintained by
Who now maintains the format.
reference impl
Link to page about the reference implementation of this format, if any.
embeddable metadata
Kinds of metadata that can be embedded in this format.
tpm
Technical Protection Mechanisms supported by the format, e.g. encryption.
dependencies
External resources that files in this format may depend upon, e.g. fonts, or even hardware.
error resiliance
Is this format able to detect damage or recover from damage to the bitstream.

Examples

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox