My name is Shelley Lau, a PM from the AppVirt team. This is the first blog entry from the engineering team in 2008, so I thought I would start with a new year greeting (in the languages which I know).
Happy New Year
新年快樂 / 新年快乐
I certainly don’t know as many languages that AppVirt 4.5 will support. Now, even without reading title, you could probably guess today’s topic is about Globalization/Localization. As the product team continues to enhance the products with new features and improvements, we finally have the opportunity to add globalization and localization supports, which are critical and will be available in the 4.5 release. Our product will better fulfill the needs of our customer base worldwide. It will help improve productivity by minimizing the language barriers and expand the deployment to reach out to non-English speaking locations in the enterprise. Speaking from my first-hand experience, I can say that this has a great appeal to and received positive response from customers and partners in the Asia (incl. Japan) and Europe market. For example, one of the customers I’ve been working closely with through the pilot program (TAP) in Germany has offices all over Europe and a few in Middle East. This customer has spearheaded the deployment of AppVirt English-only 4.5 public beta to a number of branches in Europe and tried out the globalization capability. As soon as AppVirt localized version is available, they will be in full swing to deploy AppVirt of different languages.
In the following, I’ll highlight what this feature is and supports and what’s not. Finally, I’ll provide a quick tip about deploying the beta version to Dutch OS.
So, you may ask, what does globalization/localization do or mean to 4.5? In fact, they are technically different.
For globalization, simply put, it’s to enable English version of AppVirt install and run properly on most of non-English OS (except for certain languages, see next section). It’s enabled by supporting UNICODE and making the product suitable for all International markets. AppVirt is language or locale neutral and should have full support for different languages and character scripts, sorting orders, time/date/address formats, various International keyboards and global Input Method Editors (IME), and other locale settings. This approach is called "single World-Wide binary". In the context of AppVirt 4.5, it supports the following:
· English or Non-English Servers can connect to Non-English Data Store regardless of language or locale setting. For example, the French AppVirt Servers on a French server machines should be able to connect to a Japanese Data Store on the JPN SQL server successfully.
· English or Non-English AppVirt Client can connect to English or Non-English AppVirt Server. The communication between the Client and the Server is standardized and independent to the language of the Server or the Client. A good example would be the mobile users scenario in which users travel with their laptops to other branch/regional offices. Regardless of the different languages of the Server running in the offices, AppVirt client should continue receive the same expected service.
· Sequencer can sequence applications of any supported language as long as the sequencing is done in proper system environment as per Sequencer requirements.
· AppVirt Server can configure and stream package sequenced by AppVirt Sequencer regardless of the language. This means that the package generated in the sequencing process can be published to any AppVirt Server regardless of its language. However, please note that neither the Sequencer nor the Server would enhance or alter the language support of the Application itself. (see next section)
· English AppVirt can interact correctly with Non-English backend infrastructure. This means that AppVirt will handle non-English usernames, passwords, file paths, URI, FQDN, machine names
· English or Non-English AppVirt Client can launch English or Non-English virtualized applications. AppVirt would not negatively interfere with the ability of English and non-English applications to run on the targeted client machines. For example, if and only if a locally installed German application can run on an English or Japanese OS, then it will also run if virtualized, regardless of the language of the Client.
· Server will properly handle retrieved configurations. Meaning that Publishing Refresh (fka DC Refresh) will publish the applications correctly using the language of the application. For example, if the application name is in Japanese, it will show up in Japanese on the user’s desktop of non-Japanese OS, assuming that the client’s OS can handle Japanese language (e.g. the font used by the OS supports Japanese).
· Sequencer will generate a package with the MUI enablement for MUI enabled applications. For example, when sequencing Office 2007, during monitoring, a proper language tool needs to be executed and the set of languages should be selected. This way if the language of the OS matches one of the languages selected for Office sequencing, Office will open up in the same language.
Once the product is globalized, we localize/translate it in additional languages. In 4.5, AppVirt is localized across 10 languages for the two servers and sequencer and 11 for the client components. Below is a list of languages we plan to support:
· Chinese – Simplified
· Chinese – Traditional
· (Brazilian) Portuguese
· Dutch (Client only)
For these supported languages, the text and non-text elements in the product are expected to display properly in the same languages as the OS locale setting. In addition to text in UI components, error messages will also be translated.
· AppVirt is not expected to make the application localized or culture-aware if it’s not already supported. It won’t make the application to work on a culture that the application does not originally support in the locally installation.
· Doesn’t support any complex scripts or BIDI OS or applications. Examples of these languages are Hindi, Arabic, and Hebrew
· If you want to deploy the Client of AppVirt 4.5 Beta on Dutch Vista (SP 1), you would set the system locale is to English or languages other than Dutch or Iberian Portuguese, and set the user locale to Dutch. This is due to an over-localization issue in Vista SP1 and a glitch in our beta code. Basically, Vista localized the system account name, “System”, to “Systeem” on Dutch and “Sistema” in Iberian Portugese which wasn’t meant to be localized.
PingBack from http://www.ditii.com/2008/01/16/globalizationlocalization-in-appvirt-45/
I saw this from Shelley Lau on the Application Virtualization Team blog and thought this is actually
Can App-V support Non english applications. What is the approach for non-English applications.
What are the limitations we foresee for japanese applications.