X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 10 Jun 2008 16:30:31 -0700 From: Gary Johnson To: cygwin AT cygwin DOT com Subject: Re: Extra spaces in text files in cygwin Message-ID: <20080610233030.GB18434@suncomp1.spk.agilent.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <17764646 DOT post AT talk DOT nabble DOT com> <484EFB14 DOT 65C9E56F AT dessent DOT net> <17766865 DOT post AT talk DOT nabble DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17766865.post@talk.nabble.com> X-Operating-System: SunOS suncomp1 5.8 sparc User-Agent: Mutt/1.5.17 (2007-11-01) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2008-06-10, gmarsha11 wrote: > The backticks contain the actual command that I run. > > > I'm not sure about the file's encoding. How do I tell? > > When I create a new file with vi, I can read the file with no problem. The > output is normal. > > These particular text files that I am working with were created by HP Data > Protector. I can easily parse and manipulate these files on HPUX servers, > but the Windows servers lack that functionality. I thought Cygwin would > help with this. > > How do I tell what the file's encoding is? You can look at the contents of the file in binary using od -t cx1 abc.txt for example. When I do this, I get the following: $ cat abc.txt This is abc file $ od -t cx1 abc.txt 0000000 T h i s i s a b c f i l e 54 68 69 73 20 69 73 20 61 62 63 20 66 69 6c 65 0000020 \n 0a 0000021 You can see that in this case, the character coding is ASCII. HTH, Gary -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/