YAM - Yet Another Mailer (#2) - HTML display (#42) - Message List

HTML display
 unsolved

The module that provides HTML display in YAM ignores newline characters in HTML files. So it merges the last word of a line of text (just in front of the newline character) and the first word of the following line of text. Instead each newline character (or carriage return + newline pair) should be substituted by a space.

Tree View Flat View (newer first) Flat View (older first)
  • Message #223

    The module that provides HTML display in YAM ignores newline characters in HTML files. So it merges the last word of a line of text (just in front of the newline character) and the first word of the following line of text. Instead each newline character (or carriage return + newline pair) should be substituted by a space.

    Sorry, but I feel that is not entirly correct. There is no definition on what a \n newline character should be interpreted in the HTML standard. AFAIR, a \n character should be ignored by a web browser/client interpreting HTML. And as such YAM should be perfectly correct in ignoring them more or less.

    OK. Let me review what a number of well-known browsers do when they read a HTML file with <newline> characters and no <carriage return> characters at the end of each line of text (remember: this is the Amiga standard for text files).

    • AWeb displays the file ignoring <newline> characters and substituting them with spaces.
    • IBrowse displays the file ignoring <newline> characters and substituting them with spaces.
    • Voyager displays the file ignoring <newline> characters and substituting them with spaces.
    • Firefox displays the file ignoring <newline> characters and substituting them with spaces.
    • MS-InternetExplorer displays the file ignoring <newline> characters and substituting them with spaces.

    YAM displays the file ignoring <newline> characters and doing nothing, thus merging words that were meant to be separated.

    I agree that you are perfectly entitled to let YAM display HTML files according to the HTML standard. Anyway, if the standard has a hole, it should be filled with a rational choice, not ignored!

    Firefox and MSIE cover the display experience of at least 90% of Internet users in the world. Hundreds of millions persons. The behaviour of these browsers sets a "de facto" standard, and their authors made a very clear choice.

    Regards.

  • Message #222

    The module that provides HTML display in YAM ignores newline characters in HTML files. So it merges the last word of a line of text (just in front of the newline character) and the first word of the following line of text. Instead each newline character (or carriage return + newline pair) should be substituted by a space.

    Sorry, but I feel that is not entirly correct. There is no definition on what a \n newline character should be interpreted in the HTML standard. AFAIR, a \n character should be ignored by a web browser/client interpreting HTML. And as such YAM should be perfectly correct in ignoring them more or less.

Tree View Flat View (newer first) Flat View (older first)

Attachments

No attachments created.