So the way translations work is: - the package build calls dh_translations which refreshes the translations template
example https://launchpadlibrarian.net/722260790/buildlog_ubuntu-noble-amd64.tecla_46.0-1build1_BUILDING.txt.gz dh_translations ninja: Entering directory `/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' [0/1] Running external command tecla-pot - dh_translations produces a translations tarball - launchpad imports the new template and update its list of strings to translate - translators work on those strings in the launchpad UI (they are shared across series so if the patch backports a string existing in a new version some translations might already exist and be used directly) - those translations will be included in the next langpack refresh We just had a langpack export for Noble .3 and seeing the timing it doesn't seem likely we will have translations for this point release even if the SRU is accepted. New translations put aside having an english description is probably still better than having no screen reader description, a non trivial portion of our userbase understand english and that string describes letters which might even be understandable by some non english speakers... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2116166 Title: Tecla lacks accessibility when showing available keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tecla/+bug/2116166/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
