31
trabis
Re: XOOPS 2.6 Internationalization/Local support
  • 2013/1/22 22:29

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

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.


In Portuguese I have problems with single words.
TEXT used in "article text" is different than "text a friend".
In this refactoring I'm prepending A_ (action) on single words that are also verbs.
The keys are also being extended to provide
Here are some of the conventions I've applied so far:
Quote:

/**
* 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
*/




32
trabis
Re: XOOPS 2.6 Internationalization/Local support
  • 2013/1/22 20:23

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Hi there,
I'm currently working on refactoring language definitions and I'm looking for help regarding problems you face during translations.

I wish to know special cases where the current definitions cannot be correctly translated into your language.

For example, I already know that the user gender can be a problem when you want to translate 'User %s has %s posts", or "You are registered!"
I also know that concatenation for "%s minutes" and "ago" should not be used because the order of "ago" is important. Instead we should use "%s minutes ago".

In Portuguese language, most of the times I can get around the gender issues by making the translation fit both genders, and when not possible I can append '(a)' to fit the female gender, ex:"Obrigado(a)" => Thanks. Is gender really important in other languages? If so, can you give me more examples where you cannot get around the gender issue?

Strings with ":", for example "Number of posts:", does the ":" need to be in the translation or can it be concatenated by the developer? I imagine it is required to be in the string for RTL support, please confirm.

Plural forms, in portuguese/english we can use something like "Has %s post(s)" when we are not sure if the number is plural or not. Is this possible for other languages also, or plural forms can be very different? Please give me examples of definitions that should have plural form support.

Thanks




33
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/18 19:17

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


@sabahan,
thanks, it is fixed now.



34
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/16 21:56

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

andrax wrote:
I performed a new "standard installation" (next, next, next...) and now it worked... At first, as the modules are installed before of plugins, soon after finalizing the installation, the module page does not display the comments, but after updating the module, the options of notification system and comments appear


This should be fixed on SVN now. Installation of comments and/or notifications does not require modules updates anymore.



35
trabis
Re: What is Scope of Protector Auto Spam Block?
  • 2013/1/16 18:30

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

xoobaru wrote:
Does the enabled stopforumspan.com auto-lookup and block feature of protector check and block someone(thing) from signing up if they come from a known spam IP or host?

Yes, not only on register, it checks every POST request. Comments, contact forms, etc



36
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/15 21:49

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

andrax wrote:
Well, I tried updated the modules and nothing of comments or notification system work...
I tried uninstall modules and I think that I found another problem... was not possible to uninstall modules or extensions, none of them...


Can you share your system specs?



37
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/15 20:26

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

timgno wrote:
Quote:
Can you give me more context on this? I can't reproduce it :(


Is in popup pmlite


Thanks, it is fixed now :)



38
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/15 19:34

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

demented wrote:
When Using Menus Iget this error

Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/content/s/c/a/scaremaster/html/test/xoops_lib/Xoops/Module/Helper.php on line 41


I'm sorry, but xoops 2.6 requires "PHP version >= 5.3 (PHP 5.4+ is strongly recommended)" as stated in the release article.



39
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/15 19:26

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

timgno wrote:
Quote:
Error: No entry is registered for key 'XLANGUAGE' in file /xoops_lib/Xoops/Registry.php line 144
Notice: Undefined index: XLANGUAGE in file /xoops_lib/Xoops/Registry.php line 147



Can you give me more context on this? I can't reproduce it :(



40
trabis
Re: XOOPS 2.6.0 Alpha 2 released for Testing
  • 2013/1/15 18:55

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

andrax wrote:

And to conclude, seems to me that the comments plugin is not working, at least it does not appear in the modules (Page or Publisher)


If you install comments or notifications after installing publisher or page, you have to update those modules. Only after updating them, the configs for comments/notifications become available for those modules. The same applies if you decide to uninstall comments module, the configs will be displayed on publisher configs until you update it.

At this moment, this is the behaviour. Perhaps I can change it to make it more friendly.




TopTop
« 1 2 3 (4) 5 6 7 ... 190 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

64 user(s) are online (36 user(s) are browsing Support Forums)


Members: 0


Guests: 64


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Dec 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits