Summary: | [tm lang codes] Translation Memory not showing results | ||
---|---|---|---|
Product: | [Applications] lokalize | Reporter: | Adrián Chaves (Gallaecio) <adrian> |
Component: | translation memory | Assignee: | Nick Shaforostoff <shafff> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.5 | ||
Target Milestone: | --- | ||
Platform: | Chakra | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Requested files. |
Description
Adrián Chaves (Gallaecio)
2012-09-13 06:18:55 UTC
"I decided to try to reproduce the issue, and I failed." So, to be clear. Do you see the translation memory suggestions or not? If you don't see them, then please attach to this report your $HOME/.kde4/share/apps/lokalize folder, your project folder and specify the files which you have problems with. (please compress the data to save bugs.kde.org storage space) Created attachment 73899 [details]
Requested files.
Sorry, the first paragraph used to say that the application crashed, which was what I tried to reproduce in the first place. When I tried to reproduce the crash, I could not , but the translation memory would still not show up, so I modified the report to complaint about that.
I attached the “lokalize” folder, along with a “gl” folder containing the Lokalize project file I used plus a “.po” file to reproduce the issue.
I have just realized that, opening the file separatedly (not from the project summary in Lokalize), I do get the translation memories showing up. That is:
- Click on gl/docmessages/extragear-utils/krecipes.po → Works: open in Lokalize and provides translation memory entries when browsing the translation units.
- Open Lokalize, go to “Project → Open Project”, select the gl/lokalize.ktp file, click docmessages/extragear-utils/krecipes.po on the project summary in Lokalize → It does not work: browsing the translation units, the translation memory widget stays empty.
i think the problem was that sometimes you had two-letter target language code, and sometimes 4-letter code. I have made lokalize a bit more robust: now if the target language of the file being edited doesn't match the default TM used then new TM is created with correct target language I’ve not suffered this issue recently, so I think we can assume your changes fixed it. Thank you! |