||Can user-defined characters
be transferred using XKP?
Usually, when sending
documents that include user-defined characters,
the only thing to reach the receiver is the
character codes, making it impossible to tell
what characters were used.
As one method for solving this problem, there is
the idea of sending user-defined character fonts
with the document. This method is suitable for
user-defined characters created by the sender,
but other user-defined character fonts are
covered by their respective copyrights, leading
to the problem that in many cases the use of such
fonts outside of the areas defined in the license
agreement is often limited.
For this reason, the sending of user-defined
character fonts cannot be said to be a 100%
Under the XKP standard, although a method for
sending font files is defined, a method for
transmitting the information required to know
what a character indicates is also provided.
By using this, it is possible to know what number
character of what particular character set
created by what organization is specified. In
addition, it provides a way of showing the place
to be contacted for obtaining the necessary
Furthermore, in order to increase
interoperability in data transmission, the
Windows NT Extended Kanji Processing Council is
looking at converting core modules to a single
binary, creating a common protocol for
user-defined character data exchange based on
TCP/IP, developing a wide-area server on the
Internet for exchange of user-defined characters,
and creating test software for confirming
compatibility with XKP-compliant software.