{"id":55306,"date":"2022-04-04T03:01:04","date_gmt":"2022-04-03T17:01:04","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=55306"},"modified":"2022-04-11T19:39:02","modified_gmt":"2022-04-11T09:39:02","slug":"html-carriage-return-and-or-line-feed-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/html-carriage-return-and-or-line-feed-primer-tutorial\/","title":{"rendered":"HTML Carriage Return and or Line Feed Primer Tutorial"},"content":{"rendered":"
\"HTML<\/a>

HTML Carriage Return and or Line Feed Primer Tutorial<\/p><\/div>\n

Some vertical record delimiting wonderment in HTML we just let pass through to the keeper, except to say that HTML rendering just about always works as intended, and yet back in the day<\/i> you’d need to worry about whether your desktop C program, for instance, was written using (an underlying) Windows or Linux or Mac OS X (operating system). And then we stumbled upon javascript – Why carriage return not rendered as a line break when assigned to textContent although formatted using pre? – Stack Overflow<\/a>‘s …<\/p>\n

\nHTML when it normalizes newlines will convert all \\r\\n sequences to \\n and then all remaining \\r to \\n, so effectively getting rid of all lonely \\r characters. However, Node.textContent doesn’t call this normalize-newlines algorithm, so they’re not converted to \\n and not interpreted as segment-break.\n<\/p><\/blockquote>\n

… which seemed to explain the process of vertical record delimiting HTML rendering rules<\/i> so well. This resulted in us trying to prove this, and caused us to write a proof of concept cr_andor_lf.php<\/a> web application<\/a> that you can also try for yourself below …<\/p>\n