Context: In terms of the newline, Unicode introduced U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR. This was an attempt to provide a Unicode solution to encoding paragraphs and lines semantically, potentially replacing all of the various platform solutions. In doing so, Unicode does provide a way around the historical platform dependent solutions. Nonetheless, few if any Unicode solutions have adopted these Unicode line and paragraph separators as the sole canonical line ending characters. However, a common approach to solving this issue is through newline normalization. This is achieved with the Cocoa text system in Mac OS X and also with W3C XML and HTML recommendations. In this approach every possible newline character is converted internally to a common newline (which one does not really matter since it is an internal operation just for rendering). In other words, the text system can correctly treat the character as a newline, regardless of the input's actual encoding.

Question: What is the code for separating lines? 
Answer: U+2028

Question: What is the code for separating paragraphs? 
Answer: U+2029

Question: How is newline normalization accomplished in Mac OS X? 
Answer: Cocoa text system

Question: How does the newliine normallization format work? 
Answer: every possible newline character is converted internally to a common newline

Question: What widely adopted solution did Unicode provide?
Answer: Unanswerable

Question: What uses HTML recommendations?
Answer: Unanswerable

Question: Why does it matter which newline character is chosen?
Answer: Unanswerable

Question: What is the name of the Cocoa text system?
Answer: Unanswerable

Question: What are common newlines converted into?
Answer: Unanswerable