Mark J. Reed-2 wrote:
>
> So pipe the files through iconv to something your munging tools can
> deal with and then through iconv again to change it back to whatever
> DP is using..
>
>
>
Looks like that's what I'll have to do. It's a minor inconvenience, but
doable. It's too bad that the
Gary Johnson wrote:
>
> On 2008-06-10, gmarsha11 wrote:
>>
>> Does this mean it's necessary to change the encoding for any files I
>> might
>> need to cat, grep awk, etc.?
>
> I'm no expert on any of this, but as far as I know, all traditional
Ok, have saved the file with Windows notepad as ANSI, Unicode, Unicode big
endian, and UTF-8.
Both Unicode options give me the output with the extra spaces. ANSI and
UTF-8 allow me to see the files as I would expect to see them.
Does this mean it's necessary to change the encoding for any fil
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 ca
I used the backticks to specify the command I used at the command line. When
I type that command, I get the contents of the file with spaces before each
character (yes, the spaces appear to come before each character).
I am installing additional fonts as was suggested earlier.
gmarsha11 wrote
Brian Dessent wrote:
>
> gmarsha11 wrote:
>
>> then, `cat abc.txt` returns
>>
>> T h i s i s a b c f i l e
>>
>> Anyone know what might cause this?
>
> What do you mean by "[backtick] returns"? Can you paste a full example
>
I am a brand new user of cygwin and I'm already having troubles. Whenever I
grep or cat or otherwise dump the contents of a text file to stdout, there
are extra spaces between all characters. For instance, if file abc.txt
contains:
This is abc file
then, `cat abc.txt` returns
T h i s i s a
7 matches
Mail list logo
