Text-based data

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(→‎Text formats and resources)
(Fix links)
Line 7: Line 7:
 
This section is for any text-based data formats that didn't fit into some other category.
 
This section is for any text-based data formats that didn't fit into some other category.
  
−
Text based data, AKA plain text. has proven to be very hard to understand. This has not only to do with the infinite ways text based data might be structured, but mainly because you need to know the [[Text encoding|encoding]] (eg. [[UTF8]]) before you can start  interpreting it.
+
Text based data, AKA plain text. has proven to be very hard to understand. This has not only to do with the infinite ways text based data might be structured, but mainly because you need to know the [[Character Encoding|encoding]] (eg. [[UTF-8]]) before you can start  interpreting it.
  
 
* [http://www.joelonsoftware.com/articles/Unicode.html The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)]
 
* [http://www.joelonsoftware.com/articles/Unicode.html The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)]

Revision as of 04:02, 18 January 2013

File Format
Name Text-based data
Ontology

Introduction

This section is for any text-based data formats that didn't fit into some other category.

Text based data, AKA plain text. has proven to be very hard to understand. This has not only to do with the infinite ways text based data might be structured, but mainly because you need to know the encoding (eg. UTF-8) before you can start interpreting it.

Text formats and resources

See Also

Retrieved from "http://fileformats.archiveteam.org/index.php?title=Text-based_data&oldid=8996"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox