InternationalDisplayString TC and unicode characters
Mark Ellison <ellison@world.std.com> Fri, 25 April 1997 14:11 UTC
Received: from cnri by ietf.org id aa20725; 25 Apr 97 10:11 EDT
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa10354; 25 Apr 97 10:11 EDT
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id JAA25006 for snmpv2-outgoing; Fri, 25 Apr 1997 09:56:21 -0400 (EDT)
Date: Fri, 25 Apr 1997 10:02:07 -0400
From: Mark Ellison <ellison@world.std.com>
Message-Id: <199704251402.AA15199@world.std.com>
To: winsnmp@mailbag.jf.intel.com, snmpv2@tis.com, ovforum@ovforum.org
Subject: InternationalDisplayString TC and unicode characters
Cc: p10143@psilink.com, stevew@ins.com, ellison@world.std.com
Sender: owner-snmpv2@ex.tis.com
Precedence: bulk
Has anyone any implementation experience with the InternationalDisplayString Textual Convention as defined in rfc1514? Do examples exist of the "local algorithm", as mentioned in rfc1514, to be used by network management stations to determine "which character set" is in use and "how it should be displayed"? How does unicode character (16 bit encoding) representation fit into the InternationalDisplayString paradigm? Would I be better off defining a new Unicode TC, or, would I be better off putting the Unicode characters into network byte order, and calling it an InternationalDisplayString? How will network management stations, like HP Openview handle the display of unicode strings? Regards, Mark Ellison Ellison Software Consulting, Inc. (603) 654-2703
- InternationalDisplayString TC and unicode charact… Mark Ellison