Quote:

This is planed... and probably work is on he way already if he finished with the install, contact with redhead... he is working on such, in fact will be extended DM + options to update core, modules and to apply patches. Eg. if small bug is discovered - to apply patch only for the affected files, instead - whole new distribution package/update pack.

Quote:

There are several discussions regarding this subject, older will go to archive... someone else like u may want to adopt old, outdated module and to make it compatible for 2.5/2.6/2.7... or whatever version is next release.

But there are much more important things which should be solved, before the work on such project to start.

Modules Naming and Versioning

...and bitcero and trabis have to give answer about merging of they're frameworks, bitcero to fix some important problems....

WF-Links by McDonald 1.07 works fine on 2.5.5 RC of XOOPS.
There was some minor problems with UTF-8 in past, but didn't saw them in this version (1.07).

As Cesag... block don't appears anywhere except profile page

Same on


CentOS 5.2

Could be a host problem, I did not noticed any problems with 2.5.4 Bulgarian/Croatian & English (converted files). Was testing multi-lingual feature will it for the needs of one of my clients.. unfortunately later was dropped - just bcz XOOPS is still lacking of some important modules. Otherwise there wasn't any problems with displaying content written in serbian with comments in Cyrillic.

Does this translation is done from scratch, or was based on old ISO files ?
I've did conversion to my files, and to some English files from modules released under blue-move sub-forum here.

During the alpha stages on TX, was possible to upload ISO language files - now is impossible, but when was possible, the result was mess...

@Mamba - From all 100% completed translations, which do u have ?
...and there was report (but bcz I'm using RMCommon by default have no idea, where from comes)
When the administrator is logged on site, with Zeta..blah theme as site and administrative, on front-end of the site, the bottom line with shortcuts to administration is not in Bulgarian, where those strings are located, or they're hardcoded into module/core ?

Does sv_SE alphabet contains strange symbols like Germany o with 2 dots above ? And current translation is based on non-UTF-8 ?

If sv_SE uses apostrophe like English ...let see "Someone's thing" - this should be fixed in next release of XOOPS English files, and xxx's to be replaced with .....err, there was a symbol in old days with PHPNuke.

But and can be and server-side bug
http://www.joomlapolis.com/forum/27-cb-newbies/12988-adding-an-apostrophe--to-the-language-file?limit=6&start=6#16276

More specific reading on:

Sorry for being absent last 2 weeks, but removing teeth (a thing which i should do ages ago, all of them).

Preparing Swedish translation right now... till i'm not on painkillers...

Using TX client will work maybe in 2.6/2.7 of XOOPS, when files as amount are downed to 2 max. Eg. /language/*.PHP - into one English.php. Install/language/English.php (like in XOOSLA (hopefully is not banned yet). Modules/module-name/language/admin.php and site.php, and/or if XOOPS adopt J! INI files, since POTs are double work. In that way could work.

Currently applies fine for J! language files (except core), Drupal .POT files, bcz you have to fetch one file per module, 1 for the core as whole (no matter, is it installation, administration or front-end part).

J! files looks like for extensions:
com_extension-name.ini - main file
com_extension-name.sys.ini - administration shortcuts - eg, create categories, topics, files etc. depend on the extension. Here can be:
mod_module-name.ini/php
mod_module-name-admin.ini/php

core files for the CMS looks in the same way, just they're thousands - per part of the cms, and to be avoided duplicated file names, should be used brackets or translators to separate them in to two projects.

Drupal have one file only (including all modules coming with the distribution), once is installed, everyone can use the build-in translation tool which is awfully done, or to extract English language as something.pot and to upload it there.

While we have more then one admin.php - TX client will download them as mess, and someone have to rename. So better, click and download. 2.5 core is still smaller, compared to 2.0.18.

Now every module-name-language, starts with name of the module in brackets bcz TX categories are.... pseudo tags.

sv_SE -https://sourceforge.net/projects/gtlt/files/XOOPS/sv_SE/?
most translations are still on 99%

To sv_SE translation team, manually u should add, if u want it full:

/language/xoopsdhtmleditor.php - or something like that which contains several multiple PHP arrays, still not supported by TX
/install/finish and welcome.php - they're not XOOPS PHP Define files
/per-directory/mail_templates - those should be moved to SQL with option to be changed from core/module
/per-directory/help - which should be removed from distribution and linked to help.xoops.org or wiki.xoops.org
/xoops-lib/protector - protector files are non-XOOPS PHP define files.

What's this [*/] crap added to end of my posts.... NVM.

For those planing to use old translations done for XOOPS prior 2.5.5 and TX, all language files must be encoded to UTF-8 (can be done easy with NotePad +) - Open all, convert all to UTF-8 (not UTF-8 without BOM), save all.

For those planing to loose time with Chronolabs modules onhttps://www.transifex.net/projects/p/xoops-mods-i18n/ - they're probably will be removed, since they're maintainer not pay any attention to the discovered bugs with ported modules such as MyAlbum-P by GiJoe or/and any old 2.0.x module not converted by Mamba and tagged Blue-Move. Just need confirmation from someone from devs, Mamba and they will gone.

Quote:

Nope and even if such option is added in future, will not apply to current core.
Why? Described above.

Quote:

6.4 MB translation ?
This folder should be renamed to Localized Distributions, not 2.5.x translations....

Quote:

It will be later today.

With Transifex client -http://help.transifex.com/features/client/
or
to tell me which pack is not ready so I can prepare it.

currently packaged files for XOOPS and modules -http://sourceforge.net/projects/gtlt/files/XOOPS/ - no idea if Mamba put them on X svn or not yet.

Quote:

You can't, locale.php must be provided separately

Mamba, u or me will prepare the package ?
And which translations u have to SVN ?