Plugin Author
hupe13
(@hupe13)
Unfortunately, I don’t use Polylang, so I don’t know how it works. I’ll have to look into it. So far, I’ve only dealt with TTfP in connection with my other plugin.
If you want to translate the strings from Extensions use GlotPress, so others can use this. That would be great.
It seems there is an overviewmap for only one of the languages. Yesterday it was the Dutch version, then I changed something (don’t know what), now only the markers in the overviewmap of the English version is showed. Like the Dutch categories don’t exist.
Categories of all three languages are just added to the database. So I don’t know what is going wrong here.
About the trnaslation link: I can do some Dutch translations, but never did it before, should I click on the number in the ‘Stable’ column en just strat translating strings?
Plugin Author
hupe13
(@hupe13)
I see, you translated some strings. Great! If you translate these strings for elevation in the frontend, then I include the Dutch translation in the plugin.
Polylang creates for every page, post, category and tag in each language a new one. So you have for an english page an english category and for the dutch page a dutch category. But both have the same custom field for the marker, don’t they? So you need to create different custom fields for lat and lng, for example en-latlng and dutch-latlng and use the shortcode [overviewmap latlngs=en-latlng ... ] respectively [overviewmap latlngs=dutch-latlng ... ].
Or have I got that wrong?
Ok that was a good idea, that works.
What I did was I gave the posts indeed English categories (for example) and then in overviewmap:
category=norway-en,winter-en
But that did not work.
I now turned off the sharing of custom fields and set a custom field for each language indeed. That is even easier I think. But I think the problem was the sharing of the custom fields.
Thank you!
Will look at the Dutch language translation later.
Ok done (translation).
I have some doubts about ‘a’. Acceleration is ‘Versnelling’ in Dutch but I am not sure if ‘a’ makes it more clear than ‘v’.
Plugin Author
hupe13
(@hupe13)
‘a’ is the formula sign (physics) for “Beschleunigung” (acceleration), that’s how I learned and translated it.
Plugin Author
hupe13
(@hupe13)
There are some notes. Here you can see how it will look. ‘v’ stands now for speed and acceleration, this is not good.
Ok, it should be ‘a’. But I don’t understand how to set it back to ‘a’ because it sais ‘Error: Identical rejected translation already exists.’
BTW I don’t know who psmits1567 is, but he chose ‘Tempo’ for ‘Pace’, but I think my original translation (‘Kilometertijd’) is more clear. I don’t know how to communicate with him about it?
Also, now ‘pace’ is translated two ways: below the graph in the legend it says ‘Tempo’ but in the list below it, ‘Kilometertijd’.
Plugin Author
hupe13
(@hupe13)
Ok, it should be ‘a’. But I don’t understand how to set it back to ‘a’ because it sais ‘Error: Identical rejected translation already exists.’
I tried it to change, now it is “waiting”. Not everyone is allowed to translate, it has to be confirmed. You are now a “Translation Contributor”, because you translated some strings. A “Translation Editor” (@psmits1567) must confirm your translation.
The translation for “pace” was 3 years ago not clear. The thread is in German, I hope, you can translate it with Deepl or other. “Pace” means time per distance (minutes/kilometer). I don’t know, how to translate it to Dutch.
I noticed the discussion about “a” but in Dutch it can be both “accelleratie” or “versnelling” looking at the screenshot, there is nothing wrong with the “v” it is translated there as “versnelling” The translation of “a” has been altered many times. So I propose to either change the original to a more conclusive abbreviation, or add context to it, or do not add it into the originals, and hard code it. For now I will leave it as is, only a PTE or GTE can alter it
Pace is translated in Dutch as “Tempo” just as other locales have already translated it
Regards
Dutch GTE psmits1567
@maaikez ,
We have rules for translation on https://translate.wordpress.org/projects/wp-plugins/extensions-leaflet-map/stable/nl/default/?filters%5Bstatus%5D=untranslated
Please check the Glossary link, which leads you to the Dutch glossary. Also read the style guide. I have now corrected 17 strings which were not translated according our Grammar rules/glossary.
Advice, if you translate originals, look at the suggestions below the editor. If it contains100% suggestions, take the one that suits best for the original. Be aware that you are not the only one using this plugin. Anyone can suggest translations, which will be approved by a PTE or GTE. You can ask to become PTE for this project, but then your suggestions need to be following the rules for translation. Currently your request would not be granted due to the many errors in the suggestions.
You can reach me either by replying via this ticket, or join the Dutch/ international Slack platform
I hope this helps you understand how translation for WordPress projects works.
Ok thank you for the explanation.
There are now inconsistencies between Gem versnelling and Gem. snelheid for example. I would give them all a dot or none of them.
Thanks for the links and information. It deviated a bit from the original topic, but well, that’s ok :).
There was one translation without the dot, so I corrected that. All translations for Gem. Are now the same.
The whole project is now translated, so your system will be updated with the fully translated originals soon. As soon as translations reach the threshold of 90% they will be send to WordPress installations that have the project installed.
Plugin Author
hupe13
(@hupe13)
You are great! Thank you very much!
