nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Windows to Unix - ^M (control m) removal

Baracus

I'm deploying from an instance of TeamSite on a Windows server, to a target server running Solaris.

Environment Variables:
Windows 2003, SP2 running OpenDeploy 6.0.2
Solaris 5.10, running OpenDeploy Reciever 6.2

Whenever a text-based file is deployed, a control M (^m) is added at the end of every line. This occurs because carriage returns are handled differently in windows vs. unix. The ^m represents the carriage return portion of the windows CRLF (carriage return line feed), while Unix handles the line feed accordingly.

Is there a setting/config in OpenDeploy that can remove these? I could always write a script and run a DNR, but was hoping OD could handle it.

TIA

Find more posts tagged with

Comments

ISCBorisB

I could always write a script and run a DNR

Do so. I do not think that you can configure OD itself to modify Deployed Files. You can perhaps code a Delivery Adapter
to remove CRs for you. In this particular case it is IMO easier to do by DNR - as you've mentioned

Adam Stoller

Do so. I do not think that you can configure OD itself to modify Deployed Files. You can perhaps code a Delivery Adapter
to remove CRs for you. In this particular case it is IMO easier to do by DNR - as you've mentioned

Alternatively - create a script that is run as part of the workflow to remove the ^M's before the files get submitted to TeamSite (assuming TS is on the source side) - as I do not believe that OD adds ^Ms to files being transferred - more likely the editing application being used on Windows is doing that and OD is transferring the file as-is.
A number of Windows-based editing applications allow a setting to control the EOL characters that files are saved with - perhaps the one(s) being used does to.

Baracus

I do not believe that OD adds ^Ms to files being transferred - more likely the editing application being used on Windows is doing that and OD is transferring the file as-is.

That is correct, "adding" probably wasn't the best choice of words, let's just say they "appear" when transferred to the Unix machine.

Our workflows and scripts already bog down our TS server, so for the sake of performance, I'd prefer to run a DNR.

As mentioned, I was hoping that OD or ODR could handle them for me (wishful thinking).

Thanks for the speedy replies, guys.