Translations

Re: ICMS 1.3.3 Beta English language

Quote:


core.php
Line 20-22
Can't be Bytes above and on this lines to be b, eg, Kb, Mb and so on
should be KB, MB, GB, TB, PB and so on.



Changing the 'b' to 'B' is more than just a capitalization convention. There are multiple units of measure for digital units = bits and bytes. Kb is kilobits and KB is kilobytes. They differ by a factor of 8. As they are defined in the current language file, KB, MB and GB would be consistent with the units.

Quote:


by Vaughan on 2012/8/9 22:54:46

WARNING: this might cause a little debate

I do not agree with ID instead of id.

conventions say camelCase, or 2 letter acronyms should be uppercase like DB = database

but id is NOT an acronym. it is an abbreviation. therefore id or Id should be used.



From a database perspective, all lowercase is preferred. From a filesystem perspective, case matters. From a code perspective, it depends - PHP isn't strictly case sensitive, but it is moving that way. From a user/language perspective - now we're getting into personal preferences for things the user can change.

Vaughan's preference isn't just an arbitrary choice - there is some consistency to it and can be applied as a rule, if you're not sure.

if I were to choose between Id and id, I'd go with id - it doesn't lead to possible confusion with a missing '.

Report
Topic


Re: ICMS 1.3.3 Beta English language

WARNING: this might cause a little debate

I do not agree with ID instead of id.

conventions say camelCase, or 2 letter acronyms should be uppercase like DB = database

but id is NOT an acronym. it is an abbreviation. therefore id or Id should be used.

Live as if you were to die tomorrow, Learn as if you were to live forever

The beauty of a living thing is not the atoms that go into it, but the way those atoms are put together!
Report
Topic


Re: Help needed for Translation PHP script

  • 2012/8/9 11:17:59
  • ep98

Who allowed the creation of 2 French teams ?
Pick one and remove the second, I know that XOOPers loves anarchy, but not move it and here please!

Report


Re: Help needed for Translation PHP script

  • 2012/8/9 0:50:15
  • ep98

Order, Position... anything but Weight, yack

Report


Re: Help needed for Translation PHP script

Quote:


ep98 wrote:
Order is for sorting (got experience, a lot of with all OS CMS released today)

When there is
Category A Position 3 []
Category B Position 5 []
Category C Position 1 []
(Save) Order is used for reordering them, by manually adding the new numbers.



The value of 'weight' is used for sorting, so 'order' would be a reasonable replacement. 'Position' is for placement - top, bottom, left, right, in front of, behind - and doesn't make sense to me in this context.

But, since my only language is English, and American English at that, perhaps an Englishman should weigh in.

Report


Re: Help needed for Translation PHP script

  • 2012/8/8 6:19:49
  • ep98

Or should be added in on time of changes, one section in changelog languages for 1.3.3 Beta 2 or RC, for the current BETA there is no need, since all files will be re-uploaded when someone of the dev team take care of the empty spaces.

Report


Re: Help needed for Translation PHP script

I'll see if I can make a diff between the 1.3.2 release and the 1.3 branch. That should identify the changed files

Report


Re: ICMS 1.3.3 Beta English language

  • 2012/8/8 1:51:04
  • ep98

Modules
Banners
modinfo.php
Remove invalid spaces, convert to UTF-8

admin.php
Remove invalid spaces, convert to UTF-8

common.php
Remove invalid spaces, convert to UTF-8

main.php
Remove invalid spaces, convert to UTF-8
------------------------------------------
Content
modinfo.php

Line 18 Contents ?
Articles ? What's this contents.

Line 26 - Groups allowed to add content - not contents

Line 28 - 29 - not contents for sure

Even for static content, adding single page containing one line is article.
Remove invalid spaces, convert to UTF-8

admin.php
Line 22 Contents ?

Line 30 clone this content - Clone content/article
Remove invalid spaces, convert to UTF-8

blocks.php
Line 18
Show author and published info ?
Show author and publication info maybe ?

common.php
Line 18 (wow, favorite number) Poster - no such thing as Poster, it's Author

Line 22 and xx
Content body is Full content, Content Scoop is Content Intro.

Line 30 Published date
Published

Line 32 Updated date
Updated

Line 34 - Weight... there is no Weight (ohh it was Spoon) Neo

Line 49 All contents of %1
All articles from %1

Line 50 - %1 comments, and what about if is %1 comment ?
Remove invalid spaces, convert to UTF-8

main.php
Remove invalid spaces, convert to UTF-8

profile
modinfo.php
Remove invalid spaces, convert to UTF-8

admin.php
Remove invalid spaces, convert to UTF-8

blocks.php
Remove invalid spaces, convert to UTF-8

common.php
Weight again
Remove invalid spaces, convert to UTF-8

main.php
Remove invalid spaces, convert to UTF-8

(hmm in both cores, if the user comment a story published by another author, there is no link in the profile page with those comments)

system and it's sub-folder
Remove invalid spaces, convert to UTF-8

(Global corrections)
1. Weight - everything else, but not and this misleading crap
2. Id to ID
3. Content (except module name) should be Article and Articles.


Now back to previous question - which language files are changed ?

Edit: No matter what's changed, for next beta/RC will be important, anyway u have to change all language files.

Report


ICMS 1.3.3 Beta English language

  • 2012/8/7 14:53:32
  • ep98

ImpressCMS 1.3.3 Beta English language files:

/language/english

notification.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

moduleabout.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

misc.php
Convert it to UTF-8 or UTF-8 without BOM

mail.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

global.php
Line 5 present from XOOPS 1.3 and no longer is used as feature in any XOOPS 2.x cores
define('_FETCHING','Loading...');
Line 30-31
define( '_XOBJ_ERR_REQUIRED', '%s is required' );
define( '_XOBJ_ERR_SHORTERTHAN', '%s must be shorter than %d characters.' );
(someone without work playing with formatting) - correct it.
Line 248-249
define( "_TRUST_PATH_HELP", "Warning: System failed in reaching Trust path.<br />The trust path is a folder where ImpressCMS and its modules will store some sensible code and information for more security.<br />It is recommended that this folder be outside of the web root, making it not accessible by a browser.<br /><a target='_blank' href='http://wiki.impresscms.org/index.php?title=Trust_Path'>Click here to learn more about the Trust path and how to Create it.</a>" );
define( "_PROTECTOR_NOT_FOUND", "Warning: System is unable to find if Protector is installed or active in your site.<br />We highly recommend you to install or activate Protector to improve your site's security.<br />We also have to thank GIJOE for this very good module.<br /><a target='_blank' href='http://wiki.impresscms.org/index.php?title=Protector'>Click here to learn more about Protector.</a><br /><a target='_blank' href='http://xoops.peak.ne.jp/modules/mydownloads/singlefile.php?lid=105&cid=1'>Click here to download the latest version of Protector.</a>" );
(again someone without work, to play with formatting)

except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

findusers.php
line 29-31
AIM/ICQ are the same thing and no one uses them, wont mention YIM, add FB/Skype instead
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

error.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

databaseupdater.php
line 41
define( '_DATABASEUPDATER_MSG_FROM_112', "<code><h3>You have updated your site from ImpressCMS 1.1.x to ImpressCMS 1.2 so you <strong>must install the new Content module</strong> to update the core content manager. You will be redirected to the installation process in 20 seconds. If this does not happen click <a href='" . ICMS_URL . "/modules/system/admin.php?fct=modulesadmin&op=install&module=content&from_112=1'>here</a>.</h3></code>" );
(formatting in Word, not here)
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

countries.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

core.php
Line 20-22
Can't be Bytes above and on this lines to be b, eg, Kb, Mb and so on
should be KB, MB, GB, TB, PB and so on.
Line 33 - for developer can be understandable, but for me the poor user this means nothing
define('_CORE_CLASSNOTINSTANIATED', 'This class cannot be instantiated!');
Translate it in human readable string.
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

comment.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

captcha.php
define("ICMS_CAPTCHA_RULE_TEXT", "Input the result from the expression");
Something readable by human ?
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

calendar.php
define("_CAL_TGL1STD", "Toggle first day of week");
Select first day of the week maybe ?
in some areas is used 24 hours format, what should be done with those

define("_CAL_AM", "am"); define("_CAL_AM_CAPS", "AM"); define("_CAL_PM", "pm"); define("_CAL_PM_CAPS", "PM");

define("_CAL_WK", "wk"); // shorten of week-end
Shorten ? Try again, let see it in Russian, French ?
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

banners.php
define('_BANNERS_LOGIN_INFO',"Please type your client information");
Please ENTER .....
define('_BANNERS_FUNCTIONS',"Functions");
Actions, functions can be in the debugger
yay, first file without invalid spaces
Convert it to UTF-8 or UTF-8 without BOM

auth.php
Convert it to UTF-8 or UTF-8 without BOM

admin.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

user.php
Line 198 - define('_US_LOGIN_NAME', "Loginname");
Login or Login Name.... but current ?
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

uploader.php
define("_ER_UP_INVALIDFILESIZE", "Invalid File Size");
Invalid file size is enough, there is no need to put capital on every word
define("_ER_UP_FILENAMEEMPTY", "Filename Is Empty");
Filename can't be empty is better, and no capitals again
Line 19 - define("_ER_UP_SUSPICIOUSREFUSED", "Suspicious image upload refused");
Translate it in human readable English.
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

theme.php
line 81-82
Change XOOPS info to ICMS Info, it's confusing ICMS used, but with XOOPS modules.
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

search.php
define('_SR_HITSRETURNED', 'hit(s) returned');
match(es) returned
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

privpolicy.php
No suggested changed, except remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

pmsg.php
define("_PM_SUBMIT","Submit");
no sumbit, send - since is for sending messages, can't be submit.
except mentioned changes, remove invalid intervals.
Convert it to UTF-8 or UTF-8 without BOM

pdf.php have to be translated manually and added into packages, when core is completed, or those strings to be moved into system module and sql file, like build-in option in the configuration.

/editors/FCK to be replaced by CK, FCK is outdated.
phpmailer to be updated to 5.2.1

/mail_template/ in each module/language folder have to be moved into SQL with option to be modified from within the module.
(tomorrow modules)

Report


Re: Help needed for Translation PHP script

  • 2012/8/7 14:05:43
  • ep98

Order is for sorting (got experience, a lot of with all OS CMS released today)

When there is
Category A Position 3 []
Category B Position 5 []
Category C Position 1 []
(Save) Order is used for reordering them, by manually adding the new numbers.

(due some requirements, which now I'm fighting with XOOPS.org, TX got some changes in the PHP Define statement)

Files containing such definitions

define( '_MD_XFGB_CONFIRM_CODE', 'Confirm verification code' ) ;


will be dropped.

Definitions must look like:
define('_MD_XFGB_CONFIRM_CODE','Confirm verification code');


Thanks to this bug/new feature - a lot of XOOPS modules translations was wiped, at least ICMS should be happy - there is no completed and single module translation, nor core.

Spacing and formatting - forget about TX.

Files written in French on ISO like the old Herve News module, need corrections and conversion to UTF-8. French is the only example, all European/NA languages which using different symbols then English Alphabet need corrections and conversion.

Files containing strings which should not be translated, should be split in 2 parts:
Part 1 - User readable strings for translations
Part 2 - Reserved fields which should not be translated
---------------------------------------------------------
...and since starting to verify the language files of 1.3.3 Beta release, who will tell me which files are changed, not going to reupload all files. From this announce - http://community.impresscms.org/modules/smartsection/item.php?itemid=608 nothing is changed in the language files ?

Report


Re: Help needed for Translation PHP script

or maybe 'order'.

Native English speakers, what do you think?

Report


Re: Help needed for Translation PHP script

  • 2012/8/7 9:24:31
  • ep98

at first sight - everywhere in the core
Weight must replaced with Position

Report


Re: Help needed for Translation PHP script

that falls under the improvement of the quality I think. Having a better choice of words would be great, thank you!

Report


Re: Help needed for Translation PHP script

  • 2012/8/7 4:40:48
  • ep98

Quote:


In the short term no major changes in the language system are planned, so let's focus on what can be done on the other points.

These are things I see that fall into this category:
* Make sure all language files are in UTF-8
* standardise language names
* improve the linguistic quality of the content
* eliminate duplicates and minimize contents
* investigate if the number of language files can be reduced



With both hands for, but what about terminology used in X and ICMS ?

I can make proposition list for changes in McDonald modules

Report


Re: Help needed for Translation PHP script

Okay, many topics here (and a few rants as well)...

let's focus on how we can improve the translation flow one thing at a time, starting with the 'low-hanging fruit' : the things that are not much work to do, but that will result in big improvements.

In the short term no major changes in the language system are planned, so let's focus on what can be done on the other points.

These are things I see that fall into this category:
* Make sure all language files are in UTF-8
* standardise language names
* improve the linguistic quality of the content
* eliminate duplicates and minimize contents
* investigate if the number of language files can be reduced

Report


Re: Help needed for Translation PHP script

  • 2012/7/25 8:22:03
  • ep98

Quote:


Point 1 : a no-brainer,and it should be done. Using transifex can be a solution in the end, as it will output files that are in the correct character encoding. We will need to get more people using transifex for this (module maintainers).



Force them, but I don't see why McDonald to reject using it and even what should he do there ..., and point me to the right way... but who are we talking about ? There is only one active module maintainer.
1-2 Censors (Language maintainers) are enough for that task.

Quote:


* make sure translations are in UTF-8 for ALL languages (even en-uk)



Not required for en-GB, en-UK - may stands someday for English Ukrainian. All translations should be converted to UTF-8, all comments blah blah XOOPS, blah blah ICMS, blah, blah GPL (for me general warez license) should be removed as well.

Quote:


This can be done simply by defining a standard list of languages according to international standards (en-us, en-gb). Question is, where do you stop? For now the en-gb and en-us are the same, and I don't see a reason why someone would want to create (and maintain!) both of them separately for most modules.



Totally wrong, do u wanna see phpFox language files and something in GB English like Joomla! ? You will be amazed by the americanos.

Quote:


Reduce the number of fields : We do need to look into reduciing the duplicate content. That's a tricky one, because some text strings can be exactly the same in two contexts in English



Tricky one huh ?
There are plural forms, to avoid such tricks and misplaced strings anywhere within main, modinfo and admin.php. And if there was only 2 files per module, very easily can be avoided - making/adding such duplicates.

Quote:


Unless someone jumps in to abstract the entire language layer, and make it easy to switch between the two, I don't think this will be coming in the next few months, as the other systems don't have any added functionality to the module developer/end-user.



Current versions of ICMS, XOOPS are so incompatible with everything written so far, that such statement is pointless. ICMS have few 1.3 compatible (really compatible modules), written by McDonald. Some of the rest supposed to work such as CBB, wont, and others outdated such as catzwolf wf-downloads... somehow still with small bugs keeps standing operational. What can't be changed for 5-6 modules ? There are no 300+ modules for any of them. 5-6 for I, 10 old, too old with new "Blue move administration" for X.

Asembla? forums should be enough, saw already how much time was needed to find and solve the problem in versions prior 1.1.3 with the blank page in administration/preferences (1-2 releases ?). Current build-in debugger should be extended, for cases of such blank pages - otherwise there will be nothing to report.

Quote:


if those bloody american's didn't keep changing the spelling of English words, removing letters or changing letters all the time, then there'd be no need for en_US. lol



Right between the eyes.
+1

Quote:


If you have chosen Belgian Dutch, and for some modules there is only a Netherlands Dutch available, you still get your translations displayed.



Not acceptable! There are a lot of differences between Spanish and Catalan, and u can't have core of the site in Spanish and modules in Catalan. Same is for the Indian (5 known different versions, mostly used including Bangladesh), what about my friends from China (Chinese Simplified, aka Modern, and Mandarin, Canton - they're still used).

And no idea how u cooperate or not with XOOPS, or both communities still hates each other (like kids), but current XOOPS core is in the idiotic US English.

How u can add category positioned in field Weight ?
Category A - Weight 3
Category B - Weight 2
Category C - Weight 1

Weight is used in e-Commerce solutions such as osCommerce, to declare the volume of a package for delivery. Weight ? OMG.
Or By Adding Every First Word With Capital ? No thanks of such English.

If we take this example, only as dream which will not happen soon on both places:
If McDonald imLinks 1.20 was with /language/en-GB/administration.ini and site.ini (or let it be PHP Define, since u love it so much), how the things will look:

String 1=something goes here
...
String 100=something goes there
#Added in 1.21
#Removed in 1.21
#Updated in 1.21
String 101=blah, blah

Currently imLinks have strings from the time when was WF-Links 1.06, some strange too long not needed explanations for simple tasks, and no explanations for newly added features/tasks.

When there are 2 files, everyone can simply find out if not using TX, what's changed, what's removed and what's updated/added.

Also plural forms keeps language files from adding duplicates.


1. "There are %s files in our files section" - there can be two different right translations for this one.
2. "The %s was downloaded %d time" - This can means:
The file was downloaded 1 time and The file was downloaded few times.
3. In English - I is I for everyone no matter male/female, but when there is a string.
I accept the terms & conditions - translations must be plural - I the male and I the female accept the blah.

As translator:
For the time I'll create 5 J! extensions translations, will make one X/ICMS.

First bcz Language used in those cores is far, far away from being user-friendly, secondary bcz of the too long not-needed description fields for simple tasks such as create category, 3rd and not last - bcz every J! extension have one com_name.ini for the site, and same file for the admin. It's much easier for user, the end user - to not wait for TX release and to start translate (somehow) the frontend only of the module he needs.

Report


Re: Help needed for Translation PHP script

Well, there are different flavors (or is that flavours ) of english, just like there are multiple codes of French (fr-fr, fr-be) or Dutch (nl-be, nl-nl) or Portuguese (pt-br, pt-pt).

i propose, if we don't find the exact match, we look for the first part. If you have chosen Belgian Dutch, and for some modules there is only a Netherlands Dutch available, you still get your translations displayed. if nl-be returns a result, that's ok. If 'nl' returns a result, that's a good second choice.

Comments?

Report


Re: Help needed for Translation PHP script

queens english is rarely spoken outside the upper class circles (if it is spoken then), and hardly ever used in written form unless you're doing your dissertations for university (which have to be in queens english). But queens english is more about Grammar than the spelling of words. there is no I in queens english.

so a sentence of 'I am going to the shop' in queens english would be 'One is going to go to the shop'

'you would think that' would be 'one would think that'.

One would think one should know how to spell.

but 99% of people in Britain use the British spellings regarding s & z. like colonise, digitise. but with a British accent & correct speaking, it actually sounds like colonISE (you can hear the S) it wouldn't sound like ize.

and spell colour not color, flavour not flavor, favourite not favorite.
Aluminium not Aluminum

Live as if you were to die tomorrow, Learn as if you were to live forever

The beauty of a living thing is not the atoms that go into it, but the way those atoms are put together!
Report


Re: Help needed for Translation PHP script

There's the Queen's English and then there's a bunch of people who are just wrong :)

There is actually no single definitive standard for English. Even for UK English there are two major dictionaries considered to be authoritative, which differ on things like use of s vs z.

Re. the scripts, if you had an en-whatever language folder it would still work, no presumption is made about what languages are available on the system or what they are called, it will inspect every language subdirectory. It also does not care if any of the standard language file names are missing as not all are used in all modules. However, it will not touch any file with a non-standard name, and it does not attempt to work on Protector whose language files reside somewhere else.

Report


Re: Help needed for Translation PHP script

if those bloody american's didn't keep changing the spelling of English words, removing letters or changing letters all the time, then there'd be no need for en_US. lol

#JustSayin

Live as if you were to die tomorrow, Learn as if you were to live forever

The beauty of a living thing is not the atoms that go into it, but the way those atoms are put together!
Report



 Top