Re: issue when piping from a windows program
On Tue, 11 Apr 2023 09:15:03 +0200 Leonid Mironov wrote: > I am trying to feed the output of wmic.exe - a windows console program, to > cygwin bash script. > wmic.exe produces UTF16LE output with BOM and CR/LFs, so I am using dos2unix > to convert it. > The problem is that when I write wmic.exe output to a file and then use > dos2unix to convert this file > I get the expected result - ASCII file with LFs, I get the same result when I > pipe this file to dos2unix, > but when I pipe wmic.exe output directly to dos2unix I get ASCII file with > CR/LFs and an extra empty line. > Cygwin is up to date, windows 10. What gives? > > Here are the hexdumps > > of 'wmic /NAMESPACE:root\\WMI PATH BatteryStatus get > charging,voltage,remainingcapacity,chargerate>file' > > ff fe 43 00 68 00 61 00 72 00 67 00 65 00 52 00 |..C.h.a.r.g.e.R.| > 0010 61 00 74 00 65 00 20 00 20 00 43 00 68 00 61 00 |a.t.e. . .C.h.a.| > 0020 72 00 67 00 69 00 6e 00 67 00 20 00 20 00 52 00 |r.g.i.n.g. . .R.| > 0030 65 00 6d 00 61 00 69 00 6e 00 69 00 6e 00 67 00 |e.m.a.i.n.i.n.g.| > 0040 43 00 61 00 70 00 61 00 63 00 69 00 74 00 79 00 |C.a.p.a.c.i.t.y.| > 0050 20 00 20 00 56 00 6f 00 6c 00 74 00 61 00 67 00 | . .V.o.l.t.a.g.| > 0060 65 00 20 00 20 00 0d 00 0a 00 30 00 20 00 20 00 |e. . .0. . .| > 0070 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .| > 0080 20 00 46 00 41 00 4c 00 53 00 45 00 20 00 20 00 | .F.A.L.S.E. . .| > 0090 20 00 20 00 20 00 33 00 37 00 37 00 33 00 34 00 | . . .3.7.7.3.4.| > 00a0 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 | . . . . . . . .| > 00b0 20 00 20 00 20 00 20 00 20 00 20 00 31 00 32 00 | . . . . . .1.2.| > 00c0 37 00 34 00 30 00 20 00 20 00 20 00 20 00 0d 00 |7.4.0. . . . ...| > 00d0 0a 00 |..| > 00d2 > > of wimic>file followed by dos2unix > 43 68 61 72 67 65 52 61 74 65 20 20 43 68 61 72 |ChargeRate Char| > 0010 67 69 6e 67 20 20 52 65 6d 61 69 6e 69 6e 67 43 |ging RemainingC| > 0020 61 70 61 63 69 74 79 20 20 56 6f 6c 74 61 67 65 |apacity Voltage| > 0030 20 20 0a 30 20 20 20 20 20 20 20 20 20 20 20 46 | .0 > F| > 0040 41 4c 53 45 20 20 20 20 20 33 37 37 33 34 20 20 |ALSE 37734 > | > 0050 20 20 20 20 20 20 20 20 20 20 20 20 31 32 37 34 |1274| > 0060 30 20 20 20 20 0a |0.| > 0066 > > and of wimic|dos2unix > > 43 68 61 72 67 65 52 61 74 65 20 20 43 68 61 72 |ChargeRate Char| > 0010 67 69 6e 67 20 20 52 65 6d 61 69 6e 69 6e 67 43 |ging RemainingC| > 0020 61 70 61 63 69 74 79 20 20 56 6f 6c 74 61 67 65 |apacity Voltage| > 0030 20 20 0d 0a 30 20 20 20 20 20 20 20 20 20 20 20 | ..0 | > 0040 46 41 4c 53 45 20 20 20 20 20 33 37 37 33 34 20 |FALSE 37734 | > 0050 20 20 20 20 20 20 20 20 20 20 20 20 20 31 32 37 | 127| > 0060 34 30 20 20 20 20 0d 0a 0d 0a|40| > 006a This is not cygwin problem. Please try the following in command prompt without cygwin. wmic > wmic_redirect.txt wmic | more > wmic_pipe.txt Then, open both text file using binary editor. wmic_redirect.txt has \r\n in UTF16 encoding, however, you will find wmic_pipe.txt has abnormal line endings. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: issue when piping from a windows program
On 2023-04-11 08:43, Andrey Repin via Cygwin wrote: Greetings, Leonid Mironov! I am trying to feed the output of wmic.exe - a windows console program, to cygwin bash script. wmic.exe produces UTF16LE output with BOM and CR/LFs, so I am using dos2unix to convert it. The problem is that when I write wmic.exe output to a file and then use dos2unix to convert this file I get the expected result - ASCII file with LFs, I get the same result when I pipe this file to dos2unix, but when I pipe wmic.exe output directly to dos2unix I get ASCII file with CR/LFs and an extra empty line. Cygwin is up to date, windows 10. What gives? You don't need d2u. Use `… | iconv -f UTF16LE | tr -d '\r'` (Don't even need -t for iconv - it assumes current locale settings as default source/destination encoding.) d2u -ul converts from utf-16le to utf-8 When I run wmic under mintty or | less it looks fine to me e.g.: $ wmic baseboard list full | less # optional but the output could benefut from \r stripping: $ wmic baseboard list full | tr -d '\r' | cat -A | less https://learn.microsoft.com/en-us/windows/whats-new/deprecated-features#deprecated-features The WMIC tool is deprecated in Windows 10, version 21H1 and the 21H1 General Availability Channel release of Windows Server. This tool is superseded by Windows PowerShell for WMI. https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/07-working-with-wmi -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: issue when piping from a windows program
Greetings, Leonid Mironov! > I am trying to feed the output of wmic.exe - a windows console program, to > cygwin bash script. > wmic.exe produces UTF16LE output with BOM and CR/LFs, so I am using dos2unix > to convert it. > The problem is that when I write wmic.exe output to a file and then use > dos2unix to convert this file > I get the expected result - ASCII file with LFs, I get the same result when I > pipe this file to dos2unix, > but when I pipe wmic.exe output directly to dos2unix I get ASCII file with > CR/LFs and an extra empty line. > Cygwin is up to date, windows 10. What gives? You don't need d2u. Use `… | iconv -f UTF16LE | tr -d '\r'` (Don't even need -t for iconv - it assumes current locale settings as default source/destination encoding.) -- With best regards, Andrey Repin Tuesday, April 11, 2023 17:41:32 Sorry for my terrible english... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: issue when piping from a windows program
On 11.04.2023 09:15, Leonid Mironov via Cygwin wrote: I am trying to feed the output of wmic.exe - a windows console program, to cygwin bash script. wmic.exe produces UTF16LE output with BOM and CR/LFs, so I am using dos2unix to convert it. The problem is that when I write wmic.exe output to a file and then use dos2unix to convert this file I get the expected result - ASCII file with LFs, I get the same result when I pipe this file to dos2unix, but when I pipe wmic.exe output directly to dos2unix I get ASCII file with CR/LFs and an extra empty line. Cygwin is up to date, windows 10. What gives? Here are the hexdumps of 'wmic /NAMESPACE:root\\WMI PATH BatteryStatus get charging,voltage,remainingcapacity,chargerate>file' use "iconv" to change the codification and than d2u for the line termination $ iconv -f UTF16 -t UTF8 file ChargeRate Charging RemainingCapacity Voltage 0 FALSE 0 0 $ iconv -f UTF16 -t UTF8 file |od -c 000 C h a r g e R a t e C h a r 020 g i n g R e m a i n i n g C 040 a p a c i t y V o l t a g e 060 \r \n 0 100 F A L S E 0 120 0 140 \r \n 150 $ iconv -f UTF16 -t UTF8 file |d2u | od -c 000 C h a r g e R a t e C h a r 020 g i n g R e m a i n i n g C 040 a p a c i t y V o l t a g e 060 \n 0 F 100 A L S E 0 120 0 140 \n 146 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
