I liked the "multilingual" capability in xCenter from Wishcraft, but I didn't like the name too much, as it was a little bit confusing, and the images were not consistent with other modules.

So I've forked that module as "xContent", and adjusted the images and structure.

You can download it from XOOPS SVN, just click on the "Download Snapshot" link.

Please test it and let me know what you think. Please help us to make it simpler and easier to use.

I would like to include it as our basic "content" module in future versions of XOOPS, as well as our "Basic Module Pack". I think, it provides the basic features for a content module, and the "multilingual" capability makes it very attractive.

Going to test it right now, is this one have to replace Herve News or it's for static content only ?

Hmm, language again (till I uploading XOOPS-20120718, checking them first)

in main.php
define('_XCONTENT_AD_MADEBY', 'Last Edited By');
Should be - Modified by: (Stop With Those Capital On Every Word)

define('_XCONTENT_WRITTENBY', 'Written by: ');
Why not Written by: %1 - how this   will be accepted by TX in ANSI

define('_XCONTENT_MSG_SECURITYTOKEN', 'passkey Security Token needs to be refreshed - please refresh the screen!');
Can you translate this in Human readable English - we've talked about Ease of use, such strings not make it easy

Hmmm
define('_XCONTENT_XCONTENTEXPIRED', 'xContent has passed it expiry date!');
Alternative English translation for this ?

and this
define('_XCONTENT_TOBEPUBLISHED', 'xContent has to reach it publishing date!');

define('_XCONTENT_THISCOMESFROM', 'This Comes From:');
This (ghost) comes from ?
The source of this page is: (sounds much better)

And here
Quote:

Published or Posted ?
Published on DATE
Published by SOMEONE
Published ON SITE

define('_XCONTENT_AD_TEXT_DESC', 'xContent that appears in the page under ID');
Master Yoda's English ?

--------------------------

Modinfo.php

define('_XCONTENT_AUTHOR', 'Written by Simon Roberts aka. Wishcraft');
Since is forked, there should be new definitions: XCONTENT_MAINTAINERS - Mamba, all discovered bugs and features requests to be forwarded to maintainer, author have nothing to do with this fork.

Nice comment
"// MAINTENANCE ACtioNS"

...and ANSI (why there is no conversion to UTF-8), damn forks from forks


how the definitions bellow will be accepted by TX ?

//MYSQL TABLES WITHOUT PREFIX // DO NOT CHANGE

90% of the file is DO NOT CHANGE... is this a language definition file or source code ?

Those lines bellow each comment - do not change, must be moved in another file, common.php or else.

This is for static content only (basic addition).

For advanced Content module we will need something sophisticated like News/Publisher/AMS. The current feedback from the community seems to be leaning toward Publisher as the "official" Advandced Content module, unless Voltan comes with something new and cool.

Why not static and dynamic content to be united in one code and added directly into core. CMS without content management....
xContent Features with Herve's News, AMS and Publisher features into one package, part of the core ?

I manage several small sites which just need a few static pages. A module like this is exactly what those type of installations need. There's no need for all the complexity introduced by a full article / news management system. For these type of installations I install/configure/customize the system for my customer and then they manage the static content on an 'as needed' basis. Training for a simple module is much easier than for a more complex system. Wfchannel was excellent for this type of installation, although it's no longer in development.

I think there's a need for both type of modules - gives XOOPS more flexibility. I do agree the 'full' article and/or news module should allow for both static and dynamic content, SEO, tagging, social networking, etc. but it's more than many small business sites need.

Flexibility ?
With tons of forks on content modules, XOOPS is the only one CMS at the moment without Content.

Quote:
I agree with you - it has to change.

One way or the other, next XOOPS release will have a "content" module included.

Hopefully, a good one, and very user-friendly.

Quote:

Give me the English files :)

Quote:
We'll be working on this.

First, the functionality and bugs fixing, and then correction of language files. For the spaces, we'll just need to run "search and replace"...

Thanks for keeping eye on all the language files and translations! This is very helpful for our international users.

Btw, take out the non-translatable strings in another file, till is BETA, otherwise mutli-lingual functionality will be useless.

Spaces are on places where S&R can't work

DEFINE (space) ( (space) '_SOMETHING' (space) , (space) 'Something' (space) ) (space) ;


what if the definition contains 'Something about' - then and this space will gone.