[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita-translation] CONREF best practices
Hi Everyone, This is the basic text after the suggested changes from today's meeting. If all is OK, then i will put this into the standard form suggested by JoAnn: Great care should be taken regarding the use of the 'conref' attribute. Although the conref attribute may appear as a very efficient artifice to allow for the simple substitution of product names etc. allowing for the runtime resolution of given parameters this can cause grammatical problems with highly inflected and gender sensitive languages such as most Slavonic and Germanic languages. What works extremely well for English or French source text can result in ungrammatical text for given target languages. Such an outcome is generally undesirable as it will reflect badly on the documentation concerned. As a general rule the safest way to use conref is for the inclusion of grammatically complete sentences, phrases or complete block of text (those that can stand alone and do not rely on the surrounding context). Never use conref to substitute common nouns or noun phrases such as for example 'hammer' or 'screw driver' etc. Where the conref is used for proper nouns, such as 'Ford Focus' the the safest solution is to insure that the proper noun is always the main subject of the sentence, e.g.: Do not use: Driving the Ford Focus is an exhilarating experience. Rather use: The Ford Focus provides an exhilarating diving experience. The subject of a sentence is in the nominative case and therefore does not normally require inflection. The translators should also receive appropriate instructions to insure that the substituted proper noun is translated as the subject of the sentence. In addition the translator needs to be provided with a hard copy of the source text to see the context of the text. The translator will need to see a composed version of the translation with conref resolution so that the grammatical implications of the translation can be seen. As a general point all template text within DITA should be handled via the conref mechanism. This guarantees that all translatable code can be handled via one XML translation process. Avoid holding translatable text in CSS or any other non-direct XML mechanism such as entity references. Best Regards, AZ -- email - firstname.lastname@example.org smail - c/o Mr. A.Zydron PO Box 2167 Gerrards Cross Bucks SL9 8XF United Kingdom Mobile +(44) 7966 477 181 FAX +(44) 1753 480 465 www - http://www.xml-intl.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you may not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Unless explicitly stated otherwise this message is provided for informational purposes only and should not be construed as a solicitation or offer.