Some translations don't work
This topic contains 12 replies, has 3 voices, and was last updated by Kiran 5 years, 6 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
April 24, 2019 at 6:26 am #482465
Good morning, I followed all the steps to translate the Geo Directory files. The .po and .mo files are in the path wp-content/languages/plugins and there are strings that are not translated.
If you see for example in the home page, when displaying the advanced search filter, there are words like “Near” or “City” that in the .po file are already translated and are not shown.
However, many other translations can be seen on the web.
It happens with many other words that are already translated and do not appear correctly (in Geo Directory Core and other addons).I have followed all the steps but I have also used to try Loco Translate, with the same result.
April 24, 2019 at 6:27 am #482467This reply has been marked as private.April 24, 2019 at 6:46 pm #482628Hello,
did you also translate location manager addon?
Please share ftp so we can check the file location
April 30, 2019 at 6:37 am #483627I apologize for the delay, I am already able to do the translations with PoEdit.
Regards.
April 30, 2019 at 11:45 am #483658This reply has been marked as private.April 30, 2019 at 7:44 pm #483806You will also need to translate, in addition to core, the Location Manager and Pricing Manager addons. Have you already done that?
May 3, 2019 at 6:19 am #484247Yes, in geodirlocation-es_ES.po the string Near is translated (attached image). In geodir_pricing-es_ES.po doesn´t appear.
The strange thing, as I was saying, is that there are words in those files that do appear translated and those that I put before in the screenshot no.
May 3, 2019 at 7:03 pm #484372This reply has been marked as private.May 6, 2019 at 6:57 am #484624Hello Alfonso,
This has been fixed. All .po files missing following “sources keywords” in file.
"X-Poedit-KeywordsList: __;__ngettext:1,2;__ngettext_noop:1,2;_c;_e;_ex:1,2c;" "_n:1,2;_n_noop:1,2;_nc:4c,1,2;_nx:4c,1,2;_nx_noop:4c,1,2;_x:1,2c;esc_attr__;" "esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c;gettext;" "gettext_noop\n"
I have added in geodirectory-es_ES.po, geodiradvancesearch-es_ES.po & geodirlocation-es_ES.po files.
Please make sure all .po files contains “sources keywords” at the top of file.
Let us know.
Thanks,
KiranMay 6, 2019 at 8:32 am #484638This reply has been marked as private.May 6, 2019 at 12:11 pm #484668Hello,
Those are dynamic strings stored in database. Those strings can be translated any of two ways.
– If your site is running with multilingual support then to translate those dynamic strings, follow this post: https://wpgeodirectory.com/support/topic/can-translate-everything-except-one-specific-string/#post-461088
OR
– If your site is running with single language then your can translate those text directly from WordPress Admin CPT(Ex: Places) > Settings > Custom Fields > Field(Ex: Title) labels.Let us know.
Kiran
May 7, 2019 at 10:14 am #484901Great, I managed to translate “Place Title”, “Place description”, “Select package” and others, but there are 2 strings that do not appear anywhere: “Click on above field and type to filter list or add a new region” and “Click on above field and type to filter list or add a new city.
Well, they appear in geodirlocation-es_ES.po and I’ve already translated them and put what you sent me in the file header. I don’t know what else to do.May 7, 2019 at 11:09 am #484914Hello,
Check now, there were some old strings in languages/plugins/geodirlocation-es_ES.po
Ex: in .po file was missing full stop at the end of both strings.I have re-scanned /plugins/geodirlocation-es_ES.po and now those strings are translated.
Kiran
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket