Properties Files

I am looking into the use of a properties file in a custom module. The help in Builder states that a properties file is a text file that sits in the same directory are the ospace.Section from Builder help....-----------------------------------Properties FilesA properties file is a text file contains a list of key and values. The following is an example: WEBDOC_HTMLLABEL.CancelButtonLabel = Cancel WEBDOC_HTMLLABEL.Categories = Categories WEBDOC_HTMLLABEL.Categories_ = Categories\: WEBDOC_HTMLLABEL.Category_ = Category\: WEBDOC_HTMLLABEL.ChangeOwnerInstructions2 = Then click its "Select" link.A properties file is used by a single ospace, but an ospace can deploy multiple properties files. The properties file is placed together with its ospace during runtime. For example, there are 2 properties files, llapi_en_US.properties and lliapi_en_US.properties, which are placed in the same folder with the LLIApi ospace. Notice the naming convention of the properties file. In this case, the language used is _en_US (US English).-----------------------------------Based on the above instruction, I can create a text file (in the ospace directory) with key/value pairs and name it using the format and saving it using the "properties" extension. Am I correct?

Find more posts tagged with

Comments

eLink User

Message from Carsten Kulms via eLinkYes. Afaik the properties files used by LES are like Java properties files.Therefore please obey the general rules on properties files, inparticular the information on character encodings:http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html#encoding

Jeff Lang

Chris,My company releases all of our Livelink modules in 4 different languages and these are the steps we use to create the properties files.First, we create the module with all visible strings in EnglishOnce the module is complete, we create the first properties file as an empty text file named [ospace name]_en_US.propertiesNow, from the builder, look at every object that has a script or a string feature. When you open a script, under the script menu in the builder, there are a bunch of commands for dealing with translation strings. Select the string, use the XLate selection command to create a new tag/translation pair for the string. The tool allows you to create new groups for storing the strings in meaningful groupings. For string features, use the Text menu. Don't forget to translate the HTML files as well.After you have XLated your entire module, you can create the other language .properties files to allow your module to work in other languages. Copy the properties file and change the name as follows:[ospace Name]_de.properties for German[ospace Name]_fr.properties for French[ospace Name]_ja.properties for Japanese[ospace Name]_nl.properties for Dutch[ospace Name]_es.properties for SpanishOpen each of these files in an editor that can handle the selected language and save the files in ASCII format. The special characters will get converted to a backslash with a hex representation for each character.Place all of these properties files in the ospace directory and when Livelink starts, it will select the correct language properties file to use.

eLink User

Message from Chris Bowman via eLinkJeff,Using your instructions I was able to understand how the properties file iscreated. Thanks for the help.Chris-----Original Message-----From: eLink Discussion: Livelink Builder Discussion[mailto:componentbuilder@elinkkc.opentext.com] Sent: Monday, March 26, 2007 9:31 AMTo: eLink RecipientSubject: RE Properties filesRE Properties filesPosted by Lang, Jeff on 03/26/2007 10:27 AMChris,My company releases all of our Livelink modules in 4 different languages andthese are the steps we use to create the properties files.First, we create the module with all visible strings in EnglishOnce the module is complete, we create the first properties file as an emptytext file named [ospace name]_en_US.propertiesNow, from the builder, look at every object that has a script or a stringfeature. When you open a script, under the script menu in the builder, thereare a bunch of commands for dealing with translation strings. Select thestring, use the XLate selection command to create a new tag/translation pairfor the string. The tool allows you to create new groups for storing thestrings in meaningful groupings. For string features, use the Text menu.Don't forget to translate the HTML files as well.After you have XLated your entire module, you can create the other language.properties files to allow your module to work in other languages. Copy theproperties file and change the name as follows:[ospace Name]_de.properties for German[ospace Name]_fr.properties for French[ospace Name]_ja.properties for Japanese[ospace Name]_nl.properties for Dutch[ospace Name]_es.properties for SpanishOpen each of these files in an editor that can handle the selected languageand save the files in ASCII format. The special characters will getconverted to a backslash with a hex representation for each character.Place all of these properties files in the ospace directory and whenLivelink starts, it will select the correct language properties file to use.[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: Properties Fileshttps://knowledge.opentext.com/knowledge/llisapi.dll/open/11990921Discussion: Livelink Builder Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/765419Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.componentbuilder@elinkkc.opentext.com.