xoops forums

Forum Index


Board index » All Posts (DCrussader)




DCrussader

Friend of XOOPS
Posted on: 2012/8/9 15:01
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#51

Re: XOOPS 2.6 Internationalization/Local support

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
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!


DCrussader

Friend of XOOPS
Posted on: 2012/8/9 14:13
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#52

Re: News 1.68 Beta 1 released for XOOPS 2.5.5

(Newbb is the most useless forum ever)
Why I should add new post instead to edit and add to previous....?
why post can't contain more then 5 links and why there is no error message, white page is not professional?

anyway
Tell a Friend must be removed as function - common way for spamming users.

The old Nuke way of rating content to be removed and replaced with something like this
http://www.9lessons.info/2009/08/vote ... -jquery-ajax-and-php.html
where there are xxx positive and zzz negative votes
or with 5 starts
http://extensions.joomla.org/extensio ... es/ratings-a-reviews/4901
such simple plugin can be ported easily

Due the need of eliminating invalid intervals, all previously done translations need to be updated, they're from 98 to 93%


DCrussader

Friend of XOOPS
Posted on: 2012/8/9 8:53
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#53

Re: News 1.68 Beta 1 released for XOOPS 2.5.5

Since is News, and there is News by the same author string, there should be search and replace on all Story, Stories with Article, Articles.

Outdated translations including englishUTF8 must go.

modinfo.php
Lines 122-127 must go, there is no SPAW and Koivi anymore (damn, Koivi was good editor).

Line 150 must be corrected, Tinyeditor is tinymce (yack)

For lines 186 to 190 someone desire punishment!

main.php
Line 9 must be removed with whole function
define('_NW_BYTESMORE',"%s bytes more"); - The news module is a content, not File Download management.

Line 18
define('_NW_THESCOOP',"The Scoop");
This is "Intro"

hmmm, the mess is full - main.php is full with Stories/Articles... should be Article, Articles everywhere

Line 102-112, instead of adding function for every single social network, use
http://www.addthis.com/

Line 120-131 - same, single function to one service - http://www.addthis.com/


admin.php
Someone really want punishment, guys are u really don't have work to do ? I can find u a lot of work!

Line 197-208

Is this MS Office Document or language file ?
Next module with such lines will be dropped, bcz this is the only content module will correct it once, next version - nope, no more corrections in future for modules with pseudo-formatted language files.

Wondering if 2.6.0 was adopted the Joomla! 1.5 INI files, how u will loose precious time to play with such crap?

newsletter.php must be moved into SQL with function in the module - the whole template to be edited/modified from within the module.

Removed invalid spaces, converted to UTF-8 without BOM
http://sourceforge.net/projects/gtlt/ ... ws-1.68Beta1.zip/download

TX Task - https://www.transifex.com/projects/p/xoops-mods-i18n/r/news167rc/

@Mamba - can u make sub-forum Archive and to lock and move News 1.67 RC thread there, with all old versions for other modules


DCrussader

Friend of XOOPS
Posted on: 2012/8/9 7:56
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#54

Re: Transifex Requirements for accepting files

Quote:

I want to sum up all recent posts and create a new wiki page here.


I'm expecting this wiki from ages, so finally the stupid and useless folders /help to be removed from XOOPS distribution.

"From here u can install modules" is everything else but NOT help, should looks like:
"From here u can install modules, previously uploaded via FTP to your /modules folder, if u know what the heck is FTP" - (Most users this days uses Softaculous (or whatever it name is), CPanel auto-installer scripts, and no one cares to learn what is FTP and what for is.

....and outdated mail templates to be moved in SQL with function in the system module.


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 13:49
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#55

Re: Transifex Requirements for accepting files

Quote:

### Mastop InfoDigital - Paixão por Internet


If they're in Unicode, ok... but Braizilian comments in English language files, and/or Brazilian words in English strings.. that's unacceptable.

Quote:

We definitely need a standard for all modules.


Yay, someone finally awakes :)

Just as reminder - translators, are not image designers, avoid of using any images such as
modules/newbb/images/language/english
modules
/newbb/images/language/arabic


Use CSS styling for buttons, look how is done SMF 2.0.2, no images.


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 10:03
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#56

Re: Transifex Requirements for accepting files

1. If they're in UTF-8 without BOM or UTF-8 - u can use Options préférences, but since we talking about English language files, all // comments must be English.
Example for small copyleft information, taken from latest version of mycomments
//  Author: Trabis
//  URL: http://www.xuups.com
//  E-Mail: lusopoemas@gmail.com


That's all - English symbols, not O with double dots above or such things.

2. Spaces in definitions - formatting is not allowed
correct definition:
define("_MB_MYCOM_DISPLAYC","Display %s comments");


Incorrect definition (look at GiJoe's modules)
define "_MB_MYCOM_DISPLAYC" "Display %s comments" ) ;


3. Empty lines?
If they're not formatted, they may stay.

Rest requirements are mentioned above: CR+LF for end of each line (until get response from Infidex), Unicode


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 9:52
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#57

Re: xLanguage 3.03 Beta 1 -ready for testing & feedback

This starting to become a flame, but I'm always right, since spending more then 8 hours daily for XOOPS/Banned/XOOSLA/Cube:
(Stop looking at XOOPS and rest just as Coder) XOOPS/Banned/XOOSLA/Cube are not just a code. If they're was will be classified as FRAMEWORK, not CMS, and such discussions will not be even started, who want to use the damn Framework, to translate it on his own.

I want to see at least one X core, coming close to 2.0.18 popularity. This (content)Management System have potential...

Quote:

Also you are totally wrong about Xoops 2.2 or Xoops 2.3. The english language was completely correct at that time.


If you was right, I and Mamba will not change tons of NOT readable strings within the core for 2.5.4 and 2.5.5.

You still didn't get the point, huh ?
X 2.0.18 & 300+ modules, no matter of messed up strings, outdated strings, was number one choice for CMS even over Mambo (Joomla! wasn't a dream yet). Thanks to the counts.
X 2.1 followed by 2.2 Mithrandir, was released based on same language definitions, outdated, complicated (excluding code structure, which 2.2 of Mithrandir XOOPS still have some better ideas not present and in 2.5.5), got 15 modules in total.
X 2.3 made by ...who was, damn there was a time of big changes, everyone was wanting to lead XOOPS - and the end result was "amazing", to all crap from 2.0.18, 2.1 and 2.2, there was added, more complicated language strings, making XOOPS non-understandable by the regular user, read the slogan - Powered by You (who is the you, the developer or the user?)
X 2.4 was a transition release, there was a lot of things planed to be changed, but suddenly phpPP got crazy or overdosed, that's why 2.4 was stopped of development, X3 was aborted, and they're (current team of core developers) made cloning release of 2.4 to 2.5, still keeping old language files, hard to be read and understand phrases coming all the way from XOOPS 1.3. Adding new in the same style and way.
Up to 2.5.3, XOOPS have no difference in any point to the end user from 2.3.0, was same distribution under new version. Same themes, same definitions, same small amount of modules, end result for 2.5 - (maybe chosen for project of the month - 2.5.5), is still far, far away from what was 2.0.18.

Quote:

You cannot use signature


It's not totally wrong, depend on the context can be used with small corrections.

By correcting every single line and removing formatting from those modules - XOOPS 2.5.5 gains:

1. More understandable core and modules
2. More translations - more users - more popularity
3. More Real/unreal testers - thanks to those translations - more reported and cleared bugs.

I can always return to the old way, TX XOOPS & XOOPS Modules was registered by me (Infidex allows everyone to make XOOPS project, or Joomla! project, no matter he is not a part of any of the development teams), to be able to provide at least Bulgarian and Macedonian translations 100% completed and up to date with the latest versions on this site. Later Mamba was invited and the others....

It's not a problem for most used modules/cores to keep personal releases on English files, modified and edited in the way they should be along with translations (there is a lot of space on SF.NET), but who wins from such ?
------------------------------------------------------------------------------
Back to the topic
xLanguage maybe buggy, but discovered bugs one or another day will be solved. And that module is translated by the most active translators teams this days, why they're not whining ?

So far, nor French (cesag), no Spanish (bitcero, oswaldo), Italian (txmodxoops, defkon1 and rest), or Slovaks (chaoos) got a problem with that, to translate BETA stage module (everyone knows what means BETA, ALPHA, PREVIEW RELEASE, TECH RELEASE) and to keep it up to date, no matter it's partially or not usable at all.

They have communities (localized support sites), priorities - they decide what to be translated and when, I personally, first don't have the time, 2nd - don't have the will to order which team what will translate and what not and 3rd - don't have the rights....


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 9:04
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#58

Re: Transifex Requirements for accepting files

Imtfan is right;
- yeah was mention long time ago, want me to discuss it with Infidex or u will take this part ?

Currently on banned cms I don't have problems which comes with X Core and Modules, bcz all they're files end with CR+LF, all strange symbols are removed, now they have to clean invalid spaces and my favorite Weight. Catz fork and XOOPS, still have some messed up files. (Well, not for the core) Once 2.5.6 or 2.6.0 is released as Beta, should review (for last time) every file for invalid spaces.

Some of the modules (not only Wishcraft modules) will be removed for infinite loops and no response from the module maintainer.
Some for the containing of non-transalatable strings (not only in Wishcraft modules).
Some for formatting language files to make them looking cool.

NVM, added to Infidex support desk:
Quote:

Got another problem with XOOPS/?????/XOOSLA
If the language file with PHP DEFINES ends with only LF causes infinite loop and TX platform instead to read all 377 strings read half or 1% of them - till reaches the string ending with LF.

The question from XOOPS/?????/XOOSLA developers is:
Why should be used Windows CR+LF for ending lines instead of Unix LF only, is there any reason ?

Thanks in advance.

Waiting for reply.

For me CR+LF is not a problem, for XOOPS to operate too, I'll not lock translations till Infidex respond - and they need sometimes like week or two to make reply.


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 8:18
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#59

Re: XOOPS 2.5.x Translations using Transifex

Any updates on work with Madfish script ?
does someone tried it ?

I and X modules got same structure in both places - Distributions and Transifex, so they should be fully functional, without changes.


DCrussader

Friend of XOOPS
Posted on: 2012/8/8 8:09
DCrussader
DCrussader (Show more)
Friend of XOOPS
Posts: 573
Since: 2005/7/4 7
#60

Re: Transifex Requirements for accepting files

the CR+LF bug probably is fixed, let me check.

7. All lines must end with CR+LF, LF only causes infinite loop.



TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 41 »