IndexU Deluxe is a great product and I think there is a fairly strong community that contributes, for example, to the language support.
I have one suggestion about the language support, though, and I'd be happy to hear reactions to this:
I feel IndexU is great for listing targeting a single market/language but not suitable for expansion to other markets.
There are several language packs available, which make the program itself usable in multiple languages. But when it comes to having a multinational/multilingual environment, it doesn't work so well.
Let me try to explain with an example. Language packs are available. So if a classifieds site in Saudi Arabia wants to use IndexU, it can. So can one in Czech Republic.
However, if there is a classifieds site that has ambitions beyond its own country (like mine), then we run into a problem - the users can use the language panel to "translate" the website, but the content remains in one single language! In other words, if I have English, Bhasa, and Hungarian language packs installed, users from UK/US/ANZ, Indonesia and Hungary can access it, and have interface translated just by clicking a flag - but the content (link description, name, etc) remain in a single language.
I think the development team should seriously look into implementing an Opencart (OpenCart - Open Source Shopping Cart Solution) like solution, where when Admin installs a language pack, many fields (such as product name, meta tags description, product description, category names, category description, etc etc etc) are duplicated for the new language. So now, the admin (or user) can enter content in 2 languages, and depending on the language chosen by the user, appropriate content is shown.
From my perspective, this is a very important feature. Category, subcategory names can be different in different languages (even country names are different in different languages), site descriptions and other content can be different in different languages, for some sites, the URL could be different for different languages, so I don't see why IndexU has to restrict itself to a single content model.
Believe me, implementing this single feature, would put IndexU heads and shoulders above other directory listing programs...


