Hi Bob,
Thanks for commenting. To reply:
1) ONE new object 'prtGeneralStaticLocalization'
- the object 'prtGeneralConsoleLocalization' is vintage
Printer MIB v1 (1995 text) - nothing new
2) As Randy observed during the 22 April PMP telecon, because
the SYNTAX of the three new textual conventions is
'OCTET STRING' (without even a length qualification),
the effect is clarity, with NO change of object type
The textual conventions simply make explicit the information
which is currently buried in DESCRIPTION clauses (ie, which
'prtGeneral...Localization' object controls their locale).
Lastly, and MOST important (my whole proposal aside), is that
the Printer MIB (including Randy's draft of 5 June for the I-D)
forbids the use of ANY character set except ASCII for ALL of
the strings not under 'prtGeneralCurrentLocalization' (7)
or 'prtGeneralConsoleLocalization' (2) - this is roughly 25
other string objects including ALL of the 'xxxName' objects.
This is a serious problem in markets other than Europe or
North America.
Cheers,
- Ira McDonald (outside consultant at Xerox)
High North Inc
PO Box 221
Grand Marais, MI 49839
906-494-2434
>------------------ Bob's note -------------------------<
Return-Path: <pmp-owner at pwg.org>
Received: from zombi.eso.mc.xerox.com by snorkel.eso.mc.xerox.com (4.1/XeroxClient-1.1)
id AA27217; Tue, 10 Jun 97 18:19:00 EDT
Received: from alpha.xerox.com by zombi.eso.mc.xerox.com (4.1/SMI-4.1)
id AA15450; Tue, 10 Jun 97 18:15:59 EDT
Received: from lists.underscore.com ([199.125.85.30]) by alpha.xerox.com with SMTP id <18793(3)>; Tue, 10 Jun 1997 15:16:16 PDT
Received: from localhost (daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id SAA03325 for <imcdonal at eso.mc.xerox.com>; Tue, 10 Jun 1997 18:12:21 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Tue, 10 Jun 1997 18:11:12 -0400
Received: (from daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) id SAA03211 for pmp-outgoing; Tue, 10 Jun 1997 18:10:29 -0400 (EDT)
Message-Id: <01BC75B8.BF7242E0 at hpb15510.boi.hp.com>
From: Bob Pentecost <bpenteco at boi.hp.com>
To: "pmp at pwg.org" <pmp at pwg.org>
Subject: RE: PMP> Localization changes to Printer MIB
Date: Tue, 10 Jun 1997 15:08:54 PDT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Sender: pmp-owner at pwg.org
Status: R
First a question, then some comments.
Will the two new objects, prtGeneralConsoleLocalization and =
prtGeneralStaticLocalization, be mandatory or optional?
My main concern is the magnitude of the changes that we are inducing at =
this late stage. I recalled this topic being discussed in a phone =
conference so I found the following in the minutes (conf-call-970422):
-----------
4. Should the phone:, fax: and email: tags be used in non 8-bit =
environments? non-English environments?
Ira discussed his proposal for three Textual Conventions for grouping =
all currently defined strings. Randy also discussed his proposal that =
the current localization should apply to all read/write strings that are =
intended to be human readable and are not explicitly controlled by =
prtConsoleLocalization. =20
After much group discussion, it was agreed that Randy will review Ira's =
proposal and send a recommendation to the mailing list. The goal is to =
allow the strings to be localized with a minimal impact to the document.
-----------
I don't think the goal of "minimal impact to the document" has been =
reached. We are looking at:
-- Adding two new objects.
-- Adding three new textual conventions.
-- Changing the syntax of 33 objects.
I don't believe a change of this magnitude should go into the document =
just before we submit it. Remember Lloyd's guidelines that said we are =
looking for editorial changes only at this point in time.
Bob Pentecost
HP
----------
From: lpyoung at lexmark.com[SMTP:lpyoung at lexmark.com]
Sent: Friday, June 06, 1997 7:53 AM
To: pmp at pwg.org
Subject: PMP> Localization changes to Printer MIB
Ira McDonald on 4/16/97 raised on issue that the localization
specified in the Printer MIB is not adequate for the Japan/Asia/
Far East markets. Ira has developed the following proposal and
Chris and I think we should include it in the Printer MIB.
Any discussion?
--------------------------------------------------
Add three new textual conventions:
----------------------------------
PrtCurrentLocaleDisplayString ::=3D TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type for human-readable (NOT binary) string objects:
a) whose dynamic locale (language, country, code set) shall be
indicated by the value of 'prtGeneralCurrentLocalization';
b) whose value (when updated by an SNMP Set-Request) shall be
interpreted in this locale by the management agent;
c) whose value (when returned by an SNMP Get-Response) shall =
be
interpreted in this locale by the management station."
REFERENCE
"See: 'prtGeneralCurrentLocalization' in the General group
of this Printer MIB."
SYNTAX OCTET STRING
PrtConsoleLocaleDisplayString ::=3D TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type for human-readable (NOT binary) string objects:
a) whose dynamic locale (language, country, code set) shall be
indicated by the value of 'prtGeneralConsoleLocalization';
b) whose value (when updated by an SNMP Set-Request) shall be
interpreted in this locale by the management agent;
c) whose value (when returned by an SNMP Get-Response) shall =
be
interpreted in this locale by the management station."
REFERENCE
"See: 'prtGeneralConsoleLocalization' in the General group
of this Printer MIB."
SYNTAX OCTET STRING
PrtStaticLocaleDisplayString ::=3D TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type for human-readable (NOT binary) string objects:
a) whose static locale (language, country, code set) shall be
indicated by the value of 'prtGeneralStaticLocalization';
b) whose value (when updated by an SNMP Set-Request) shall be
interpreted in this locale by the management agent;
c) whose value (when returned by an SNMP Get-Response) shall =
be
interpreted in this locale by the management station."
REFERENCE
"See: 'prtGeneralStaticLocalization' in the General group
of this Printer MIB."
SYNTAX OCTET STRING
Update/Add to General group:
----------------------------
prtGeneralCurrentLocalization OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write -- write many, read many
MIN-ACCESS read-only -- move to Conformance section
STATUS current
DESCIRPTION
"The value of 'prtLocalizationIndex' corresponding to the
language, country, and character set to be used when
interpreting dynamically localized 'human-readable' string
objects of type 'PrtCurrentLocaleDisplayString'. This object
shall not apply to strings of 'PrtConsoleLocaleDisplayString'
or 'PrtStaticLocaleDisplayString' type.
Usage: This object may be updated (repeatedly) during normal
operation of this network printer or network print server."
REFERENCE
"See: 'prtGeneralConsoleLocalization' (console strings) and
'prtGeneralStaticLocalization' (static strings)
objects in the General group of this Printer MIB."
::=3D { prtGeneralEntry 2 }
prtGeneralConsoleLocalization OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write -- write many, read many
MIN-ACCESS read-only -- move to Conformance section
STATUS current
DESCIRPTION
"The value of 'prtLocalizationIndex' corresponding to the
language, country, and character set to be used when
interpreting console localized 'human-readable' string
objects of type 'PrtConsoleLocaleDisplayString'. This object
shall not apply to strings of 'PrtCurrentLocaleDisplayString'
or 'PrtStaticLocaleDisplayString' type.
Usage: This object may be updated (repeatedly) during normal
operation of this network printer or network print server."
REFERENCE
"See: 'prtGeneralCurrentLocalization' (dynamic strings) and
'prtGeneralStaticLocalization' (static strings)
objects in the General group of this Printer MIB."
::=3D { prtGeneralEntry 10 }
prtGeneralStaticLocalization OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write -- write once, read many
MIN-ACCESS read-only -- move to Conformance section
STATUS current
DESCIRPTION
"The value of 'prtLocalizationIndex' corresponding to the
language, country, and character set to be used when
interpreting statically localized 'human-readable' string
objects of type 'PrtStaticLocaleDisplayString'. This object
shall not apply to strings of 'PrtCurrentLocaleDisplayString'
or 'PrtStaticLocaleDisplayString' type.
Usage: This object may be updated (at most) once at 'device
install' time for this network printer or network print =
server."
REFERENCE
"See: 'prtGeneralCurrentLocalization' (dynamic strings) and
'prtGeneralConsoleLocalization' (console strings)
objects in the General group of this Printer MIB."
::=3D { prtGeneralEntry 20 }
Change the SYNTAX of these objects to 'PrtCurrentLocaleDisplayString':
----------------------------------------------------------------------
prtCoverDescription
prtInputDescription
prtOutputDescription
prtMarkerSuppliesDescription
prtMediaPathDescription
prtInterpreterDescription
prtAlertDescription
Change the SYNTAX of these objects to 'PrtConsoleLocaleDisplayString':
----------------------------------------------------------------------
prtConsoleDisplayBufferText
prtConsoleDescription
Change the SYNTAX of these objects to 'PrtStaticLocaleDisplayString':
---------------------------------------------------------------------
prtGeneralCurrentOperator
prtGeneralServicePerson
prtGeneralAdminName
prtGeneralSerialNumber
prtLocalizationLanguage
prtLocalizationCountry
prtInputMediaName
prtInputName
prtInputVendorName
prtInputModel
prtInputVersion
prtInputSerialNumber
prtInputMediaType
prtInputMediaColor
prtOutputName
prtOutputVendorName
prtOutputModel
prtOutputVersion
prtOutputSerialNumber
prtMarkerColorantValue
prtChannelProtocolVersion
prtInterpreterLangLevel
prtInterpreterLangVersion
prtInterpreterVersion
Lloyd Young Lexmark International, Inc.
Senior Program Manager Dept. C14L/Bldg. 035-3
Strategic Alliances 740 New Circle Road NW
internet: lpyoung at lexmark.com Lexington, KY 40550
Phone: (606) 232-5150 Fax: (606) 232-6740