Using Toolset Maps with Polylang translation plugin. Would like your input on an issue. I am using Polylang (WPML broke global function in Divi so I had to switch ... ) and it seems to be automatically attempting to do string translation on the Map Market Hover Title on a marker on a Toolset map. Since I haven't used the string translations on the site it isn't affecting much of anything on the front end that I can see except the HOVER status on a Map Marker title. Why anyone would build a plugin to translate a map marker is beyond me since you don't translate proper nouns (unless you don't know how to translate) such as businesses, building names, neighborhoods, etc. This present a problem because when you hover on over a map market it provides some oddball translation and begins repeating the same translation. Only happens on the secondary language side of the site. Can you please help me remedy this problem? Thanks.
I imagine if nothing else you would want to translate nouns if your site were in Russian, Hebrew, Arabic, Japanese, Korean, etc., so I don't think the problem is that the strings should not be translatable.
But, in any case, we can't really offer support for translating with Polylang, I'm afraid, it's not something any of us are familiar with, we are all used to providing support for WPML.
If you cannot resolve the problem between WPML and Divi, perhaps Polylang support can help explain why this is happening.
Nigel: Sorry. I got sidetracked. Regarding your first paragraph ... actually NO .. you never change a PROPER NOUN (such a person's name )(although the highly uninformed make the mistake of doing it sometimes). George Washington is George Washington in all languages. Only bad interpreters would change his name to Jorge. Similarly, if you pick up a book written by Argentina's most noted author /poet "Jorge Luis Borges" ... it will say Author: Jorge Luis Borges (not George Louis Borges). So in summary, it would be WRONG to translate the name of a hotel, a restaurant , etc. (a map marker on Google Maps) to something other than it's actual name (which is of course what is plastered all over the signs out front, etc.)
Okay. So now that we have that out of the way. Let's figure out why my translation plugin feels compelled to add a string translation for each marker on a map every time a map is rendered with Toolset. I have contacted the Polylang tech support staff but want to make sure there isn't something related to Toolset that is participating in this anamoly.
There are many things built into Toolset Views (and possibly maps) that are designed to make translation work. Most notably the inclusion of a translation string shortcode like this one that is added every time you create a filter label >>>
[wpml-string context="wpv-views"]Restaurant cuisine[/wpml-string]
What I suspect is happening is that your development team has included something like this in the marker coding that creates a translation string for each marker (and Polylang is then using those strings without me asking the plugin to do it).
Does that make any sense?
P.S. Has nothing to do with Divi. And to clarify I originally had WPML but couldn't use it due to an unrelated issue so switched to Polylang. Thanks.
Are you setting the hover content using a Toolset shortcode such as wpv-post-title?
That will automatically pass the text through a gettext filter so that it can be translated (regardless of where on the site it is rendered).
I don't know if Polylang offers the same kind of settings as WPML. With WPML one option would be to use a custom field for the text and set that custom field as not translatable, not sure if that would be an option with Polylang.
Alternatively, you could register your own custom shortcode to get the post title of the current post and return that without passing it through any gettext call, so that the untranslated text is shown.
The topic ‘[Closed] Eliminating String Translation on Map Markers’ is closed to new replies.
