2
en-GB corrected language files, converted to Unicode UTF-8 and transformed to XOOPS coding standards -
http://sourceforge.net/projects/gtlt/files/XOOPS/Modules/en-GB_XOOPS2_mod_avaman-0.22RC2_Mamba.zip/download(a bit offtopic) I'm afraid that some modules made by GiJoe and currently maintained by randoms (XOOPS Community, Wishcraft) are affected by this "anarchy").
This is how each line in the language file must look
define('_MI_AVAMAN_MODULEDESC','Managing system avatars and smilies');
not like GiJoe wrote it
define( '_MI_AVAMAN_MODULEDESC' , 'Managing system avatars and smilies' ) ;
quote from Marc Andre:
Quote:
Line Termination
Line termination follows the Unix text file convention. Lines must end with a single linefeed (LF) character. Linefeed characters are represented as ordinal 10, or hexadecimal 0x0A.
Note: Do not use carriage returns (CR) as is the convention in Apple OS's (0x0D) or the carriage return - linefeed combination (CRLF) as is standard for the Windows OS (0x0D, 0x0A).
Protector language files are not included anyway. But they're affected by the anarchy set.
MyAlbum-P currently maintained by Wishcraft, Unix delimiters, but GiJoe way of typing.... translations are halved, over 90% of the strings are not included.
During my absence next 2 weeks, will try to verify every XOOPS 2.5.5 RC file for Apple OS (CR - 0x0D) and to replace it with CRLF, probably the userinfo bug will gone. For rest modules.... if got time.
Should I write How To coders to maintain they're modules and language files, or u will do it ?
May The Source Be With You!
