Menu
▾
▴
tsheetx-developers
|
From: Isabelle V. <ver...@fr...> - 2011-07-17 18:48:18
|
Revision 333, modifications for internationalization: * include/language/en-GB.ini and include/language/fr-FR.ini * include/tsx/common.class.php, * js/client_proj_task_javascript.class.php and js/simple.js * tsx/client_proj_task_javascript.class.php, tsx/simple.php * and tsx/tasks/task_maint.php Isabelle. |
|
From: Isabelle V. <ver...@fr...> - 2011-08-26 21:18:43
|
Hello, In this revision: - minor changes: utf8_encode added for correct display of dates; use of the utf-8 charset for meta tag of popup_template.php - modification of datetimepicker_css.js for translation of month names and week day names: o removal of MonthName, WeekDayName1 and WeekDayName2 in datetimepicker_css.js o new corresponding values of these variables in language files o new file include/language/datetimepicker_lang.inc to set variables using the language files o before each use of datetimepicker_css.js in PHP files, addition of require_once for datetimepicker_lang.inc I think what the datetimepicker is only needed for forms about a short period of time (less than a month) as for: daily, weekly, simple, weekly and half-month reports. For other forms where the period of time is a month (monthly, submit, absence, ...), I suggest a small calendar displaying only month and year or the use of two "selects" (month, year). What is your opinion? Isabelle. |
|
From: Peter L. <pal...@gm...> - 2011-08-28 03:14:43
|
Isabelle, thanks for these changes in update 389. I agree with your comment about just selecting month and year for forms where the period is a month. I am making modifications to datetimepicker which will implement that function. Peter On 08/27/2011 07:18 AM, Isabelle Vergely wrote: > Hello, > > In this revision: > > - minor changes: utf8_encode added for correct display of dates; use of the utf-8 charset for meta tag of popup_template.php > > - modification of datetimepicker_css.js for translation of month names and week day names: > o removal of MonthName, WeekDayName1 and WeekDayName2 in datetimepicker_css.js > o new corresponding values of these variables in language files > o new file include/language/datetimepicker_lang.inc to set variables using the language files > o before each use of datetimepicker_css.js in PHP files, addition of require_once for datetimepicker_lang.inc > > I think what the datetimepicker is only needed for forms about a short period of time (less than a month) as for: daily, weekly, simple, weekly and half-month reports. > For other forms where the period of time is a month (monthly, submit, absence, ...), I suggest a small calendar displaying only month and year or the use of two "selects" (month, year). What is your opinion? > > Isabelle. > > ------------------------------------------------------------------------------ > EMC VNX: the world's simplest storage, starting under $10K > The only unified storage solution that offers unified management > Up to 160% more powerful than alternatives and 25% more efficient. > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers |
|
From: Peter L. <pal...@gm...> - 2011-08-28 03:41:58
|
Update 392 implements the suggestion Isabelle made re selecting just month and year for monthly type forms. I have only implemented it for monthly.php so far. There is a small bug in the datetimepicker.js when used in monthly.php. It puts "undefined" at the top of the date picking popup, and I haven't worked out where that is coming from. If someone can help fix that error it would be much appreciated. Once the bug is fixed, i will propagate the change to other monthly type forms. Peter On 08/27/2011 07:18 AM, Isabelle Vergely wrote: > Hello, > > In this revision: > > - minor changes: utf8_encode added for correct display of dates; use of the utf-8 charset for meta tag of popup_template.php > > - modification of datetimepicker_css.js for translation of month names and week day names: > o removal of MonthName, WeekDayName1 and WeekDayName2 in datetimepicker_css.js > o new corresponding values of these variables in language files > o new file include/language/datetimepicker_lang.inc to set variables using the language files > o before each use of datetimepicker_css.js in PHP files, addition of require_once for datetimepicker_lang.inc > > I think what the datetimepicker is only needed for forms about a short period of time (less than a month) as for: daily, weekly, simple, weekly and half-month reports. > For other forms where the period of time is a month (monthly, submit, absence, ...), I suggest a small calendar displaying only month and year or the use of two "selects" (month, year). What is your opinion? > > Isabelle. > > ------------------------------------------------------------------------------ > EMC VNX: the world's simplest storage, starting under $10K > The only unified storage solution that offers unified management > Up to 160% more powerful than alternatives and 25% more efficient. > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers |
|
From: Isabelle V. <ver...@fr...> - 2012-03-03 15:40:07
|
Hello,
As txsheet-2.0-demo can be used now with English or French language,
I suggest to modify the "locale" field in the "_config" table.
Currently, it's a varchar (127). I think that it could be useful to
enumerate the "current available languages" (to avoid deception for
not implemented translations):
At this stage, the "locale" field in the "_config" table could be
modified like this:
Type: enum('en-GB','fr-FR'); 'en-GB' could be the default value.
To this end, changes to use a drop list for this parameter in the
config.php page are probably not too difficult to do.
What is your opinion?
Esteban,
have you a Spanish language file (es-ES.ini) ready to add as a
third available language in txsheet-2.0-demo?
Is someone could contribute to the en-US.ini file or to another
language like German?
--
Isabelle.
|
|
From: Peter L. <pal...@gm...> - 2012-03-03 21:36:45
|
Isabelle,
very good suggestion. I will implement it.
Peter
On 4 March 2012 02:39, Isabelle Vergely <ver...@fr...> wrote:
> Hello,
>
> As txsheet-2.0-demo can be used now with English or French language,
> I suggest to modify the "locale" field in the "_config" table.
> Currently, it's a varchar (127). I think that it could be useful to
> enumerate the "current available languages" (to avoid deception for
> not implemented translations):
> At this stage, the "locale" field in the "_config" table could be
> modified like this:
> Type: enum('en-GB','fr-FR'); 'en-GB' could be the default value.
> To this end, changes to use a drop list for this parameter in the
> config.php page are probably not too difficult to do.
> What is your opinion?
>
> Esteban,
> have you a Spanish language file (es-ES.ini) ready to add as a
> third available language in txsheet-2.0-demo?
>
> Is someone could contribute to the en-US.ini file or to another
> language like German?
>
> --
> Isabelle.
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X