Bug 477366

Summary: Lokalize does not support "ast" locale in some parts
Product: [Applications] lokalize Reporter: Enol P. <enolp>
Component: generalAssignee: Simon Depiets <sdepiets>
Status: RESOLVED WORKSFORME    
Severity: normal CC: aacid, shafff
Priority: NOR    
Version First Reported In: 23.08.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Two translation memory windows where "ast" locale is sneaky

Description Enol P. 2023-11-22 12:51:57 UTC
Created attachment 163361 [details]
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
Comment 1 Albert Astals Cid 2023-12-03 00:21:07 UTC
as is assamese, not Asturian.

Are you sure it's not you that made a bug choosing the language when creating the translation memory?
Comment 2 Bug Janitor Service 2023-12-18 03:45:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-01-02 03:46:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!