Title: Localization of SermonBrowser Last modified: August 19, 2016 --- # Localization of SermonBrowser * [DJIO | Dionizio Bach](https://wordpress.org/support/users/djio/) * (@djio) * [15 years ago](https://wordpress.org/support/topic/localization-2-2/) * This one is to start a topic about localization of SermonBrowser * In Brazilian Portuguese several churches use different names to sermons (preaches, sermons, studies, even lectures). I’ve updated the pt_BR strings for 0.44, now with 5 variations. [http://www.djio.com.br/sermonbrowser-em-portugues-brasileiro-pt_br/](http://www.djio.com.br/sermonbrowser-em-portugues-brasileiro-pt_br/) * Maybe theres a way to make the user select the name they want to use in the Options page. * One other thing: series in english is a word with no plural form, but in other languages there is a singular form (i.e. série) and plural (i.e. séries), can you fix the .POT structure to support this? * Congratulation on the new Website and thanks again for the development of this plugin. * Best, * Djio Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Author [Mark Barnes](https://wordpress.org/support/users/mark8barnes/) * (@mark8barnes) * [15 years ago](https://wordpress.org/support/topic/localization-2-2/#post-2061260) * Djio, * Thanks for your continued work on this translation. Your idea of allowing the user to specify the word they want to use for things like “Preacher”, “Sermon” and so on is a good one. I will look at implementing this in a future version. * Adding different contexts of the same word is possible in WordPress (using the _x function), but context is not supported by Poedit, unless I provide a .POT file, and I don’t know how to create .POT files automatically. [http://wordpress.org/support/topic/translation-does-not-work-ok](http://wordpress.org/support/topic/translation-does-not-work-ok) * If you can help me with this, I’m happy to make the necessary changes in SermonBrowser. * Thread Starter [DJIO | Dionizio Bach](https://wordpress.org/support/users/djio/) * (@djio) * [15 years ago](https://wordpress.org/support/topic/localization-2-2/#post-2061264) * I agree Poedit is quite limited * As far as I understand the POT file is just a clean PO file with a different extension. In other words is simply done by creating a new PO file, configuring the Project, Paths and Keynotes, save it as PO, close Poedit and rename your file from *.po to *.pot * I wasn’t aware of contexts til now, so I’ll check them out. Meanwhile, please check these resources I use help me with Localization/Translation. * • **Codestyling Localization** > [http://wordpress.org/extend/plugins/codestyling-localization/](http://wordpress.org/extend/plugins/codestyling-localization/) > [http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en](http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en) * • **WPML** (went commercial, but there’s an old Free version) > [http://wordpress.org/extend/plugins/sitepress-multilingual-cms/](http://wordpress.org/extend/plugins/sitepress-multilingual-cms/) > [http://wpml.org/](http://wpml.org/) * • Check **GlotPress**, I use it to Translate some plugins and the WordPRess itself. It needs to be installed in your server and you must add validators for every language so it will generate the proper PO files > [http://glotpress.trac.wordpress.org/](http://glotpress.trac.wordpress.org/) > [http://blog.glotpress.org/](http://blog.glotpress.org/) * Thread Starter [DJIO | Dionizio Bach](https://wordpress.org/support/users/djio/) * (@djio) * [14 years, 10 months ago](https://wordpress.org/support/topic/localization-2-2/#post-2061335) * Sorry for taking this long to reply. Just found this Context documentation * [http://codex.wordpress.org/I18n_for_WordPress_Developers#Disambiguation_by_context](http://codex.wordpress.org/I18n_for_WordPress_Developers#Disambiguation_by_context) * But I don’t think it applies to our case. A better approach would be set some fields in the plugin settings where people could customize the name for their own reality. * ie: How do you call you local Sermon? Singular: [regular] | [Capitalized] Plural:[ regular] | [Capitalized] * How about it? * [Interpolat Solutions](https://wordpress.org/support/users/jmdziba/) * (@jmdziba) * [14 years, 4 months ago](https://wordpress.org/support/topic/localization-2-2/#post-2061442) * I am currently installing Sermon browser on a client’s site. The client is a men’s group that seeks to minister to men, and bring in men who may not be Christians, into an understanding and acceptance of the Christian faith. With this in mind, teachings are not referred to as Sermons, but Teachings. I would like to make this simple change to the Sermon Browser so that all instances of the word Sermon or Sermons, are changed to Teaching or Teachings. I have not yet ventured into the world of po files, and am hesitant to. Is there a way to accomplish this without creating a new translation using poedit as I have seen to be the best suggestion so far for accomplishing the above objective? Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Localization of SermonBrowser’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/sermon-browser_10232e.svg) * [Sermon Browser](https://wordpress.org/plugins/sermon-browser/) * [Frequently Asked Questions](https://wordpress.org/plugins/sermon-browser/#faq) * [Support Threads](https://wordpress.org/support/plugin/sermon-browser/) * [Active Topics](https://wordpress.org/support/plugin/sermon-browser/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/sermon-browser/unresolved/) * [Reviews](https://wordpress.org/support/plugin/sermon-browser/reviews/) ## Tags * [Localization](https://wordpress.org/support/topic-tag/localization/) * [pt_BR](https://wordpress.org/support/topic-tag/pt_br/) * 4 replies * 3 participants * Last reply from: [Interpolat Solutions](https://wordpress.org/support/users/jmdziba/) * Last activity: [14 years, 4 months ago](https://wordpress.org/support/topic/localization-2-2/#post-2061442) * Status: not resolved