https://bugs.kde.org/show_bug.cgi?id=477366
Bug ID: 477366
Summary: Lokalize does not support "ast" locale in some parts
Classification: Applications
Product: lokalize
Version: 23.08.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: sdepi...@gmail.com
Reporter: en...@softastur.org
CC: aa...@kde.org, sha...@ukr.net
Target Milestone: ---
Created attachment 163361
--> https://bugs.kde.org/attachment.cgi?id=163361&action=edit
Two translation memory windows where "ast" locale is sneaky
SUMMARY
***
For years, I was aware about this bug but I just ignore it because it was not
affecting my workflow until now. For some reason, Lokalize misses "ast" locale
in various parts of the app making impossible, for example, to manage memory
translations correctly.
I think Loklize assumes that "as" locale is the ISO 639-1 code for Asturian but
this is very wrong, Asturian has no ISO 639-1 code, only ISO 639-2.
However, if translation memory is automatically created by Lokalize, "ast"
locale appears magically.
***
STEPS TO REPRODUCE
1. Try to create a new translation memory
2. On "Target language", see there is no "ast" locale
OBSERVED RESULT
"ast" locale appears inconsistently across the app
EXPECTED RESULT
"ast" locale should appear across the app consistently
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
I attach an screenshot
--
You are receiving this mail because:
You are watching all bug changes.
