joomla-projects / com_localise Goto Github PK
View Code? Open in Web Editor NEWforked version of the original com_localise for experimental purposes
License: GNU General Public License v2.0
forked version of the original com_localise for experimental purposes
License: GNU General Public License v2.0
Clicking the help button does not return any help info
Create help screen for https://github.com/joomla-projects/com_localise/blob/develop/administrator/components/com_localise/help/en-GB/screen.translations.html
view: administrator/index.php?option=com_localise&view=translations
To display the comments is necessary. It was never implemented.
As well, no way to uncomment some strings
If impossible to edit them in com_localise, these files should also be included in the package by browsing when package making.
The css is used to replace the main font in back-end for readability (Arabic)
The js concern Calendar. See Persian pack.
We have to review this way of getting client:
https://github.com/joomla-projects/com_localise/blob/develop/administrator/components/com_localise/controllers/language.php#L75-L92
Also check the tag later.
It would be awesome if you @zanardigit or @puneet0191 could create here: https://github.com/joomla-projects/com_localise/tree/develop/tests/system a readme.md file that explains step by step how to run the tests. Something like we have at http://docs.joomla.org/Running_Automated_Tests_for_the_Joomla_CMS but smaller, just with a few steps to set up.
This task consist in work together between @gibilogic and @puneet0191 to create the base classes to use https://github.com/facebook/php-webdriver library instead of current Nearsoft based Joomla classes (https://github.com/joomla/joomla-cms/tree/staging/tests/system/webdriver see (SeleniumClient)
I've seen in a few places new JObject
- we should switch to using JRegistry in several of those places.
Review the current status of icons in the "Icons" at translations screen and report the issues that needs to be fixed
In some models I saw that component is wrongly populating model state. Example:
To populate the state we should be using something like this:
$name = $this->getUserStateFromRequest($this->_context . '.name', 'name');
Then we can probably remove the getForm()
method that is double checking the data in session.
I am not exactly sure what is going wrong but it does not work. There are no JS errors.
index.php?option=com_localise&view=translation&layout=edit
Clicking on the bing button should automatically translate the sentence.
When accessing translations view (administrator/index.php?option=com_localise&view=translations) 3rd party icon is appearing in core language files.
There is still some uses of JRequests, needs to be moved to JInput https://github.com/joomla-projects/com_localise/search?q=JRequest&ref=cmdform&type=Code
This tool will generate the language packages from the files in the system
Currently we have this view: administrator/index.php?option=com_localise&view=packages
The goal of this view is to allow us to generate a language package, right now is not working well but it shouds allow us to:
See comment of Jean Marie below
In translations view (administrator/index.php?option=com_localise&view=translations) replace cog icon for translated column with translation percentage
All the file headers should look like:
<?php
/**
* @package Com_Localise
* @subpackage XXX
*
* @copyright Copyright (C) 2005 - 2014 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/
defined('_JEXEC') or die;
Where XXX can be: controller, model...
Create the page and the test class for:
administrator/index.php?option=com_localise&view=languages
We have this in the options of the component:
This is used to show the suggested string by Bing translator:
So if I create the French translation I will probably translate from the original en-GB files. However if I'm doing the French Canadian I will probably want to set the "reference language" as the fr-FR.
The question is: can we set "reference language" foreach language instead of setting it in the component configuration. That will allow us to have:
Right we can't only do:
Because we can only set one general "reference language"
Issue at: administrator/index.php?option=com_localise&view=language&layout=edit&client=site&tag=
This description is not correct:
It should say something that explains that we are referring to this:
https://github.com/joomla-projects/translate-joomla#standard-iso-codes-for-naming-language-packages
en-GB is usually the main language for translating, it would be nice if we can add a button to Sync the en-GB language and get the latest version from Github at:
I think the most important part for tomorrow would be to implement a nice way to use the Github Framework package here
There are several files and folders starting by "--"
I haven't check what does it means but much probably we are not using it and can be removed. See this examples:
I think we can stop using JObject (see https://github.com/joomla-projects/com_localise/search?q=JObject&ref=cmdform) and use a StdClass instead, isn't it?
@gunjanpatel or @wilsonge are any of you interested in taking this task?
Thanks
We need this for plurals.
Already, the interface displays the strings which are present in the file edited but not in the reference file
Right now the folder structure for the SQL files is not good, please refactor the component so it follows the standard folder structure:
/ component / admin / sql / install / mysql /
and
/ component / admin / sql / updates / mysql /
remember to update the XML manifest ^_^
Create help screen for translation: https://github.com/joomla-projects/com_localise/blob/develop/administrator/components/com_localise/help/en-GB/screen.translation.html
page: administrator/index.php?option=com_localise&view=translation
In translations view (administrator/index.php?option=com_localise&view=translations) replace current columns and icons with this structure:
Tag | Translation name | Translated | Storage / Path | Strings / Phrases | Author | Type | info
Tag: Language tag
Translated: Percentage of wokr done
Storage/Path: Path of the language file
Strings /Phrases: Number of strings language files contains
Author : Whose the author of the lnaguage file and it would be nice to include an icon if it's Joomla core
Type: Component, module, plugin, library...
Info: An icon with tooltip for extra information
Com_localise reads the date of the packages:
The problem is that when the date in the XML is not in american format it causes a crash in com_localise. To reproduce try to modify the creation date in the .XML manifest file of a language package and then make com_localise to read it. We need to make com_localise able to read a wrong date without chrashing. Later on the user can fix the date using this screen:
As it is now, one can edit the reference language and get this error;
Error
RecursiveDirectoryIterator::_construct(/language): failed to open dir: No such file or directory
( ! ) Warning: constant(): Couldn't find constant LOCALISEPATH in ROOT/administrator/components/com_localise/models/translation.php on line 558
I think we just should not let edit the reference language.
What you think? PR would be quite easy.
link to text editor and to strings need to be more clear
Currently the first load of com_localise starts processes all the .ini causing very poor performance. In some servers you get timeouts.
We need to study the current component and find a solution that makes it more performant. Maybe the solution could be an AJAX view that processes step by step all the things that needs to be done.
at 14m50s in the video we see the languages list and also the translation list, they have a colour for every status:
green => translated,
orange => translated but warning because the origin and translated are the same
red => is not tranlsated or is wrong
I suggest that we create a legend at the top of the screen that describes what the color does
PHP Fatal error: Class 'coding-standards_Sniffs_WhiteSpace_SemicolonSpacingSniff' not found in /home/travis/.phpenv/versions/5.3.27/pear/PHP/CodeSniffer.php on line 1053
We need to find a solution for this: #19 (comment)
Some ini files are displayed as not existing in reference language although they are.
Example in site: com_messages
It looks like this is due to the fact that there is no com_messages in front-end
When we create a new language, the main ini file xx-XX.ini (in admin and site) is not proposed to translation
@puneet0191 I think this task could be done by you ^_^
related to #94
If you generate the package you will get this:
It generates a language.localise.php empty file
Create this help page: administrator/index.php?option=com_localise&view=packages
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.