Binary file in the context of Document file format


Binary file in the context of Document file format

Binary file Study page number 1 of 1

Play TriviaQuestions Online!

or

Skip to study material about Binary file in the context of "Document file format"


⭐ Core Definition: Binary file

A binary file is a computer file that is not a text file. The term "binary file" is often used as a term meaning "non-text file". Many binary file formats contain parts that can be interpreted as text; for example, some computer document files containing formatted text, such as older Microsoft Word document files, contain the text of the document but also contain formatting information in binary form.

↓ Menu
HINT:

👉 Binary file in the context of Document file format

A document file format is a text or binary file format for storing documents on a storage media, especially for use by computers.There currently exists a multitude of incompatible document file formats.

Examples of XML-based open standards are the ISO/IEC standards OpenDocument (ISO 26300:2006) and the Strict and Transitional versions of Office Open XML (ISO 29500:2008). Another example is DocBook which is used for writing structured documentation such as manuals, books, technical guides, and then processed with stylesheets/toolchains to generate HTML, PDF, EPUB, man pages, etc. XHTML, an earlier document file format over time became part of HTML5.

↓ Explore More Topics
In this Dossier

Binary file in the context of Human-readable medium and data

In computing, a human-readable medium or human-readable format is any encoding of data or information that can be naturally read by humans, resulting in human-readable data. It is often encoded as ASCII or Unicode text, rather than as binary data.

In most contexts, the alternative to a human-readable representation is a machine-readable format or medium of data primarily designed for reading by electronic, mechanical or optical devices, or computers. For example, Universal Product Code (UPC) barcodes are very difficult to read for humans, but very effective and reliable with the proper equipment, whereas the strings of numerals that commonly accompany the label are the human-readable form of the barcode information. Since any type of data encoding can be parsed by a suitably programmed computer, the decision to use binary encoding rather than text encoding is usually made to conserve storage space. Encoding data in a binary format typically requires fewer bytes of storage and increases efficiency of access (input and output) by eliminating format parsing or conversion.

View the full Wikipedia page for Human-readable medium and data
↑ Return to Menu

Binary file in the context of Object code

In computing, object code or object module is the product of an assembler or compiler.

In a general sense, object code is a sequence of statements or instructions in a computer language, usually a machine code language (i.e., binary) or an intermediate language such as register transfer language (RTL). The term indicates that the code is the goal or result of the compiling process, with some early sources referring to source code as a "subject program".

View the full Wikipedia page for Object code
↑ Return to Menu

Binary file in the context of E-text

e-text (from "electronic text"; sometimes written as etext) is a general term for any document that is read in digital form, and especially a document that is mainly text. For example, a computer-based book of art with minimal text, or a set of photographs or scans of pages, would not usually be called an "e-text". An e-text may be a binary or a plain text file, viewed with any open source or proprietary software. An e-text may have markup or other formatting information, or not. An e-text may be an electronic edition of a work originally composed or published in other media, or may be created in electronic form originally. The term is usually synonymous with e-book.

View the full Wikipedia page for E-text
↑ Return to Menu

Binary file in the context of Firefox 3.5

The project that became Firefox today began as an experimental branch of the Mozilla Suite called m/b (or mozilla/browser). Firefox retains the cross-platform nature of the original Mozilla browser, using the XUL user interface markup language. The use of XUL made it possible to extend the browser's capabilities through the use of extensions and themes. The development and installation processes of these add-ons raised security concerns, and with the release of Firefox 0.9, the Mozilla Foundation opened a Mozilla Update website containing "approved" themes and extensions. The use of XUL sets Firefox apart from other browsers, including other projects based on Mozilla's Gecko layout engine and most other browsers, which use interfaces native to their respective platforms (Galeon and Epiphany use GTK+, K-Meleon uses MFC, and Camino uses Cocoa). Many of these projects started before Firefox, and may have served as inspiration.

Hyatt, Ross, Hewitt and Chanial developed their browser to combat the perceived software bloat of the Mozilla Suite (codenamed, internally referred to, and continued by the community as SeaMonkey), which integrated features such as IRC, mail, news, and WYSIWYG HTML editing into one internet suite. After it was sufficiently developed, binaries for public testing appeared in September 2002 under the name Phoenix. This name carried the implication of the mythical firebird that rose triumphantly from the ashes of its dead predecessor, in this case Netscape Navigator which lost the "First browser war" to Microsoft's Internet Explorer. The name Mozilla began as the internal codename for the original 1994 Netscape Navigator browser aiming to displace NCSA Mosaic as the world's most popular web browser. The name for this would-be "Mosaic killer" was meant to evoke the building-crushing Godzilla.

View the full Wikipedia page for Firefox 3.5
↑ Return to Menu

Binary file in the context of Documentation generator

In software development, a documentation generator is an automation technology that generates documentation. A generator is often used to generate API documentation which is generally for programmers or operational documents (such as a manual) for end users. A generator often pulls content from source, binary or log files. Some generators, such as Javadoc and Doxygen, use special source code comments to drive content and formatting.

View the full Wikipedia page for Documentation generator
↑ Return to Menu