Text Files on Linux - Revision history

>Wongck at 15:13, 1 January 2013

2013-01-01T15:13:57Z

← Older revision		Revision as of 11:13, 1 January 2013
Line 17:		Line 17:
	''This page needs links to appropriate websites''		''This page needs links to appropriate websites''
	<br />		<br />
			<br />
			Back to [[Data Formats]]
	<br />		<br />
	<br />		<br />
	[[Category:Data Formats]]		[[Category:Data Formats]]

>Wongck at 11:57, 11 October 2011

2011-10-11T11:57:47Z

← Older revision		Revision as of 07:57, 11 October 2011
Line 16:		Line 16:

	''This page needs links to appropriate websites''		''This page needs links to appropriate websites''
			<br />
			<br />
			<br />
			[[Category:Data Formats]]

>Barthax: /* Plain Text */

2006-07-11T12:58:19Z

Plain Text

← Older revision		Revision as of 08:58, 11 July 2006
Line 6:		Line 6:

	* Line breaks. The standard line break on the Atari ST (and on MSDOS and Windows) is a carriage return (0x0D) followed by a line feed (0x0A). On Linux and other Unix systems, it's just a line feed (0x0A). The Unix utility fromdos will convert the linebreaks for you. (There's a comparable todos that works in the other direction). Some editors (e.g. vim) automatically handle line break differences for you.		* Line breaks. The standard line break on the Atari ST (and on MSDOS and Windows) is a carriage return (0x0D) followed by a line feed (0x0A). On Linux and other Unix systems, it's just a line feed (0x0A). The Unix utility fromdos will convert the linebreaks for you. (There's a comparable todos that works in the other direction). Some editors (e.g. vim) automatically handle line break differences for you.
	* Encoding. The Atari ST character set has some interesting characters in its upper half, not all of which are present in the usual iso8859-1 or iso8859-15 that Linux has been using recently. You should be able to use GNU recode to perform a conversion to unicode with the code: "recode AtariST..UTF-8 <file>"		* Encoding. The Atari ST character set has some interesting characters in its upper half, not all of which are present in the usual iso8859-1 or iso8859-15 that Linux has been using recently. You should be able to use [http://www.gnu.org/software/recode/recode.html GNU recode] to perform a conversion to unicode with the code: "recode AtariST..UTF-8 <file>"
	* Formatting. There may be some characters that work with the ST's vt52 emulator to control the formatting of the text. Some of these characters will have the same effect on an xterm or the Linux console, but others will be misinterpreted.		* Formatting. There may be some characters that work with the ST's vt52 emulator to control the formatting of the text. Some of these characters will have the same effect on an xterm or the Linux console, but others will be misinterpreted.

>Barthax: /* Plain Text */

2006-07-11T12:53:53Z

Plain Text

← Older revision		Revision as of 08:53, 11 July 2006
Line 6:		Line 6:

	* Line breaks. The standard line break on the Atari ST (and on MSDOS and Windows) is a carriage return (0x0D) followed by a line feed (0x0A). On Linux and other Unix systems, it's just a line feed (0x0A). The Unix utility fromdos will convert the linebreaks for you. (There's a comparable todos that works in the other direction). Some editors (e.g. vim) automatically handle line break differences for you.		* Line breaks. The standard line break on the Atari ST (and on MSDOS and Windows) is a carriage return (0x0D) followed by a line feed (0x0A). On Linux and other Unix systems, it's just a line feed (0x0A). The Unix utility fromdos will convert the linebreaks for you. (There's a comparable todos that works in the other direction). Some editors (e.g. vim) automatically handle line break differences for you.
	* Encoding. The Atari ST character set has some interesting characters in its upper half, not all of which are present in the usual iso8859-1 or iso8859-15 that Linux has been using recently. You should be able to use GNU ~~record~~ to perform a conversion to unicode with the code: "recode AtariST..UTF-8 <file>"		* Encoding. The Atari ST character set has some interesting characters in its upper half, not all of which are present in the usual iso8859-1 or iso8859-15 that Linux has been using recently. You should be able to use GNU recode to perform a conversion to unicode with the code: "recode AtariST..UTF-8 <file>"
	* Formatting. There may be some characters that work with the ST's vt52 emulator to control the formatting of the text. Some of these characters will have the same effect on an xterm or the Linux console, but others will be misinterpreted.		* Formatting. There may be some characters that work with the ST's vt52 emulator to control the formatting of the text. Some of these characters will have the same effect on an xterm or the Linux console, but others will be misinterpreted.

>Daeghnao at 10:56, 10 March 2006

2006-03-10T10:56:27Z

New page

Your Atari text files may be ordinary plain text (the kind you can double-click and "Show" in GEM) or they could have some formatting.

== Plain Text ==

For plain text files, there are three issues to consider:

* Line breaks. The standard line break on the Atari ST (and on MSDOS and Windows) is a carriage return (0x0D) followed by a line feed (0x0A). On Linux and other Unix systems, it's just a line feed (0x0A). The Unix utility fromdos will convert the linebreaks for you. (There's a comparable todos that works in the other direction). Some editors (e.g. vim) automatically handle line break differences for you.
* Encoding. The Atari ST character set has some interesting characters in its upper half, not all of which are present in the usual iso8859-1 or iso8859-15 that Linux has been using recently. You should be able to use GNU record to perform a conversion to unicode with the code: "recode AtariST..UTF-8 <file>"
* Formatting. There may be some characters that work with the ST's vt52 emulator to control the formatting of the text. Some of these characters will have the same effect on an xterm or the Linux console, but others will be misinterpreted.

== Formatted Text ==

Formatted text can come in any number of application specific formats:

* 1st Word (Plus). This can be converted to RTF with the program wpls2rtf.

''This page needs links to appropriate websites''