This series is part of a wider series on Internationalizing a ClassicPress plugin.
In the first posts on the parent series, I explained what internationalization and localization are and, in this sub-series, I am going to explain the process of internationalizing a plugin developed for ClassicPress.
Continue reading “Internationalizing a ClassicPress plugin: Series Index”
This series if a is part of the Translating a ClassicPress plugin series.
In the last post I discussed why internationalization was important, but the follow on from this is when should a plugin be internationalized.
When developing a plugin, it is tempting to work on the functionality first and then go back to internationize the strings afterwards. When I started developing plugins, none of them were interationalized. When I started doing so, I had to go back and find all the strings and then wrap them in the relevant functions.
New plugins, I have internationalized from the beginning and this is much less work and also means there is much less opportunity to miss a string which going back afterwards makes quite likely.
My recommendation, is to internationalize your plugin from the beginning and thereby save yourself time and errors.
This post is part of the sub-series on Translating a ClassicPress plugin which is part of the Translating a ClassicPress plugin series.
ClassicPress is already used in many different countries where English is not the main language; and even where it is, there can be variations in the spelling of words. ClassicPress itself is internationalized and can be localized.
Plugins and themes developed for ClassicPress should also be internationalized so that they can then be localized. The developer who authors the plugin doesn’t have to do the localization (translations), but by internationalizing the plugin it means that others can easily translate the plugin without needing to modify any code.
By making translations easy to do, you increase the audience for your plugin as site admins can easily translate it into their sites language.
This post is part of the sub-series on Translating a ClassicPress plugin which is part of the Translating a ClassicPress plugin series.
Internationalization (often abbreviated as i18n as there are 18 letters between the letters i and n) is the process of developing a plugin so it can easily be translated into other languages.
Localization (often abbreviated as l10n as there are 10 letters between the letters l and n) is the process of translating an internationalized plugin.
If you are a theme or plugin author, you should regard internationalization (i18n) and localization (l10n) as a requirement for your ClassicPress projects.
I started using WordPress when I launched this blog back in 2011 and a couple of years later started writing plugins to add missing functionality. At the end of last year I switched over to ClassicPress, a hard-fork of WordPress.
As part of my transition to ClassicPress I created new versions of my plugins which added new functionality and improved security. I had already done some work to internationalize my plugins, but took the opportunity to improve this aspect as well.
Having done so, I thought that a series on how to internationalize and localize plugins might be a useful thing to write; while the series is targeted at plugins, as I am a plugin author, the principles are the same for themes.
This series will include a couple of sub-series as well as the core series; the index for all are below and will automatically grow as the posts go live.
Continue reading “Translating a ClassicPress plugin: Series Index”
ClassicPress v1 was released on 5th March 2019 and has now been shared onto Product Hunt, which is a website that lets users share and discover new products.
Check it out and cast your vote!
I’ve decided to go all in on ClassicPress; I moved all my sites across to it a little while ago and have also created new versions of my plugins specially for it.
If you want to use ClassicPress I also have you covered with series on installing it and migrating to it.
For those who don’t know, ClassicPress is a hard fork of WordPress 4.9; the last version before the horrendous Gutenberg block editor was forced out by Automattic (WordPress.org is ostensibly a community-led open source project, but Gutenberg was decided upon and forced by Automattic without engaging with the community).
ClassicPress has a petitions site where the community can vote on what features are added to or changes made to ClassicPress. ClassicPress is intended to be a community-led project where no-one person can dictate changes; to this end additional directors have recently been added to the board.
This is part of the azurecurve ClassicPress Plugins which introduces the plugins I have available for ClassicPress.
All of the plugins I have created for ClassicPress have been created to support translations. I only speak English so the plugins currently only ship with English vailable; pot files are included in the plugins /languages folder which can be used to translate the plugin using software such as PO Edit.
In addition, I have a translation website which can be used to translate plugins without needing to install any software. To request a language be added for translation, visit my community site and ask for the language to be added.
This is part of the azurecurve ClassicPress Plugins which introduces the plugins I have available for ClassicPress.
Over the course of this series, I have announced all of the plugins I have created for ClassicPress. I have created a Community site where I will provide support.
Whether you have a bug report, feature request, question or want to translate the plugin, this site is the place to go.
This is part of the azurecurve ClassicPress Plugins series which introduces the plugins I have available for ClassicPress.
The plugin I am going to cover in this post, is a brand new one written specially for ClassicPress; Loop Injection.
Allows content to be injected before, within and after the loop. All content is configurable via an admin settings page; perfect for adverts.
Each of the three content locations can be activated individually; location within the loop is configurable.
Shortcodes are supported in Loop Injection; allows Snippets to be used.
The advert five posts down on the homepage and archives has been inserted using this plugin.
The plugin can be downloaded via my Development site.
This is part of the azurecurve ClassicPress Plugins series which introduces the plugins I have available for ClassicPress.
The plugin I am going to cover in this post, is a brand new one written specially for ClassicPress; Add Twitter Cards.
Use Add Twitter Cards to attach rich photos to Tweets, helping to drive traffic to your website.
Options allow:
You can see this plugin in action by Tweeting this, or any other post, using the available sharing buttons.
The plugin can be downloaded via my Development site.