Randy Turner said:
> I thought this was what you meant. I just wanted to make it clear that
> client-localization requires defining a strict set of possible messages,
> with an associated token or code so that the client knows how to look up
> the localized version of this message in a localization dictionary (or
> catalog, or whatever). I wonder if absolutely restricting the set of
> messages that can be sent from server to client is too constraining?
For one existing example along these lines, look at the Adobe
Printer Description File specification. Part of the specification
for a printer model is a complete list of messages generated by the
printer, and the PDF can also provide translations for the messages.
So the set of messages can be "relatively" restricted, rather than
"absolutely." ;-)
:: David Kellerman Northlake Software 503-228-3383
::david_kellerman at nls.com Portland, Oregon fax 503-228-5662