{"id":6936,"date":"2019-12-11T10:30:15","date_gmt":"2019-12-11T10:30:15","guid":{"rendered":"https:\/\/www.utalk.com\/news\/?p=6936"},"modified":"2019-12-16T10:57:55","modified_gmt":"2019-12-16T10:57:55","slug":"utalks-ladino-journey","status":"publish","type":"post","link":"https:\/\/utalk.com\/news\/utalks-ladino-journey\/","title":{"rendered":"uTalk&#8217;s Ladino Journey"},"content":{"rendered":"\n<figure class=\"wp-block-image\"><img loading=\"lazy\" width=\"2223\" height=\"1349\" src=\"https:\/\/www.utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800.jpg\" alt=\"\" class=\"wp-image-6937\" srcset=\"https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800.jpg 2223w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-250x152.jpg 250w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-700x425.jpg 700w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-768x466.jpg 768w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-1536x932.jpg 1536w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-2048x1243.jpg 2048w, https:\/\/utalk.com\/news\/wp-content\/uploads\/2019\/12\/GettyImages-485947800-120x73.jpg 120w\" sizes=\"(max-width: 2223px) 100vw, 2223px\" \/><\/figure>\n\n\n\n<p><em>After months of hard work, we\u2019ve just added our 144th language to the uTalk app\u2014Ladino! In this blog post, we share how we go about adding new languages, as well as the unique issues that arise when it comes to adding languages that are endangered.&nbsp;<\/em><br><\/p>\n\n\n\n<p>Way back at the beginning of 2019, two individuals met and had a conversation that would eventually lead to the development and release of Ladino on the uTalk app. Specifically, Carlos Yebra L\u00f3pez, from the organisation Ladino 21, met Kevin Sun, <a href=\"https:\/\/utalk.com\/news\/2019\/08\/28\/game-of-phones-utalk-at-langfest\/\">a man who has famously topped the leaderboard at many of our Kahoot quizzes<\/a>\u2014and they got to talking about the ways in which Ladino, an endangered language that Carlos has been trying to help preserve and promote, could be further helped.<br><\/p>\n\n\n\n<p>So when uTalk was then approached by Carlos in March, it was the first time many of the staff had even heard of the language. Carlos offered the assistance of Ladino 21 in translating our script and finding native speakers and it was clear from the start that uTalk\u2019s values lined up with what Ladino 21 want to achieve\u2014record and preserve Ladino via digital means while reaching a wider and younger audience.<\/p>\n\n\n\n<h2>How do we go about adding a new language?<\/h2>\n\n\n\n<p>At 144 languages, it\u2019s clear that we have a system going that works for us\u2014although, of course, problems can still arise. In fact, every language comes complete with its own set of issues, and this is especially true when it comes to minority or endangered languages such as Ladino.<br><\/p>\n\n\n\n<p>The first step is always choosing a language and finding people from that language community who would like to get involved and help. If we find no speakers, then that language doesn\u2019t go ahead\u2014but with Ladino, we were lucky, as Ladino 21 approached us first.<br><\/p>\n\n\n\n<p>So, with the language chosen, it\u2019s time to look for the first bit of help we\u2019ll need: translators. Since the script we have is the same for every language, we get hold of two translators, who work independently of one another. With around 2,500 words and phrases, this is about a week\u2019s worth of work, though it can take more time than that, depending on what other work our busy translators have to do!<br><\/p>\n\n\n\n<p>Once they\u2019ve both translated the entire script, they then swap files and check each others\u2019 work. This is an easy way to spot any common errors or hash out initial discrepancies. After this, the translated scripts are returned to our Languages Manager, who checks them and then jumps on a call with the translators to go over any lingering issues. There are always a few, but by the end of this stage, everything is more-or-less ready to go.<br><\/p>\n\n\n\n<p>Next, it\u2019s time for our voice actors, aka, the people you hear when you use the app. For every language, we source one female and one male native speaker (very few languages are exceptions to our native speaker rule: Latin and Ancient Greek being the obvious ones!) and have them come and record at our studio.<br><\/p>\n\n\n\n<p>The advantage to our office being based in London is that London is one of the most multicultural cities in the world, with approximately 200-300 languages spoken here. This means that when we need native speakers for the app, we usually only have to put the word out and we can find our voice actors locally.<br><\/p>\n\n\n\n<p>However, with Ladino, <a href=\"https:\/\/www.utalk.com\/news\/2017\/08\/14\/blog-behind-the-scenes-manx-recording\/\">much like with Manx<\/a>, we had to search a little further afield. Fortunately, Carlos and his deputy director, Alejandro Acero, already had people in mind. Our voice actors were sent the script, as they usually are, to also get two new sets of eyes on it, and then flew over to record.<br><\/p>\n\n\n\n<p>There are always more checks on the script while recording\u2014as any translator knows, sometimes what is written down does not always lend itself well to speech!\u2014and this recording takes at least a couple of days with both speakers sitting in and listening out for any mistakes.&nbsp;<br><\/p>\n\n\n\n<p>After the recording is all wrapped up, we go into post-production: editing the audio for things like background noise and mouth noise (a super common thing!), and then into app building, lots and lots and <em>lots<\/em> of testing, and finally the release.<\/p>\n\n\n\n<h2>What about Ladino?<\/h2>\n\n\n\n<p>Working with Ladino 21 was really a great partnership for us because they already had speakers in mind for the app and on top of that, they offered to share their connections in the Ladino community, which is important for us when trying to drum up support. By October, we were all ready to go with the recording, our voice actors were ready to fly over\u2026 but then, disaster struck!<br><\/p>\n\n\n\n<p>At the last minute, one of our speakers couldn\u2019t make it, so <a href=\"https:\/\/www.utalk.com\/news\/2019\/12\/15\/meet-our-speakers-benni-aguado-ladino\/\">another Ladino speaker, Benni Aguado<\/a>, was roped in, dropping everything in New York last minute so he could fly over and help out. This did mean, however, that he didn\u2019t really have a chance to check out the script before his arrival in London.<br><\/p>\n\n\n\n<p>Between this and the fact that Ladino is now spoken by a diaspora that is geographically scattered, there was a lot of discussion throughout the week between our voice actors, <a href=\"https:\/\/www.utalk.com\/news\/2019\/12\/14\/meet-our-speakers-rachel-bortnick-ladino\/\">Rachel Bortnick<\/a> and Benni Aguado, as to the word or phrase they would use in a specific situation, as sometimes the two had very differing opinions. Sometimes one of them would use a word the other had never heard of, too!\u00a0<br><\/p>\n\n\n\n<p>One of these examples is the word for \u2018kite.\u2019 In the app, we have chosen to use the word \u2018la filandra,\u2019 which is used among Ladino speakers from Turkey or Greece. However, Rachel\u2019s family\u2014and she herself\u2014are from Izmir, where they instead say \u2018el hacho.\u2019 This was something that had to be discussed, especially as the word \u2018hacho\u2019 actually comes up in a different context: jellyfish! The Ladino word for jellyfish is \u2018el hacho de mar,\u2019 or, \u2018the kite of the sea,\u2019 but \u2018la filandra\u2019 was chosen for \u2018kite,\u2019 not to lose out on this imagery, but for the fact that it is likely to be understood by a higher number of speakers.<\/p>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<ul class=\"wp-block-gallery columns-2 is-cropped\"><li class=\"blocks-gallery-item\"><figure><img src=\"https:\/\/www.utalk.com\/news\/wp-content\/uploads\/2019\/12\/Image-from-iOS.png\" alt=\"\" data-id=\"6938\" data-link=\"https:\/\/www.utalk.com\/news\/?attachment_id=6938\" class=\"wp-image-6938\"\/><\/figure><\/li><li class=\"blocks-gallery-item\"><figure><img src=\"https:\/\/www.utalk.com\/news\/wp-content\/uploads\/2019\/12\/Image-from-iOS-1.png\" alt=\"\" data-id=\"6939\" data-link=\"https:\/\/www.utalk.com\/news\/?attachment_id=6939\" class=\"wp-image-6939\"\/><\/figure><\/li><\/ul>\n\n\n\n<hr class=\"wp-block-separator\"\/>\n\n\n\n<p>So, there was a lot to consider and this meant that recording took about a week! After the recording was finished\u2014and after Rachel and Benni had returned home to Texas and New York, respectively\u2014the post-production fun began, with Emily, our Languages Manager, working hard on audio editing before everything was handed off to be built into the app.<br><\/p>\n\n\n\n<p>Checks after checks and tests after tests were performed, including a round of everyone in the office doing their best to update their app after Ladino first went live, and what exists now in the app is a labour of love that has taken our company around nine months to achieve.&nbsp;<br><\/p>\n\n\n\n<p>And that nine months? While it\u2019s longer than it usually takes for us to get a language finished and in the app (we estimated that our absolute quickest time to add a language would be around a month), considering the scope of this project\u2014a severely endangered language, speakers scattered around the globe, a very fixed time limit on how long the recording could take\u2014nine months is not all that bad.&nbsp;<br><\/p>\n\n\n\n<p>We don\u2019t think so, anyway!<br><\/p>\n\n\n\n<p>Of course, if you\u2019d like to get your hands on Ladino, <a href=\"http:\/\/utalk.com\/plans\/blog40?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=ladino-journey\">you can get a subscription (with 40% off) here<\/a>. You might not find a native speaker local to you (though you might be surprised, <em>especially<\/em> if you\u2019re in the US!) but there\u2019s a strong online community who will surely all be happy to speak with you.&nbsp;<\/p>\n\n\n\n<p>From all of us at uTalk, <em>mazal bueno<\/em> (good luck) with your Ladino journey\u2014and drop us a comment if you start learning; we\u2019d love to hear all about it!<\/p>\n\n\n\n<p><br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>After months of hard work, we\u2019ve just added our 144th language to the uTalk app\u2014Ladino! In this blog post, we share how we go about adding new languages, as well as the unique issues that arise when it comes to adding languages that are endangered.&nbsp; Way back at the beginning of 2019, two individuals met &#8230; <a title=\"uTalk&#8217;s Ladino Journey\" class=\"read-more\" href=\"https:\/\/utalk.com\/news\/utalks-ladino-journey\/\" aria-label=\"More on uTalk&#8217;s Ladino Journey\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1784],"tags":[1671,1786,1785,2,333,793],"_links":{"self":[{"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/posts\/6936"}],"collection":[{"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/comments?post=6936"}],"version-history":[{"count":0,"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/posts\/6936\/revisions"}],"wp:attachment":[{"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/media?parent=6936"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/categories?post=6936"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/utalk.com\/news\/wp-json\/wp\/v2\/tags?post=6936"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}