Multilanguage support in K2.net 2003:

K2.net Studio: The menu and control structures in will always be English regardless of the language settings of your environment. For Activities, Events and lines all the names can be done in any language also support double byte characters. This is handy for things like the View Flow component in reports and normal reports.

K2.net Service Manager: This component will always be in English regardless of the environment settings. However all process related information e.g. Process, Activity, Event names and Data / Xml Fields names/values will be in the language that you have used during development and runtime values stored in the fields.

K2.net Workspace/Worklist: This component will always be in English regardless of the environment settings. However all process related information e.g. Process, Activity, Event names and Data / XML Fields names/values will be in the language that you have used during development and runtime values stored in the fields.

K2.net Runtime: Any language can be used as input for data/XML fields.

UI Development: This can be 100% localized based on Multilanguage support available in VS .NET

---

Some more on this one!

Unfortunately K2.net 2003 wasn t designed to support localization at the outset. Although the underlying data- and infrastructure architecture does support multiple languages through support for extended character sets, the supporting component user interfaces do not. These components are not resource file driven and standard interfaces cannot be easily or dynamically changed according to user locales.

What this means is that although you can t customize the interface of the MMC plug-in or Workspace for instance, you can design processes with Activity- and Event names in your required language and store data entered in that language. We currently support customers in locations such as China, Israel and the Middle East in this manner. These customers typically implement a customized workspace built around our published APIs supported by SmartForms, InfoPath- or web forms in the appropriate language.

We are however acutely aware of the requirement for localization support in every aspect of the product. It is very important for us to be able to not only support customers in various locations, but also customers that need to deploy solutions that span different locales. To this end we are incorporating localization as a guiding principle in the design of the next major release of the product.

If you have any specific questions around the current product and localization please feel free to ask.

---

Hi,

I need all interfaces to displayed in arabic (menue...etc)

any updates since sep 2005?

thank you

---