Challenges in Translation: Terminology and Language Support
Exploring the complexities faced in translation, especially with technical content, due to factors like terminology, lack of context, and difficult syntax. The text emphasizes the importance of comprehension for experienced translators and the intricacies involved in conveying meaning accurately across languages.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
the annotation system And when one of you falls down he falls for those behind him, a caution against the stumbling stone. Ay, and he falls for those ahead of him, who though faster and surer of foot, yet removed not the stumbling stone. Kahlil Gibran The Prophet
Ronan Martin terminology manager SAS Software (not the airline) terminology and language support
Part 1: background Part 2: the system itself Part 3: experiences so far
A nice text: An easily understood text can be translated quite quickly. However, the more technical the content, the more challenging the task becomes. For an experienced translator, the main challenge is one of comprehension, and this can be due to terminology, lack of context, ambiguity, difficult syntax, or a host of other reasons. Part 1: background
A slightly tricky text: Part 1: background
A highly challenging text: jfkdljk_1.txt=This is a focusable div with the APPLICATION role jfkdljk_2.txt=Are you sure you want to delete these {0} hierarchies? jfkdljk_3.txt=Updating hierarchy line items may impact dependent worksheets jfkdljk_4.txt=All previous filter selections are removed because Transpose action performed. jfkdljk_5.txt=Query was stopped at {0}. Click to resume the query. Part 1: background
syntax context terminology Part 1: background
syntax Input server path Is Input used as an adjective or as a verb here? Part 1: background
context Assume Superuser Could you please explain the meaning of 'Assume' here? Part 1: background
terminology A baseline creative ID is required for processing a job. We have problems understanding the meaning of 'baseline creative' Part 1: background
?begins....term....ends? what does it mean? what does it mean here? what do I call it in ..... Part 1: background
developers are not writers non-English developers Part 1: background
been there... ...and doing that but how do we distribute answers to resolved issues? Part 1: background
CAT tool? translation memories? source files Part 1: background
across languages across versions across organizations across tools Part 1: background
capture storage retrieval delivery Part 2: the system itself
assessement list query system submit form annotations - editable string bank martif dictionary (xml) term base direct update and display in CAT tool in real time CAT tool interaction Part 2: the system itself
http://koelcterm.sdk.sas.com/add_string_info.htm?string=Remediation%%2ALead%%2A&product=\vehttp://koelcterm.sdk.sas.com/add_string_info.htm?string=Remediation%%2ALead%%2A&product=\ve rtical\Products\RiskAndCompliance\Monitor\Source\mrm\Config\Deployment\Content\Preload\Confi g::d4grc62&properties_key=linkType.MRM.finding_remediationLead.name1.txt%3D&scope=MRM&au thor=spnmxc Part 2: the system itself
HTML forms CGI perl SAS scripts javascript arrays martif dictionary termbase Part 2: the system itself
data changes daily best time to build a dictionary? translators sometimes need prompting Part 2: the system itself
surprisingly no negativity at all! full support all round! vendors needed more detailed instruction immediate management support Part 2: the system itself
many tricky characters! short segments common words scalability numbers are growing CAT tool limitations Part 2: the system itself
quick browser demo Part 2: the system itself
50% of queries become annotations many dictionary builds each day Part 3: experiences so far
an inseparable pair Part 3: experiences so far
translators always up to date with queries better quality translations less traffic on communication lines Part 3: experiences so far
great help for external translators much easier to bring new languages onboard translation choices: a record of why? Part 3: experiences so far
language-specific annotations annotations written up-front by UI analysts annotations as an avoidable symptom Part 3: experiences so far
thank you! feedback welcome ronan.martin@sas.com Part 3: experiences so far