i18n

March 19th, 2014 Leave a comment Go to comments



 

Previously Submitted Translation files

Submitted
Version
PO
MO
July 11, 2014 5:01 am
February 21, 2014 8:25 am
February 18, 2014 7:31 am
January 16, 2014 10:48 am
October 3, 2013 5:00 am
October 2, 2013 8:15 am
July 18, 2013 4:57 pm
July 11, 2013 5:42 am
February 19, 2013 12:55 pm
January 25, 2013 3:40 pm
November 24, 2012 2:55 am
September 12, 2012 2:56 pm
September 7, 2012 4:30 pm
August 17, 2012 1:54 pm
July 13, 2012 8:07 am
June 27, 2012 12:53 pm
May 28, 2012 5:26 pm
April 23, 2012 8:33 pm
April 20, 2012 11:19 pm
February 14, 2012 1:29 pm
February 13, 2012 6:07 am
January 23, 2012 10:51 pm
December 20, 2011 2:44 pm
September 9, 2011 7:26 pm
July 30, 2011 5:23 am
1.8
July 1, 2011 12:16 pm
1.8
March 28, 2011 4:24 am
1.8
March 16, 2011 5:34 pm
March 16, 2011 5:32 pm
March 16, 2011 8:53 am
March 3, 2011 3:14 pm
March 3, 2011 9:27 am
February 22, 2011 11:05 am
February 22, 2011 9:55 am
February 16, 2011 5:33 pm
February 16, 2011 3:54 pm
February 16, 2011 3:17 pm
February 16, 2011 2:29 pm

Help Internationalize (i18n) this Plug-in!

You can create a language translation file for this plugin. You do not have to be technical to do this. Just follow the steps….

Creating a translation from scratch

1. Download and install the free Poedit application. This application will allow you to easily type in translations for all the display strings that appear in the plugin.

2. Download the contact-form-7-to-database-extension.pot file.
This file contains the strings to translate.

3. Start Poedit. If this is the first time you have run Poedit, it will take you through some screens.

Setup dialog – Click OK
Preferences dialog – Click OK

4. Open the downloaded file.

File menu, New catalog from POT file…
Open the downloaded file
A Settings dialog will appear. You can just click OK

5. Save your file with the correct name indicating language and country.

Save As using the correct filename for the language/country.
Use the following to determine the file name: 

Language: 

Country: 

File name:

6. Input your translations

Click on each string and type in the translation

7. When finished SAVE. This creates two files: one with a “.po” extension and one with a “.mo” extension.

8. Test your files on your installation.
You will need to manually upload your .mo file to your WordPress installation in the directory:

wp-content/plugins/contact-form-7-to-database-extension/languages/
The file must be named correctly for it to work. 

NOTE: Your i18n setting is defined in your wp-config.php file, like this:
#define ('WPLANG', 'it_IT');
(this example: it_IT means italian of Italy)
You can change it to test a different language configuration.

9. Upload your working translation files! We will include them in the next release.

Your .po file (required)

Your .mo file (required)

Your Email (optional)

Enter this code below:
captcha

  1. ed
    February 14th, 2012 at 13:31 | #1

    forget about the es_ES I just emailed… i did not see that it was already done… at least I learned something, it was my first translation

  2. April 23rd, 2012 at 20:37 | #2

    Please help me important
    Worked only in Arabic translation, and followed the steps described here
    contact-form-7-to-database-extension-ar_SA.po
    But the translation did not work!!!
    What do I do?

  3. April 23rd, 2012 at 22:33 | #3

    When you save the translation in Arabic
    This problem appears!!!

    http://www.almlf.com/get-4-2012-almlf_com_go3hr6cz17.png

    File errors
    I want to solve this problem? :(

    • Michael Simpson
      April 24th, 2012 at 11:38 | #4

      I see this is an error in POEdit on Mac. I googled for the error “X-Poedit-SearchPath”. The issue may be having a space in the path where you are saving the file. If that is the case for you, try saving at a different location. I think this is coming from trying to compile the .PO file to a .MO file. If you can send me the .PO file (if it lets you save it) I can try creating the .MO file on a Windows machine.

  4. April 24th, 2012 at 13:33 | #5

    نعم استطيع حفظ ملف ترجمة العربيه
    بعد ظهور الأخطاء

    هذه هي الملفات

    http://www.pixel-d.com/blog/wp-content/uploads/contact-form-7-to-database-extension-ar_SA.po_.zip

    http://www.pixel-d.com/blog/wp-content/uploads/contact-form-7-to-database-extension-ar_SA.mo_.zip

    وقد قمت برفع الملفات الى مسار
    wp-content/plugins/contact-form-7-to-database-extension/languages/

    ولكن لم تعمل الترجمة

  5. April 24th, 2012 at 13:34 | #6

    Yes, I can save a file Arabic translation
    After the appearance of errors

    These are the files

    http://www.pixel-d.com/blog/wp-content/uploads/contact-form-7-to-database-extension-ar_SA.po_.zip

    http://www.pixel-d.com/blog/wp-content/uploads/contact-form-7-to-database-extension-ar_SA.mo_.zip

    The files you raise to the track
    wp-content/plugins/contact-form-7-to-database-extension/languages ​​/

    But the translation did not work

  6. April 24th, 2012 at 14:04 | #7

    Note:
    When you open the program and choose Poedit Arabic Language
    I get this message
    http://www.pixel-d.com/blog/wp-content/uploads/see.png

  7. luminousspice
    September 7th, 2012 at 16:53 | #8

    Hi, Michael. Thanks for your great code. This plug-in is really helpful for me.
    I’ve uploaded Japanese resources ‘contact-form-7-to-database-extension-ja_JP.po’ according to your guideline. Unfortunately, the current WordPress Japanese resource files itself uses ‘ja’ instead of ‘ja_JP’. I don’t know why.
    I note that it’s necessary to change file names ‘ja_JP’ to ‘ja’ or make symbolic links to activate these Japanese resource files for your plug-in.

  8. Michael Simpson
    September 12th, 2012 at 21:25 | #9

    @luminousspice
    Thanks. I’ll add two copies: “ja” and “ja_JP” files

  9. October 3rd, 2013 at 05:12 | #10

    I updated the contact-form-7-to-database-extension-nl_NL.mo again today.
    The version I sent yesterday (oktober 1) was incomplete and should be removed.

    There’s still a field missing in the “pot” file:
    * I have donated to this plugin

    (Thanks for this GREAT plugin, pity I did not discover it earlier)

You must be logged in to post a comment.