51
Gettext POT/PO files are readable with NotePad + which should present on every translator/developer desktop with Windows OS.
PO/POT will open double work for developers, as already noticed, some deserves POT to stop loosing they're time and playing with formatting.
For Joomla! which was best core developed until last release of 1.6 followed by 1.7 and 2.5
INI files with "" - is more faster then even POT files, well for me as end user, 2.5, 1.6 and 1.7 ruined the myth for the best cms ever with the awfully written core ever.
But INI files with "" still causes a lot of troubles on TX platform, no matter that I'm working really hard with Infidex (bcz with joomla.org cooperation is impossible) to make TX platform fully compatible to this stupid standard.
INI files without "" used in 1.5 are better, and everyone with 5 minutes free time can see the difference in speed between 1.5 with demo content and 2.5 demo content. Just out of words how slow is 2.5
J! 2.5 INI file
J! 1.5 INI file
By adopting J! 1.5 INI files structure, XOOPS gains:
- The need of maintaining 4 to 10 files per module with double content will gone, 1 file is enough
- Formatting lovers can't play with language files anymore
- Easily maintaining content such as web site addresses or mail templates within language files
Quote:
(XOOPS need diplomat to solve problems with rest communities)
Extended on above - developing function for syncing completed language files from TX to the current core and installed modules (work in progress by banned CMS)
Quote:
Absolutely, current way is awful.
Quote:
This missing feature stops XOOPS from evolving.
Quote:
Also there is a TEXT OVERRIDE, where users can use different words for something u love to use in XOOPS, with text override u can keep your beloved WEIGHT and users to use ORDER or POSITION, in this way of thinking will eliminate the need to edit the misleading terminology still used somewhere in XOOPS, every user can rewrite
WEIGHT - to ORDER, Posted to Published, Account to Profile.
Regarding POT, bitcero throw the bomb and get away, RMCommon supports only en.po, which for me is not support at all. There is the bug with this framework and all of his modules for not accepting anything other then en.po, also as POT files, there will be loosed a lot of time for finding and removing Spanish/Brazilian words from English files.
PO/POT will open double work for developers, as already noticed, some deserves POT to stop loosing they're time and playing with formatting.
For Joomla! which was best core developed until last release of 1.6 followed by 1.7 and 2.5
INI files with "" - is more faster then even POT files, well for me as end user, 2.5, 1.6 and 1.7 ruined the myth for the best cms ever with the awfully written core ever.
But INI files with "" still causes a lot of troubles on TX platform, no matter that I'm working really hard with Infidex (bcz with joomla.org cooperation is impossible) to make TX platform fully compatible to this stupid standard.
INI files without "" used in 1.5 are better, and everyone with 5 minutes free time can see the difference in speed between 1.5 with demo content and 2.5 demo content. Just out of words how slow is 2.5
J! 2.5 INI file
NAME="Name"
TITLE="Directory"
NAVIGATE TREE="Navigate Tree"
ADD LISTING="Add Listing"
EDIT LISTING="Edit Listing"
ADD CAT="Add Category"
J! 1.5 INI file
NAME=Name
TITLE=Directory
NAVIGATE TREE=Navigate Tree
ADD LISTING=Add Listing
EDIT LISTING=Edit Listing
ADD CAT=Add Category
By adopting J! 1.5 INI files structure, XOOPS gains:
- The need of maintaining 4 to 10 files per module with double content will gone, 1 file is enough
- Formatting lovers can't play with language files anymore
- Easily maintaining content such as web site addresses or mail templates within language files
Quote:
1- develop lang tools
(XOOPS need diplomat to solve problems with rest communities)
Extended on above - developing function for syncing completed language files from TX to the current core and installed modules (work in progress by banned CMS)
Quote:
auto diff
Absolutely, current way is awful.
Quote:
full customization of language files in themes like this:
themes/YOUR_THEME/module/YOUR_MODULE/language/YOUR_LANG
This missing feature stops XOOPS from evolving.
Quote:
have different definitions for different clones of the same module. very useful and needed.
Also there is a TEXT OVERRIDE, where users can use different words for something u love to use in XOOPS, with text override u can keep your beloved WEIGHT and users to use ORDER or POSITION, in this way of thinking will eliminate the need to edit the misleading terminology still used somewhere in XOOPS, every user can rewrite
WEIGHT - to ORDER, Posted to Published, Account to Profile.
Regarding POT, bitcero throw the bomb and get away, RMCommon supports only en.po, which for me is not support at all. There is the bug with this framework and all of his modules for not accepting anything other then en.po, also as POT files, there will be loosed a lot of time for finding and removing Spanish/Brazilian words from English files.
May The Source Be With You!
