for translations.

Such things, like
Quote:

Forget to be accepted or someone else to convert it to the normal way, which should be:


Also modules like xcontent and benchmark, containing strings which are not supposed to be translated are not welcome too, if u want to see it translated - move them out in another file.

Modules written in past for XOOPS 2.0.18 by some great developers like Herve, Catzwolf, GiJoe - need a lot corrections:
1. Convert them to UTF-8
2. Remove the copyleft information from the headers (french on ISO looks very nice, like Herv?.
3. Check and remove any invalid spaces before making new additions to the language files. Do not add invalid spaces in new additions.

Global (in addition to rest):
1. Verify that all strings are in English (I know that some of u're not native English speakers, but please Spanish words or French in English/ folder are not accepted). If you don't know English at all, contact with one of the team leaders to make it available in normal English, instead of using Google or such automated services to provide English language files.
2. Avoid double posting, same strings in main.php and modinfo.php
2.1. Since XOOPS core files contains so much definitions already, why module developers simply not call them instead to write new one ?
3. When u release new version to a module, no matter from Beta to RC or from RC to Final, mention which files are changed (Language) if there are any changes.
4. When u get response for coding bug, syntax error - respond fast as possible, otherwise looks like the module is released and abandoned.
5. If you get translation submitted from user done with 3rd party program (eg. email, your local support forums), provide it for synchronization with Transifex Platform.
6. Avoid to use misleading terminology, lets take example with e-commerce solution such as osCommerce and it's thousand forks. You are using Weight for Position, and Weight by the default is using to point the user for weight of the package. There is no such thing as Weight for categorization or file sorting. Imagine how will look Category A in position Weight translated as Weight - stupid.

(more to come)....

Also UNIX LF instead of windows CR+LF
IMO the above is very important.
long discussion before but still is not a regulation.

edit:
also utf-8 files should save without BOM.

Quote:
That was important for the time of 2.0.xx of XOOPS with PHP 4 and MySQL 3, the ready production from TX is in UTF-8 and there is no problem with any XOOPS.

No long or short discussion, they're disallowed, anarchy can be allowed and supported here, but not on TX, if the module developer wants his module in many languages will follow the rules.

And the rule in Transifex is windows CR+LF?
then the rule should be promoted here too.

the CR+LF bug probably is fixed, let me check.

7. All lines must end with CR+LF, LF only causes infinite loop.

Quote:
Where? On Transifex???

Yes, DCrussader already wrote it in some topics.
Also i told you to send an email to this TX admins and ask about their reasons.
Now our developers are confused between these methods.

Imtfan is right;
- yeah was mention long time ago, want me to discuss it with Infidex or u will take this part ?

Currently on banned cms I don't have problems which comes with X Core and Modules, bcz all they're files end with CR+LF, all strange symbols are removed, now they have to clean invalid spaces and my favorite Weight. Catz fork and XOOPS, still have some messed up files. (Well, not for the core) Once 2.5.6 or 2.6.0 is released as Beta, should review (for last time) every file for invalid spaces.

Some of the modules (not only Wishcraft modules) will be removed for infinite loops and no response from the module maintainer.
Some for the containing of non-transalatable strings (not only in Wishcraft modules).
Some for formatting language files to make them looking cool.

NVM, added to Infidex support desk:
Quote:
Waiting for reply.

For me CR+LF is not a problem, for XOOPS to operate too, I'll not lock translations till Infidex respond - and they need sometimes like week or two to make reply.

Quote:

1. What with regular comments?

2. Spaces before line?
3. Empty lines?

Any restrictions or requirements?

1. If they're in UTF-8 without BOM or UTF-8 - u can use Options préférences, but since we talking about English language files, all // comments must be English.
Example for small copyleft information, taken from latest version of mycomments


That's all - English symbols, not O with double dots above or such things.

2. Spaces in definitions - formatting is not allowed
correct definition:


Incorrect definition (look at GiJoe's modules)


3. Empty lines?
If they're not formatted, they may stay.

Rest requirements are mentioned above: CR+LF for end of each line (until get response from Infidex), Unicode