On Thu, 25 Jun 2009, Peter Rosin wrote:
I'm not sure how their version will affect anything. Given the history, you can never be sure that this field will display correctly when using anything other than ASCII.This is exactly my point. You can't use anything but ASCII it you want it to display as intended. And this fact will remain for a looong time.
There's a distinction between "use by developers" and "use by end users". The fact is that in practice, non-ASCCI doesn't work today. That is, non-ASCII cannot be used by end users. This is a big problem which needs to be fixed as soon as possible. By introducing some new magic extension we are requiring that *every* single VNC implementation out there is modifed/updated, before users can use non-ASCII. *That* would take a "looong time".
If I have an RFB server somewhere that serves a variety of clients. 50% of the clients speak CP1252, 30% speak UTF-8 and 10% speak ISO 8859-1 and 9% speak ISO 8859-whatever. The last percent (probably less) speak something non-ASCII-compatible, but I don't care about those because that's just not compatible... If I really want to serve some "international" text in that scenario, what options do I have? Whatever I do, it will look like crap for many.
In this (fictional) example, ASCII is the only common subset. Thus, you must configure the server to only use ASCII desktop names. And as we have discussed before, this happens automatically with todays implementations: You can't get anything else with the Windows servers, and both the Xvnc and vncserver scripts setups ASCII only desktop names by default.
Without a poll or something like that we'll never know how many uses "strange" desktop names today, but my guess is that it's something like 1 out of 10000 or so. Speaking of "many" just doesn't feels right.
skåra -> skara is just way better than skåra -> skÃ¥ra IMHO.
I disagree. Replacing non-ASCII characters with ASCII ones may cause confusion or even security problems. If characters are to be replaced, it is critical that this is visible to the user. (If I remember correctly, this is pointed out in the Unicode book). A replacement character such as a box or something like that can used (this is what Microsoft Word does), but no such character is available in ASCII. But the UTF-8 way should work good enough, since sequences such as "Ã¥" are very rare in practice. This is a good property of UTF-8, and this is by design.
Rgds, ---
Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________ tigervnc-rfbproto mailing list tigervnc-rfbproto@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-rfbproto
