<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Localization of AR applications in BMC Remedy ARSystem</title>
	<atom:link href="http://remediesforremedy.com/2009/07/localization-of-ar-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://remediesforremedy.com/2009/07/localization-of-ar-applications/</link>
	<description>Its all about Remedy</description>
	<lastBuildDate>Sat, 05 May 2012 15:45:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Venkat</title>
		<link>http://remediesforremedy.com/2009/07/localization-of-ar-applications/comment-page-1/#comment-5303</link>
		<dc:creator>Venkat</dc:creator>
		<pubDate>Thu, 20 Oct 2011 14:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=29#comment-5303</guid>
		<description>Hi Kristin,

The localization that was done is not complete solution but a partial one which only uses the values of menus and filed values that we have provided the system with. We havent seen any performance issues but seen issues with data reporting for global management.

1. Pros of the implementation was that we were able to show the form view in the local language which helped end users and fill most of the form in the local language. The main disadvantage is that we dont have any complete translation tool set in place but only partial.

2. We havent faced any issues with user tool as the view of the form is based on the language used on the system. More over in web version is better to use than user tool for this as it increases the performance of the overall system.

3.Yes, the Data language is the main language of the ar database that it primarily configured for, we had English for this.

4. Since there are several special characters in each language some the these are not compatible with each other. For example, both AR server and database can be either French or German, when the Display language used on the user tool or web is French or German. But, when you have French database, Japanese language cant be used on the user tool.

With 7.6 I believe there is localization kit provided for easy updates of form views, havent used it but should be helpful. Its always better to use English as database and server language as its supports almost all display languages. 

Cheers,
Venkat Maddala.</description>
		<content:encoded><![CDATA[<p>Hi Kristin,</p>
<p>The localization that was done is not complete solution but a partial one which only uses the values of menus and filed values that we have provided the system with. We havent seen any performance issues but seen issues with data reporting for global management.</p>
<p>1. Pros of the implementation was that we were able to show the form view in the local language which helped end users and fill most of the form in the local language. The main disadvantage is that we dont have any complete translation tool set in place but only partial.</p>
<p>2. We havent faced any issues with user tool as the view of the form is based on the language used on the system. More over in web version is better to use than user tool for this as it increases the performance of the overall system.</p>
<p>3.Yes, the Data language is the main language of the ar database that it primarily configured for, we had English for this.</p>
<p>4. Since there are several special characters in each language some the these are not compatible with each other. For example, both AR server and database can be either French or German, when the Display language used on the user tool or web is French or German. But, when you have French database, Japanese language cant be used on the user tool.</p>
<p>With 7.6 I believe there is localization kit provided for easy updates of form views, havent used it but should be helpful. Its always better to use English as database and server language as its supports almost all display languages. </p>
<p>Cheers,<br />
Venkat Maddala.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kristina</title>
		<link>http://remediesforremedy.com/2009/07/localization-of-ar-applications/comment-page-1/#comment-5261</link>
		<dc:creator>kristina</dc:creator>
		<pubDate>Mon, 17 Oct 2011 12:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://remedy75.wordpress.com/?p=29#comment-5261</guid>
		<description>Dear Venkat,

Since you applied localization for a global company, did you tested any downsides of it. E.g. Costs (slower performance etc.?). I am new to this and got a task to understand localization issues of Remedy 7.6.

Have you encountered any &gt;
1.	Pros and Cons of applying localization before and after the AR system installation for a global company that operates in Japan, China, US, europe, Brasil.
2.	AR system installation and AR system clients (what is a client (tenant?) in Remedy)?
3.	Clarification on data and display language needed. Is Data language the language of input, meaning info/requests added/managed by requesters/support staff? And display language – language of interface (menu buttons, help text, error messages)?
4.	Data and display language compatibility (what is meant by this? French is not German, however in documentation it is said French and German can be installed in any combination, however French and Japanese can’t…)

Any help appreciated,
thanks a lot,
kristin</description>
		<content:encoded><![CDATA[<p>Dear Venkat,</p>
<p>Since you applied localization for a global company, did you tested any downsides of it. E.g. Costs (slower performance etc.?). I am new to this and got a task to understand localization issues of Remedy 7.6.</p>
<p>Have you encountered any &gt;<br />
1.	Pros and Cons of applying localization before and after the AR system installation for a global company that operates in Japan, China, US, europe, Brasil.<br />
2.	AR system installation and AR system clients (what is a client (tenant?) in Remedy)?<br />
3.	Clarification on data and display language needed. Is Data language the language of input, meaning info/requests added/managed by requesters/support staff? And display language – language of interface (menu buttons, help text, error messages)?<br />
4.	Data and display language compatibility (what is meant by this? French is not German, however in documentation it is said French and German can be installed in any combination, however French and Japanese can’t…)</p>
<p>Any help appreciated,<br />
thanks a lot,<br />
kristin</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 1.365 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-05-18 03:12:46 -->

