view release on metacpan or  search on metacpan

NPAdmin/MIBs/Printer-MIB.txt  view on Meta::CPAN

         repertoires that may occur.  The third region (>1999) is
         intended for vendor specific coded character sets.

         NOTE: Unicode and ISO 10646 character coded data may be
         processed and stored in either Big Endian (most
         significant octet first) or Little Endian (least
         significant octet first) order.  Intel x86, VAX, and
         Alpha/AXP architectures are examples of Little Endian
         processor architectures. Furthermore, in environments
         where either order may occur, so-called Unicode BYTE
         ORDER MARK (BOM) character (which is ISO 10646 ZERO
         WIDTH NO BREAK SPACE), coded as FEFF in two octets and
         0000FEFF in four octets is used at the beginning of the
         data as a signature to indicate the order of the
         following data (See ISO 10646 Annex F).  Thus either
         ordering and BOM may occur in print data streams sent to
         the interpreter.  However, ISO 8824/8825 (ASN.1/BER)
         used by SNMP is quite clear that Big Endian order shall
         be used and BOM shall NOT be used in transmission in the
         protocol. Transmitting Unicode in Big Endian order in
         SNMP should not prove to be a hardship for Little Endian
         machines, since SNMP ASN.1/BER requires integers to be
         transmitted in Big Endian order as well.  So SNMP
         implementations on Little Endian machines are already
         reversing the order of integers to make them Big Endian
         for transmission via SNMP.  Also Unicode characters are
         usually treated as two-octet integers, not short text
         strings, so that it will be straightforward for Little
         Endian machines to reverse the order of Unicode