Talk:Unix2dos

Learn more about this page

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Does this command handle byte order mark? edit

Latest comment: 11 years ago1 comment1 person in discussion

As windows standard is to use byte order mark, and unix standard might be to not use byte order mark to use autodetection, does this command handle byte order mark the appropriate way? — Preceding unsigned comment added by 84.99.16.252 (talk) 21:35, 30 June 2012 (UTC)Reply

tr -d '\r' is too utf-8 safe edit

Latest comment: 2 years ago1 comment1 person in discussion

Regarding:

tr -d '\r' < file > file2 # For ASCII and other files which do not contain multibyte characters (Not utf-8 safe).

That tr command is utf-8 safe. See UTF-8:

"ASCII bytes do not occur when encoding non-ASCII code points into UTF-8"

It is not UTF-16 safe because UTF-16 is incompatible with ASCII, although I've read that tr on MacOS can handle unicode character sets depending on the value of LC_CTYPE. Robin A. Meade (talk) 20:01, 1 June 2021 (UTC)Reply

Add topic