Thematic 1.0.3.1 release notes

Thematic 1.0.3.1 is now available from the WordPress theme repository. This release was focusing on improving the internationalization and localization, with a complete string overhaul and updated pot-file. The introduction of glotpress to manage translations have been a success, and several languages have already been updated and are included in this release. Many languages still need updating though, so if you speak a language where the translation is incomplete we would be happy if you helped us with translating.

WPML logoAlso, Thematic is now fully compatible with WPML multilingual plugin! They worked well together already before, but this release includes a XML config file for even better integration.

Other new things are that the sample child theme have been updated to include sample code for custom headers and background.

And that the functions thematic_body_class() and thematic_post_class() have been moved/removed to filtering the core filters body_class and post_class respectively. Adding the following code to your child theme will enable Thematic’s classes to filter into the body_class() and post_class() output.

add_theme_support('thematic_legacy_body_class');
add_theme_support('thematic_legacy_post_class');

There are some more minor changes and bugfixes too, full changelog is in the readme file. Get the latest version from the WordPress theme repository.

Report any bugs you find on the github issue tracker and head over to the forums if you are having any trouble with upgrading.

Updating strings for upcoming 1.0.3

Update Oct 26th 2012: Thematic 1.0.3.1 has been released. Thanks to all that contributed. Keep the translations coming!

The time has come folks! We have gone through all of the Thematic strings and optimized them. This means removing leading and trailing whitespaces, include punctuation for better support of rtl languages, and generally making sentences complete instead of broken up in seperate pieces. We have also removed html markup from the strings as far as possible.

There are also comments and contexts on some strings so that placeholders (all the strange %s-es) are explained. Hopefully it will help in cases where the translation would differ depending on the content of the placeholder, for example in languages with different genders depending on the objects.

All in all almost half of the strings have changed, and we now need help to make the translations up to date. The new pot-file is uploaded to the Thematic glotpress so head over to translate.thematictheme.com and start adding strings in your languages!

Consider this a first runthrough, we are mostly there but small details might change. There are a lot of strings and it’s quite possible that something slipped throught the cracks, so if you spot something weird create an issue on github for it.

Note: If you prefer to use the traditional way of translating with poedit or similar software, the actual potfile can be found on a branch on github included in the release. Though you certainly can use it as a base and send a pull request with your translation, we would prefer if you use glotpress since it makes our lives easier to keep the translations in one place. But your contribution is welcome no matter how you choose to do it!

Thematic Development Moves to Github

At the begging and insistence of myself and Middlesister, we’ve shifted all the Thematic development over to Github.

Find us on the hub: https://github.com/ThematicTheme/Thematic

Github's octocat logo

Come on, Octocats are cute.

Visually, the Github website makes me feel like we’re not coding in the dark ages any more, I personally find the git fork and pull idea more intuitive and inclusive, but the biggest benefit (in my sometimes humble opinion) is that Github is infinitely more social.  There is a community of coders working on different things, and that’s what Thematic really needs right now.  We need more people chipping in or Thematic will get stagnant again.

The next major release for Thematic is going to be 1.0.3 and it is intended to be a major improvement to all the theme’s translatable strings, but this is going pretty slowly since those of us who work on it have been busy.  We need your help.  If you are already on github and understand how git works (I am still learning too!) then please Fork Us, read Otto’s definitive article on Internationalization and just go through 1 or 2 files to improve all the strings, then send a pull request.

And I’m aware that getting set up with git is not the easiest.  If anybody would like to step up and write a tutorial on how to set up a fork that’d be amazing.  If you think git is a bit over your head, don’t worry you can still help out by reporting bugs at: https://github.com/ThematicTheme/Thematic/issues

Thematic 1.0.2 Release Notes

Thematic 1.0.2 has been available in the WordPress Theme Repository for about a week now and a few bugs have been reported in the forums.

The title tag not displaying properly and shortcodes not producing the expected output. I’m glad to say that thanks to helgatheviking the bugs have been patched and you can find the officially theme reviewed, latest, and greatest Thematic 1.0.2.1 here:

http://wordpress.org/extend/themes/download/thematic.1.0.2.1.zip

An easier way to translate Thematic

The main focus for the upcoming 1.0.3 release is to improve and optimize the internationalization and localization of Thematic. The internationalization part refers to simply enable things to be translated, whereas the localization is the actual process of translating to different languages. Both of these things needs some attention.

There are many language files that come with Thematic but not many of them is up to date. With the 1.0 update, the pot file used for translations became out of sync and was regenerated for 1.0.2. This means that the language files need to be updated again, or some strings that have not been translated yet will show up in english on your site.

Regarding the strings, there are some issues regarding leading and trailing spaces in the translatable strings that needs to be looked over. Some needs to include punctuation so to better support rtl languages. This would mean that when we are finished, the pot file will need to be regenerated again and all languages will become out of sync. Again. Plus, since many strings will change in the backend, there is a high probability of untranslated content showing up on your site until the languages files become updated.

To speed up the process of localization and hopefully make it easier for everyone, we have decided to install Glotpress. This is the same tool that is used by WordPress itself for handling translations. You can read about the basics at their own Glotpress installation. Translation of strings will be done through the web, powered by the community. Say hello to translate.thematictheme.com!

In short, if you are a registered member of the forum, you are a contributor and can suggest translations for strings in any language. The current language files are loaded here. As you can see, not very many are up to date. You can log in with the same credentials as for the forum and start adding suggestions. A validator will then need to choose the correct translation if there are several suggestions and mark it as such. If you are a native speaker of a language and wish to become validator, talk to one of the admins. The same applies if you want to add a locale not yet in the list, tell us so we can add it.

When we are finished with the internationalization part, we will regenerate the pot file and give everyone a heads up so you can go to glotpress and start working on the localization part. Since we don’t speak all languages of the world, we are dependent on your contributions for this. Easiest way of contributing to Thematic!

So what happens when all is translated? Well in each language screen, there are export links at the bottom. You can at any given moment export your desired translation files. You will need to export twice, once for the .mo file and once for the .po file. Rename your files to locale.mo and locale.po (for example sv_SE.mo and sv_SE.po) and drop them in the library/languages folder of thematic.

This means that you are no longer tied to waiting for Thematic releases to get your translations. We will of course continue to include language files in the releases, but this will hopefully speed up the process and  make it easier for everyone to keep translations up to date.