Little spinoff library from one of my projects: `go-gettext`! Want to use GNU #gettext in #Go , e.g. to do i18n in your GTK app, but without using CGo? Then this might be helpful to you :) https://github.com/pojntfx/go-gettext

GitHub - pojntfx/go-gettext: G...

Little spinoff library from one of my projects: `go-gettext`!

Want to use GNU #gettext in #Go, e.g. to do i18n in your GTK app, but without using CGo? Then this might be helpful to you :)

https://github.com/pojntfx/go-gettext

potodo 0.25 released last Friday! A number of quality of life improvements inside 🫡 Thank you @mdk for the release! #i18n #gettext

https://git.afpy.org/AFPy/potodo#release-history

Learning a bit more every day. #til
Here is a piece of #django or better #gettext, #Django is just the user.

{% trans "Series" context "singular" %}

The "context ..." is a contextual marker [1].
Here I need it because the word "Series" in german (and other language) has a different translation for singular and plural, so I explicitly pass it a context that I will get in my .po file. Now I can differentiate

Series => Serie (singular)
Series => Serien (plural)

[1] https://docs.djangoproject.com/en/5.2/topics/i18n/translation/#contextual-markers

Just discussed it with a friend and shared that I am quite rigorous on doing translations in a certain way.
One example is the last change, read the commit message:

Don't do any simple string translations like "in" which totally miss all context, they will go wrong in some language. Use "in $location" now, so one can see the context what the "in" is meant to be for.

#i18n #django #gettext #goodcode

I was always struggling with wrapping in GNU #gettext PO files; #Django ./manage.py makemessages does it one way, Poedit.app does it differently. To avoid dirty Git diffs, I used to re-wrap the strings by hand this whole time... until TIL that you can just use msgcat without arguments :neocat_facepalm:

msgcat -o django.po django.po

To re-wrap all PO files:

fd -epo . -x msgcat -o '{}' '{}'

Gettext is adding support for custom flags in PO files! 🎉

The intention it to make it easier to handle workflows like AI pretranslation, review/approval, or project-specific checks — all while keeping flags reliably stored. ✨

Details: https://lists.gnu.org/archive/html/bug-gettext/2025-06/msg00018.html

#gnu #gettext #gnugettext #i18n #l10n #internationalization #localization #translation #FOSS

What are the modern tools available for #translation #po files? #gettext I specially want to know about how to find suggestions from all the previous work done in many other project's po files. I can clone those repos somewhere locally, but is there any way to find suggestion from existing translations? #l10n #localization

cl-po-parser is a Common Lisp package for parsing a GNU Gettext po file.

https://github.com/veer66/cl-po-parser

#commonlisp #po #gettext

#taidan is now #gettext free
full migration to #fluent ​:ablobcatattentionreverse:​

#ultramarinelinux #rust #foss #linux

News in my #guile minimal #gettext run-time for static (expand-time) #i18n!
The API changed: there is now only 1 macro with keyword arguments, which does not update PO files by default.
Your PO files now have scheme-format and range flags, and translator comments!
I now parse PO files directly and not MO files anymore.
The next step is to show how to use this with #Hoot (the license also changed to AGPL).
https://labo.planete-kraus.eu/guile-static-i18n.git/tree/example.scm

Looks like actually using gettext takes a bit too much steps for my liking for a few simple Guile scripts I wrote. The example was using automake, which certainly didn’t help 🤷

#lang_en #gettext #guile

I don’t know how you feel about it, but I find #hoot very interesting. There’s a problem though: you can’t do #i18n (internationalization). In #guile, you would use the #gettext library, but since its run-time is written in C and relies on the file system, it’s a bit inconvenient to use in Hoot.
I present to you my static-i18n library: it provides translations at compile-time and so it does not need the gettext runtime.
https://labo.planete-kraus.eu/guile-static-i18n.git/

It was more work than I hoped for, but I finally moved #Lazarr! from #Luanti's legacy TR format to the superior #gettext PO format and added the missing level names and level hints to #Codeberg Translate (#Weblate).

#GameDev #translation

With #Luanti (formerly #Minetest) version 5.10 out, games can finally use the #gettext PO format natively.

I've recently updated #Repixture to use this format, which makes the translation process much simpler. Previously, I had to use a hacky Python script to convert between formats before I could upload the texts to Weblate. Now it can be used natively.

▶️ Repixture translations: https://translate.codeberg.org/projects/repixture/

#GameDev #translation

Перевод CLI-приложения на Python: локализация click и typer с GNU gettext

Для регистрации ПО в реестре Минцифры России нужно соблюсти несколько условий, одно из них — наличие русского языка на сайте и в документах. И хотя требований к языку в самом программном обеспечении я не нашёл (может быть, пока), но задача по русификации интерфейса появилась. Мы в «Тантор Лабс» развиваем корпоративную платформу баз данных Tantor XData, один из её компонентов — CLI (интерфейс командной строки) на Python с библиотекой Typer , которая, в свою очередь, написана поверх Click . Этот инструмент мы и попробуем русифицировать, а в идеале — научимся переводить приложение на разные языки, если потребуется. В статье рассмотрим концепции и инструменты, применяемые для локализации, включая использование библиотеки gettext в Python, а также стандарты, предоставляемые GNU gettext . Разберём работу с .pot , .po и .mo файлами, а также обработку плюральных форм, учитывающих языковые особенности множественных чисел.

https://habr.com/ru/companies/astralinux/articles/861814/

#python #gettext #typer #click #локализация #локализация_интерфейса #cli

Excited about #C17, #gettext, and #Make 😍; good riddance to the “newline in file-name” charade 😒:

“What’s New In POSIX 2024 – XCU”, Chloe Kudryavtsev (https://blog.toast.cafe/posix2024-xcu).

Via HN: https://news.ycombinator.com/item?id=41978197

On Lobsters: https://lobste.rs/s/puq8jd/what_s_new_posix_2024_xcu

#POSIX #Unix #Standards

Good .po #gettext editor for #Windows ? #translation

@Minetest #gettext support to me personally is the killer feature of this update! 👍

Just pushed version 3.0.0 of #Kielet, my GNU #Gettext package for #Gleam: https://hexdocs.pm/kielet/index.html

This release brings support for pgettext and npgettext, which are used to provide context and disambiguate translations of words that are written identically but need different translations, such as homographs.

I considered adding dgettext and dcgettext and all their variations, but they don't seem to provide enough benefit in Gleam.