Support » Theme: Accesspress Lite » Translation problems

  • After the last update of the theme one of the terms used on my site are not translated on the sites blog page (“Read More” are not translated to the Swedish expression “Läs mer”). I have checked the sv_SE.po file, and nothing seems to be wrong. The other translations used works fine. Do you have any explanation and possibly a solution?
    Regards!

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @gurra
    I’m not related in any way to this theme. But I do know a bit about WordPress translations (and especially about translations to Swedish 🙂 )

    First of all: When WordPress runs, it doesn’t use .po files, but .mo files. That’s a compiled version of the same translation. If you edit your .po file with poedit, for instance, then this application can create the .mo file for you.

    The Swedish translation at https://translate.wordpress.org/locale/sv/default/wp-themes/accesspress-lite/ is currently 60% ready. A language pack that install automatically via the “updates” page in WordPress admin will be created when the translation reaches at least 95%. You’re more than welcome to suggest translations for the remaining strings (or better translations of already translated strings, too!). Also: If we see that your translations are good (follows the style guide https://wpsv.se/engagera-dig/stilguide-for-oversattningar/ etc) then we can assign you as translation editor for the Swedish translation of this theme.

    There IS a way for you to start using the currently existing translation:
    1. Go to https://translate.wordpress.org/projects/wp-themes/accesspress-lite/sv/default/
    2. At the bottom of that page: export all translations in .mo format.
    3. Rename the received file into: accesspress-lite-sv_SE.mo
    4. Upload it via ftp to /wp-content/languages/themes/
    It’s safe to do this, when a language pack gets generated, it will replace this file automatically.

    If you want to help with this translation, consider joining the Swedish Slack team, see instructions in the “Welcome note” at https://sv.wordpress.org/team/

    Ha de gott!

    Hi @tobifjellner,

    Thanks very much for your tip and information about WP translations. It’s a lot I didn’t know before, so the information is very welcome. I will check further if what you suggest is something for me to commit to, including the Swedish slack team.

    Regarding this case, yes, the mo file is also in the correct/same folder as the po file. So, this shouldn’t be the problem. But there are two other things that confuses me slightly. In the po/mo file I used before the last theme update, I translated “More” to Swedish, and this worked fine on the blog page. But when “Read more” occurred on the blog page after the last theme update, I also translated this expression in the po/mo file. But nothing happened. Furthermore, the expression “Read more” is partly placed on different places in different po files (the one I used before last update of the theme, the one generated by the accesspress-lite.pot file which accompanies the theme, and the WP translation on https://translate.wordpress.org/projects/wp-themes/accesspress-lite/sv/default/ which you refer to), and the expression also occurs two times in the dot file. May some of these things have a connection to the problem?

    Otherwise I wonder if something in the last update of the theme may have an impact on how the translations works? I guess this is a question primarily the theme creator will be able to answer.

    Regards / Ha det gott!

    A correction: In the last comment I wrote “…the expression also occurs two times in the dot file”. Of course it should be “pot file”, not “dot file”.

    There are a few things here:
    Each theme and plugin uses their own text-domain. Some of the strings seen in front-end are a part of core, but most are from the theme. And plugins, obivously have their own strings. It can get messy sometimes.

    It’s possible to create strings that are “context aware”. _x(). In WordPress core, you can see this for example in https://build.trac.wordpress.org/browser/trunk/wp-includes/class-wp-locale.php?marks=163-173#L162 where the translation is for the genitive form of the months’ names.

    Also: You were using the .pot file from the developer. But was it created correctly? The translate.wordpress.org totally disregards any .pot file in a plugin or theme. Instead, the platform scans the code for calls to the translation functions.

    By the way, if you’ve generated locally a po file, why not upload it on translate.wordpress.org?

    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.

    Well. Sooner or later, I guess a language pack will be build and suddenly replace the translation you’ve prepared.
    There are a couple of plugins that allow you to override things and translate specific strings under certain conditions: say-what and loco-translate. I don’t use neither of them myself, though. And in your particular case that might turn out to be an unnecessary complicated and slow solution.

    Thanks again for all comments, information and suggestions! I guess I will wait a while to see if a new language pack will appear, and if not I will sure take a look on the plugins you mention.

    Hi @tobifjellner

    Thank you for your contribution. We appreciate it.

    Regards!

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.