Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the betterdocs domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data/user/htdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the jnews-view-counter domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data/user/htdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-statistics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data/user/htdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpdiscuz domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data/user/htdocs/wp-includes/functions.php on line 6114

Notice: 函数 _load_textdomain_just_in_time 的调用方法不正确jnews 域的翻译加载触发过早。这通常表示插件或主题中的某些代码运行过早。翻译应在 init 操作或之后加载。 请查阅调试 WordPress来获取更多信息。 (这个消息是在 6.7.0 版本添加的。) in /data/user/htdocs/wp-includes/functions.php on line 6114

Notice: 函数 _load_textdomain_just_in_time 的调用方法不正确jnews-like 域的翻译加载触发过早。这通常表示插件或主题中的某些代码运行过早。翻译应在 init 操作或之后加载。 请查阅调试 WordPress来获取更多信息。 (这个消息是在 6.7.0 版本添加的。) in /data/user/htdocs/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /data/user/htdocs/wp-includes/functions.php:6114) in /data/user/htdocs/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":35322,"date":"2024-10-21T11:27:14","date_gmt":"2024-10-21T03:27:14","guid":{"rendered":"https:\/\/linguaresources.com\/?p=35322"},"modified":"2024-10-21T11:27:14","modified_gmt":"2024-10-21T03:27:14","slug":"new-research-uses-of-ai-translation-in-public-services","status":"publish","type":"post","link":"https:\/\/linguaresources.com\/?p=35322","title":{"rendered":"New Research – Uses of AI Translation in Public Services"},"content":{"rendered":"
\n

The Chartered Institute of Linguists (CIOL) is pleased to have partnered with the University of Bristol on the ‘Uses of AI Translation in UK Public Service Contexts’<\/a>. This groundbreaking research, authored by Dr Lucas Nunes Vieira of the University of Bristol, examines a previously unstudied aspect of our public services: the use of machine translation tools by frontline workers.<\/span><\/p>\n

The findings are both informative and concerning. They reveal significant use of AI-powered translation tools, including Google Translate and ChatGPT, in healthcare, legal, emergency, and police services – a practice that has largely gone unnoticed and unregulated.<\/span><\/p>\n

The data, from over 2,500 UK professionals, shows that a third of respondents have used machine translation in their work, often in public-facing situations where miscommunication could have serious consequences. Of particular concern is the lack of institutional awareness and acknowledgement of this practice and the absence of appropriate policy frameworks to protect the public and public service workers themselves. The majority of respondents reported that machine translation had never been mentioned in their workplace training, despite its frequent use. This institutional silence means frontline workers are navigating complex linguistic situations with public service users and the public in ad hoc ways without guidance or support.<\/span><\/p>\n

We wholly endorse the recommendations put forth in this report. The call for organisations to acknowledge the existence and potential use of AI\/machine translation, to address that use in policies, and to place much more emphasis on staff education and training on AI and machine translation are all crucial steps. However, we believe these recommendations should be seen as a starting point rather than the end state. They should be implemented alongside robust safeguards and a commitment to maintaining human oversight by professional translators and experienced linguists in critical translation tasks.<\/span><\/p>\n

The risks of getting translation wrong in public service contexts, through mistranslation, cultural insensitivity, or loss of nuance are simply too high to not use appropriately qualified language professionals. Another concern is the potential for AI to perpetuate or even amplify biases present in its \u2018training data\u2019, leading to systemic discrimination in translated content.<\/span><\/p>\n

In light of these concerns, we strongly advocate for maintaining and, where possible, increasing public service budgets for professional translation services. While we recognise that it may not be realistic for human translation to be used in every circumstance, it is crucial that funding for skilled linguists is protected, especially in high-stakes situations where accuracy and cultural sensitivity are paramount.<\/span><\/p>\n


\n

Read the full report here.<\/a><\/span><\/strong><\/p>\n


\n<\/div>\n

\u539f\u2f42\u94fe\u63a5<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

The Chartered Institute of Linguists (CIOL) is pleased […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[391],"tags":[],"class_list":["post-35322","post","type-post","status-publish","format-standard","hentry","category-391"],"_links":{"self":[{"href":"https:\/\/linguaresources.com\/index.php?rest_route=\/wp\/v2\/posts\/35322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linguaresources.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linguaresources.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linguaresources.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linguaresources.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=35322"}],"version-history":[{"count":0,"href":"https:\/\/linguaresources.com\/index.php?rest_route=\/wp\/v2\/posts\/35322\/revisions"}],"wp:attachment":[{"href":"https:\/\/linguaresources.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=35322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linguaresources.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=35322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linguaresources.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=35322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}