Did the two translations.
Exported the two .po files.
Compiled them with poedit to .mo.
Placed both .po and .mo files in the appropriate folders.
That’s about it…

any reason why you didnt download the .mo file right from out glotpress site?  at the bottom, export…

if you extracted the .po file, you would need to add your translations again…  the .po file is on glotpress and what you are translating…  then you export the .mo file and are good to go…

you only need to place the .mo file in your languages folder for sp, by default sp-resources/languages/simple-press for core and admin…  the storage location is determined by forum – integration – storage locations…

you also need to tell wp to switch languages in the wp-config.php

Sorry but that wasn’t made clear in the glotpress site. Not obvious imho, and there was no reason to select anything other thatn the default…

I verified if the translations are in the po file, and they are.

My WP is dutch, and running as such, so that is covered correctly.

Will have a look where to extract the .mo file directly.

Thanks

Found the problem… the files have the wrong name:

Please advise translators to add a space after a colon on the end of a string when translating.

Actually – officially your language code should not have the _NL portion. The language codes are optionally two part. The first part represents a parent language. The second part should only be used for a country code that uses a variant of that language.

So – for example – The code for Portuguese is ‘pt’. They speak a version of Portuguese in Brazil so their code is ‘pt_BR’. The code for Britain is ‘en’. The code for the USA is (officially) ‘en_US’.

So in your case the only code necessary is actually ‘nl’. However – as long as the code in your wp-config and the name of the file match then it makes no difference to the actual operation.

My 2c:

I know of that… but no (or maybe a few 😉 ) plugin maker or even WordPress itself did follow up on that as you can see in the wp-config-sample.php I quoted above.

A year ago I tried to do it as you describe and declared define(‘WPLANG’, ‘nl’); in my wp-config.php, but found myself renaming files on every update of every plugin… it is just not done.

I’ve translated quite a few plugins and themes, and this issue always causes confusion.

A few versions ago we named all of our language packs with the ‘double’ code and had a lot of complaints about that so now we do it the proper way.
There is an article on our current V4 wiki about this and this will also be written up in the new V5 codex.

Respect that. As I did say… my 2c… It is just my opinion/experience as a none anglo (dutch) user… so renaming it is!
BTW: Looked it up at the dutch wordpress site and the proper dutch language code is officially “nl_NL”.

No that is just the WP interpretation. By ‘official’ I mean official in terms on international agreement of whatever bodies decide these things. WP have it wrong.

As I say, in the past we have tried it both ways and we always get complaints from half the users! You can’t get it right for everyone.

Fine… renaming it is, for us dutch!