bcit-ci / codeigniter3-translations Goto Github PK
View Code? Open in Web Editor NEWTranslations of the CodeIgniter system messages
License: MIT License
Translations of the CodeIgniter system messages
License: MIT License
The following language files have not been fully translated: date, email, form_validation, ftp, migration, number?, profiler, unit_test
$lang['form_validation_valid_base64'] = 'The {field} field must contain a valid Base64 string.';
CI 3.1.10
don't have english
.../language/.../imglib_lang.php
$lang['imglib_writing_failed_gif'] = 'GIF image.';
The above tag has been removed in the core repository, and can be removed in any translations here or in progress.
File: system/language/english/form_validation_lang.php (at the end).
$lang['form_validation_error_message_not_set'] = 'Unable to access an error message corresponding to your field name {field}.';
There is a new language setting in language/english/form_validation_lang.php, part of PR#3521 (merged). We need to incorporate that into our translations, thanks!
$lang['form_validation_in_list'] = 'The {field} field must be one of: {param}.';
Some of the translators' acocunts do not appear active anymore.
If I cannot find them, I will ask for new translation maintainers for these on the forum.
serbian 3.1.0 @novakurosevic Novak Urosevic ???
vietnamese 3.0.4 @tinhphaistc Trần Xuân Sâm ???
japanese 3.0.3 @tsukasa Tsukasa Takao???
https://github.com/bcit-ci/codeigniter3-translations/blob/develop/core/MY_Lang.php#L130
Codeigniter 3.0.1 use SYSDIR as system path alias
I cannot properly open some of the simplified Chinese translation files inside NetBeans ... it complains about UTF-8 compatibility and many of the characters appear as question marks on a sort of stop sign background. Is this a problem generally? Is there a workaround?
Thanks
There has been much discussion in the core repo about the opening license/comment blocks in our source code files. It makes sense that they remain, inside core framework files, i.e. those that are meant to end up inside system/.
I don't see them as necessary inside application/ files, but we want to make sure here that any contributed translations are freely usable by anyone who downloads this translations repo.
For the translations, I am comfortable removing the block at the beginning of each _lang.php file, but replacing it with a license.txt file in the same folder as an idiom's folder. This preserves the intent while reducing the clutter.
Comments?
The following translations are missing the translated text for $lang['form_validation_in_list'], which was added recently.
@tsukasa japanese
@MSDehghan persian
@karidoe thai
@obozdag turkish
@Rufnex german
It would be great if you could tend to this, so I don't have to resort to Google translate
/* End of file autoload.php */
/* Location: ./application/config/autoload.php */
are removed.
@jim-parry My question is, should this change be applied within this project too?
@andrejflorjancic Would you be able to add these? Thanks
language/slovenian/email_lang.php
email_exit_status *** Missing translation! ***
Exit status code: %s
language/slovenian/form_validation_lang.php
form_validation_in_list *** Missing translation! ***
The {field} field must be one of: {param}.
lookout for the language functionality of the website university page.
make sure it is upto the mark.
also it is working fine
A new translation item has been added to the imglib library translations:
$lang['imglib_invalid_image'] = 'The provided image is not valid.';
@tgrnmrdn @Qarakom @kabircse @Ignasimg @pkrul @Rufnex
@xargr @shindesushilkumar @tsukasa @Chanthoeun
@dgvirtual @KwonLatte @vadimyer @novakurosevic
@peterdenk @karidoe @codeonion
Once you update your translation, I will remove your handle from this list :)
Hi,
I would like to maintain the translation to Arabic, My name is: Ihab Abou Afia.
What should I do when I finish translation.
Thank you,
Hi people. When I came here today to grab one translation, I was wondering, wouldn't it be better to separate every single translation in an specific repo? In a world like nowadays where we're using much of composer, bower, npm, it would be better to have the translations as separate dependencies, I think. That way we could simply install each of them like composer install translation-x
, or even through a yeoman generator, like yo generator-ci-translate en
.
What do you guys think about it? The best way I think, it would be having them integrated through composer. Any thoughts about that? Don't know if you've already discussed that somewhere...
Hope opening this issue is ok to discuss about it, if is not, just let me know...
Regards, Gio.
@Chanthoeun 3 translation lines are missing, and two are extra
:(
form_validation_lang ... $lang['form_validation_in_list'] needs translation, thanks
@shindesushilkumar
Normally, to get this repo files, I have to download then copy the required files. The copied files are included on Git.
I have an idea to add this repo as a composer package.
Three Russian time zones were changed on Oct 26, 2014 and in bcit-ci/CodeIgniter#3444 date_lang.php was updated accordingly. Now it also needs to be updated in each language.
Line 73: $lang['UP3'] = '(UTC +3:00) Moscow Time, East Africa Time, Arabia Standard Time';
Line 75: $lang['UP4'] = '(UTC +4:00) Azerbaijan Standard Time, Samara Time';
Line 89: $lang['UP11'] = '(UTC +11:00) Srednekolymsk Time, Solomon Islands, Vanuatu';
Looking at the list of translations, I see "simplified-chinese", and then further down "traditional-chinese". Shouldn't these be named "chinese-simplified" and "chinese-traditional", so that they appear in the correct order with the other languages?
Do you agree or disagree?
@denghongcai @PeterDaveHello
Some translations have been proposed, but no pull request received yet.
We are getting ready to finalize version 3, and missing translations will be removed from the list in the README.
@Muzikant Slovak?
@ngangchill Bangla?
top courses of the universities
A number of translation maintainers were added to the list, but pull requests for their work have not been forthcoming. At some point soon, I will be tagging the master branch as the 3.0 branch, synchronized with the framework versioning, and I will be creating a develop branch for new translations.
Any translations not ready for this will be removed from the 3.0 branch, although I can leave them in the develop one.
@Ihabafia @rogervila @hafizhassan @MSDehghan
@oldwizard @depchuanseo
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.