Posted on: 2013/1/25 12:37
Re: Translation Teams on Transifex
I am not sure, this is required. Their example is having spaces after the comma:
Is this required by Transifex? I didn't see it anywhere...
She got me wrong probably, currently writing explanation, where is accepted and where not. And she is doing her job well, not insulting anyone (If I was on her place, everyone can imagine the result:) ), she is just new to the whole system...
XOOPS and all forks, have same structure. Once with ', another time with ", this is up to the core dev team, how they will be written and maintained, the important is to NOT have spaces between ) and ; and between last word inside the line, eg.
"words are here" ) ; - this will lead to strange TX error.
("_AM_MYTABS_CREATE_TAB", "Create a new tab");
('_AM_MYTABS_CREATE_TAB', 'Create a new tab');
('_AM_MYTABS_CREATE_TAB', "Create a new tab");
( "_AM_MYTABS_CREATE_TAB" , "Create a new tab" ) ;
("_AM_MYTABS_CREATE_TAB", "Create a new tab") ;
What will be inside for _AM_SOMETHING or the text, can be set by Trabis and rest currently working on tree. If will be " or ' or both, AM_Something with ' and text with " or vise verse. During the beta releases of TX there was requirements, inside the bracket to be (AM_DEFINE) with same symbols, but thanks to M.A. and some other people and Infidex of course, those limits are gone.
Protector files have to be changed (definitions) to standard XOOPS definitions in order to be included in 2.5.6 Final. Currently XOOPS (only core) on TX, don't have protector files.
@Rest of translators, yeah... when I had in past XOOPS Bulgaria for unofficial local support sites, the priorities was set by the users. Content at first place, Web Links at second and so on. Now priorities are different, not set as REQUIRED ORDER, only as option. All of us have families, rl stuff/tasks and a lot of more things to do, but when we have time, to translate all modules under Blue-Move section, so when a user, random visitor got XOOPS-2.5.6 from here and the Basic Module Pack, to have fully functional CMS in his own language. That's all, no one sets time limits/deadlines (that's best on volunteer job) on translation tasks. If you don't like TX by any reason (really it's not important, what the reason is), simply select your language as coordinator and upload the translations to each language file per module. If you are not Language Team Coordinator, forward it to such or via GoogleCode/SF.NET or mirrorcreator to Cesag, she will have all REALLY latest modules translated and updated on GIT.
@Cesag... drop me a PM with your email, bcz I forgot it, even don't remember and name... (damn empty old head..:) )
ps. and the problem with infinite lines caused by CRLF still exist probably... have to verify it next few days... Cesag if have time can upload one file with CRLF to see if is corrected in latest version of the platform.