If you added custom attributes to the schema, you also need to add translation strings in the custom file. Such file contains the translations for the attributes you've added in Prepare custom GN4.XSD schema and Prepare custom TARK4.XSD schema.

A sample, rather short file shows just one example of translating: the attribute lwSubLocation is translated for when it appears in object caption, in a message, in an attribute labels, and in a message related to the attribute. The last two lines are examples taken from the standard files that shows how to add instructions to the form, and how to translate any other name (Scope = "Default").

<?xml version="1.0"?>

<StringList

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns="http://www.teradp.com/schemas/GN4/1/StringList.xsd">

 

 <!--

 #### Strings corresponding to schema elements (object types, attributes and enumerations)

 #### defined in LWGN4.xsd

-->

 

 <!-- Object type name translation used as a caption -->

 

 <StringDesc Scope="ObjTypeCaption" Name="lwSubLocation" Value="Sublocation" />

 <!-- Object type name translation used inside a message -->

 

 <StringDesc Scope="ObjTypeMsg" Name="lwSubLocation" Value="Sublocation" />

 <!-- Object attribute name translation used as a caption -->

 

 <StringDesc Scope="ObjAttrCaption" Name="lwSubLocationRef" Value="Sublocation" />

 <!-- Object attribute name translation used inside a message -->

 

 <StringDesc Scope="ObjAttrMsg" Name="lwSubLocationRef" Value="Sublocation" />

 <!-- ObjAttrInstruction -->

 

 <StringDesc Scope="ObjAttrInstruction" Name="edition.date" Value="Leave empty for template editions" />

 <StringDesc Scope="Default" Name="BudgetNames" Value="Budget names" />

</StringList>