Den 2009-09-01 11:08 skrev Pierre Ossman: > There are still a couple of string issues remaining: > > - SecurityResult doesn't mention encoding for reason-string. It should > probably be ASCII though, which is what is specified for > reason-string in Security.
Generate ASCII, hope for UTF-8 if you receive something else. That's the best you can do from a compatibility point of view. > - Tight's capability handshake uses something that looks like strings, > but should be handled like opaque, 8 byte blobs (or so I'm > assuming). Perhaps this should be clarified? I assume the same re blobs, but I'm just adding that they are probably traced with various log options so it would be good if the encoding could be known (e.g if Const could state that all future capabilities will also be ASCII). That said, I think it's fairly safe to assume ASCII, there is little reason to use anything else... > - The GII stuff doesn't mention anything about encodings for its > strings. If it's undefined then we should refer to the new encoding > chapter. This is of course originally my fault, referring to the new UTF-8 chapter would be the best option. Cheers, Peter ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
