Thanks for quick reply!
Checking the theme readme.txt changelog, strengthen my suspicion the problem is caused by the last theme update. One of the changes is “Added Read More Option for Blog Page”. Seems directly connected to the problem on my site. Perhaps the developer missed to add a “language string” to this option. But at the same time some strange – I thought it was exactly this option I have used for a long time.
Well, also a somewhat strange that, as you say, themes own pot files sometimes can be corrupt. Anyway, in this case it worked when I used it when starting the site. But if something changed, I now also have tried the WP-translation. I downloaded it as a po file, made some changes, saved it as sv_SE.po file and consequently also as a mo file (using the Poedit app), and uploaded it to the server. Nothing happens/changes.
Interesting what you write about strings that are “context aware”. But I guess that this can’t be applied in this case as an explanation.
Well, my own created po file only includes two translated words, who are already translated in the in the WP translation, so it will hardly contribute to anything more. The changes I did in the WP translation, were only minor adjustments, matters of taste.
