Skip to content

Font Server Naming

Font clients that expose font server names to the user are encouraged to provide ways of naming font servers symbolically (e.g. DEPARTMENT-FONTS). However, for environments that lack appropriate name services transport-specific names are necessary. Since these names do occur in the protocol, clients and servers should support at least the applicable formats described below. Formats for additional transports may be registered with the X Consortium.

TCP/IP Names

The following syntax should be used for TCP/IP names:

    <TCP name>  ::=  "tcp/" <hostname>":" <ipportnumber> ["/" <cataloguelist>]

where <hostname> is either symbolic (such as expo.lcs.mit.edu) or numeric decimal (such as 18.30.0.212). The <ipportnumber> is the port on which the font server is listening for connections. The <cataloguelist> string at the end is optional and specifies a plus-separated list of catalogues that may be requested. For example:

     tcp/expo.lcs.mit.edu:8012/available+special
     tcp/18.30.0.212:7890

DECnet Names

The following syntax should be used for DECnet names:

    <DECnet name>  ::=  "decnet/" <nodename> "::font$" <objname>
               ["/" <cataloguelist>]
    <DECnet name>  ::=  "decnet/" <nodename> "::font$" <objname>
               ["/" <cataloguelist>]

where <nodename> is either symbolic (such as SRVNOD) or the numeric decimal form of the DECnet address (such as 44.70). The <objname> is normal, case-insensitive DECnet object name. The <cataloguelist> string at the end is optional and specifies a plus-separated list of catalogues that may be requested. For example:

     DECNET/SRVNOD::FONT$DEFAULT/AVAILABLE
     decnet/44.70::font$other