Posted by Art on 08/30/07 19:54

On 8/30/07 2:20 PM, Harlan Messinger wrote:

> Art wrote:
>
>>
>> To clarify, the results for Firefox, Opera, Safari, and Seamonkey were
>> observed on a Mac. IE6 was observed under W2K. However, I mistakenly
>> transcribed the Seamonkey and Firefox results: Works on Seamonkey,
>> yields a single space on FF.
>>
>> On IE6, the CR is ignored, the LF is sufficient.
>>
>> Opera ignores the LF and maps the CR to a space.
>>
>> Actually, encoding a LF/CR combination on Safari results in TWO line feeds.
>>
>> I saw the same title behavior with both <acronym> and <span>.
>>
>> Your results on Linux re-enforces my original statement - this encoding
>> isn't universally recognized by all browsers for tool-tips.
>>
>> Thus, the LF/CR encoding with either <acronym> or <style> elements would
>> satisfy the OP request if the browser and platforms can be limited.
>
> AFAIK the LF + CR combination isn't the line separator on any operating
> system. The combination you should be testing is CR + LF.
My results with CR/LF are the same with the exception that on Safari
either a CR or CR/LF sequence does result in two lines of text where
LF/CR resulted in one line, a blank line and a the second line.

FWIW - The Mac uses CR as a line separator in text files. AFAIK,
Unix/Linux uses LF, Windoze uses the CR/LF combination.

[Back to original message]