<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: translation</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/translation.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2026-04-27T17:37:47+00:00</updated><author><name>Simon Willison</name></author><entry><title>Speech translation in Google Meet is now rolling out to mobile devices</title><link href="https://simonwillison.net/2026/Apr/27/speech-translation-in-google-meet-is-now-rolling-out-to-mobile-d/#atom-tag" rel="alternate"/><published>2026-04-27T17:37:47+00:00</published><updated>2026-04-27T17:37:47+00:00</updated><id>https://simonwillison.net/2026/Apr/27/speech-translation-in-google-meet-is-now-rolling-out-to-mobile-d/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://workspaceupdates.googleblog.com/2026/04/speech-translation-in-google-meet-is-now-rolling-out-to-mobile-devices.html"&gt;Speech translation in Google Meet is now rolling out to mobile devices&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I just encountered this feature via a "try this out now" prompt in a Google Meet meeting. It kind-of worked!&lt;/p&gt;
&lt;p&gt;This is Google's implementation of the ultimate sci-fi translation app, where two people can talk to each other in two separate languages and Meet translates from one to the other and - with a short delay - repeats the text in your preferred language, with a rough imitation of the original speaker's voice.&lt;/p&gt;
&lt;p&gt;It can only handle English, Spanish, French, German, Portuguese, and Italian at the moment. It's also still very alpha - I ran it successfully between two laptops running web browsers, but then when I tried between an iPhone and an iPad it didn't seem to work.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="translation"/></entry><entry><title>Shisa V2 405B: Japan’s Highest Performing LLM</title><link href="https://simonwillison.net/2025/Jun/3/shisa-v2/#atom-tag" rel="alternate"/><published>2025-06-03T04:07:55+00:00</published><updated>2025-06-03T04:07:55+00:00</updated><id>https://simonwillison.net/2025/Jun/3/shisa-v2/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://shisa.ai/posts/shisa-v2-405b/"&gt;Shisa V2 405B: Japan’s Highest Performing LLM&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Leonard Lin and Adam Lensenmayer have been working on &lt;a href="https://shisa.ai/"&gt;Shisa&lt;/a&gt; for a while. They describe their latest release as "Japan's Highest Performing LLM".&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Shisa V2 405B is the highest-performing LLM ever developed in Japan, and surpasses GPT-4 (0603) and GPT-4 Turbo (2024-04-09) in our eval battery. (It also goes toe-to-toe with GPT-4o (2024-11-20) and DeepSeek-V3 (0324) on Japanese MT-Bench!)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This 405B release is a follow-up to the six smaller Shisa v2 models they released &lt;a href="https://shisa.ai/posts/shisa-v2/"&gt;back in April&lt;/a&gt;, which took a similar approach &lt;a href="https://simonwillison.net/2025/Jan/20/deepseek-r1/"&gt;to DeepSeek-R1&lt;/a&gt; in producing different models that each extended different existing base model from Llama, Qwen, Mistral and Phi-4.&lt;/p&gt;
&lt;p&gt;The new 405B model uses Llama 3.1 405B Instruct as a base, and is available under the &lt;a href="https://www.llama.com/llama3_1/license/"&gt;Llama 3.1 community license&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Shisa is a prominent example of &lt;strong&gt;Sovereign AI&lt;/strong&gt; - the ability for nations to build models that reflect their own language and culture:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We strongly believe that it’s important for homegrown AI to be developed both in Japan (and globally!), and not just for the sake of cultural diversity and linguistic preservation, but also for data privacy and security, geopolitical resilience, and ultimately, independence.&lt;/p&gt;
&lt;p&gt;We believe the open-source approach is the only realistic way to achieve sovereignty in AI, not just for Japan, or even for nation states, but for the global community at large.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The accompanying &lt;a href="https://shisa.ai/posts/shisa-v2-405b/#overview-report"&gt;overview report&lt;/a&gt; has some fascinating details:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Training the 405B model was extremely difficult. Only three other groups that we know of: Nous Research, Bllossom, and AI2 have published Llama 405B full fine-tunes. [...] We implemented every optimization at our disposal including: DeepSpeed ZeRO-3 parameter and activation offloading, gradient accumulation, 8-bit paged optimizer, and sequence parallelism. Even so, the 405B model still barely fit within the H100’s memory limits&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In addition to the new model the Shisa team have published &lt;a href="https://huggingface.co/datasets/shisa-ai/shisa-v2-sharegpt/viewer"&gt;shisa-ai/shisa-v2-sharegpt&lt;/a&gt;, 180,000 records which they describe as "a best-in-class synthetic dataset, freely available for use to improve the Japanese capabilities of any model. Licensed under Apache 2.0".&lt;/p&gt;
&lt;p&gt;An interesting note is that they found that since Shisa out-performs GPT-4 at Japanese that model was no longer able to help with evaluation, so they had to upgrade to GPT-4.1:&lt;/p&gt;
&lt;p&gt;&lt;img alt="Comparison of GPT-4.1 vs GPT-4 as judges showing two radar charts comparing Shisa V2 405B and 70B models on JA MT-Bench benchmarks, with text &amp;quot;Why use GPT-4.1 rather than GPT-4 as a Judge?&amp;quot; and explanation that Shisa models exceed GPT-4 in Japanese performance and GPT-4 cannot accurately distinguish performance differences among stronger models, noting GPT-4.1 applies stricter evaluation criteria for more accurate assessment" src="https://static.simonwillison.net/static/2025/shisa-gpt-4.jpg" /&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/leonard-lin"&gt;leonard-lin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llama"&gt;llama&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/fine-tuning"&gt;fine-tuning&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/evals"&gt;evals&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm-release"&gt;llm-release&lt;/a&gt;&lt;/p&gt;



</summary><category term="leonard-lin"/><category term="translation"/><category term="ai"/><category term="generative-ai"/><category term="llama"/><category term="llms"/><category term="fine-tuning"/><category term="evals"/><category term="llm-release"/></entry><entry><title>A professional workflow for translation using LLMs</title><link href="https://simonwillison.net/2025/Feb/2/workflow-for-translation/#atom-tag" rel="alternate"/><published>2025-02-02T04:23:19+00:00</published><updated>2025-02-02T04:23:19+00:00</updated><id>https://simonwillison.net/2025/Feb/2/workflow-for-translation/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://news.ycombinator.com/item?id=42897856"&gt;A professional workflow for translation using LLMs&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tom Gally is a &lt;a href="https://gally.net/translation.html"&gt;professional translator&lt;/a&gt; who has been exploring the use of LLMs since the release of GPT-4. In this Hacker News comment he shares a detailed workflow for how he uses them to assist in that process.&lt;/p&gt;
&lt;p&gt;Tom starts with the source text and custom instructions, including context for how the translation will be used. &lt;a href="https://www.gally.net/temp/20250201sampletranslationprompt.html"&gt;Here's an imaginary example prompt&lt;/a&gt;, which starts:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;code&gt;The text below in Japanese is a product launch presentation for Sony's new gaming console, to be delivered by the CEO at Tokyo Game Show 2025. Please translate it into English. Your translation will be used in the official press kit and live interpretation feed. When translating this presentation, please follow these guidelines to create an accurate and engaging English version that preserves both the meaning and energy of the original: [...]&lt;/code&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It then lists some tone, style and content guidelines custom to that text.&lt;/p&gt;
&lt;p&gt;Tom runs that prompt through several different LLMs and starts by picking sentences and paragraphs from those that form a good basis for the translation.&lt;/p&gt;
&lt;p&gt;As he works on the full translation he uses Claude to help brainstorm alternatives for tricky sentences:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;When I am unable to think of a good English version for a particular sentence, I give the Japanese and English versions of the paragraph it is contained in to an LLM (usually, these days, Claude) and ask for ten suggestions for translations of the problematic sentence. Usually one or two of the suggestions work fine; if not, I ask for ten more. (Using an LLM as a sentence-level thesaurus on steroids is particularly wonderful.)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;He uses another LLM and prompt to check his translation against the original and provide further suggestions, which he occasionally acts on. Then as a final step he runs the finished document through a text-to-speech engine to try and catch any "minor awkwardnesses" in the result.&lt;/p&gt;
&lt;p&gt;I &lt;em&gt;love&lt;/em&gt; this as an example of an expert using LLMs as tools to help further elevate their work. I'd love to read more examples &lt;a href="https://news.ycombinator.com/item?id=42897856"&gt;like this one&lt;/a&gt; from experts in other fields.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/hacker-news"&gt;hacker-news&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tom-gally"&gt;tom-gally&lt;/a&gt;&lt;/p&gt;



</summary><category term="hacker-news"/><category term="translation"/><category term="ai"/><category term="generative-ai"/><category term="llms"/><category term="tom-gally"/></entry><entry><title>OpenAI o3-mini, now available in LLM</title><link href="https://simonwillison.net/2025/Jan/31/o3-mini/#atom-tag" rel="alternate"/><published>2025-01-31T21:50:36+00:00</published><updated>2025-01-31T21:50:36+00:00</updated><id>https://simonwillison.net/2025/Jan/31/o3-mini/#atom-tag</id><summary type="html">
    &lt;p&gt;OpenAI's &lt;a href="https://openai.com/index/openai-o3-mini/"&gt;o3-mini is out today&lt;/a&gt;. As with other o-series models it's a slightly difficult one to evaluate - we now need to decide if a prompt is best run using GPT-4o, o1, o3-mini or (if we have access) o1 Pro.&lt;/p&gt;
&lt;p&gt;Confusing matters further, the benchmarks in &lt;a href="https://openai.com/index/o3-mini-system-card/"&gt;the o3-mini system card&lt;/a&gt; (PDF) aren't a universal win for o3-mini across all categories. It generally benchmarks higher than GPT-4o and o1 but not across everything.&lt;/p&gt;
&lt;p&gt;The biggest win for o3-mini is on the Codeforces ELO competitive programming benchmark, which I think is &lt;a href="https://arxiv.org/abs/2501.01257"&gt;described by this 2nd January 2025 paper&lt;/a&gt;, with the following scores:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;o3-mini (high) 2130&lt;/li&gt;
&lt;li&gt;o3-mini (medium) 2036&lt;/li&gt;
&lt;li&gt;o1 1891&lt;/li&gt;
&lt;li&gt;o3-mini (low) 1831&lt;/li&gt;
&lt;li&gt;o1-mini 1650&lt;/li&gt;
&lt;li&gt;o1-preview 1258&lt;/li&gt;
&lt;li&gt;GPT-4o 900&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Weirdly, that GPT-4o score was in an older copy of the System Card PDF which has been replaced by an updated document that doesn't mention Codeforces ELO scores at all.&lt;/p&gt;
&lt;p&gt;One note from the System Card that stood out for me concerning intended applications of o3-mini for OpenAI themselves:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We also plan to allow users to use o3-mini to search the internet and summarize the results in ChatGPT. We expect o3-mini to be a useful and safe model for doing this, especially given its performance on the jailbreak and instruction hierarchy evals detailed in Section 4 below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is notable because the existing o1 models on ChatGPT have not yet had access to their web search tool - despite the mixture of search and "reasoning" models having very clear benefits.&lt;/p&gt;
&lt;p&gt;o3-mini does not and &lt;a href="https://twitter.com/nikunjhanda/status/1885415728624656481"&gt;will not&lt;/a&gt; support vision. We will have to wait for future OpenAI reasoning models for that.&lt;/p&gt;
&lt;p&gt;I released &lt;a href="https://llm.datasette.io/en/stable/changelog.html#v0-21"&gt;LLM 0.21&lt;/a&gt; with support for the new model, plus its &lt;code&gt;-o reasoning_effort high&lt;/code&gt; (or &lt;code&gt;medium&lt;/code&gt; or &lt;code&gt;low&lt;/code&gt;) option for tweaking the reasoning effort - details &lt;a href="https://github.com/simonw/llm/issues/728"&gt;in this issue&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Note that the new model is currently only available for &lt;a href="https://platform.openai.com/docs/guides/rate-limits/usage-tiers#tier-3-rate-limits"&gt;Tier 3&lt;/a&gt; and higher users, which requires you to have spent at least $100 on the API.&lt;/p&gt;
&lt;p&gt;o3-mini &lt;a href="https://openai.com/api/pricing/"&gt;is priced&lt;/a&gt; at $1.10/million input tokens, $4.40/million output tokens - less than half the price of GPT-4o (currently $2.50/$10) and massively cheaper than o1 ($15/$60). The GPT-4o comparison isn't quite as simple as that though, as o3-mini's invisible reasoning tokens still count towards the output tokens you get charged for.&lt;/p&gt;
&lt;p&gt;I tried using it to summarize &lt;a href="https://news.ycombinator.com/item?id=42890627"&gt;this conversation about o3-mini on Hacker News&lt;/a&gt;, using &lt;a href="https://til.simonwillison.net/llms/claude-hacker-news-themes#user-content-adding-a--m-model-option"&gt;my hn-summary.sh script&lt;/a&gt;.&lt;/p&gt;

&lt;div class="highlight highlight-source-shell"&gt;&lt;pre&gt;hn-summary.sh 42890627 -o o3-mini&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;Here's &lt;a href="https://gist.github.com/simonw/09e5922be0cbb85894cf05e6d75ae050"&gt;the result&lt;/a&gt; - it used 18,936 input tokens and 2,905 output tokens for a total cost of 3.3612 cents.&lt;/p&gt;

&lt;p&gt;o3-mini (and o1-mini) are text-only models: they don't accept image inputs. The full o1 API model can accept images in the same way as GPT-4o.&lt;/p&gt;

&lt;p&gt;Another characteristic worth noting is o3-mini's token output limit - the measure of how much text it can output in one go.  That's 100,000 tokens, compared to 16,000 for GPT-4o and just 8,000 for both DeepSeek R1 and Claude 3.5.&lt;/p&gt;

&lt;p&gt;Invisible "reasoning tokens" come out of the same budget, so it's likely not possible to have it output the full 100,000.&lt;/p&gt;

&lt;p&gt;The model accepts up to 200,000 tokens of input, an improvement on GPT-4o's 128,000.&lt;/p&gt;

&lt;p&gt;An application where output limits really matter is translation between human languages, where the output can realistically be expected to have a similar length to the input. It will be interesting seeing how well o3-mini works for that, especially given its low price.&lt;/p&gt;
&lt;p&gt;Update: Here's a &lt;a href="https://news.ycombinator.com/item?id=42894215#42895610"&gt;fascinating comment&lt;/a&gt; on this by professional translator Tom Gally on Hacker News:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I just did a test in which both R1 and o3-mini got worse at translation in the latter half of a long text. [...]&lt;/p&gt;
&lt;p&gt;An initial comparison of the output suggested that, while R1 didn’t seem bad, o3-mini produced a writing style closer to what I asked for in the prompt—smoother and more natural English.
But then I noticed that the output length was 5,855 characters for R1, 9,052 characters for o3-mini, and 11,021 characters for my own polished version. Comparing the three translations side-by-side with the original Japanese, I discovered that R1 had omitted entire paragraphs toward the end of the speech, and that o3-mini had switched to a strange abbreviated style (using slashes instead of “and” between noun phrases, for example) toward the end as well. The vanilla versions of ChatGPT, Claude, and Gemini that I ran the same prompt and text through a month ago had had none of those problems.&lt;/p&gt;
&lt;/blockquote&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/projects"&gt;projects&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openai"&gt;openai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm"&gt;llm&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm-pricing"&gt;llm-pricing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm-reasoning"&gt;llm-reasoning&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/o3"&gt;o3&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llm-release"&gt;llm-release&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="projects"/><category term="translation"/><category term="ai"/><category term="openai"/><category term="generative-ai"/><category term="llm"/><category term="llm-pricing"/><category term="llm-reasoning"/><category term="o3"/><category term="llm-release"/></entry><entry><title>Quoting Eric Lehman</title><link href="https://simonwillison.net/2024/Feb/11/eric-lehman/#atom-tag" rel="alternate"/><published>2024-02-11T22:59:38+00:00</published><updated>2024-02-11T22:59:38+00:00</updated><id>https://simonwillison.net/2024/Feb/11/eric-lehman/#atom-tag</id><summary type="html">
    &lt;blockquote cite="https://www.techemails.com/i/141315424/google-engineer-ai-is-a-serious-risk-to-our-business"&gt;&lt;p&gt;One consideration is that such a deep ML system could well be developed outside of Google-- at Microsoft, Baidu, Yandex, Amazon, Apple, or even a startup. My impression is that the Translate team experienced this. Deep ML reset the translation game; past advantages were sort of wiped out. Fortunately, Google's huge investment in deep ML largely paid off, and we excelled in this new game. Nevertheless, our new ML-based translator was still beaten on benchmarks by a small startup. The risk that Google could similarly be beaten in relevance by another company is highlighted by a startling conclusion from BERT: huge amounts of user feedback can be largely replaced by unsupervised learning from raw text. That could have heavy implications for Google.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://www.techemails.com/i/141315424/google-engineer-ai-is-a-serious-risk-to-our-business"&gt;Eric Lehman&lt;/a&gt;, internal Google email in 2018&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bert"&gt;bert&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/machine-learning"&gt;machine-learning&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;&lt;/p&gt;



</summary><category term="bert"/><category term="google"/><category term="machine-learning"/><category term="translation"/><category term="ai"/><category term="generative-ai"/><category term="llms"/></entry><entry><title>Seamless Communication</title><link href="https://simonwillison.net/2023/Dec/1/seamless-communication/#atom-tag" rel="alternate"/><published>2023-12-01T17:01:37+00:00</published><updated>2023-12-01T17:01:37+00:00</updated><id>https://simonwillison.net/2023/Dec/1/seamless-communication/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://ai.meta.com/research/seamless-communication/"&gt;Seamless Communication&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A new “family of AI research models” from Meta AI for speech and text translation. The live demo is particularly worth trying—you can record a short webcam video of yourself speaking and get back the same video with your speech translated into another language.&lt;/p&gt;

&lt;p&gt;The key to it is the new SeamlessM4T v2 model, which supports 101 languages for speech input, 96 Languages for text input/output and 35 languages for speech output. SeamlessM4T-Large v2 is a 9GB file, available on Hugging Face.&lt;/p&gt;

&lt;p&gt;Also in this release: SeamlessExpressive, which “captures certain underexplored aspects of prosody such as speech rate and pauses”—effectively maintaining things like expressed enthusiasm across languages.&lt;/p&gt;

&lt;p&gt;Plus SeamlessStreaming, “a model that can deliver speech and text translations with around two seconds of latency”.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://github.com/facebookresearch/seamless_communication"&gt;facebookresearch/seamless_communication&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/facebook"&gt;facebook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/transformers"&gt;transformers&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;&lt;/p&gt;



</summary><category term="facebook"/><category term="transformers"/><category term="translation"/><category term="ai"/><category term="llms"/></entry><entry><title>Introducing speech-to-text, text-to-speech, and more for 1,100+ languages</title><link href="https://simonwillison.net/2023/May/22/massively-multilingual-speech/#atom-tag" rel="alternate"/><published>2023-05-22T19:22:38+00:00</published><updated>2023-05-22T19:22:38+00:00</updated><id>https://simonwillison.net/2023/May/22/massively-multilingual-speech/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://ai.facebook.com/blog/multilingual-model-speech-recognition/"&gt;Introducing speech-to-text, text-to-speech, and more for 1,100+ languages&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
New from Meta AI: Massively Multilingual Speech. “MMS supports speech-to-text and text-to-speech for 1,107 languages and language identification for over 4,000 languages. [...] Some of these, such as the Tatuyo language, have only a few hundred speakers, and for most of these languages, no prior speech technology exists.”&lt;/p&gt;

&lt;p&gt;It’s licensed CC-BY-NC 4.0 though, so it’s not available for commercial use.&lt;/p&gt;

&lt;p&gt;“In a like-for-like comparison with OpenAI’s Whisper, we found that models trained on the Massively Multilingual Speech data achieve half the word error rate, but Massively Multilingual Speech covers 11 times more languages.”&lt;/p&gt;

&lt;p&gt;The training data was mostly sourced from audio Bible translations.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="https://news.ycombinator.com/item?id=36034211"&gt;Hacker News&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/facebook"&gt;facebook&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/training-data"&gt;training-data&lt;/a&gt;&lt;/p&gt;



</summary><category term="facebook"/><category term="translation"/><category term="ai"/><category term="training-data"/></entry><entry><title>Google Translate (beta)</title><link href="https://simonwillison.net/2007/Jul/3/google/#atom-tag" rel="alternate"/><published>2007-07-03T16:43:19+00:00</published><updated>2007-07-03T16:43:19+00:00</updated><id>https://simonwillison.net/2007/Jul/3/google/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://translate.google.com/translate_t"&gt;Google Translate (beta)&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Google’s beta translator based on statistical analysis of things like the United Nations corpus. I have no idea how long this has been available; it isn’t linked from their homepage.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/i18n"&gt;i18n&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/languages"&gt;languages&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="i18n"/><category term="languages"/><category term="translation"/></entry><entry><title>Django-fr</title><link href="https://simonwillison.net/2007/Jun/21/djangofr/#atom-tag" rel="alternate"/><published>2007-06-21T10:50:16+00:00</published><updated>2007-06-21T10:50:16+00:00</updated><id>https://simonwillison.net/2007/Jun/21/djangofr/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.django-fr.org/"&gt;Django-fr&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Community site for French language Django developers. They’ve already made a promising start on translating the documentation.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/documentation"&gt;documentation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/france"&gt;france&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/french"&gt;french&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;&lt;/p&gt;



</summary><category term="django"/><category term="documentation"/><category term="france"/><category term="french"/><category term="translation"/></entry><entry><title>Comment transformer votre blog en une OpenID ?</title><link href="https://simonwillison.net/2006/Dec/21/french/#atom-tag" rel="alternate"/><published>2006-12-21T15:26:57+00:00</published><updated>2006-12-21T15:26:57+00:00</updated><id>https://simonwillison.net/2006/Dec/21/french/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://xtof.livejournal.com/3305.html"&gt;Comment transformer votre blog en une OpenID ?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
My piece on OpenID tranlated in to French by Christophe Ducamp.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/french"&gt;french&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/translation"&gt;translation&lt;/a&gt;&lt;/p&gt;



</summary><category term="french"/><category term="openid"/><category term="translation"/></entry></feed>