irmtfan wrote:
@Trabis:
I review your updates. they are really fantastic.
Now all local needs are covered include isRtl and isMultiByte.

just 2 point:
1- will you add strtotime in the future?

2- a bug in your example pt_BR in xoops26/locale/pt_BR/locale.php

le="color: #000000"><?php class XoopsLocale extends XoopsLocaleEn_US{

should be XoopsLocalePt_BR

flipse wrote:
I can't reproduce examples now but most difficulties when translating arrise when strings are used on more then one place. In some cases an English phrase or word cannot be used in a different context where it is no problem in the original language. Avoiding similar language strings at more places might be translator friendly but can be a pain in the ass in some cases.

/**
* Naming conventions
* - All translations must be enclosed with ""
* - All translations must start with Uppercase, do not use CamelCase
* Good ex: "User groups"
* Bad ex: "user groups" or "User Groups"
* - All keys must be as descriptive as possible.
* - All keys must use complete words between each '_',
* - Keys should be prepended with identifiers in following cases:
* F_ Formatted, use this when strings are parsed with sprintf()
* A_ Action, use this when using a single word which is a verb
* S_ Success, use this for success messages and exclamations
* E_ Error, use this for error messages
* C_ Colon, use this when string ends with a colon ":"
* Q_ Question, use this when string is a question
* - Chain keys alphabetically with the exception of F, F always comes in last
* ex: SF_ (formatted success message), EF_ (formatted error message)
* - Special cases:
* CONF_ Configs, prepend this for your module configs.
* Config keys are stored in database, try to make them as short as possible!
* _DESC Description, append this for configs description
*/