IFX Mail Archive: RE: IFX> Legal Requirements on Classic fax

RE: IFX> Legal Requirements on Classic fax

From: don@lexmark.com
Date: Tue Feb 20 2001 - 09:34:04 EST

  • Next message: pmoore@netreon.com: "RE: IFX> Legal Requirements on Classic fax"

    I am not sure that mandating all implementations have the font data necessary to
    print the thousands and thousands of glyphs accessible using UTF-8 encoding is
    practical.

    **********************************************
    * Don Wright don@lexmark.com *
    * Chair, Printer Working Group *
    * Chair, IEEE MSC *
    * *
    * Director, Strategic & Technical Alliances *
    * Lexmark International *
    * 740 New Circle Rd *
    * Lexington, Ky 40550 *
    * 859-232-4808 (phone) 859-232-6740 (fax) *
    **********************************************

    MAEDA toru <maeda.toru%canon.co.jp@interlock.lexmark.com> on 02/20/2001 04:57:53
    AM

    To: "Carl Kugler" <kugler%us.ibm.com@interlock.lexmark.com>
    cc: Dan Wing <dwing%cisco.com@interlock.lexmark.com>,
          jdahmen%atl.mediaone.net@interlock.lexmark.com, "'Wagner,William'"
          <wwagner%netsilicon.com@interlock.lexmark.com>,
          ifx%pwg.org@interlock.lexmark.com (bcc: Don Wright/Lex/Lexmark)
    Subject: RE: IFX> Legal Requirements on Classic fax

    Carl-san

    We can use a universal character encoding scheme like UTF-8.
    A terminal can send information by UTF-8,
    but the receiver could not print the information written in UTF-8
    since it needs font data to print.

    We can raise the bar that IPP FAX must print all UTF-8.

    Regards.

    Toru Maeda

    At 09:28 01/02/16 -0700, Carl Kugler wrote:

    >Wouldn't a universal character encoding scheme like UTF-8 solve the
    >character set problem?
    >
    > -Carl
    >
    >
    >
    >MAEDA toru <maeda.toru@canon.co.jp>@pwg.org on 02/16/2001 03:11:43 AM
    >
    >Sent by: owner-ifx@pwg.org
    >
    >
    >To: Dan Wing <dwing@cisco.com>
    >cc: jdahmen@atl.mediaone.net, "'Wagner,William'"
    > <wwagner@netsilicon.com>, ifx@pwg.org
    >Subject: RE: IFX> Legal Requirements on Classic fax
    >
    >
    >
    >Wing-san
    >
    >Thank you very much for the clarification.
    >
    >"And an ifax device would need
    >to understand all sorts of different character sets to interpret all
    >sorts of different headers."
    >
    >This idea is not practical, so the fax sends the image header
    >on top of the page and the coded Sender ID over T.30 protocol.
    >
    >
    >Regards,
    >
    >Toru Maeda
    >
    >At 08:21 01/02/14 -0800, Dan Wing wrote:
    > >On Wed, 14 Feb 2001 18:07 +0900, MAEDA toru wrote:
    > >
    > > > Wing-san
    > > >
    > > > I understand that all common mailers, including Eudora, Netscape, pine,
    > > > and many others, are capable of handling RFC2047-encoded headers.
    > > > But printing or imaging RFC2047-encoded headers are different
    >capability.
    > >
    > >Agreed.
    > >
    > > > I am not sure that you can print out my email signature in Japanese
    >below.
    > >
    > >Of course not; it doesn't identify itself as a MIME type in a different
    > >character set -- it is merely some ASCII embedded in a normal message.
    > >
    > >But you're right - even if it did, my mailer (pine) doesn't try to
    > >display it on the VT100 emulator I use. And an ifax device would need
    > >to understand all sorts of different character sets to interpret all
    > >sorts of different headers.
    > >
    > >The advantage of using computer-readable headers, of course, is allowing
    > >for sorting, searching, and other computer-assisted operations. That
    > >can only be done with image data using unreliable OCR.
    > >
    > >-d
    > >
    > > > -----------------------------------
    > > > $B%-%d%N%s3t<02q<R(B
    > > > $B1GA|;vL35!(BMIE$B?d?J%;%s%?!<(B
    > > > $B1GA|;vL35!(BMIE$BBh#23+H/It(B
    > > > $BA0ED!!E0(B
    > > > 146-8501$B!!El5~ETBgED6h2<4];R#3!]#3#0!]#2(B
    > > > $BEEOC!!(B03-3757-9738$B!"(BFAX$B!!(B03-3757-8205
    > > > -----------------------------------
    > > >
    > > > Toru Maeda
    > > >
    > > >
    > > > At 18:46 01/02/13 -0800, Dan Wing wrote:
    > > > >On Tue, 13 Feb 2001 19:29 +0900, MAEDA toru wrote:
    > > > >
    > > > > > Jim-san
    > > > > >
    > > > > > We designed that the IFAX header is similer as G3 header.
    > > > > > The IFAX header consists of date, time,mail address of transmitter
    >and
    > > > > page
    > > > > > number.
    > > > > > One of reason that fax header is send as image form is character
    >font
    > > > > > converting to image.
    > > > > > The receiver could not print the information form transmitter
    > > > > > when Japanese characters are send from the transmitter in the
    > > information.
    > > > >
    > > > >Hi.
    > > > >
    > > > >RFC2047-encoded headers can handle non-ASCII character sets, including
    > > > >Japanese. Almost all common mailers, including Eudora, Netscape,
    >pine,
    > > > >and many others, are capable of handling RFC2047-encoded headers when
    >both
    > > > >sending and receiving messages.
    > > > >
    > > > >-d
    > > > >
    > > > > > I know that the user may not understand the Japanese characters in
    >the
    > > > > > image header.
    > > > > >
    > > > > > Regards,
    > > > > >
    > > > > > Toru Maeda
    > > > > >
    > > > > >
    > > >
    > > > --------------------
    > > > MAEDA TORU
    > > > MIE Development Div. 2
    > > > CANON Inc.
    > > > --------------------
    > > >
    >
    >-----------------------------------
    >

    $B%-%d%N%s3t<02q<R(B
    >$B1GA|;vL35!(BMIE$B?d?J%;%s%?!<(B
    >$B1GA|;vL35!(BMIE$BBh#23+H/It(B
    >$BA0ED!!E0(B
    >146-8501$B!!El5~ETBgED6h2<4];R#3!]#3#0!]#2(B
    >$BEEOC!!(B03-3757-9738$B!"(BFAX$B!!(B03-3757-8205
    >-----------------------------------
    >
    >

    --------------------
    MAEDA TORU
    MIE Development Div. 2
    CANON Inc.
    --------------------



    This archive was generated by hypermail 2b29 : Tue Feb 20 2001 - 14:50:04 EST