
I’ve published a string freeze announcement for #Fretboard and #Keypunch:
https://discourse.gnome.org/t/upcoming-keypunch-and-fretboard-releases/27773?u=bragefuglseth
They will both get new releases in two weeks.

I’ve published a string freeze announcement for #Fretboard and #Keypunch:
https://discourse.gnome.org/t/upcoming-keypunch-and-fretboard-releases/27773?u=bragefuglseth
They will both get new releases in two weeks.
Help us test internationalization for Fedora 42! Testing is running from Mar 4-10.
https://fedoramagazine.org/contribute-at-the-fedora-linux-42-i18n-test-week/
Speaking of "tail -c". There is a lot one could say about how complicated Unicode in general and UTF-8 in particular are. But it's also easy to forget how difficult it was for POSIX systems to get there. Unix wasn't even really 8-bit clean until SVR4 and 4.4BSD. It essentially was a 7-bit ASCII system throughout the 1970s and 1980s.
I noticed the German translation of Planify [flathub.org] could use some improvements. Some of the text strings made no sense and were outright wrong about how the app works.
Then I noticed some peculiarities of some of the source text strings — lots of duplicates, differing in capitalization, weird phrasings, etc.
Went into the code to investigate in hopes of eliminating duplicates and learn the context in which they're used.
Let's just say this is me right now: https://www.youtube.com/watch?v=AbSehcT19u0
« Econception logicielle, pourquoi et comment coder "green" »
#ecodesign #ecoconception #opensource #a11y #i18n #androiddev #iosdev #webdev #VieDeDev
Support sous CC-BY-SA
The example web 2.0 best practices app I'm working on is now fully translated in:
- English (US)
- English (UK)
- French (France)
- French (Québec) (yes it uses courriel)
- German
#i18n is actually lots of fun for language learning
Presumably, if said website didn't implement any kind of analytics (perhaps because they didn't wish to worry about the consequences of GDPR/DPA, CCPA et al.), the owner may be blissfully unaware of whether their site "has links with the United Kingdom" (per section 4).
Given the extra-territorial effect, any tool #Ofcom produces is gonna need some major #i18n. What an unholy mess.
Localization (#l10n) and internationalization (#i18n) are more than just translating words. Colors, idioms, fonts, layouts, imagery, structure, etc are all affected (some of which I learned the hard way running a localization company & product).
Eric has some examples of iconography:
https://ericwbailey.website/published/dont-forget-to-localize-your-icons/
Why we must internationalize the source code (yes) of computer programs, a concrete example: ggplot has both scale_color_continuous and scale_colour_continuous (note the british letter u).
Here is a tool to annotate PO translation files using LibreTranslate, so that project maintainers can make sure the human-provided translations look plausible, even when they don't speak the target languages.
https://codeberg.org/a-j-wood/po-translation-auto-assistant
I developed this to be able to vet submitted translations for Pipe Viewer and other projects, to have some confidence that the submitter understood each string they translated in the context I'd intended, and to limit the likelihood of malicious mistranslations or vandalism.
It relies on LibreTranslate, but the project README outlines how to quickly install that on your local machine.
The project is hosted on the @Codeberg platform and was developed with their Translathon (https://codeberg.org/codeberg/translathon-2024) in mind.
Is anybody using #FluentRS in their #RustLang project? I am thinking about setting it up for the upcoming #CodeBerg #Translathon.
I was thinking of using #GetText but it seems outdated and not very friendly.
Pipe Viewer needs your help to work better in non-English locales.
If you speak more languages than English, please consider helping translate Pipe Viewer's documentation and error messages.
Thanks to @Codeberg you can do this through a Weblate interface, straight from your web browser, here: https://translate.codeberg.org/projects/pv/ - no programming required.
If you don't have a Codeberg account yet, registration is quick and free.
Currently, Pipe Viewer has translation files for French, German, Polish, and Portuguese, all in various states of completeness. I'd love to get these up to date. And adding more languages is simple - just let me know.
Your help would be greatly appreciated.
Do you hope for better translation coverage in your projects?
Register your project for our #Translathon on October 12 + 13 and translate together with our community.
Find all the details here: https://codeberg.org/Codeberg/translathon-2024#readme
Find the event: https://codeberg.codeberg.page/Events/events/2024/10-12_translathon/
#flohmarkt goes international!
we have finished #i18n and are now ready for #localization
These are the five #language s we're starting with! If you want to help with #translation s, you can do so under https://translate.codeberg.org/projects/flohmarkt
if you want to add another locale, open an issue on codeberg and we'll hit you up :)
I really love it when websites guess my language wrongly. Today, it's OpenLibrary that decided I wanted all text in Sardu (Sardinian: language code "sc")
I have my browser language set to Scots (language code "sco") and I guess OpenLibrary doesn't know that some languages don't have two-letter codes ...
Hey Fediverse friends!
I am looking for #help with #Weblate for an #Eleventy static website for my workshop Knitting Our Internet [ournet.rocks].
I tried setting it up, but I can’t get my head around it!
Could anyone help out? I would just need help with the initial configuration.
More information about the task in this post on Weblate’s GitHub discussion [github.com]
#Boosts are welcome!
I recently received very helpful feedback for my PolyglotMarkdown project.
It currently consists of a draft Spec for Markdown documents that can contain multiple languages, with a Python implementation underway.
I have continued working on it, based on feedback, further reading, and best guesses
Would really love feedback on current best practices for language codes.
pro-tip: #Accessibility is a lot like #Internationalization It's trivial to incorporate if you write your app with it in mind from the beginning. It's a pain in the ass to shoe-horn in after the fact. The longer you put it off, the harder it will be to add it in, and the less likely you are to ever do it.