Re: Problem with SSI and BOM

From: Frank Ellermann (
Date: Sat Sep 23 2006 - 15:51:09 CDT

  • Next message: "Re: Unicode 5.0 success"

    Jukka K. Korpela wrote:

    > Lynx 2.8.5 shows it as the inverted question mark character
    > (don't ask me why - the browser can handle UTF-8 in general,

    Lynx 2.8.5dev16 apparently gets this right, keeping the NCRs
    for a BOM as is, showing nothing for UTF-8 proper.

    > when interpreted as UTF-8. The first one, , in the first
    > paragraph is correct

    As Latin-1 or windows-1252, it's quite different for cp 858 ;-)

    > Using the nonbreaking hyphen character is not a realistic
    > option, because it creates problems far too often, due to its
    > absence in most fonts.

    At least it works as expected in the ASCII output of xml2rfc.


    This archive was generated by hypermail 2.1.5 : Sat Sep 23 2006 - 20:25:08 CDT