Language support

@fizzgigg – I found the issue … I wrote the code to take into consideration both singular and plural conditions for the item labels (Post/Posts, Page/Pages, etc.) and the translation files you shared only provided text for the singular forms. I used Google Translate to find plural forms and based my translations on your version but I imagine it will need to be reviewed.

As it is, with the plural texts added to the translation files all works as expected. Thanks, I really don’t do much as far as translation files go so this was an opportunity to play with Poedit and get to understand how it works.

Here is what I created and works for me: https://dl.dropboxusercontent.com/u/10029767/bns-site-data-sv_SE.zip

~Cais.

You are making progress. ?? To the visitor, the translations looks as intended, but the admin interface when you work with the widget is still in English, and the “header” Site Data is not translated.

@fizzgigg – The administration panels are translated in my test sites. This is what I am seeing: https://take.ms/ZfEFP

As far as the “title” goes, technically it is translatable as the code shows but it is also user defined so you could simply enter the appropriate information in your own language.

Thanks!

– Cais.

*Facepalm* Of course I can name the widget myself.

This morning the admin interface was translated too, it may have been a cache or something that was messing it up last night. Nice work. ??

Well, now the translation is finished and you can get it here: https://dl.dropboxusercontent.com/u/8772619/bns-site-data-sv_SE_finished.zip

@fizzgigg – Thanks for the follow-up. I’ll likely add a note into the readme.txt explaining where to put translation files going forward. I really appreciate your help sorting out these last details.

If there are any changes in the .pot file it will be noted in the changelog, which you should also see under Plugins > Installed Plugins when an update is available.

~Cais.

No problem, it was in my interest as well, since I wanted a Swedish translation. ??
Since I’m no coder – why placing the language files in the ../wp-content/languages/plugins/ folder and not in the ../wp-content/plugins/bns-site-data/ folder? Wouldn’t it be easier for the use with the later solution, as well as easier to update the language files when needed?

@fizzgigg – Using the ../wp-content/languages/plugins/ location fits better with the ideas behind WordPress’ language packs and having the community in general maintain translations for plugins and themes in the WordPress repositories.

Also, I do not have any plans to maintain the actual translation files at this time; as well as keeping in mind, the current Plugin update process removes *all* files from the plugin’s folder and replaces them with the latest stable release, if the translation files are not in the plugin’s package they will be removed and potentially “lost”.

~Cais.

Ah, now I have learned something. Thanks. ??