Seeing the responses and then reading what I sent out two
months ago, I realize that in the interests of terseness
I was very unclear about the impact of my proposal. So
a few corrections.
While the SYNTAX clause of the OBJECT-TYPE macro for
most strings would change to use one of the three
new string-type textual conventions, the actual syntax
of the objects would remain the same (they are now
OCTET STRING and they would remain OCTET STRING with
the same SIZE clauses).
Only ONE new object was proposed:
prtGeneralStaticLocalization
And the DESCRIPTION of this object should probably
state that it is "updated (infrequently) by system
administrators when they install, upgrade, or move
to another network location the managed device."
(This is in response to David Perkins criticisms
that Chris posted.)
At the 22 April PMP telecon, Randy mentioned that some
strings are not suitable for re-localization. He is of
course right - the mnemonics line 'US', 'EN', from ISO
or IANA stds, the 'prtInputMediaName' (which needs to
be a well-known set of strings, to be useful), the
new 'prtChannelInformation' object (although NOT
localizing it still gives a problem for a server name
in a non-English environment or worse a non-8-bit
environment).
So, how about FOUR textual conventions:
PrtCurrentLocaleString
PrtConsoleLocaleString
PrtStaticLocaleString
PrtEnglishASCIILocaleString
Cheers,
- Ira McDonald (outside consultant at Xerox
High North Inc
PO Box 221
Grand Marais, MI 49839
906-494-2434