Post #2684155
2026-01-19 12:56 UTC
@CoMaps@floss.social I’d love to, but … your translation strings are so weird and confusing.
Why is %#@value@ a translatable string? Why are there multiple NULL as translatable strings? … and what the hell is this?
money|U+1F3E6|U+1F4B0|U+1F4B2|U+1F4B3|U+1F4B4|U+1F4B5|U+1F4B6|U+1F4B7
Translators should not have to deal with technical terms, strings that should not be translated at all, or weird lists of IDs and Unicode codepoints.
Having the app translatable was clearly and obviously an afterthought. Are there any plans to clean that mess up? Is there a reasonable way to help?
Replies (1)
-
@CoMaps@floss.social 2026-01-19 13:09
@dirk@gts.0x7be.net for now the easiest would be to skip those, for the category bits you picked and example of, we have detailed instructions for those search synonyms, which as those go beyond just translating and into localisation: https://codeberg.org/comaps/comaps/src/branch/main/docs/TRANSLATIONS.md#categories-strings The unicode ones are for people being able to use emoji to search for POI