Today I tested Chronoforms 5.0.10 on Joomla 3.4.5, and it seems very powerful. Then I tried to translate it into my native language (Chinese), but then I found out that this component does NOT use .ini format language files. It uses the lang.php file for language strings.
Obviously this is not the Joomla standard. Why not use .ini format language files and choose filenames following Joomla conventions?
Thanks.
Hi baijianpeng,
For some code reasons, but its very easy to translate the .php language files, the .ini don't have extra advantage.
Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
At first, I think .ini format is the Joomla 3 standard for language file type.
Second, .ini format is very easy to validate translations and check for update with another Joomla translating tool named "com_localise".
If you use .php format for language files, I can not validate and check them with com_localise.
Do you have any better tool to validate translations for .php format language files?
What's the meaning of "validating" translations ?
we don't have such tools, but if the problem is just the file type, then I can make a small tweak to read .ini files also, but they will have to be under the same path, if this is ok then you can send me a message using the "contact us" page to check for progress.
Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.