{"id":902,"date":"2025-03-24T14:27:59","date_gmt":"2025-03-24T14:27:59","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-to-translate-or-localize-geodirectory\/"},"modified":"2025-04-03T15:24:19","modified_gmt":"2025-04-03T14:24:19","slug":"how-to-translate-or-localize-geodirectory","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/how-to-translate-or-localize-geodirectory\/","title":{"rendered":"How To Translate Or Localize GeoDirectory"},"content":{"rendered":"\n

GeoDirectory, by default, comes in English. (en_US)<\/h2>\n\n\n\n
<\/span>Our users fully translated GeoDirectory into several languages<\/a>. If yours is incomplete or you want to edit a language, you can by following the steps in this document.<\/span><\/div>\n\n\n\n

There are 2 options, creating a translation file or using an existing translation file.<\/p>\n\n\n\n

\n
\n

Create a translation file.<\/strong><\/p>\n\n\n\n

Download and install POEdit<\/a>. Launch it to open this file:<\/p>\n\n\n\n

geodirectory\/languages\/geodirectory-en_US.po<\/pre>\n\n\n\n
Add your translations<\/strong> and once you finish, click <\/strong>File > Compile to MO…<\/strong><\/p>\n\n\n\n
Change the file name<\/strong> to reflect your Locale<\/strong> (the Locale is a unique code for each language). For example, if your translation is to <\/strong>Italian<\/strong>, the locale is it_IT.<\/strong> <\/p>\n\n\n\n
The file name should be:<\/p>\n\n\n\n
geodirectory-it_IT.mo<\/pre>\n\n\n\n
Here you can find the full list of Locale<\/a> codes.<\/p>\n\n\n\n
Inside the wp-content folder, create the folder \/languages\/<\/p>\n\n\n\n
Inside the languages folder, create the folder \/plugins\/<\/p>\n\n\n\n
Transfer the .mo file<\/strong> via FTP into the newly created folder:<\/p>\n\n\n\n
The complete path should look like this:<\/p>\n\n\n\n
wp-content\/languages\/plugins\/geodirectory-it_IT.mo<\/pre>\n<\/div>\n\n\n\n
\n
Using an existing translation file<\/strong><\/p>\n\n\n\n
Download<\/strong> the desired language file from the GeoDirectory GlotPress page<\/a>.<\/p>\n\n\n\n
You can download the file as .po file and modify it following point 1 of this doc or download it directly as .mo file, skip editing with POEdit \/ compiling the mo file, and follow the steps from point 1.<\/p>\n\n\n\n
<\/span>If you save the translation file in the wp-content\/plugins\/geodirectory\/languages\/ folder, you will lose your translation with each plugin update.<\/span><\/div>\n<\/div>\n\n\n\n
\n
Change WordPress language<\/strong><\/strong><\/p>\n\n\n\n
From your WordPress dashboard, go to Settings > General > Site Language. Change it to your language. WordPress and GeoDirectory will start using the translation files for your language.\u00a0<\/p>\n\n\n\n
\"\"\/<\/figure>\n<\/div>\n<\/div>\n\n\n\n
Translating Add-ons<\/h2>\n\n\n\n
to translate the add-ons<\/strong> the procedure is identical<\/strong>. Only the location of the translation files changes:<\/p>\n\n\n\n
They can be downloaded from our website and not from wordpress.org. <\/p>\n\n\n\n
The URL is https:\/\/wpgeodirectory.com\/translate\/projects<\/a>.<\/p>\n\n\n\n
Once you are ready to load your translation file<\/strong>, the path for example for the Location Manager should look like this<\/strong>:<\/p>\n\n\n\n
\/wp-content\/languages\/plugins\/geodirlocation-en_US.mo<\/pre>\n\n\n\n
Let’s take another example. For the Advanced search add-on the path should look like this:<\/p>\n\n\n\n
\/wp-content\/languages\/plugins\/geodiradvancesearch-en_US.mo<\/pre>\n\n\n\n
Translating themes<\/h2>\n\n\n\n
The translation file for themes<\/strong> is found in the\u00a0languages folder<\/strong> of the theme.<\/p>\n\n\n\n
When you are ready with the translation file, create the folder \/themes\/<\/strong> inside the  wp-content\/languages folder<\/p>\n\n\n\n
Transfer the .mo file via FTP<\/strong> into the newly created folder:<\/p>\n\n\n\n
For example, the complete path for the Directory Starter theme should look like this<\/strong>:<\/p>\n\n\n\n
\/wp-content\/languages\/themes\/directory-starter-en_US.mo<\/pre>\n\n\n\n
For the Supreme Directory child theme, the complete path should look like this:<\/p>\n\n\n\n
\/wp-content\/languages\/themes\/supreme-directory-en_US.mo<\/pre>\n\n\n\n
Updating Translations<\/h2>\n\n\n\n
sometimes, a new release comes out with new features, and in some cases, these new features require new text strings.<\/p>\n\n\n\n
When this happens, you’ll need to merge your translated PO file with the new language file provided with the update.<\/p>\n\n\n\n
To do so, you need to have both files on your desktop. For example: <\/p>\n\n\n\n
geodirectory-it_IT.po (your translated PO file)
&
geodirectory-en_US.po (the new translation file shipped with the plugin update)<\/pre>\n\n\n\n
Open the first file<\/strong> (geodirectory-it_IT.po) with POEdit<\/b> <\/p>\n\n\n\n
From the PoEdit menu, click Catalogue<\/strong> and then Update from POT file\u2026<\/strong><\/p>\n\n\n\n
This will not find the PO file, so use the file type option to look for PO files.
Browse to the new PO file (geodirectory-en_US.po) and press the open button.<\/p>\n\n\n\n
That will merge the new language strings with your translated file. Make any changes as required, save and upload the new MO file with updated translation in the wp-content\/languages\/plugins folder.    <\/p>\n\n\n\n
POEdit<\/p>\n\n\n\n
Use POEdit’s built in tools like the ‘Find’ tool to find the string you want to change.<\/p>\n\n\n\n
POEdit looks like this<\/p>\n\n\n\n
\"\"
hide a variable with CSS<\/p>\n\n\n\n
You can hide a variable in the output of the translation with some CSS like this.

Be sure to pay attention to syntax errors. POEdit will infom you if the string needs to end with a period or is missing a variable. Referring back to the original will usually clarify errors if they sound obscure.<\/p>\n\n\n\n
My new string<span style='display: none;'>%s <\/span>.<\/pre>\n\n\n\n

The %s is the variable, and the CSS around it hides that variable from the output\/display.<\/p>\n\n\n\n
Translating Custom Fields<\/h3>\n\n\n\n
Translate Custom Fields without WPML<\/a><\/p>\n\n\n\n
Translate Custom Fields with WPML<\/a><\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
GeoDirectory, by default, comes in English. (en_US) There are 2 options, creating a translation file or using an existing translation file. Translating Add-ons to translate the add-ons the procedure is identical. Only the location of the translation files changes: They can be downloaded from our website and not from wordpress.org.  The URL is https:\/\/wpgeodirectory.com\/translate\/projects. Once […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,432],"class_list":["post-902","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-how-tos"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=902"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/902\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=902"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=902"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}