Ray,
The PServer and RPrinter Channel entries in the Printer MIBv2 give some
character set information for some of the fields you asked about as follows:
                  chNetwareRPrinter(9),
                      -- Novell, Inc.
                      -- For each entry of this type, the
                      -- prtChannelInformation must have a pair of
                      -- keywords. For Netware 3.x channels this must
                      -- be a (PServer, Printer) pair. For Netware 4.x
                      -- channels and for IntranetWare channels this
                      -- must be a (NDSTree, NDSPrinter) pair.
                      --
                      -- prtChannelInformation entries:
                      -- Print Server Name
                      --   Keyword:      PServer
                      --   Syntax:       Name
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The Pserver's SAP name
                      --
                      -- Printer Number
                      --   Keyword:      Printer
                      --   Syntax:       Integer
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The printer number
                      --
                      -- NDSTree
                      --   Keyword:      NDSTree
                      --   Syntax:       Name
                      --   Multiplicity: Single
                      --   Description:  The tree's SAP name
                      --
                      -- NDS Printer object
                      --   Keyword:      NDSPrinter
                      --   Syntax:       Text (Unicode)
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The fully qualified
                      --                 name of the Printer
                      --
                      -- In the Netware 3.x environment, the
                      -- client checks the Bindery object
                      -- representing the named PServer. The
                      -- client then checks for queues which
                      -- are associated with the numbered
                      -- printer. In the 4.x and IntraNetware
                      -- environment, the client looks up the
                      -- queues which are associated with the
                      -- NDS Printer Object in the named Tree.
                      -- Depending on client access rights to
                      -- those queues, the client submits jobs
                      -- to the appropriate queue.
                  chNetwarePServer(10),
                      -- Novell,Inc.
Lewis, Gocek, Turner   Expires 9 February 2001              [Page 31]
 
INTERNET DRAFT              Printer MIB V2               9 August 2000
                      -- For each entry of this type, the
                      -- prtChannelInformation must have a pair
                      -- of keywords. For Netware 3.x channels
                      -- this must be a (Server, PServer) pair.
                      -- For Netware 4.x and IntranetWare
                      -- channels, this must be a
                      -- (NDSTree, NDSPServer) pair.
                      --
                      -- prtChannelInformation entries:
                      --
                      -- Server Name
                      --   Keyword:      Server
                      --   Syntax:       Name
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The SAP name of the
                      --       server for which the PServer is defined.
                      --
                      -- PServer
                      --   Keyword:      PServer
                      --   Syntax:       Name
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The bindery name of
                      --                 the PServer
                      --
                      -- NDS Tree
                      --   Keyword:      NDSTree
                      --   Syntax:       Name
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The NDS Tree name
                      --
                      -- PServer
                      --   Keyword:      NDSPServer
                      --   Syntax:       Text (Unicode)
                      --   Status:       Mandatory
                      --   Multiplicity: Single
                      --   Description:  The fully qualified
                      --     name of the PServer object in the tree.
                      --
                      -- In the 3.x environment, the client
                      -- checks the bindery object
                      -- representing the named PServer on the
                      -- named Server. In the 4.x and
                      -- IntranetWare environment,
                      -- the client checks the NDS object
                      -- representing the named PServer in the
                      -- named Tree. In either case, the
                      -- client then checks for all queues
                      -- associated with the Pserver object.
                      -- Depending on client access rights
                      -- to those queues, the client submits
                      -- jobs to the appropriate queue.
Lewis, Gocek, Turner   Expires 9 February 2001              [Page 32]
 
INTERNET DRAFT              Printer MIB V2               9 August 2000
Tom
-----Original Message-----
From: Ray Casterline [mailto:RayCasterline@lhsolutions.com]
Sent: Monday, April 09, 2001 14:31
To: pwg@pwg.org
Subject: PWG> Question about Localization
Hello,
        I had some questions with regards to localization
        specifically for PServer, RPrinter and LPD.
        The questions are as follows:
                Character set/encoding supported?
                Character set identification?
                Character set negotiation?
                Character Transformation encoding?
        Specifically in regards to:
                Path name,
                User name,
                Domain name,
                Host name,
                Queue name,
                Printer name,
                Print server name,
                Repository name
        Does anyone know of any RFC's or other documents that
        I can get access to that would help me resolve these
        questions?
        Thanks in advance for any and all help.
Best Regards,
Ray Casterline
Principle				Lighthouse Solutions, LLC
716.218.9910 - voice			2604 Elmwood Ave., #346
716.218.9913 - fax			Rochester, NY   14618
This archive was generated by hypermail 2b29 : Mon Apr 16 2001 - 15:11:45 EDT