From: Scott M. <sco...@gm...> - 2011-03-10 20:37:16
|
I'm unfamiliar with the term "config points". I am certainly championing the change to a more fluid (ie changable) configuration table within the database such that it is much easier to add new configuration items. If that style of storing configuration data is called "config points", then yes I am :-) -Scott On Thu, Mar 10, 2011 at 4:46 PM, David Thompson < tom...@us...> wrote: > Yes, Scott using setlocale solves most date/time representation issues > (though I am not sure about the comma instead of point one though...). > > And Isabelle, I would love to see the config points that you mention (lang, > holidays, working times, etc.) - even if they are not used in 2.0, we could > add them as a guide for the future. Scott, you're adding config points right > now, aren't you? > > Isabelle, if you would like commit access, just tell me your > sourceforge.net id, and I will add you. > > Cheers > > ------------------------------ > Date: Thu, 10 Mar 2011 15:19:45 +0100 > From: ver...@fr... > To: tsh...@li...; sco...@gm...; > ma...@rw...; tom...@us... > Subject: Re: language and jclasses discussion > > > Hello, > > For internationalization of dates, I don't think that routines are > necessary > as the language files like"/language/en-GB/en -GB.ini" allow to specify > the values of the months, of the days of the week and of the date formats > (eg DATE_FORMAT_LC). > > In France, we often also use the week number for our schedules. I added > this number on relevant pages in "my timesheet 1.5.2". As the parameter > "%V" of the strftime function didn't work on my computer, I used the > function > "week_isonumber" posted by Anonymous 12-Oct-2010 07:04 here: > http://php.net/manual/fr/function.strftime.php > > For the time format in French, just replace the occurrences of colon as > in this example: > - English: 10:30:56 > - French: 10h 30m 56s > > As I said earlier, to have the correct dates in French, you must specify > the language 'fra' for the locale: setlocale(LC_ALL,'fr_FR','fra'); > > For numbers in French, the decimal separator is a comma instead of the > point. This is important for excel export. > > For billing and currency: > The euro is the official currency of the Eurozone in the European Union. > The html entity for the euro sign is € > > For the translation of the different status for projects and for tasks > as well as of the different types of users, would it be possible to add > the values in the language files if it's allow to not modify "enum" in > the database? > > Do you want me to contribute at this stage to the project by making an > fr-FR.ini file for translation of the current en-GB.ini file in > "/branches/txsheet-2.0-demo/"? > If yes, how to join the project? > > I was also thinking about that: on the configuration page of the future > Timesheet 2.0, would it be possible to define the following data > depending on each country: > - dates of the days being public holidays > - the legal duration of work per day and/or per week > - the legal number of days for holidays per year > > Sincerely. > > Isabelle. > > ----- Mail Original ----- > De: "Scott Miller" <sco...@gm...> > À: "tsheetx" <tsh...@li...>, "Mark Wrightson" > <ma...@rw...>, "David Thompson" < > tom...@us...>, "Isabelle Vergely" < > ver...@fr...> > Envoyé: Mercredi 9 Mars 2011 00:16:34 GMT +01:00 Amsterdam / Berlin / Berne > / Rome / Stockholm / Vienne > Objet: language and jclasses discussion > > Hi all, > > I've checked in a few more changes, mainly focused on further trimming down > of un-needed stuff from the various classes, and the removal of un-needed > classes. > > I'm still waiting for a discussion on whether we want to continue using J* > class names (JLanguage, JText, JFile, JFolder, etc) or if we want to use > something different, and if so, what. > > Also still waiting to hear about how the error classes work, and how to > replace the commented out error stuff in the jclasses with error stuff that > will actually work for us. > > I'm beginning to think about how to go about integrating the JLanguage > stuff into our existing classes. Should the JLanguage stuff be part of the > master site class? I'm currently thinking it should. > > Isabelle, I think it will be useful to have language specific routines that > deal with how to correctly format times, dates, and numbers in general. Can > you point us in the right direction as to how to go about doing this? > > -Scott > |