| Summary: | Changing lokalize application language does not affect all strings in UI | ||
|---|---|---|---|
| Product: | [Applications] lokalize | Reporter: | Frederik Schwarzer <schwarzer> |
| Component: | general | Assignee: | Nick Shaforostoff <shafff> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | adrian, lpapp, lueck |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Frederik Schwarzer
2010-06-01 02:25:49 UTC
Another case of the notorious OTT's (One Time Translation) spread all over kde. Running trunk usually in locale x-test for testing purposes I have already a few hundred unchangeable strings with translation from x-test in $KDEHOME for just a few applications. I guess starting all applications from the main kde modules there will be some thousands of OTT'S. This string is taken from lokalize-scripts/scripts.rc, which is generated on the first start of lokalize using the actual locale. To switch the language for that string you have to rm lokalize-scripts/scripts.rc and start lokalize in the desired locale. Changing the application language now displays a dialog box that indicates that an application restart is required, so I guess we can close this as fixed. Removing subscriber per abuse report we've received. |