Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!home.csc.ti.COM!Oren From: Oren@home.csc.ti.COM (LaMott Oren) Newsgroups: comp.windows.x Subject: TEXTITEM16 frustration Message-ID: <2773848788-983808@SI> Date: Wed, 25-Nov-87 12:33:08 EST Article-I.D.: SI.2773848788-983808 Posted: Wed Nov 25 12:33:08 1987 Date-Received: Sun, 29-Nov-87 09:11:33 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 10 While playing around with PolyText16 requests in CLX, I discovered that somewhere along the way the protocol was changed so font changes generate an odd number of bytes (5 instead of 6). Thus a strings16 after a font change is no-longer on a 16bit boundary. Why was this change made? Some feeble attempt at compatibility with PolyText8? Is it too late to fix it? While I'm asking, why was the decision made that the CLIENT do byte swapping for 16 bit text requests? Why are the formats of the ImageText requests different from PolyText? Everything else in the protocol seems (to me) to be very well thought out, so I figure there must be reasons for these text inconsistencies.