[SOLVED] Unix style to ms-dos style line terminator one-liner converter.

scasey · 09-21-2018, 09:21 PM

15 responses to this thread, and the OP still hasn't shown us what they've attempted and need help with. They're almost 4/5 of the way to being an "LQ Guru"...I don't get it.
There's a recent thread here that discussed this same issue in great depth.

Here's another idea:
Do an ASCII transfer with (S)FTP of the files from a windows box to a Linux box. That will convert the line end characters....that's pretty much the definition of an ASCII (S)FTP transfer...change nothing but the line-ends.

wpeckham · 09-22-2018, 04:00 AM

Quote:

Originally Posted by scasey

15 responses to this thread, and the OP still hasn't shown us what they've attempted and need help with. They're almost 4/5 of the way to being an "LQ Guru"...I don't get it.
There's a recent thread here that discussed this same issue in great depth.

Here's another idea:
Do an ASCII transfer with (S)FTP of the files from a windows box to a Linux box. That will convert the line end characters....that's pretty much the definition of an ASCII (S)FTP transfer...change nothing but the line-ends.

In general, SFTP does not do "edits" to the files, all transfer is binary. FTP tools do in-transfer conversions. There may be specific exceptions (I have not used EVERY tool in the world) but that is my experience. Also, I find the conversions done by dos2unix and unix2dos more accurate. Cases where the FTP tools get it wrong are rare, but not as rare as the cases where dos2unix gets it wrong.

I cannot imagine starting a thread and then not responding to suggestions, but we experience that fairly often here. I would not let it bother me much.

Michael Uplawski · 09-22-2018, 04:31 AM

Quote:

Originally Posted by wpeckham

WHY BOTHER, when the tool has already been built, tested, optimized, and folded into the repos for distribution more than ten years ago?

A new tool could write “Don't Panic” in big friendly letters across the whole screen, when done.

hydrurga · 09-22-2018, 05:28 AM

Quote:

Originally Posted by scasey

15 responses to this thread, and the OP still hasn't shown us what they've attempted and need help with. They're almost 4/5 of the way to being an "LQ Guru"...I don't get it.
There's a recent thread here that discussed this same issue in great depth.

Here's another idea:
Do an ASCII transfer with (S)FTP of the files from a windows box to a Linux box. That will convert the line end characters....that's pretty much the definition of an ASCII (S)FTP transfer...change nothing but the line-ends.

I've long suspected that some membership names are actually multi-use, say at educational establishments or large companies, where the name and password are pasted up on a board and anyone who has a Linux query is encouraged to use them. In that way it would explain some of the rather "interesting" and "novice" requests from members with long posting histories. Ok, so it's a tinfoil hat theory, but I like it.

Anyway, to the OP, see https://en.wikipedia.org/wiki/Dos2unix

stf92 · 09-22-2018, 09:27 AM

Quote:

Originally Posted by stf92

Anyway, the problem as stated in post #3 can be broken into two parts. Part (a) Implement the foo command. This will be a certain sequence of linux commands, including tr.

Part (b)
Process all files in this directory ending in .unix using the foo command.

Part (a) is finished, as the following sequence of commands show.

Code:

539	 cat text01.unix 
540	 hexdump -C text01.unix 
541	 sed  's/$/\r/' text01.unix 
542	 sed  's/$/\r/' text01.unix > text01.dos
543	 hexdump -C text01.dos

Code:

bill@darkstar~/work$ cat text01.unix 
En un lugar de la mancha
de cuyo nombre no quiero acordarme,
no ha mucho que vivia un hidalgo.
bill@darkstar~/work$ hexdump -C text01.unix 
00000000  45 6e 20 75 6e 20 6c 75  67 61 72 20 64 65 20 6c  |En un lugar de l|
00000010  61 20 6d 61 6e 63 68 61  0a 64 65 20 63 75 79 6f  |a mancha.de cuyo|
00000020  20 6e 6f 6d 62 72 65 20  6e 6f 20 71 75 69 65 72  | nombre no quier|
00000030  6f 20 61 63 6f 72 64 61  72 6d 65 2c 0a 6e 6f 20  |o acordarme,.no |
00000040  68 61 20 6d 75 63 68 6f  20 71 75 65 20 76 69 76  |ha mucho que viv|
00000050  69 61 20 75 6e 20 68 69  64 61 6c 67 6f 2e 0a     |ia un hidalgo..|
0000005f
bill@darkstar~/work$ sed  's/$/\r/' text01.unix 
En un lugar de la mancha
de cuyo nombre no quiero acordarme,
no ha mucho que vivia un hidalgo.
bill@darkstar~/work$ sed  's/$/\r/' text01.unix > text01.dos
bill@darkstar~/work$ hexdump -C text01.dos
00000000  45 6e 20 75 6e 20 6c 75  67 61 72 20 64 65 20 6c  |En un lugar de l|
00000010  61 20 6d 61 6e 63 68 61  0d 0a 64 65 20 63 75 79  |a mancha..de cuy|
00000020  6f 20 6e 6f 6d 62 72 65  20 6e 6f 20 71 75 69 65  |o nombre no quie|
00000030  72 6f 20 61 63 6f 72 64  61 72 6d 65 2c 0d 0a 6e  |ro acordarme,..n|
00000040  6f 20 68 61 20 6d 75 63  68 6f 20 71 75 65 20 76  |o ha mucho que v|
00000050  69 76 69 61 20 75 6e 20  68 69 64 61 6c 67 6f 2e  |ivia un hidalgo.|
00000060  0d 0a                                             |..|
00000062
bill@darkstar~/work$ fc -l

As to part (b):

Code:

for i in *; do foo "$i"; done

That is

Code:

for i in *; do 
    sed  's/$/\r/' $i > $i.dos
done

This is not yet tested.

stf92 · 09-23-2018, 06:10 PM

Solution for part (b) tested. Runs OK.