{"id":23657,"date":"2018-03-24T15:50:11","date_gmt":"2018-03-24T15:50:11","guid":{"rendered":"https:\/\/wpgeodirectory.com\/docs\/?p=23657"},"modified":"2018-03-24T20:41:17","modified_gmt":"2018-03-24T20:41:17","slug":"translation","status":"publish","type":"post","link":"https:\/\/wpgeodirectory.com\/docs\/translation\/","title":{"rendered":"Translation"},"content":{"rendered":"

Introduction<\/a> | What you need to know<\/a>
\nTranslation Files<\/a> | Core<\/a> | Addons<\/a> | Themes<\/a> | Download<\/a>
\nTranslation process<\/a> | Setup<\/a> | Edit<\/a> | PoEdit<\/a>
\nMore information<\/a> | Resources<\/a> | FAQ<\/a><\/p>\n

<\/a><\/p>\n

Introduction<\/h3>\n

WordPress and GeoDirectory both are configured with English by default, but can easily be translated into other languages. In this document we will introduce the how translated strings are stored, edited, and loaded to a site to display a new translation.<\/p>\n

The goal of this guide is not just to help you become familiar with translation. Once the new translations are setup in the GD site, you can edit and update your translation files any time. Once you start translating, and even changing the default text, you will probably find many ways to make the text ‘speak’ to your community of users. <\/p>\n

<\/p>\n

<\/a>What you need to know<\/h3>\n
    \n
  1. .po<\/strong><\/em> and .mo<\/strong><\/em>\u00a0files are the standard method for storing “translated strings”.<\/li>\n
  2. .po<\/strong><\/em> files are for doing translations<\/em><\/strong>.<\/li>\n
  3. .mo<\/strong><\/em> files are for showing translations<\/em><\/strong> on your site.<\/li>\n
  4. .po<\/strong><\/em> files can be edited with PoEdit<\/a><\/strong><\/em>, the free cross-platform desktop translation app.<\/li>\n
  5. When you edit a .po<\/strong><\/em> file in PoEdit, and then save the file, PoEdit will also create\/update a matching .mo<\/strong><\/em> file.<\/li>\n
  6. Store BOTH the .po and the .mo files<\/strong><\/em> in the the proper site folder.<\/li>\n
  7. GeoDirectory Core Translations are maintained at https:\/\/translate.wordpress.org\/projects\/wp-plugins\/geodirectory<\/a>, so go there if you want to download existing translations of GD Core.<\/li>\n
  8. GeoDirectory Addon Translations are maintained at https:\/\/wpgeodirectory.com\/translate\/projects<\/a>, so go there if you want to download existing translations of GD Addons.<\/li>\n
  9. Finished translation files for plugins are stored in wp-content\/languages\/plugins\/<\/strong><\/em><\/li>\n
  10. Finished translations for themes are stored in wp-content\/languages\/themes\/<\/strong><\/em><\/li>\n<\/ol>\n

     <\/p>\n

    <\/a><\/p>\n

    Core Translation Files<\/h3>\n

    GeoDirectory Core plugin translations are maintained at https:\/\/translate.wordpress.org\/projects\/wp-plugins\/geodirectory<\/a>. If you are looking for existing translations of the GeoDirectory Core plugin in additional languages, you can go there to see which languages are available. <\/p>\n

    If your language is not currently available or at less than “100%” then consider joining the GeoDirectory translation team where members work together to make excellent, accurate translations available in every language. Visit the Translators Handbook<\/a> to find out more.<\/p>\n

    <\/a>GeoDirectory Core Languages Folder Location<\/h4>\n

    Once you have completed your translation of GeoDirectory core plugin into a new language, the .po and .mo files must be transferred to your GD Site, usually by FTP. On your GD Site, the translation files for GeoDirectory core are stored in “wp-content\/languages\/plugins\/”. <\/p>\n

    Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is named incorrectly or because it is stored in an improper folder. <\/p>\n\n\n\n\n
    Name<\/th>\n.po\/.mo folder path and file name (text domain)<\/th>\n<\/tr>\n
    GeoDirectory Core<\/td>\n\/wp-content\/languages\/plugins\/geodirectory-en_US.mo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n

    <\/a><\/p>\n

    Addon Translation Files<\/h3>\n

    GeoDirectory Addon translations are maintained\u00a0https:\/\/wpgeodirectory.com\/translate\/projects<\/a>. If you are looking for existing translations of addons you should go there to see if your desired language is available. <\/p>\n

    If your language is not currently available or at less than “100%” then consider joining the GeoDirectory translation team where members work together to make excellent, accurate translations available in every language. Visit the Translators Handbook<\/a> to find out more.<\/p>\n

    <\/p>\n

    <\/a>GeoDirectory Addons Languages Folder Location<\/h4>\n

    Translated files for GeoDirectory Addons are stored in “wp-content\/languages\/plugins\/”. Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is incorrectly named or because it is stored in an improper folder. <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Addon\/Theme name<\/th>\n.po\/.mo folder path (text domain)<\/th>\n<\/tr>\n
    Advance Search Filters<\/td>\n\/wp-content\/languages\/plugins\/geodiradvancesearch-en_US.mo<\/td>\n<\/tr>\n
    Ajax Duplicate Alert<\/td>\n\/wp-content\/languages\/plugins\/geodir_duplicatealert-en_US.mo<\/td>\n<\/tr>\n
    BuddyPress Integration<\/td>\n\/wp-content\/languages\/plugins\/gdbuddypress-en_US.mo<\/td>\n<\/tr>\n
    Claim Listing<\/td>\n\/wp-content\/languages\/plugins\/geodirclaim-en_US.mo<\/td>\n<\/tr>\n
    Custom Google Maps<\/td>\n\/wp-content\/languages\/plugins\/geodir_customgmaps-en_US.mo<\/td>\n<\/tr>\n
    Custom Post Types<\/td>\n\/wp-content\/languages\/plugins\/geodir_custom_posts-en_US.mo<\/td>\n<\/tr>\n
    Event Manager<\/td>\n\/wp-content\/languages\/plugins\/geodirevents-en_US.mo<\/td>\n<\/tr>\n
    Franchise Manager<\/td>\n\/wp-content\/languages\/plugins\/geodir-franchise-en_US.mo<\/td>\n<\/tr>\n
    Location Manager<\/td>\n\/wp-content\/languages\/plugins\/geodirlocation-en_US.mo<\/td>\n<\/tr>\n
    Markercluster<\/td>\n\/wp-content\/languages\/plugins\/geodir_markercluster-en_US.mo<\/td>\n<\/tr>\n
    Payment Manager<\/td>\n\/wp-content\/languages\/plugins\/geodir_payments-en_US.mo<\/td>\n<\/tr>\n
    Review Rating Manager<\/td>\n\/wp-content\/languages\/plugins\/geodir_reviewratings-en_US.mo<\/td>\n<\/tr>\n
    Name<\/td>\n\/wp-content\/languages\/plugins\/geodir_sagepay-en_US.mo<\/td>\n<\/tr>\n
    Social Importer<\/td>\n\/wp-content\/languages\/plugins\/geodir_socialimporter-en_US.mo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    <\/a><\/p>\n

     <\/p>\n

    Theme Translation Files<\/h3>\n

    Only the default English translation is available for AyeCode’s GeoDirectory themes. You can find the default file inside the languages folder of the theme. <\/p>\n

    <\/p>\n

    <\/a>GeoDirectory Themes Language Folder Location<\/h4>\n

    Translated files for GeoDirectory themes are stored in “wp-content\/languages\/themes\/”. Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is incorrectly named or because it is stored in an improper folder. <\/p>\n\n\n\n\n\n
    Addon\/Theme name<\/th>\n.po\/.mo folder path (text domain)<\/th>\n<\/tr>\n
    Directory Starter Theme<\/td>\n\/wp-content\/languages\/themes\/directory-starter-en_US.mo<\/td>\n<\/tr>\n
    Supreme Directory Child Theme<\/td>\n\/wp-content\/languages\/themes\/supreme-directory-en_US.mo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n

    <\/a><\/p>\n

    Download Existing Translations for a Plugin<\/h3>\n

    Here we provide an example of how to download an existing translation.<\/p>\n

    In the example below, we will download an Italian translation of GeoDirectory Core, and then add the translation file to the GD site.<\/p>\n

      \n
    1. Navigate to the\u00a0GeoDirectory language project pages.<\/a><\/li>\n
    2. Select the language and addon of your choice.<\/li>\n
    3. Example: Italian:
      \n\"\"<\/li>\n
    4. Select the language file you want:
      \n\"\"<\/li>\n
    5. Scroll to the bottom of the page and Export<\/strong><\/em> the file (accept the defaults so you download the whole PO<\/strong><\/em> file):
      \n\"\"<\/li>\n
    6. Load the file to the proper folder (See Translating Addons<\/a> for more information).
      \n<\/i> Change the file\u00a0extension, if necessary, for your locale. Example: -it<\/strong><\/em> to -it_IT<\/strong><\/em>.
      \n\"\"<\/li>\n
    7. Create the MO<\/strong><\/em> file using PoEdit or download from the same page where you downloaded the PO<\/strong><\/em> file:
      \n\"\"<\/li>\n
    8. Review the translations on your site. If you find untranslated strings, continue to the next section for information about how to edit the translation files.<\/li>\n<\/ol>\n

       <\/p>\n

      <\/a><\/p>\n

      Translation Process<\/h3>\n

      <\/a><\/p>\n

      Setup New Language Translation Files on the Site<\/h4>\n

      First, the translations need to be setup on the site. Here is the overview of that process:<\/p>\n