#i18n — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #i18n, aggregated by home.social.
-
Italians, in a business context, what would be a sentence that looks like perfectly normal Italian sentence but is actually an insult?
#languages #linguistic #i18n #l10n #G11n #internationalisation #internationalization #localisation #localization #globalization #globalisation #FollowerPower
-
Oooh, exciting! Keila kommer snart att finnas tillgänglig på svenska! https://github.com/pentacent/keila/pull/571 🇸🇪 🫎 #sverige #svenska #i18n #opensource #buildinpublic
-
Oooh, exciting! Keila kommer snart att finnas tillgänglig på svenska! https://github.com/pentacent/keila/pull/571 🇸🇪 🫎 #sverige #svenska #i18n #opensource #buildinpublic
-
Oooh, exciting! Keila kommer snart att finnas tillgänglig på svenska! https://github.com/pentacent/keila/pull/571 🇸🇪 🫎 #sverige #svenska #i18n #opensource #buildinpublic
-
Oooh, exciting! Keila kommer snart att finnas tillgänglig på svenska! https://github.com/pentacent/keila/pull/571 🇸🇪 🫎 #sverige #svenska #i18n #opensource #buildinpublic
-
📢 New #updates · 9 Sept #6
· Firefly III develop-20260909 — Latest fixes and features in a buggy test release
· teable release.2026-09-09T04-35-35Z.2997 — Improved search and fixed Grid view loading issues
· convex precompiled-2026-09-09-bbca5ed — Added data filters to feedback form
· remark42 v1.17.0 — Fixed stale configuration and contributor docsCheck out more on https://selfhost.directory
-
There are few things I love more than wacky software #i18n localization bugs
#PlannedParenthood promotes a #Facebook post endorsing a candidate in the upcoming #RhodeIsland elections. The image has English text, as you would expect, but the text is in German and Italian.
I don't know why. Facebook's machine translation gone wrong? Human error in ad configuration?
-
There are few things I love more than wacky software #i18n localization bugs
#PlannedParenthood promotes a #Facebook post endorsing a candidate in the upcoming #RhodeIsland elections. The image has English text, as you would expect, but the text is in German and Italian.
I don't know why. Facebook's machine translation gone wrong? Human error in ad configuration?
-
There are few things I love more than wacky software #i18n localization bugs
#PlannedParenthood promotes a #Facebook post endorsing a candidate in the upcoming #RhodeIsland elections. The image has English text, as you would expect, but the text is in German and Italian.
I don't know why. Facebook's machine translation gone wrong? Human error in ad configuration?
-
There are few things I love more than wacky software #i18n localization bugs
#PlannedParenthood promotes a #Facebook post endorsing a candidate in the upcoming #RhodeIsland elections. The image has English text, as you would expect, but the text is in German and Italian.
I don't know why. Facebook's machine translation gone wrong? Human error in ad configuration?
-
There are few things I love more than wacky software #i18n localization bugs
#PlannedParenthood promotes a #Facebook post endorsing a candidate in the upcoming #RhodeIsland elections. The image has English text, as you would expect, but the text is in German and Italian.
I don't know why. Facebook's machine translation gone wrong? Human error in ad configuration?
-
I do the odd bit of translation for #WordPress and its plugins; just from Wronglish (en-US) to English (en-AU|NZ|CA). When I get a chance, I dip in to suggested translations to approve / reject for people who need review.
Last night I discovered that some are using OpenAI or DeepL LLM translations. It's crap.
Cell → Mobile Phone.
Row → argument.
break-all → smash everything.
List Between Space → Inventory Amongst the Stars.Fucksake. We are running towards the precipice.
-
I do the odd bit of translation for #WordPress and its plugins; just from Wronglish (en-US) to English (en-AU|NZ|CA). When I get a chance, I dip in to suggested translations to approve / reject for people who need review.
Last night I discovered that some are using OpenAI or DeepL LLM translations. It's crap.
Cell → Mobile Phone.
Row → argument.
break-all → smash everything.
List Between Space → Inventory Amongst the Stars.Fucksake. We are running towards the precipice.
-
📢 New #updates · 8 Sept #15
· Wekan v11.62
· Bitwarden v2026.8.2 — Fixed route parameter enforcement
· fluxer [email protected] — Added new feature for user authentication
· Wallos v5.6.0 — Added Azerbaijani language and configurable upcoming payment count
· Rundeck v6.2.0
· lightdash 2.167.0
· Olares 1.12.7-20260908Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #10
· Langfuse v4.31.0 — Added analytics and cost tracking to experiments and traces
· Firefly III develop-20260908.3 — Latest fixes translations and features
· fluxer [email protected] — Added new feature for user authentication
· lightdash 2.158.0 — CLI now accepts project slugsMore self-hosted updates → https://selfhost.directory
-
📢 New #updates · 8 Sept #7
· teable release.2026-09-08T06-17-32Z.2983
· Weblate weblate-2026.9.1
· rudderstack v1.86.0Browse everything at https://selfhost.directory
-
📢 New #updates · 8 Sept #6
· Firefly III develop-20260908.1
· teable release.2026-09-08T05-53-30Z.2982
· lightdash 2.151.0
· docker-webtop ubuntu-kde-411f4513-ls178
· webtop fedora-kde-2b0360f2-ls294
· octelium v0.42.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #4
· Firefly III develop-20260908
· teable release.2026-09-08T01-36-21Z.2976
· onecli v2.6.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #2
· Sunshine v2026.907.203631
· teable release.2026-09-07T15-08-33Z.2973
· lightdash 2.150.0
· Directory Lister 5.7.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #2
· Sunshine v2026.907.203631
· teable release.2026-09-07T15-08-33Z.2973
· lightdash 2.150.0
· Directory Lister 5.7.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #2
· Sunshine v2026.907.203631
· teable release.2026-09-07T15-08-33Z.2973
· lightdash 2.150.0
· Directory Lister 5.7.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #2
· Sunshine v2026.907.203631
· teable release.2026-09-07T15-08-33Z.2973
· lightdash 2.150.0
· Directory Lister 5.7.0Check out more on https://selfhost.directory
-
📢 New #updates · 8 Sept #2
· Sunshine v2026.907.203631
· teable release.2026-09-07T15-08-33Z.2973
· lightdash 2.150.0
· Directory Lister 5.7.0Check out more on https://selfhost.directory
-
i18n в Next.js без SEO-дублей, locale в маршрутах, metadata и hreflang
Перевод интерфейса меняет текст, но сам по себе не создаёт отдельную языковую страницу. Один адрес /search/music может показать английский или русский интерфейс в зависимости от client state, cookie или настроек браузера. URL при этом остаётся тем же. Для поисковой индексации языковые версии удобнее разделить адресами:
https://habr.com/ru/articles/1079438/
#nextjs #i18n #seo #typescript #react #app_router #nextintl #hreflang #canonical #server_components
-
i18n в Next.js без SEO-дублей, locale в маршрутах, metadata и hreflang
Перевод интерфейса меняет текст, но сам по себе не создаёт отдельную языковую страницу. Один адрес /search/music может показать английский или русский интерфейс в зависимости от client state, cookie или настроек браузера. URL при этом остаётся тем же. Для поисковой индексации языковые версии удобнее разделить адресами:
https://habr.com/ru/articles/1079438/
#nextjs #i18n #seo #typescript #react #app_router #nextintl #hreflang #canonical #server_components
-
i18n в Next.js без SEO-дублей, locale в маршрутах, metadata и hreflang
Перевод интерфейса меняет текст, но сам по себе не создаёт отдельную языковую страницу. Один адрес /search/music может показать английский или русский интерфейс в зависимости от client state, cookie или настроек браузера. URL при этом остаётся тем же. Для поисковой индексации языковые версии удобнее разделить адресами:
https://habr.com/ru/articles/1079438/
#nextjs #i18n #seo #typescript #react #app_router #nextintl #hreflang #canonical #server_components
-
Устарел ли next-intl? И как реально оптимизировать такую архитектуру
Когда Next.js перешел с Pages Router на App Router и убрал встроенную поддержку i18n-роутинга, библиотека next-intl стала стандартом по умолчанию для большинства команд. Ян Аманн проделал отличную работу по ее поддержке, и долгое время это был самый надежный выбор для мультиязычных проектов.
-
Устарел ли next-intl? И как реально оптимизировать такую архитектуру
Когда Next.js перешел с Pages Router на App Router и убрал встроенную поддержку i18n-роутинга, библиотека next-intl стала стандартом по умолчанию для большинства команд. Ян Аманн проделал отличную работу по ее поддержке, и долгое время это был самый надежный выбор для мультиязычных проектов.
-
Устарел ли next-intl? И как реально оптимизировать такую архитектуру
Когда Next.js перешел с Pages Router на App Router и убрал встроенную поддержку i18n-роутинга, библиотека next-intl стала стандартом по умолчанию для большинства команд. Ян Аманн проделал отличную работу по ее поддержке, и долгое время это был самый надежный выбор для мультиязычных проектов.
-
Looking for testers 🌍
ihasmail's UI now ships in nine languages besides English — de, es, fr, ja, nl, pt-BR, ru, uk, zh-Hans — and I'd like native speakers to check the wording.
No Stalwart server needed use the demo: https://demo.ihasmail.com/
-
Know a second language? You can make GNOME speak your language! Check out Damned Lies, our translation platform for our desktop and various GNOME apps, at https://l10n.gnome.org/, and help make GNOME accessible to everyone in the world, not just English speakers.
-
🇧🇷 The #Brazilian #Portuguese #translation of Back In Time has dropped from ~80% to just 16%.
Why? A batch of low-quality, apparently AI-generated translations had to be reverted. Unfortunately, this means many existing translations now need to be reviewed again.
If you speak Brazilian Portuguese, we'd really appreciate some help getting this translation back on track! 🙏
https://translate.codeberg.org/projects/backintime/-/pt_BR/
#opensource #foss #linux #backup #debian #ubuntu #i18n #l10n
-
Fellow Hungarian devs, please check if the Hungarian localization for Forgejo is broken for you as well. If you are not self-hosting, but using codeberg.org, that also counts. I opened an issue at Forgejo:
-
Status Report 2026-08-29 and Outlook for September\October 2026
Today we released Infinito.Nexus 13.0.0 with integrated Tor and .onion support. The release notes you will find here and the blog article about the functionality here.
https://www.youtube.com/watch?v=6czcc1gZ7Ak
This feature didn’t have a high business value, anyhow it allowed to clean up the architectural base for everything what comes now.
Anyhow here I want to give you insights into the Infinito.Nexus project and what’s planed.
Infinito.Nexus Core >= 14.0.0a
Email Software Replacement
From the current point of view at least 2 Major releases will arrive in the next month. The first one is the substitution of Mailu by Stalwart, implemented by Alejandro. This is necessary due to the deprecation of Mailu itself.
https://www.youtube.com/watch?v=lJqtQG6lmc4&t=24s
The release state and the related discussion you can follow here .
AI Integration
The other release is, let’s call it the “AI” release. Long story short:
Infinito.Nexus will allow the use and the integration of AI, local and external models in almost all SaaS applications. It will also allow the Integration in Software via MCP.Lite LLM
All applications which support AI like OpenWebUI, WordPress, Nextcloud, Matrix etc. will have an inteface which connects to an Lite LLM Gateway. The Lite LLM Gateway will allow the use of local models like Qwen, Gema etc. Besides this it’s possible to integrate OpenRouter or e.g. Anthropic or OpenAI etc.
https://www.youtube.com/watch?v=nQCOTzS5oU0
So enterprises which use Infinito.Nexus can decide by themself if they prefer to use their local AI and models and keep everything on their infrastructure or if they prefer to use external proprietary models.
The customer has the choice about the level of data sovereignty they want to keep and the infrastructure which they want to setup.
MCP
https://youtu.be/eur8dUO9mvE?si=vTJW30tCZz2ZdUD6
The second AI related topic is the integration of MCP into all kind of applications.
It’s already in progress since a few weeks and my agents are working on this 24h. Relevant in this context is the security aspect.
Similar to the Infinito.Nexus 13.0.0 TOR Release, the MCP Release will have a high impact on security and MUST due to this reason be declared as PoC. Why?
In my understanding you can’t easily implement RBAC into MCP clients.
So my current implementation works like this;You have per Infinito.Nexus application two MCP RBAC groups:
- Reader
- Writer
If one is part of the reader group they can read all of the application data via Open WebUI and if one is part of the Writer group they can modify all of the data via Open WebUI.
https://www.youtube.com/watch?v=VNPMl8oOzHU
This is off course highly dangerous. It may makes sense to give people reading rights, but in consequence this means that they can access and utilize all of the users data via an AI.
We don’t have to talk about that this goes against any kind of data protection regulations and is a hard invasion into the privacy of your platform users.
Anyhow there are scenarios in which it may makes sense.
E.g. let’s assume you’re fully virtual organisation and you don’t have humans employed, but instead on your Infinito.Nexus platform just bot and agents account exist;
In this scenario if you have reading and writing rights you’re de facto in the “God Mode” in which you can instantly see what your agents are doing.
An example is if you use it e.g. with AgentCrew (WiP). You can orchestrate Agents and AI on a way you can’t imagine. AgentCrew I will explain in the next paragraphs.
Also if it’s in the current state absolutely not recommended to activate the MCP functionality, it doesn’t mean it must be like this in the future. Like I said currently it’s seen as PoC and the full MCP compatible RBAC implementation isn’t impossible, it just will take a lot of human resources, because for every part of the Infinito.Nexus software we need humans which take responsibility for the code.
“We stay in the loop” – We aren’t controlled by AI, instead we’re the masters. In consequenz this means that the full RBAC MCP will be implemented as soon as we have sufficient customers which request it and developers which can manage it intellectually to implement a clean architectural solution.
i18n
Besides the AI topic there is one key thing missing in the Infinito.Nexus Core Repository, but also in the Store and this is the implementation of the 184 ISO 639-1 into our software solution.
The software was primarily designed with German customers and the debate about digital sovereignty of European and especially German enterprises from American Big Tech in mind. Still some frontend elements like the dashboard just supported English as language.
The implementation of German is off course an hard requirement before it can be distributed and promoted on the DACH market. Actually I figured out that there is a easy design pattern to implement this, so part of the 14/15th major release will also be the support of all 184 ISO 639-1 languages.
Infinito.Nexus Store
Besides the Core development the AI Agents of course worked in the last weeks on implementing the store.
Theoretically the store is ready. Off course there are a few issues but overall I think it’s heading in the right direction.
Somewhere in the next weeks I will release a beta version of the store, but before we use it in production there needs to be a deeper security audit.
The store itself is from my point of view at the current situation the weakest part in the security chain and could be used by attackers as entry point into our system. So I don’t feel confident yet to release it, but I have some ideas in my mind how I can use AI supported attacks against the store to penetrate the system and to find all loopholes.
Besides this the API’s for auto-provisioning of enterprise infrastructure are currently just implemented as mocks.
The reason therefore is again a resource issue on my side. To implement them, do the billing etc. I need people in the back office which take care about the bureaucracy and right now we’re just a bunch of programmers.
So the bottleneck since the start of this project is still to have people in the back office, administration and on the business side which could take over tasks like this. Currently we don’t have anybody for this tasks.
Agentic Projects
Besides Core and Store there are two other IT projects which I want to mention.
AgentBox
The first one is AgentBox. The idea behind AgentBox is to encapsulate the agents which work on your code in an highly isolated environment.
This is necessary due to the reason that the agents are currently working in sandboxes like the one which Claude ships onboard, but they can easily break out. It’s just a question of will.
If the agent decides that they want to break out they can break out and can take control over your system. Due to this reason I’m working on a better cage to keep them isolated. I first will use this as part of the Store aka. GUI repo and as soon as I feel confident I will also “box” all of my other repos.
It will be part of PKGMGR so that I can setup and develop new solutions much faster and much safer then ever before.
AgentCrew
The second one is AgentCrew. AgentCrew addresses the problem, that this project requires a lot of people to run and set up a business.
A few weeks ago, during a chat with Amadeus, we talked about that there are existing frameworks like ITIL, SAFe, etc. which describe in detail how to set up an Enterprise Organisation.
With AgentCrew you decide for a framework, define framework roles, characters and the related LLM to use. All people which are normally human beings are replaced by an agent and they will take over the roles.
Due to the reason that not all of the roles need the same capabilities it’s possible to give some agents lower models and other agents better models. In kombination with OpenRouter and local LLM’s you can scale up an organisation for very low costs.
The advantage for us as Infinito.Nexus team is, that we developed the infrastructure tool to give every agent their own account with all tools which they need. Let it be developing tools like gitea\GitLab\jenkins, project management tools like Taiga\OpenProject, cloud access via Nextcloud etc.
Infinito.Nexus can be the base to setup fully autonom working agentic teams.
I will focus on AgentCrew as soon as the store is ready, because then we need urgently agents in the back office, distribution etc.
Business Strategy
The strategy stays the following; The focus is on finishing the core like mentioned above.
Parallel the development of the store continous.
As soon as the store is ready I will contact all people in our CRM system.
Besides this is would be good to get some low level investment. We have now a ready product. A little money as an catalyst to enlighten the engine for digital sovereignty would make our life much easier, but it will also work without it.
The advantage which we have is that as soon as the store is standing and the API’s are integrated we have an scalable product with almost non fix costs, so we can beat all of our competitors by price.
Besides this it’s almost impossible that a real competitor raises.
And now you ask me the question:
Why? Kevin hadn’t you been an hypocrat? Didn’t you tough in your position as agile coach that you find customers and develop a project dependent on their needs and scale up your business by realizing what your customer needs from you?
I can tell you it would had been impossible.
If we would have customers already, we couldn’t had developed an clean architectural solution. We would had acquired a huge amount of technical debt due to the reason that we would had been required to maintain outdated infrastructure and couldn’t implement the radical architectural design which was necessary to implement a tool which can compete in the times of AI with the other companies.
A lot of businesses will fail in the next month and years. The reason therefore is that they vibe coded bad software which is unmaintainable. Our solution is as well designed as as Rolex and usable like a Swiss Pocket Knife.
I don’t know any other software company which delivers such an high quality like we’re doing and we can dump the price almost as low as we like.
Vibe Coding and Agentic Engineering
https://www.youtube.com/watch?v=PbsocBPkoUc
One last sentence I would like to mention concerning vibe coding and agentic engineering and how I apply both practices. So you have an idea how I could realize such an project.
I would say in general I use classical software engineering practices.
- Writing well defined requirements documents\ADR witch AC
- Writing test for them
- Let the AI iterate against the tests until all of them pass
The AI works in general autonomously. I inspect the code before commiting and steer the AI in the right direction.
With a lot of the implementations I don’t have any glue at the beginning of the feature how to realize this exactly. This counts e.g. for the docker swarm implementation, the tor implementation, but also the current MCP implementation.
So I let the AI turn wild but I question critically the output and the modifications. The most of the time I have at least 3 agents parallel running which are working on different topics.
Still I need to review all of the code and I feel responsible to understand what the agents are doing. I have the final say about the best approach.
This means that in the last month I still had my 16 hour days just reviewing, deciding and understanding what’s going on, besides that the AI is working parallel 24/7.
I really look forward to the point when this isn’t my daily business anymore.
I hope anybody who is interested in it has now a betting understanding where the project stands, what final challenges have to be tackled and where we will stand in approx. 2 month.
#AcceptanceCriteria #ADR #agentIsolation #AgentBox #AgentCrew #agenticEngineering #agenticTeams #AIAgents #AIGovernance #AIOrchestration #AIPenetrationTesting #AISecurity #AIWorkforce #AIAssistedSoftwareDevelopment #AINativeCompany #AINativeSoftwareDevelopment #architectureDecisionRecords #automatedProvisioning #autonomousAgents #autonomousEnterprise #autonomousOrganizations #cleanArchitecture #Cybersecurity #DACH #DevOps #digitalInfrastructure #DigitalSovereignty #digitalSovereigntyPlatform #DockerSwarm #enterpriseAutomation #enterpriseInfrastructure #EuropeanDigitalSovereignty #futureOfWork #Gitea #Gitlab #heterogeneousLLMs #humanInTheLoop #humanOversight #i18n #InfinitoNexus #InfinitoNexusStore #InfrastructureAsCode #infrastructureAutomation #internationalization #ISO6391 #ITIL #Jenkins #LLMOrchestration #localLLMs #localization #lowCostInfrastructure #MCP #MCPRBAC #MCPSecurity #ModelContextProtocol #multiAgentSystems #multilingualSoftware #Nextcloud #OpenSource #openSourceBusiness #OpenProject #OpenRouter #penetrationTesting #PKGMGR #platformEngineering #privateCloud #roleBasedAccessControl #SaaS #SAFe #sandboxing #scalableBusiness #scalableInfrastructure #secureAIAgents #securityAudit #SelfHosting #softwareArchitecture #softwareEngineering #softwareMarketplace #Taiga #TDD #technicalDebt #TestDrivenDevelopment #Tor #vibeCoding #virtualOrganizations #zeroTrust -
Good :blobnomcookie:
#iOS #iOSdev #Mastodon #fediverse #opensource #l10n #i18n #UI
-
EDIT : c'est bon, j'ai eu suffisamment de retours, plus besoin de partager, merci tout le monde !
Hello le Fédi des #devWeb !
Je cherche à recruter une presta sur un outil d'aide à la décision développé dans le cadre d'un projet de recherche publique.L'outil est ici : https://outil-cafe.fr
Et le code là : https://codeberg.org/tfardet/CAFE (c'est #Vite et #preact pour le front et du python avec #FastAPI pour le back)Il y aurait trois choses principales que j'aimerais faire (rangées par priorité décroissante) :
1. passer le site en multilingue pour avoir une version en anglais
2. supprimer tailwindcss pour avoir du CSS propre à travers le site
3. limiter le contenu qui dépend de preact, en transformant une partie des conteneurs react en template html, de sorte que la majeure partie de la page d'accueil et les pages support (doc, FAQ...) n'ait pas besoin de javascript pour charger
La priorité très claire, pour moi c'est vraiment le point 1, donc je cherche avant tout une personne qui puisse travailler là-dessus, les autres points sont appréciés mais pas centraux.
Je précise également que je veux du code "à l'ancienne", garanti sans IAg 😉
Côté deadline, il faut nécessairement que ce soit avant la fin de l'année parce que sinon mes sous repartent...#jeRecrute #getFediHired #presta #prestation #i18n #internationalization #webDev
-
Good :blobnomcookie:
#opensource #ios #iosdev #lemmy #mlem #fediverse #l10n #i18n
-
Локализация уже скомпилированных React компонентов в node_modules
🇧🇷 🇨🇳 🇮🇳 Локализуем React не трогая код компонентов React-компоненты из node_modules уже скомпилированы, поэтому внедрить react-i18next в них обычно невозможно без форка библиотеки. В статье показываю, как перехватить все вызовы jsx/jsxs через кастомный react/jsx-runtime и автоматически локализовать текст даже внутри уже собранных компонентов, не меняя их исходный код.
https://habr.com/ru/articles/1058286/
#i18n #i18next #локализация #интернационализация #react #typescript #javascript #vite #бандлер #переводы
-
Dear translators and localizers,
If you have time during this summer, please join in to translate #MATE Desktop on Translate Fedora :blobheart:
Weblate : https://translate.fedoraproject.org/projects/mate-desktop/
Save the link or bookmark this toot 🎺
-
This thing here is something the #GNOME project always did; I'm glad gettext is helping making it default behavior:
"In a po/ directory, the PO files are now exactly those that the translators submitted or committed in version control, or a translation project's daemon committed on behalf of the translators. They are no longer regularly updated with respect to the POT file in the same directory."
-
As a #RDataTable translator and, more importantly, as a former #GNOME translator, I'm happy with the 1.0 release of gettext, an incredibly good internationalization and localization toolkit. If your software project is not using gettext yet, do consider changing that.
https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00007.html
+
-
Explore a classic DebConf5 talk: Denis Barbier shows how to customize GNU libc locale files — great for sysadmins, i18n enthusiasts, and anyone tweaking glibc. Retro tech knowledge worth revisiting! #GNU #glibc #locales #Linux #DebConf #i18n #opensource #English
https://friprogramvarusyndikatet.tv/videos/watch/499f76b2-37e4-489a-b100-5fa41a444a68 -
aha okei, Mastodonissa postauksen oletuskieli vaihtuu käyttöliittymän kielen vaihtamalla? Aivot räjähtää :mindblown:
Oon tätä vastaan tapellut noin 20 vuotta eli siitä asti, kun aloitin Drupalin (versio 5.0) käytön ja monikielisten saittien kanssa puuhailun.
Käyttöliittymä on yksi kieli.
Sisältö on toinen kieli.
Järjestelmästä riippuen myös konfiguraatio saattaa olla kolmannella kielellä.Ne. On. Eri. Asioita.
EDIT: Olin väärässä.
-
This is a dumb mistake based on a decision by someone who doesn't use locales and doesn't understand what they're for. Presumably this will get fixed at some point.
But it is just the installer. You should be able to change your timezone and locale settings after install without this restriction. Not ideal for techies, and a blocker for Linux newbies, so the installer definitely should get this fixed.
-
“The Best – But Not Good – Way To Limit String Length”, Adam Pritchard (https://adam-p.ca/blog/2025/04/string-length/).
On HN: https://news.ycombinator.com/item?id=43850398
#Programming #PLDI #Strings #Length #Unicode #Characters #Bytes #Graphemes #UTF #CodePoints #I18N #Internationalization
-
Are you struggling with managing huge i18n configurations for multiple languages? I have a tool just for that and I am looking to open source it and deploy a demo, which could be used for testing - no data safety included, would you be interested?
