Thanks for the speedy reply.
My philosophy that life should be simple.
Not all projects [themes, plugins etc.] have to be translated as long as they complie with WP standards and ready for Latin and RTL.
In most cases admins do not need translation, therefore the time spent on complete translation of the back-end and creating a language file is waste of time and an added resource for sites.
On the other hand, if a widget has to display to the end users 3-5 line of text it would be much simpler to have a text box like this:
users on line;[users]
guest on line;[guest]
And so on where the words in brackets are the parameters.
And in Hebrew, Arabic or any other language like that:
משתמשים;[users]
אוחים;[guests]
I think that this is a better approach then having hard coded check boxes.
In addition, this way wallows you to compose the text with or without the line break like on my site:
https://mityaalim.org/
stats
You can think of it like having a display name instead of pre-defined text.
Thanks for listening
-
This reply was modified 8 years, 5 months ago by
axiosil.
Actually translation are based on WordPress system,
So if a language translated to approximately 80%,
The system use that locale in installed plugins
I understand your point but from a user perspective it is a pain in a… to deal with language file because most of the times it is not up-to-date and many phrases are missing in the developer English file.
I do appreciate the hard work in the development of this plug and I’m sure also that you understand the value of using variable instead of hard coded phrases.
Even the forum that I’m using that is loaded with text in the front end, translated 90% + it is impossible to keep up with translations and they’ve added local phrase translation that overrides the language file. In some other similar plugins the solution was to have in the widget a text + var and that’s it, very simple without translation of WP community.
I’m writing to you as appreciation to your hard work and want to help development for a better user experience.
From my point of view, it is not worth the time and I’m using now another plug, with lesser options but adoptable to any language without a language file.
Thanks for listening.