X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <17766865.post@talk.nabble.com> Date: Tue, 10 Jun 2008 16:12:49 -0700 (PDT) From: gmarsha11 To: cygwin AT cygwin DOT com Subject: Re: Extra spaces in text files in cygwin In-Reply-To: <484EFB14.65C9E56F@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: gary DOT marshall AT hp DOT com References: <17764646 DOT post AT talk DOT nabble DOT com> <484EFB14 DOT 65C9E56F AT dessent DOT net> 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 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? -- View this message in context: http://www.nabble.com/Extra-spaces-in-text-files-in-cygwin-tp17764646p17766865.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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/