Translation Tips

The examples, screen shots, and folder paths throughout this document are based on the translation of Aras Innovator into Japanese.

The following section glances at use cases that may arise during translation and how to resolve them.

Although the session context has not been determined prior to logging into Aras Innovator it is still possible to have the Login Screen localized for the user.

The text fields of the Aras Innovator login page are being pulled from the ui_Resources.xml file that can be located in the \\Innovator\Client\xml.ja folder of your Aras Innovator code tree. In this file, you will find the following section that contains the UI resources that populate the login page.

<!-- +++++ Client/Scripts/login.aspx +++++ -->

 <resource key="login.login_page_title_sfx” value="Login"/>

 <resource key="login.login_name_html” value="Login Name:&amp;nbsp;"/>

 <resource key="login.pwd_html” value="Password:&amp;nbsp;"/>

 <resource key="login.db_html” value="Database:&amp;nbsp;"/>

 <resource key="login.server_html” value="Server:&amp;nbsp;"/>

 <resource key="login.cookies_are_disabled_msg_html” value="Please confirm that cookies are enabled in &lt;br&gt;your browser before to login to Innovator."/>

 <resource key="login.enter_login_name_status_msg” value="Enter Login Name"/>

 <resource key="login.enter_pwd_status_msg” value="Enter Password"/>

 <resource key="login.selected_base_status_msg” value="Selected base:"/>

 <resource key="login.missing_login_name_wrn” value="Missing Login Name."/>

 <resource key="login.missing_pwd_wrn” value="Missing Password."/>

 <resource key="login.missing_db_wrn” value="Missing Database."/>

 <resource key="login.version_html” value="Version:"/>

 <resource key="login.build_html” value="Build:"/>

 <resource key="login.bookmark_this_page_txt” value="Bookmark this page"/>

 <resource key="login.bookmark_this_page_txt2" value="Bookmark this page..."/>

 <resource key="login.login_btn_label” value="Login"/>

 <resource key="login.cancel_btn_label” value="Cancel"/>

 <!-- Client/Scripts/login.aspx -->

The values highlighted in yellow above control what is displayed on the Login Page along with any messages that may pop up. After translating these values save the ui_Resources.xml file and verify the login page adheres to your changes.

Although the tabs inside the Form Editor appear to be basic Relationship tabs, they are actually being populated by the ui_Resources.xml file that can be located in the \\Innovator\Client\xml.ja folder of your Aras Innovator code tree. In this file you will find the following section that contains the UI resources that populate the text for the Form Editor Tabs.

<!-- +++++ Client/Scripts/FormTool/formTabs.html +++++ -->

 <resource key="formtabs.field_type” value="Field Type"/>

 <resource key="formtabs.field_label” value="Field Label"/>

 <resource key="formtabs.field_physical” value="Field Physical"/>

 <resource key="formtabs.field_border” value="Field Border"/>

 <resource key="formtabs.field_event” value="Field Event"/>

 <resource key="formtabs.form_props” value="Form Properties"/>

 <resource key="formtabs.form_body” value="Form Body"/>

 <resource key="formtabs.form_event” value="Form Event"/>

 <resource key="formtabs.populating_data_source_list” value="populating data source list"/>

 <!-- Client/Scripts/FormTool/formTabs.html -->

The values highlighted in yellow above control the text that appears on the Form Editor tabs along with any messages that may pop up. After translating these values save the ui_Resources.xml file and verify the Form Editor adheres to your changes.

If you have Project Management installed, the column headers for the ‘Project Plan’ of the Project ItemType are maintained in the ‘World’ Preference Item.

To add multi-lingual labels to these column headers, you need to edit the ‘World’ Preference in Administration\Preferences.

The Label column contains the multi-lingual string that maps to the Project Team column header. Changing this text can be done by simply putting the desired grid cell in edit mode and pressing F2.

The Project Plan relationship for the Project Template ItemType does not behave like other standard relationships. The Project Plan relationship is controlled and populated through separate HTML that populates the column names using the projectGridLayoutXML.xml file located in the \Innovator\Client\Solutions\Project\xml.ja folder. In this XML file, you can see multiple items that look like the following:

<Item type="PM_ProjectGridLayout">

<!--//TreeNode-->

 <position>2</position>

 <width>200</width>

 <name>tree_node</name>

 <label>Project Tree</label>

 <is_system>1</is_system>

</Item>

For each Item in the projectGridLayoutXML.xml the text highlighted in yellow between the <label> tags is used as the column names of the Project Plan. After translating all of the labels save the XML and verify that your changes adhere to the Project Template form.

Just like the ‘Project Plan’ relationship described earlier, the ‘Changes’ relation to the Part and Document ItemTypes does not behave like a standard relationship within Aras Innovator. The ‘Changes’ relationship is controlled and populated through separate HTML that populates the column names using the ChangesGrid.xml file located in the \\Innovator\Client\Solutions\PLM\xml.ja folder. In this XML file, you can see the following fields:

<thead>

 <th align="c">Type</th>

 <th align="c">Number</th>

 <th align="c">Title</th>

 <th align="c">State</th>

</thead>

The fields highlighted in yellow are the column names that are displayed for the Changes relationship. After you have translated these labels save the XML file and verify that the changes adhere to the Changes relationship for the Part and Document ItemTypes.

In the relationship grid for Items within Aras Innovator you can see the properties of not only the related item that are visible, but also properties of the RelationshipType ItemType that are made visible as well. The trickiness of this feature arises from the fact that the label in the relationship tab does not necessarily match up with the relationship ItemType.

In the following example, we take a look at the ‘Grid’ ItemType. Looking at the form for the Grid ItemType you notice that there is a relationship tab that says Grid Events.

If you do a search on ItemTypes, you notice that there is an ItemType called ‘Grid Event’. You may have translated the sort_order property for the ‘Grid Events’ ItemType and noticed it is not translated in the Grid form. Although the relationship tab label displays ‘Grid Event’, the ‘Grid Event’ ItemType is not the relationship ItemType for the Grid -->Event relationship. The correct ItemType to edit for the Grid --> Event relationship is ‘Configurable Grid Event’.

By selecting RelationshipType in the Administration branch of the TOC you can perform a search of the ‘Source ItemType’ to verify what the ‘Relationship ItemType’ is.

After verifying the proper relationship ItemType, you then need to edit the label of the necessary properties and save the ItemType. After saving the ItemType verify that your translation adheres to the relationship grid.