Re: converting text input in any encoding to unicode
Re: converting text input in any encoding to unicode
- Subject: Re: converting text input in any encoding to unicode
- From: Eric Schlegel <email@hidden>
- Date: Sun, 27 Apr 2003 14:46:59 -0700
On Sunday, April 27, 2003, at 01:26 PM, Ben Dougall wrote:
in fact, do plain text files have encoding info as standard, or is no
encoding indication standard?
Typically, a plain text file will have no encoding information at all.
Plain text is just that - a sequence of bytes in some encoding, but
with no indication of what encoding it might be.
Typically this hasn't been much of a problem when plain text files were
the file format of choice, because a user's system would only use one
encoding anyways - whether it's MacRoman, MacJapanese, Windows Latin 1,
etc. But if you're just looking at an arbitrary text file, there's no
way to know for sure what encoding that file uses.
this is the question i probably should have asked in the first place:
do plain text files always / sometimes / never have encoding embedded?
Never.
in a header maybe?
Plain text files don't have headers. They're just text.
how can i look at the raw contents of text files? when you open a text
file in say bbedit, you just get the text - is there a unix command
line tool that enables you to see the raw full contents of a file?
What you see in BBEdit is the full contents of the file. BBEdit isn't
hiding anything; it's showing you every byte in the file.
-eric
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.