Re: XOOPS 2.6 Internationalization/Local support
Did I've said it already, images like
Open, Save, Post, New Thread, Reply, PM etc.
should be text declaration within INI files, CSS designers will make them looking like buttons, for example SimpleMachines Forum 2.0.2
Translators are not Graphics Designers and most modules, currently existing for XOOPS 2.5.5 and lately moved to 2.6 will remain untranslated - whole interface, error messages etc. translated, but images in English - yack!
any official confirmation in which alpha stage will see INI or POT (wish is not POT selected, but will be better then existing) ?
Does anyone take the position and initiative to rewrite X 2.6 core language files ?
1. Profile must be wiped out and rewritten from scratch.
Except all bugs discovered so far in this black hole generator, there are tons of unfinished tasks.
During user registration (for English speakers is simple, I always means me (as male and/or female), but for rest languages there are 2-3 forms. There should be used/required field - Gender.
2. Joined / Registered - got 2 translations too based on Gender
2.1. Joined for male (got one translation in Bulgarian, Russian and several more languages), Joined for female - another.
3. The user based on gender:
3.1. User made %1 posts - got another translation for male and other for female
4. Time based statistics, avoiding to hard coding "ago", 5 minutes ago must be written as %1 minute ago and %1 minutes ago - there are different translation for single minute and for several minutes, also if is written into code, translation will look awful. 5 Minutes Ago is ok for US, not for the rest of the world, in Bulgarian is ago 5 minutes (well, not really with Latin alphabet, but in this order).
5. Social activities on site:
5.1. User %1 have downloaded %2, %3 time
5.1.1. User %1 have downloaded %2, %3 times
5.2 User %1 made %1 post in our forums
5.2.1. User %1 made %1 posts in our forums
and so on...
Replacing WEIGHT, STORY, DIGEST (need to download a nulled version of another US English written script, to see that this thing DIGEST is Newsletter, grrr) and few others strange words used only by hmm(censored) with local community rule/law!
Putting option for TEXT OVERRIDE for every piece of XOOPS in administration
Replacing default media/file management with Lucio's File Manager
Wiping and rewriting from scratch Blocks Administration
X25/6 is still the easiest Framework after the "most powerful, slowish, useless" J! 3.0 release. But there is a multifunctional easy to use and upgradeable Bridge plugin (www.jfusion.org
), JFusion makes life easier - if u have idea to make site with the CMS, but currently the CMS don't have important feature u need such as forum (yay, X and J! don't have much options..... 1 forum per core, no choices), you can simply write plugin for the Bridging plugin and use MyBB, SMF or whatever u want.
Mail Templates must be re/moved to SQL and to be made editable from Administration.
Help must be moved to wiki.xoops.org
(Can't wait to see redheaded Install script)
After some tests during my vacation on latest CMS cores, including:
J! 3.0 Beta 1
XOOPS 2.6.0 Alpha 1
Tomato Cart 2 SVN
PresaShop 1.5 SVN
I've noticed some very funny bugs which should be avoided here.
Joomla! 3.0 works fine with GPC Magic Quotes On, but the stupid installation pre-check script prevent user to install it with On value in they're PHP.INI files.
X 2.6.0 Alpha 2, must includes option to ignore pre-check if one of the optional values such as GPC Magic Quotes is enabled or not.
PrestaShop 1.5 made a big progress in making administration easy to use, but, there is always but.
+ Single click module installation and auto-upgrade from the administration, but bcz there is lacking of MD5 or SHA1 checksum verification on modules, such installation can't be done properly, for RC2 - looking more like Alpha 2, is very disappointing result. Again... lack of coordination here, makes redheaded and wishcraft to work separately on different modules/frameworks for one simple task.
+ Making administration sorted (User tasks in one menu with several drop-down options), here as I saw users tasks are still in menus which no one expect to be there
+ TomatoCart/pincore - Windows XP still remains most used Desktop this days, and maintaining such administration style in X 2.6, will be a plus. The 2nd big advantage of this theme are the conflicts between Internet Exploder versions prior 9.0 SP1 with Ext JS library, if the user want to use Ext JS style have to switch to Firefox - and bye, bye Exploder - no more pointless threads on support forums regarding any part of the CMS which is not displayed properly thanks to damn MS Exploder.
+ "Responsive" Templates... err, themes here. Every core of the new CMSystems got one Responsive template for they're default administration/site view, which in one word - shows no difference in site/administration display on Chromium with Gentoo, Firefox with 7/8, Chrome on Android or Opera latest beta (don't remember which is latest 12.xx. beta) - http://www.newspaperwebdesign.com/node/15874
Main Dashboard of X26 should be full with statistics blocks, not with double information about installed modules. Eg. Registered Users, used system resources (specially when X is mostly used on shared hosting plans), made posts in any area - news, forums, top authors, users with most applauds or most warning and so on), why there are modules and tasks with big icons, and with small icons in header bellow menus, and again in menus.
PrestaShop 1.5 administration (if u want to see it and don't have time to install it, drop me PM) is a perfect example, how modern administration must look.
There are planed updates on TX (but still in development and tests), for GIT support for the Reviewed releases (eg, finished and reviewed for bugs translations).
X 26 Alpha 3-4, must support cURL and GiT for sync directly with translated, verified only modules, then the need of packing and listing them in several threads on forums here will gone. If Iranian (Farsi) user plans to use X26, News, NewBB, simply with one click from administration will be able to download and apply the required language files.
In past there was Lang_tool (XOOPS 2.0.18) written by Vietnamese or... can't remember right, but I'm 99% sure, he was an Asian developer, module which allows u to edit, correct, write new language files for core and any of the 3rd party installed modules, such option must exists first for the TEXT OVERRIDE option, 2nd... if the above Farsi user don't like something how looks translated to be able to correct it in the way he want for his site and needs.
....and DECISION which standard will be used, INI (1.5 or 2.5, or derivative mix of both), POT (yack, big sorry for all translators, bcz there is only 1 English native speaker as module developer, and is not Wishcraft) or PHP Define which will be a big step backward.
(In 5 days will update X Modules translations and will see if there are new core translations, just I'm still on road almost every day).
May The Source Be With You!