Getting errors stray ‘\342’ and ‘\200’ and ‘\214’ [duplicate] This is a Unicode character that is encoded in UTF-8 as three characters with values 0xE2, 0x80, and 0x8C (or in base 8, \342, \200, and \214) This probably happened because you copy and pasted some code from a document (HTML web page?) that uses those special characters
c++ - Error: stray ‘\342’ in my program, but I cant find the bad . . . The close reason is incorrect This is a duplicate, asked many times over ("Error: stray ‘\342’" makes it quite clear what the problem is (is entirely reproducible and is not caused by a typo)) The canonical is Compilation error: stray ‘\302’ in program, etc –
compiler errors - Stray \342 in C++ program - Stack Overflow A much more direct analysis is 342 200 235 (octal) → 0xE2 0x80 0x9D (hexadecimal) → UTF-8 sequence for Unicode code point U+201D (RIGHT DOUBLE QUOTATION MARK) Most text editors (e g Geany (Linux and Windows) and Notepad++) with a regular expression mode will be able to do search replace for Unicode code point U+201D, using \x{201D}
“error: stray \342 ”, “stray \200 ”, “stray \213 ” in C compiling \342 \200 \213 is octal for 0xE2 0x80 0x8B which is a zero width space in UTF-8 (Unicode U+200B), something no C compiler can make sense of (and something you can't see, zero-width after all, when UTF-8 is displayed correctly)
. ssh config: line 1: Bad configuration option: \342\200\234host 342 (octal) is a signature start of a UTF-8 byte sequence 342 200 234 (octal) is the UTF-8 sequence for LEFT DOUBLE QUOTATION MARK (U+201C) It can be searched for in a modern text editor with \x{201C} in regular expression mode –
c - Getting error: stray \342 when compiling - Stack Overflow The stray ‘\342’ errors are not related to the errror I pointed out in the comment above They are most likely due to the fact that you edited your code with an inappropriate editor They are most likely due to the fact that you edited your code with an inappropriate editor
Error message error:0308010C:digital envelope routines::unsupported Downgrading to 16 13 0 is not enough, and it still won't let you use --openssl-legacy-provider To use this parameter, you must be on v17 and up, and the parameter must be placed inside your package json, it won't allow you to just place it in the NODE_OPTIONS env var for security reasons