Hi Ron, On 20 June 2015 at 01:36, Ron Wheeler <[email protected]> wrote:
> DITA not only supports i18n but has specific features to reduce the > translation management effort. > For instance: > You can identify terms that should not be translated "Tomcat", "Windows". > > You can provide translations of phrases that are frequently used so they > do not get translated more than once. "Cancel", "Open for Business". "This > feature requires administrative privileges.", etc. > This also adds consistency in a single language and make customization of > labels easier. "This feature requires administrative privileges." should > not come up as "Administrative role required." or "You need admin privs to > do this." If you have decided to use "HST" to replace "VAT" on a label, you > only have to change one term to convert all of your docs. > > You can create country, industry-specific or language-specific manuals > easily. You're starting to sell me on this! Would it be possible to use the OFBiz resources like applications/accounting/config/AccountingEntityLabels.xml as an input? I understand the translated terms would need to be in DITA format to integrate with DITA documentation. But could be use the same property keys as in OFBiz (e.g. AcctgTransType.description.AMORTIZATION) and do you think there's any prospect of using XSLT to transform our resources into DITA format? Thanks Paul Foxworthy -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Australia Phone: +61 3 9585 6788 Fax: +61 3 9585 1086 Web: http://www.coherentsoftware.com.au/ Email: [email protected] Small. Complete. Perfect. Your business with BonsaiERP. http://www.bonsaierp.com.au/
