dodged In the history of computer science, an aspect of the acquisition is a consistent coding scheme.
There have been many attempts to standardize a character encoding scheme, but everyone has to about 20 years ago was a strong dark side had.
The invention of UTF-8 in 1992 by Ken Thompson is based on Unicode, the solution of the original problem of the universal coding was. It offered the opportunity possible to represent any character in the smallest space. It also preserves the compatibility with ASCII. Other solutions do not have full coverage or uses too much memory
UTF-8 1981-4 :. Most efficient and compatible
| Encoding | Year Adopted | Bytes / Char | Description |
|---|---|---|---|
| ASCII | 1964 | 1 | Early Standard. Made popular by PC |
| UCS-2 | 1993 | 2 | First Unicode encoding |
| UTF-16 | 1996 | 2.4 | UCS-2 model with more characters |
| UTF-32 | 1996 | 4 | Simple, but the amount of memory used |
Based on timing, adopted Windows -UCS- 2 first with Windows NT, 1993
This was 3.x. as an improvement over the conventional single-byte character sets from DOS and Windows Seen Unfortunately, she added, the complexity for Windows development and support of the dual model of Unicode and non-Unicode support. It led to the doubling of the classic Windows APIs. A version of the API is appended with 'W' (Wide / Unicode) and the other 'A' (ASCII). A brief explanation can be found here.
Citrix XenApp and XenDesktop are built on Windows models. Citrix also Linux VDA has its roots in the Windows-coding schemes. Overall, this is makes sense because it is the story of what has happened, and it made sense to share code between platforms.
has This philosophy for Linux VDA version 1.1 changed. Instead of trying to obtain the Microsoft-coding schemes, now everything is internally converted to UTF-8. First, this could have a lot of importance to the customer does not appear. However, this provides some immediate benefits and also some longer-term improvements.
Because UTF-8 is now the core coding in Linux VDA, it has to convert no more strings internally. This improves performance slightly and also reduces the risk of something in the translation to lose. It also reduces the footprint, how much space do the strings.
Another advantage is that it allows for a native encoding on Linux. News of administrators come, will now be displayed with full Unicode support allows. Although the message in UTF-16 arrives from the studio, the message in UTF-8 is converted and displayed GTK + is used.
Another reason for the use of UTF-8 is that it is now possible to support full Unicode text transmissions to the clipboard. Again, although the Clipboard UTF-16 receives text, it is automatically translated into UTF-8 for reasons of applications Linux. This is very important for Asian languages, which typically have large character sets.
A positive side effect is improved user handling. It is now possible to support user names containing non-ASCII characters. This has been attempted in the context of the 1.1 Linux tests VDA. The user in this case had signs above the BMP-range (> 64 K), which is rarely considered, but valid.
now use Apart from these changes, the logging and tracing components UTF-8. This allows the full character set use for log messages and trace output. There is still more work needed to locate the log messages to non-English languages, but at least it will be activated and will be UTF-8 content to display.
Internally it simplifies the code in many places. This will allow for more consistent handling of strings and fewer problems with the conversion.
As for the future, it provides better support each language a basis for Linux VDA. It also allows the possibility to have a server, which supports simultaneously with various users of different languages. The overall greatest potential is the complete integration with Linux text.
To read more of the Linux Virtual Desktop team to see here all our contributions.
0 Komentar