MKVTOOLNIX UNICODE 4.9.1 SETUP EXE 64 BIT
MKVTOOLNIX UNICODE 4.9.1 SETUP EXE UPDATE
MKVTOOLNIX UNICODE 4.9.1 SETUP EXE UPGRADE

MKVTOOLNIX UNICODE 4.9.1 SETUP EXE UPGRADE

With the new approach in Cygwin that seems to be broken, so we did not upgrade Cygwin since then (we currently use gawk 4.1.3). That worked widely fine so far, since most Windows and other application SW we use accept both record formats, fortunately (we had issues with SW upgrades of other vendors no longer accepting pure LF, but that only concerned a very small number of scripts). That's a developer's decision in my opinion.īut since with pipes or output redirection gawk used to write no CRs even in previous versions, we already had the problem that gawk had to accept *both* inputs, LF with or without CR. e., gawk reads LF in Unix and CR/LF in Win), or it interprets line endings in a Unix-style no matter of the underlying OS used. What is Unix-like or OS-like or Posix-like behaviour in that context? You could argue that gawk interprets line endings like the underlying OS does (i.

MKVTOOLNIX UNICODE 4.9.1 SETUP EXE UPDATE

I have followed the discussions about the CR/LF behaviour changes in the past attentively and decided not to update in near future, because that would lead to a massive problem with many hundreds of scripts - hoping that sometimes there will be a change in gawk again.

MKVTOOLNIX UNICODE 4.9.1 SETUP EXE 64 BIT

I soon realized that upgrades of Cygwin may cause troubles with existing scripts, so we only update if we really need to (e.g.: New functionality that would be important, 32 to 64 bit shift, eventually new Windows versions, bugs we needed to be fixed). that we are using in shell scripts running under cmd.exe (no Unix shells involved). We use tools like gawk (hundreds of scripts), head, tail, sort, etc. We have been using Cygwin for some 15+ years now. > Please don't get me wrong, but this raises a real issue here and I am not sure which rationale other than 'let's get more of the Linux-feel' drove the decision.Īnother solution which we have been using for many years now, though it might not be feasible for you: another issue originated by the change and which didn't exist before. > work for DOS files as well as for linux files. > of files you want to handle in the awk script.

plus the disadvantage to systematically amend all the scripts instead of having an external solution The only disadvantage: you have to know what kind > without the artificial obstacle to now know the EOL type of the input file ahead of running gawk. > 4 - Using another compiled version of gawk which does *not* disable the out-of-the-box gawk feature to swallow CRs (cf., e.g., ), i.e. > 3 - Wrapping a d2u/u2d pipe solution (additional app and wrapper needed again) > 2 - Calling 'gawk -vRS= -vORS= ' instead of 'gawk' (hack to turn back the additional the latest gawk's complexity, wrapper needed) > 1 - Inserting the BEGIN section as you suggested into more than 1k scripts (not feasible due to additional regression test workload) > Now I can see the following *easy* solutions to the very situation here (input only for now):

Subject: gawk 4.1.4: CR separate char for CRLF files

Inux (better: glibc) supports en_DK, but wha=įrom: (Vermessung AVT - Wolfgang Rieger)

Mkvtoolnix unicode 4.9.1 setup exe