I am sending you my default English_US translations, which have all these strings,
but i am not sure what might be the best method for you to add only these "missing strings" to your .po file without losing any of the strings which you already translated.
Yes, I also have that English file with 2120 strings left.
However, I must use a Spanish translation, which is not included in your files, so I created a new file, and I think that's where the problem lays.
As you don't provide any template file (.pot) in your plugin, LocoTranslate search for strings in the plugin, pulls them, and create a new translation file. As this process is automatic, for sure it's not getting all the strings available.
I have created a new template from the empty English translation, but your developers should include an official template by default, instead of leaving an empty English translation, if you may pass this information to them. They are basically the same thing, but the template makes things easier, as is the expected behavior from translation plugins.
I would attach the template (.pot file) in case you want to act on this and add it to your next release, but the form doesn't allow me to attach .pot files. However, I found a conversion tool:
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
-
Thank you for passing these details to us.
Yes, at the moment we do not have any default .po and .mo files as a default Spanish file in our languages folder. ( And a number of other languages)
So, in order to be sure that our users get all the strings, i recommend that "workaround" where we copy the default English translations to a new language folder,
then rename the .po and .mo files - that ensures that all the strings are there for translations.
As you maybe know, we do not have a professional translations Team,
so all of our translations are sent to us by our users - when they translate what they need, and if it is a new language;
they send it to us, so our developers add the new language for them along with their translated strings in the plugin's languages folder - so that they won't have to overwrite the files during plugin updates.
-
I will pass your feedback to our developers, though, and they will do their best to improve everything,
as you described, to make all of this easier for our users going forward.
Thank you for this improvement suggestion and for sending all details.
I can't promise an exact ETA if they will be able to add this to the upcoming Update, or if it might get postponed to one of the later updates, but we will do our best to improve it as soon as possible.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
our developers will discuss this subject with our Planning Team,
they will do their best to come up with a solution to add templates for adding new languages that have still not been set as "ready for translation"
in order to make this entire process easier for our users.
At this point in time, we are still not able to say a realistic ETA when they might add this improvement,
so for the time being, it is as we mentioned,
if our users wish to ensure that they get all the strings ready for translation,
the workaround needs to be done where we take the "default" english files and copy them in a new language folder > rename and then work on translations, etc.
We will make a patch note in one of the future updates when this has been improved.
Thank you again for the feedback and the suggestion.
I'm not really sure if I had explained myself correctly, but you don't need to create a single template for each language. If you create a .pot file, instead of an English .po file, that template will work for every new language any user want to translate. And the creation of a .pot file should take your dev team around 20 seconds to create. That's what it took me, at least.
Yes, our developers understood what you meant, my apology - i did not correctly pass what they said.
The goal will be exactly as you described; to have a "universal file" which will serve for any new language creation that has all the strings ready for translation, a .pot file ,
which will be a template for every new language any user want to translate.
There are a lot of other requests which other users have also requested,
our developers are doing their best to prioritize and they have to go through all of the tasks that are set by our management and the planning Team;
but that being said, they will still do their best to add this in one of the future updates, as soon as possible.
to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Hi, I'm unable to find certain strings in the translation file. Those are the "Export", "New entry", and "Edit" buttons on any table's frontend.
Attached files: wpDatasTables.png
Hello.
Sorry for the late reply.
That is strange. Do you have the latest plugin version 5.4.1?
On my version, when i check in our default translation files, for example, in the English US .po and .mo files,
if i check in the Loco Translate, it shows 2,120 available strings for translation.
Amongst them, there are "Export", "New Entry" and "Edit" so i am able to translate them in any language i need on my Test site.
You can see my Video here, how it looks on my default translation files.
https://watch.screencastify.com/v/39U3ayb8AZdesECEujXI
I am sending you my default English_US translations, which have all these strings,
but i am not sure what might be the best method for you to add only these "missing strings" to your .po file without losing any of the strings which you already translated.
I hope that helps, let me know how it goes.
Attached files: en_US.zip
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Yes, I also have that English file with 2120 strings left.
However, I must use a Spanish translation, which is not included in your files, so I created a new file, and I think that's where the problem lays.
As you don't provide any template file (.pot) in your plugin, LocoTranslate search for strings in the plugin, pulls them, and create a new translation file. As this process is automatic, for sure it's not getting all the strings available.
I have created a new template from the empty English translation, but your developers should include an official template by default, instead of leaving an empty English translation, if you may pass this information to them. They are basically the same thing, but the template makes things easier, as is the expected behavior from translation plugins.
I would attach the template (.pot file) in case you want to act on this and add it to your next release, but the form doesn't allow me to attach .pot files. However, I found a conversion tool:
https://mlocati.github.io/jsgettext/
Simply upload your .po file, hit the "Tools" icon and click "Convert to .pot".
More info about templates here (LocoTranslate):
https://localise.biz/wordpress/plugin/manual/templates
Hello, Against.
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
-
Thank you for passing these details to us.
Yes, at the moment we do not have any default .po and .mo files as a default Spanish file in our languages folder. ( And a number of other languages)
So, in order to be sure that our users get all the strings, i recommend that "workaround" where we copy the default English translations to a new language folder,
then rename the .po and .mo files - that ensures that all the strings are there for translations.
As you maybe know, we do not have a professional translations Team,
so all of our translations are sent to us by our users - when they translate what they need, and if it is a new language;
they send it to us, so our developers add the new language for them along with their translated strings in the plugin's languages folder - so that they won't have to overwrite the files during plugin updates.
-
I will pass your feedback to our developers, though, and they will do their best to improve everything,
as you described, to make all of this easier for our users going forward.
Thank you for this improvement suggestion and for sending all details.
I can't promise an exact ETA if they will be able to add this to the upcoming Update, or if it might get postponed to one of the later updates, but we will do our best to improve it as soon as possible.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hello, Against.
Just following up on this,
our developers will discuss this subject with our Planning Team,
they will do their best to come up with a solution to add templates for adding new languages that have still not been set as "ready for translation"
in order to make this entire process easier for our users.
At this point in time, we are still not able to say a realistic ETA when they might add this improvement,
so for the time being, it is as we mentioned,
if our users wish to ensure that they get all the strings ready for translation,
the workaround needs to be done where we take the "default" english files and copy them in a new language folder > rename and then work on translations, etc.
We will make a patch note in one of the future updates when this has been improved.
Thank you again for the feedback and the suggestion.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Milos,
I'm not really sure if I had explained myself correctly, but you don't need to create a single template for each language. If you create a .pot file, instead of an English .po file, that template will work for every new language any user want to translate. And the creation of a .pot file should take your dev team around 20 seconds to create. That's what it took me, at least.
Hi, Against.
Yes, our developers understood what you meant, my apology - i did not correctly pass what they said.
The goal will be exactly as you described; to have a "universal file" which will serve for any new language creation that has all the strings ready for translation, a .pot file ,
which will be a template for every new language any user want to translate.
There are a lot of other requests which other users have also requested,
our developers are doing their best to prioritize and they have to go through all of the tasks that are set by our management and the planning Team;
but that being said, they will still do their best to add this in one of the future updates, as soon as possible.
Please feel free to search on our suggestions page,
to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
My bad then, I didn't understand you correctly :)
All set then, have a nice day!
Hi, Against.
No, that was from my end, i did not really pass what our developers explained at first in a clear way.
But it's absolutely OK, what matters is that we are on the same page about the goal.
No problem at all.
Please don't hesitate to open new tickets if anything else comes up, we will do our best to advise.
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables