Support » Plugins and Hacks » [Resolved] Translation files

[Resolved] Translation files

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Eric Andrew Lewis


    The translation files for the plugin should stay bundled where they are in the plugin.

    They will be automatically used by WordPress when you have the corresponding language activated.



    To create a translation in your language, you can save and then use a local copy of the plugin’s .pot (or .po & .mo) files. Then you can translate the individual words & phrases (instructions & tutorials to do this with POedit are on the web – I don’t have that link with me in this moment) and then generate another language file.

    Once you are done translating you should save or save as or export (depending on your preferences in the POedit application); POedit creates the new .po & .mo files in your local language. Make sure that you name them properly, then use FTP to upload both files into the /language directory of the CollabPress plugin on the server.

    Then Eric’s advice will work correctly: “They will be automatically used by WordPress when you have the corresponding language activated.” You should then have CollabPress successfully displaying in your local language!

    Good luck – and thanks!



    yeah yeah … The fact is i know how translation files are working … and the fact is that a broke my heads on that, and the fact is that there are sooooo much translations missing in your php files ..

    ex in dashboard.php:

    <div class="collabpress-project new">
    			<a href="#inline_content" class="add-new-project">
    				<div class="plus-sign">+</div>
    				<h2>Add new project</h2>
    		<?php } ?>
    		<div style="clear: both"></div>
    		<div style='display:none'>
    			<div id='inline_content' style='padding:10px; background:#fff;'>
    			<h2><?php _e( 'Add Project', 'collabpress' ); ?></h2>

    So i have to create a template file juste to translate a h2 .. argh ..

    Execpt this ***** eorors, your plugins is very promising, and i think i will use for myself .. There is a lot of potential and display designin possibilities .. i’m still trying it, but loving it!

    Plugin Author Eric Andrew Lewis


    Sorry about that. I’ll have a review of all strings and put in translation wrappers where necessary in 1.3.1, which should drop on Wednesday.

    Filed in Github.



    Thanks for that ..

    But don’t be sorry, thats just nothing next to the work you’ve done on this plugin!

    I’m already planning to buy you a beer ^^

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Resolved] Translation files’ is closed to new replies.