Bug 345925 - Kross is missing support for a different translation domain in .rc files
Summary: Kross is missing support for a different translation domain in .rc files
Status: RESOLVED UNMAINTAINED
Alias: None
Product: frameworks-kross
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-06 17:07 UTC by Lasse Liehu
Modified: 2023-07-03 20:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lasse Liehu 2015-04-06 17:07:22 UTC 
It seems that Kross always uses the "kross5" translation domain for translating strings in KrossScripting .rc files. There needs to be a way to specify the domain to use and to use application domain when no domain is specified.

KXmlGui does something similar for its .rc files.

Using latest Kross git master from today, 2015-04-06.

Reproducible: Always

Steps to Reproduce:
1. Build KF5-based Lokalize.
2. Build x-test.
3. Run Lokalize using x-test.

Actual Results:  
In File menu the item "Update file from template" is untranslated because translation is looked up from domain "kross5", not from application domain "lokalize". See bug 345920.

Expected Results:  
In File menu the item "Update file from template" is translated.
Comment 1 Justin Zobel 2021-03-09 05:53:58 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 Christoph Cullmann 2023-07-03 20:28:41 UTC 
kross was already in pure maintenance mode in kf5, for kf6 it got removed,
there will be no future work spend on this beside critical security issues, if
at all.