[WG: I18N & L10N] http://jira.sakaiproject.org/browse/SAK-14453

DAVID ROLDAN MARTINEZ darolmar at upvnet.upv.es
Mon Jan 17 02:39:13 PST 2011


Alan,

Please, take a look at https://jira.sakaiproject.org/browse/SAK-14453. This provides a language-independent codes for event types while maintaining backward compatibility. 

If you want, we can take a look to iCal import process.

Cheers,
	David

-----Mensaje original-----
De: Adam Marshall [mailto:adam.marshall at oucs.ox.ac.uk] 
Enviado el: miércoles, 01 de diciembre de 2010 12:56
Para: DAVID ROLDAN MARTINEZ; sakai-dev at collab.sakaiproject.org; i18n at collab.sakaiproject.org; mt at collab.sakaiproject.org
Asunto: RE: http://jira.sakaiproject.org/browse/SAK-14453

I'm probably a little late here , however, ......

I just added a new issue (SAK-19613) which we've had in our local Jira for a while now - I thought I'd add ir centrally as it's related to David's issue.

In short, the event type string that is used in a CVS sometimes matches the on-screen event type string and sometimes doesn't. This is very confusing for the user. 19613 say the names that are accepted in the imported file should be the same as the on screen names.

Now obviously this is a very English-centric solution to the problem - I think David's language-agnostic solution would be far better.

I would plump for codes rather than numbers as it is easier to spot mistakes. It would be good (essential) if these codes were explained in the pop-up help.

I think we would need to maintain backwards compatibility for a while (if not in perpetuity) so the unfriendly strings should still be accepted.

adam

-----Original Message-----
From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of DAVID ROLDAN MARTINEZ
Sent: 28 November 2010 17:47
To: sakai-dev at collab.sakaiproject.org; i18n at collab.sakaiproject.org; mt at collab.sakaiproject.org
Subject: [Building Sakai] http://jira.sakaiproject.org/browse/SAK-14453

Hi all,

I'm about to start working on this i18n blocker bug: http://jira.sakaiproject.org/browse/SAK-14453

To import events from a csv file, you must specify the type of the event. For example:
Example Event 1, This is the description for event #1, 9/1/2008, 11:00 AM, 1:00, Deadline, Taubman Library 2919

'Deadline' is not internationalized. In fact, if you specify 'Término de plazo' instead of 'Deadline', event type is not recognized properly. One quite straightforward approach to this problem would be to use a numeric event type (1=Deadline, 2=Quiz...and so on), as number are not language-dependent.

There also problems with dates. You'll find a detalied description in the JIRA: http://jira.sakaiproject.org/browse/SAK-14453

Before to fix it, I would like feedback community about using numbers  (1=Deadline, 2=Quiz...and so on) or codes (event.deadline = deadline, event.quiz = quiz, ...) in the import file. Any suggestion/help would be appreciated.

Thank you very much in advance.

David
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


More information about the i18n mailing list