Re: Problem with SSI and BOM

From: Frank da Cruz (
Date: Wed Sep 27 2006 - 12:44:44 CST

  • Next message: Philippe Verdy: "Re: Problem with SSI and BOM"

    > My solution: I edit my HTML sources on my PC, transfer them to
    > the Unix server, and there I remove the coding signature (using
    > the vi program). This works, though not very elegantly. Of
    > course, the file transfer program should handle the coding
    > signature (the same way it handles the different line feeds),
    > but as long as I can't have that, I will work around this
    > problem, at the point of its origin -- and nowhere else.
    By the way, Kermit: (The Kermit Project) (Kermit for Windows) (Kermit for Unix, etc)

    when used as a file transfer agent, can do this. It converts from
    various "legacy" character sets to UTF-8 (or vice-versa), and will
    add a BOM if desired, or remove one if undesired. If the file to
    be uploaded already is UTF-8, the same choices apply:

    The pertinent command is SET FILE UCS BOM { ON, OFF }.

    A few advances in this area were made in the next Kermit release,
    8.0, most notably the character-set aware FTP client:

    and automatic character-set detection for local files when

    Kermit can be used to transfer files over serial-port connections,
    modem connections, Telnet/RSH/SSH connections (both clear-text and
    secure), and FTP connections (ditto), and can also convert the
    encoding of local files.

    I'm not sure that the FTP client does anything with the BOM, but
    if not this can easily be added since the code is already there
    for Kermit protocol. If anybody is intrerested in trying this,
    let me know; if any adjustments are necessary I'll make them.
    The latest version (whose most notable new feature is support
    for "large files") is here:

    - Frank

    This archive was generated by hypermail 2.1.5 : Wed Sep 27 2006 - 12:46:26 CST