With current language files written in Yoda English or even Alien English - XOOPS will remain less used CMS, bcz of the hard way to be understanded.
And again - this are strict rules placed from Infidex
http://help.transifex.com/features/formats.html#php-files
Scroll down to PHP Define statement, if there is a formatting - forget to be supported.
Quotation from private discussion with Infidex developers.
Regarding quotes (predicted question, before to upload any files):
Quote:
Well, _QQ_ is used in Joomla!, but not in PHP. So, our PHP handler does not expect it to be a replacement for quotes in PHP strings in the PHP files. Currently the implementation supports PHP type strings. Let me explain with examples:
Below are the strings supported by the PHP hanlder:
"This is a string"
'This is also a string'
"This is a double quoted string with a single quote ' in it."
'This is a single quoted string with a double quote " in it."
"This is a double quoted string with a double quote " inside it and a single quote ' too."
'This is a single quoted string with a single quote \' inside it and a double quote " too.'
I hope this the above example is self explanatory. To conclude, double quote " inside a double quoted string should be escape ". But a single quote ' inside a double quoted string need not be escaped. Similarly for a single quoted string too.
Thanks,
Regards,
Ratnadeep
Reported errors coming from mostly XOOPS files (banned cms is clean of them, no matter they're using same modules). This was and my mistake, but who the hell got the idea, that everyone in xoops.org maintain language files without following any rules and standards. And the result is present. Errors bellows, plus smaller sizes - if the language file is 37k, TX reads only 7k.
Some PHP Define files returns strange errors or no errors.
List of strange errors
'utf8' codec can't decode byte 0xe3 in position 101: invalid continuation byte
'utf8' codec can't decode byte 0xa3 in position 695: invalid start byte
'utf8' codec can't decode byte 0xe9 in position 7120: invalid continuation byte
'utf8' codec can't decode byte 0xe9 in position 2105: invalid continuation byte
'utf8' codec can't decode byte 0xe9 in position 104: invalid continuation byte
Answer from Infidex:
Quote:
Hi Stefan,
We do not yet support nested elements in PHP files. This in our TODO list in the future. But I am not able to give an ETA on this.
Regards,
Ratnadeep
question: Can you give example how one PHP DEFINE must looks:
answer:
Quote:
Hey Stefan,
You can find some examples herehttp://help.transifex.com/features/formats.html#php-files
Regards,
Ratnadeep
--
Transifex Support Team
What u will get from *real* testers ?
fully functional, bug free module, written in Alien/Yoda English, not understandable, not translatable, not usable. Thanks but no thanks, XOOPS 2.2 Mithrandir and the next release 2.3 are pure example of that. Thanks to *real* and unreal testers, u got somehow stable core, not readable, not understandable, except Wishcraft forks, no other modules are made for 2.3, and except Mithrandir forks nothing else was written for XOOPS 2.2.
I personally don't split testers on Real and Unreal (damn good game, I should spend some more time instead in OS).