[Building Sakai] Change proposal for 2.8: export_filename_date_format (i18n to configuration)

[Jean-Francois Leveque]

Great map, though the mm-dd-yyyy was used in most English-speaking 
countries. Maybe I've been influenced too much by the US.

I wonder how the countries with more than one date format are doing. At 
least using both dd-mm-yyyy and yyyy-mm-dd is unambiguous when you use 4 
digits for the year.

Unless Feliz has an objection, maybe it's time to get this to the TCC 
because I think coordination is needed. A CC to the i18n WG will not 
hurt. We will need input from code owners. I found the following Leads 
in JIRA.
Gradebook: Jonathan Cook
Roster: Daniel Robinson
Tests & Quizzes (Samigo): Karen Tsao
User Membership and SiteStats: Nuno Fernandes

I think Nuno's away right now. Maybe Feliz can answer for him. Maybe 
someone at UFP or a member of the MT could do this for Nuno if it's OK.

If at least one is ready to include this change, the MAINT TEAM which is 
lead on config could do the default part.

WDYT?

J-F

Steve Swinsburg a écrit :
> I would also argue that most English locales are not comfortable with the US format date string either, as the MM-dd-yyyy format seems illogical to the rest of us. This format is not even used outside the US. However, the ISO format of yyyy-MM-dd is perfectly suitable and I would +1 this being the default with the option to configure.
> 
> Interesting map here: http://en.wikipedia.org/wiki/Date_and_time_notation_by_country
> 
> cheers,
> Steve
> 
> On 22/07/2010, at 11:50 PM, Beth Kirschner wrote:
> 
>> Possibly true, but just aiming to simplify localization. I'm doubtful  
>> most translators will know how to 'localize' the date format string,  
>> so as long as folks are comfortable with most locales defaulting to a  
>> US format, than this shouldn't be a problem.
>>
>> - Beth
>>
>> On Jul 22, 2010, at 5:10 AM, Jean-Francois Leveque wrote:
>>
>>> I think your suggestion is not as simple as needed and may be risky.  
>>> Are we sure we only need to remove spaces in every locale to have a  
>>> suitable string for part of a file name? I wouldn't bet on it.
>>>
>>> J-F
>>>
>>> Beth Kirschner a écrit :
>>>> I would suggest formatting the date automatically, leveraging the  
>>>> Java DateFormat.getDateFormat() which takes Locale as an argument.  
>>>> The resulting date string can then be transformed into a suitable  
>>>> filename by removing spaces. Automating this would be one less  
>>>> thing to worry about when localizing Sakai.
>>>> - Beth
>>>> On Jul 21, 2010, at 10:49 AM, Jean-Francois Leveque wrote:
>>>>> Hi all,
>>>>>
>>>>> I think export_filename_date_format (used in Gradebook, Roster,  
>>>>> Tests &
>>>>> Quizzes (Samigo), User Membership and SiteStats) is not a i18n  
>>>>> property
>>>>> but a configuration property.
>>>>>
>>>>> Because it's used in several tools, I would like it to become a  
>>>>> general
>>>>> configuration property.
>>>>>
>>>>> I propose to use the name general.export_filename_date_format in
>>>>> configuration and to set its default to the ISO date format of  
>>>>> yyyy-MM-dd.
>>>>>
>>>>> For further details and related problems, you can check:
>>>>> http://jira.sakaiproject.org/browse/SAK-17240
>>>>> http://jira.sakaiproject.org/browse/STAT-191
>>>>> http://jira.sakaiproject.org/browse/SAK-15872
>>>>> http://jira.sakaiproject.org/browse/SAK-15682
>>>>>
>>>>> What do the code owners and others devs think?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Jean-Francois