Text-based data
From Just Solve the File Format Problem
(Difference between revisions)
Dan Tobias (Talk | contribs) (→Text formats and resources) |
(→Text formats and resources) |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
|formattype=electronic | |formattype=electronic | ||
|thiscat=Text-based data | |thiscat=Text-based data | ||
| + | |image=Binder folder.png | ||
}} | }} | ||
| − | =Introduction= | + | ==Introduction== |
| − | + | ||
| − | + | ||
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. | 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. | ||
| Line 11: | Line 10: | ||
* [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!)] | ||
| − | =Text formats and resources= | + | ==Text formats and resources== |
* [[AsciiDoc]] | * [[AsciiDoc]] | ||
* [[Attribute-Relation File Format]] | * [[Attribute-Relation File Format]] | ||
* [[Column Delimited]] | * [[Column Delimited]] | ||
* [[CSV]] (Comma Separated Values; comma-delimited) | * [[CSV]] (Comma Separated Values; comma-delimited) | ||
| − | * [[ | + | ** [[CSV Dialect Description Format]] |
| + | ** [[CSV Schema]] | ||
| + | ** [[JSON Table Schema]] | ||
* [[Microsoft Office File List]] (filelist.xml) | * [[Microsoft Office File List]] (filelist.xml) | ||
| + | * [[NestedText]] [https://nestedtext.org/en/stable/] | ||
| + | * [[Org-mode]] | ||
* [[Softdisk Publishing UDF files]] | * [[Softdisk Publishing UDF files]] | ||
* [[Strings File]] (OS X, iOS) (.strings) | * [[Strings File]] (OS X, iOS) (.strings) | ||
| Line 25: | Line 28: | ||
== See Also == | == See Also == | ||
| − | * [[ | + | * [[Plain text]] |
| − | * Some text-based formats are listed in [[Document]], [[Markup]], or [[Serialization]] | + | * Some text-based formats are listed in [[Document]], [[Markup]], [[Metaformats]], or [[Serialization]] |
| + | |||
| + | == Links == | ||
| + | * [http://hellodot.net/lute/lotcl-03 Information wants to be plain text.] | ||
Latest revision as of 17:24, 9 October 2020
Contents |
[edit] Introduction
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.
[edit] Text formats and resources
- AsciiDoc
- Attribute-Relation File Format
- Column Delimited
- CSV (Comma Separated Values; comma-delimited)
- Microsoft Office File List (filelist.xml)
- NestedText [1]
- Org-mode
- Softdisk Publishing UDF files
- Strings File (OS X, iOS) (.strings)
- Tab delimited
- Text Encoding Initiative
- Textile
[edit] See Also
- Plain text
- Some text-based formats are listed in Document, Markup, Metaformats, or Serialization
