Dr Flex & Dr LiveCycle

Disease:

Developing multi-lingual forms can be time-consuming and difficult to implement. 

Prescription: 

LiveCycle Designer 8.2, currently in beta, offers XLIFF support.  The generic idea is to extract field labels, hints, etc. from the xdp-template and store these in a xml-file. Translate the labels in the xml-file. Merge the original template with the xml-file to create a new xdp-template which will contain the translated  ‘labels’. These are the different steps:

1) You need to create a DWORD key ‘EmbedTranslationAttributes’ equal to 1 in the windows registry in order to include the XLIFF definitions in your xdp template. Under HKEY_CURRENT_USER – Software – Adobe – Designer – 8.2 – Options   

2) Develop/save your template (e.g. xliff.xdp)  

3) Install an xslt parser (I used the Saxon xslt parser)

4) Execute the following command to export the ‘labels’ (field labels, hints, error messages, etc.) out of the xdp

java net.sf.saxon.Transform -s:xliff.xdp -xsl:XDPtoS2X.xslt -o:strings.xml

5) Change the labels in the strings.xml file

6) Execute the following command to import the ‘labels’ in the newly created xdp (e.g. new.xdp)

java net.sf.saxon.Transform -s:strings.xml -xsl:S2XtoXDP.xslt -o:new.xdp

Please be noted that in the S2XtoXDP.xslt the input-XDP (e.g. xliff.xdp) is hard-coded in the sample; You may change the name of the xdp at line 24 in the xslt-file. 

That’s it.

Tip to stay healthy: 

Thanks to the support of Dr. Steve and Dr. Marc, I have created a zip-file which contains the xslt’s, command-file’s and the sample xliff.xdp. Download the package here. Get familiar with this new feature and develop multi-lingual forms more rapidly.

Trackback URI | Comments RSS