International translations: who can help?

[henmedia]

layerling is available in English and German today. Thanks to everyone who offered to help with more languages: this is the place to collect them.

Who is on board so far

• Russian: @CjCrash (pull request feat(web): Russian interface and guide #124)
• Dutch: @rmpel and @rjacobs1969
• Spanish and Catalan: @rjacobs1969

How it will work

• Every language needs native speakers who can read each other's work, so a language only goes in when at least two people have looked at it. Spanish and Catalan still need a second reader.
• The language selector in the app is a row of buttons and will not hold many more languages. Before more languages go in, I'll change it into a list.
• A text that is not translated yet falls back to English instead of showing an empty label.
• The guide screenshots are shared between languages, please don't add copies of them.

What I'd like to know

• Do you speak another widely used language and would like to help translate or review it?
• Is there a language you would like to see, even if you can't translate it yourself?

Nothing is decided on a date. I'll post here when we start.

[gogades]

I speak French, I could at least review it.

[ZelTroN-2k3]

Je vous partage mon GitHub: https://github.com/ZelTroN-2k3/layerling-1.7x.x Version 1.72.3 je suis actuellement sur la mis a jour de la version 1.74.0 je partagerai cette version Multilingue EN/DE/NL/FR/PL/RU

[henmedia]

@ZelTroN-2k3, thank you. Your repository is a copy of the whole of layerling, not a fork, so GitHub cannot make a pull request from it. For @gogades to read your French the usual way, it needs a pull request that holds only the French files: messages.fr.ts, the entry in languages.ts, one line in i18n.ts and the folder docs/guide/fr/. The simplest way: on the repository click Fork, put those files into your fork (the web editor with the . key works), and open a pull request. Start from the current version, 1.74.0: npm run i18n:status -- fr shows what is still missing. @gogades, once the pull request is there you can read it in it.

[henmedia]

@ZelTroN-2k3, thank you for keeping up with 1.74.0. A repository that is a copy of the whole of layerling still cannot become a pull request, so @gogades cannot read the French in it. There are two ways:

1. You make the pull request: click Fork on henmedia/layerling, copy only your French files into a branch of the fork (apps/web/src/lib/messages.fr.ts, the folder docs/guide/fr/, the entry in languages.ts and the line in i18n.ts) and GitHub offers Open pull request.
2. I do it: if that is too much, say here that I may take messages.fr.ts and docs/guide/fr/ from your repository (both AGPL-3.0 like layerling), and I will open the pull request with your name as co-author, so @gogades can read it.

En bref : un dépôt qui est une copie complète ne peut pas devenir une pull request. Soit vous faites un Fork et ne mettez que les fichiers français, soit vous me dites ici que je peux reprendre messages.fr.ts et docs/guide/fr/ de votre dépôt, et j'ouvre la pull request avec vous comme co-auteur.

[ZelTroN-2k3]

J'au crée la Pull Request vers le dépôt officiel #368

[henmedia]

@ZelTroN-2k3, thank you, I have it and answered in the pull request. @gogades, here is the pull request with the French, you can read it there: #368

[welyson1]

Hello, as instructed, I am posting here to express my interest in translating this into Brazilian Portuguese, and I am waiting for another collaborator for this task.

[lmagalhaes]

Hi all! Since @rustammesquita offered to help as well, I've opened a pull request with the interface translation so it can start being read: #672. @marcome1701, @rustammesquita, any comments there on what sounds off are very welcome. @welyson1, if you have your own version, we can still compare the two there. 🙂

For the guide (17 chapters), maybe each of us says here which ones we'd like to take, so nobody does the same work twice? I can start with 01 (Getting started) and 05 (Solids and holes).

[henmedia]

@lmagalhaes thank you. The interface is merged and comes with the next release, so the reading can happen right there in layerling. Splitting the guide by chapter is a good idea: one pull request per chapter or two is easiest to read, and a chapter that is not translated yet simply shows in English.

@rustammesquita welcome, and thank you for offering. Reading the interface once it is out, or taking a few guide chapters, would both help. If you'd like to support layerling in another way, a small donation is always welcome too. 🙂

[rustammesquita]

Great! I'll start with a read in the entire interface then I'll take some chapters in the guide.
I just realize the "New since your last visit" is not entirely in portuguese, but the same happens in other languages so I'm checking if there's a bug report for this already.

[henmedia]

@rustammesquita thank you for reading it! That one is not a bug: the "New since your last visit" cards are written by hand for every release, in English and German, and a language without its own text shows the English one. Any language can have its own, though: in apps/web/src/lib/whatsNew.json each card has its title and text per language, so a "pt-br" entry beside "en" is all it takes. The cards of the coming release are in docs/whatsNew-unreleased.json. If you'd like to add Portuguese there, a pull request is welcome, but the interface and the guide matter more.

[lmagalhaes]

Atualização rápida sobre o português do Brasil, caso alguém queira acompanhar:

• Translate guide chapter 01 into Brazilian Portuguese #712: capítulo 01 do guia (Primeiros passos)
• Tidy up Brazilian Portuguese wording in the interface #714: pequenos ajustes de redação na interface
• O capítulo 05 (Sólidos e orifícios) é o próximo; abro o PR dele depois da próxima versão.

Comentários sobre qualquer coisa que soe estranha são muito bem-vindos, direto nos PRs. @macgldesign obrigado por se oferecer! O jeito mais fácil de ajudar é abrir um desses PRs, ir em "Files changed" e deixar um comentário em qualquer linha que não pareça natural. Não precisa instalar nada. 🙂

[henmedia]

The groundwork for more languages is out in 1.67.2. The language choice is a list now, and a new language no longer needs changes all over the code: it is an entry in one table, a messages file and a folder for the guide. A language does not have to be finished to start. What is not translated yet shows in English, in the interface and in the guide, so you can begin with a few hundred sentences and one chapter. Having two people who speak the language read it before it goes into a release is a strong wish, not a rule. How to add a language is in TRANSLATING.md, and npm run i18n:status shows where a language stands. @CjCrash, your Russian pull request will need to move onto this structure; that is yours to do whenever you like.

[cyryllo]

Hi! I'm working on a Polish translation of layerling (pl), following docs/TRANSLATING.md.

Current state:

• pl registered in languages.ts (complete: false, numberLocale pl-PL, guide folder instrukcja)
• loader added to LOADERS in i18n.ts, so Polish is fetched only when chosen
• messages.pl.ts: about 37% of the interface translated so far (843 / 2299), the rest falls back to English
• npm run i18n:status, npm run typecheck and npm test all pass

I'd like to finish the interface first and open the pull request once it is complete or close to it, so Polish browsers don't land in a half-translated UI. The guide chapters will come after that.

Terminology follows the Polish Tinkercad where they overlap (bryła, otwór, płaszczyzna robocza), so people switching from it feel at home.

One note: Polish has three plural forms (1 projekt, 2 projekty, 5 projektów), and the catalogue has one sentence per count, so for now I use a neutral form like "Projekty: {count}". If plural support is ever planned, Polish would benefit from it.

If anyone else speaks Polish and would like to be the second reader, let me know here.

Cyryl

[henmedia]

@cyryllo thank you, that is a great start, and the way you go about it is just right. The neutral form ("Projekty: {count}") is the way to go for now: the catalogue has one sentence per count.

Please keep working on the interface and finish it first. A language is picked from the browser, so as soon as Polish is in the list, every visitor with a Polish browser lands in it. That is why I'd like to merge it when it is complete or close to it, and when a second person has read it. I'll leave #307 open until then.

[Henrikth12]

I would like to participate with the Danish language.

[henmedia]

@Henrikth12, thank you, the pull request arrived and I merged it. All 2,449 sentences and the 16 chapters are there.

Two small things I did on my side: the entry for Danish in languages.ts was not part of the pull request (it was only on your fork), so I added it from your earlier branch; and in chapter 06 the picture was called hollow-resultat, but the pictures keep their English names, so it is hollow-result now.

I set complete to false for now. That means sentences added later show in English until their Danish follows, so a release never waits for it. A small pull request with the new sentences is all it takes, and npm run i18n:status -- da lists them. If you want it marked complete later, say so.

One question: the word for the legal page is "Impressum" in your entry, which is the German word. Is there a Danish word that fits better?

[henmedia]

@Henrikth12, Danish is in 1.80.0. It is chosen automatically for a browser set to Danish and can be picked in the language list. Reload the page to get it; the installed app needs a restart. If you see a wrong word in the program, a small pull request fixes it. I am still curious about the word for the legal page instead of "Impressum".

[Henrikth12]

It would be something like "About Us" but in danish "Impressum" is widely used by a lot of companies as well, because it's an internationaly wide known word and almost everybody knows what it is, I would leave it like it is..

[henmedia]

@Henrikth12, thank you, then "Impressum" stays. And thank you again for the whole Danish translation.

[Henrikth12]

@henmedia Created a bug repport on som unexpected behavior with a translation i the shapes group.

[brauwers1981]

I can help with the Dutch translations.

[rmpel]

excellent, Thank you!

I'll be posting my first draft later tonight, will let you know once the PR is ready for review/refinement

[rmpel]

Decided to PR early as it is a lot to review, and did not want to make you wait forme to finally finish, while you (or anyone else, of course) can review in parallel.

#312

[yokobond]

I'm a native Japanese speaker, and I use TinkerCAD and Fusion frequently in education. I'd love to help translate Layerling into Japanese.

[henmedia]

@yokobond, thank you, noted for Japanese. It is best if a second person who speaks Japanese reads it before it goes into a release, but that is nice to have, not a must; if you know someone, ask them to write here too. How to start is in TRANSLATING.md: you can begin with a few hundred sentences and one chapter of the guide, and whatever is not translated yet shows in English. npm run i18n:status shows where a language stands.

[champierre]

@yokobond introduced me as someone who could help with the Japanese translation. I'm a software engineer, and we work together at a university lab focused on STEAM education. I'd be happy to join as a second translator.

[henmedia]

@champierre, thank you, noted for Japanese: with @yokobond you are two people who can read each other's work, which is what a language needs before it goes into a release. How to start is in TRANSLATING.md: you can begin with a few hundred sentences and one chapter of the guide, and whatever is not translated yet shows in English. The Dutch pull request #312 shows which files a language needs, and npm run i18n:status shows where a language stands. Start from the current version, 1.74.0.

[yokobond]

@henmedia, a note on Japanese before the translation arrives: #523 adds Japanese text.

• It is opened from the tukumanalab account, our lab's fork, but it is the work of @yokobond and @champierre.
• Japanese needs it first: the built-in typefaces have no kana or kanji, so a Japanese name on a text or a name tag, the default name tag of a Japanese interface among them, comes out as question marks without it. It would be good to merge it before the translation.
• The Japanese translation itself (the interface and the guide) will come as a separate pull request, following TRANSLATING.md.

[henmedia]

@yokobond, thank you for the note, and for the work on the typeface. #523 is merged, so it is in before the translation. It comes with the next release: a Japanese name on a text or a name tag then shows in Japanese letters instead of question marks. When the translation is ready, a pull request following TRANSLATING.md is the way, and npm run i18n:status shows where it stands.

[henmedia]

Dutch is in: 1.71.0 has the whole interface, the 16 chapters of the guide and the README in Dutch. Many thanks to @rmpel, who made it, and @brauwers1981, who offered to read it through. It is the first language that was added the way TRANSLATING.md describes, so it is a good model if you want to see what a finished language looks like - including the names of the guide's chapters in its own language, which the page now explains. Wrong words in Dutch, or in any language that is there, are fixed with a small pull request.

For the languages that are on their way - @cyryllo with Polish, @Henrikth12 with Danish, @yokobond with Japanese, @welyson1 with Brazilian Portuguese - nothing changes: start whenever you like, and a language goes in when it is complete or close to it.

[rmpel]

Excellent :) I have started an external review ;) I asked my dad (82, Dutch only, TinkerCAD user) to take a look.

[maxciava]

Hi, I can help with the Italian translation.

[henmedia]

@maxciava, thank you, noted for Italian. It is best if a second person who speaks Italian reads it before it goes into a release, but that is nice to have, not a must; if you know someone, ask them to write here too. How to start is in TRANSLATING.md: you can begin with a few hundred sentences and one chapter of the guide, and whatever is not translated yet shows in English. The Dutch pull request #312 shows which files a language needs.

[plazmabokor]

Hungarian: I'd like to translate layerling into Hungarian; I'm a native speaker. There is demand for it: layerling already has a big following in Hungary. I'd go about it as @cyryllo does with Polish: following TRANSLATING.md, the interface first and the pull request when it is complete or close to it, the guide after that.

One point that is special to Hungarian: it puts case endings on words (a logó → a logót, 3 címke → 3 címkét), and the ending depends on the word. So where a {name} or {count} would need one, I'll word the sentence so that the placeholder stands on its own, like the neutral form you suggested for Polish.

If anyone else speaks Hungarian and would like to be the second reader, please say so here.

[henmedia]

@plazmabokor, thank you, noted for Hungarian. Following TRANSLATING.md and doing the interface first is just right, and so is the neutral form: with {name} or {count} standing on its own, an ending never has to be added to a placeholder. A language goes in when it is complete or close to it and a second person who speaks it has read it; that is nice to have, not a must. Start from the current version, 1.74.0: npm run i18n:status shows where a language stands. If another Hungarian speaker wants to be the second reader, they can write here.

[gms004a]

I speak/write fluent Polish. Can help

[henmedia]

@gms004a, thank you, noted for Polish. @cyryllo is making the Polish translation and asked for a second person who reads it, so you two can read each other's work. Start from the current version, 1.76.0; npm run i18n:status -- pl shows where Polish stands.

[murartdursun25]

layerling-turkce.zip
Hi! I'd like to contribute a Turkish (Türkçe) translation of the interface.

The attached ZIP contains:

• apps/web/src/lib/messages.tr.ts – all 2547 interface sentences in Turkish
• the "tr" entry in languages.ts (complete: false, guideDir "kilavuz") and the loader line in i18n.ts
• turkce-ceviri.patch – the same change as a git patch against v1.86.2

Checked with: npm run i18n:status (tr 2547/2547, no problems), npm run typecheck, npm test (all passing). The user guide chapters are not translated yet, so they fall back to English.

The translation was made with the help of an AI assistant (Claude). I'm a native Turkish speaker and I'm using it on my own copy now; a second Turkish reader would be very welcome, as TRANSLATING.md suggests.

Thank you for layerling!

[henmedia]

@murartdursun25, thank you, a Turkish interface is very welcome, and it is good to know that you are a native speaker. The easiest way to get it in is a pull request: you already have the change as a patch against v1.86.2, so fork the repository, apply the patch (git apply turkce-ceviri.patch), push it and open a pull request here. That way your name stays with the commit, and the automatic checks run on it. A guide that is not translated yet falls back to English, and complete: false is the right setting for now. A second Turkish reader is welcome but not a condition; if someone here reads Turkish, please say so below.

[ryd2jcwd2c-afk]

Hello Stefan!

I would love to see Swedish added as a language option in Layerling, if possible. I am a Swedish user interested in 3D modelling and 3D printing, and a Swedish interface would make the program much easier for me to use.

Thank you for developing Layerling!

Best regards,
Hasse from Sweden

[henmedia]

@ryd2jcwd2c-afk, thank you, and nice to hear from Sweden. There is no Swedish translation yet, and I can't write it myself at the quality it needs. It has to come from someone who speaks Swedish. If you or someone you know would like to do it, TRANSLATING.md in the repository explains how: the interface is about 2500 sentences, and npm run i18n:status shows where a language stands. A language goes in when it is complete or close to it, and a second person who speaks it has read it. If someone here reads Swedish and wants to help, please write below.

[ryd2jcwd2c-afk]

Hi Stefan!

Thank you for your kind reply!

I completely understand that the translation needs to be of high quality and reviewed by another Swedish speaker.

Unfortunately, translating 2,500 sentences would be too big a task for me, but I hope someone in the Swedish community will be interested in helping.

I look forward to using Layerling, and I think a Swedish version would be wonderful for users like me.

Thank you for your work on Layerling!

Best regards,
Hasse from Sweden

[marcome1701]

Sim eu posso conferir o que foi traduzido, meu inglês não é bom mas eu ajudo usando tradutor. Enviado do meu iPhoneEm 18 de out. de 2026, à(s) 09:13, Stefan ***@***.***> escreveu: @marcome1701 obrigado pela mensagem, e por querer divulgar o layerling entre os amigos que usam o Tinkercad. Ainda não existe uma tradução para o português. @welyson1 se ofereceu para traduzir para o português do Brasil e espera uma segunda pessoa que leia o trabalho dele. O que ainda não estiver traduzido aparece em inglês, então dá para começar aos poucos; como começar está em TRANSLATING.md. Se você fala português e quiser ajudar, traduzindo uma parte ou lendo o que o @welyson1 fizer, escreva aqui. Se o layerling for útil para você, você pode apoiá-lo aqui: https://layerling.com/support.html —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[macgldesign]

Sou Brasileiro, posso ajudar revisando.
Só preciso de instruções pois ainda não entendi muito bem como funciona para colaborar. 😅

[henmedia]

@macgldesign obrigado, e bem-vindo! O caminho que o @lmagalhaes descreveu é o certo: abra o #712 ou o #714, vá em "Files changed" e comente em qualquer linha que soe estranha. Os dois já estão aceitos aqui e saem com a próxima versão, então sua leitura entra direto.

[marcome1701]

Sem problema, sou Brasileiro nato. Aguardo…Enviado do meu iPhoneEm 18 de out. de 2026, à(s) 16:23, Stefan ***@***.***> escreveu: @marcome1701 obrigado, isso ajuda muito: uma segunda pessoa que leia o trabalho é exatamente o que falta. @welyson1 ainda não publicou a tradução; quando ele abrir o pull request, você poderá lê-lo lá. Um tradutor automático ajuda, mas o importante é que você diga se as frases soam naturais em português do Brasil. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[Rodold]

Hola quisiera ayudar con la segunda lectura del idioma español si es que aún hace falta, es mi idioma nativo, nací y vivo en Argentina, saludos.

[henmedia]

@Rodold ¡gracias, y bienvenido! Lo anoto para el español. Todavía no hay una traducción al español: @rjacobs1969 se ofreció al principio, pero aún no ha llegado ninguna. Así que hace falta primero alguien que la haga, y luego una segunda persona que la lea.

Si te apetece empezarla tú, aquí está cómo funciona: TRANSLATING.md. Lo mejor es empezar por la interfaz, la guía puede venir después. Y si otra persona la empieza, te aviso aquí para que la leas.

Si quieres apoyar el proyecto, una pequeña donación es muy bienvenida: https://layerling.com/support.html