[WG: I18N & L10N] [WG: Accessibility] [Building Sakai] Does Client Side JavaScript Have Access to Internationalization Resource Strings in Sakai 2.x?

[Steve Swinsburg]

As a followup, yes the jQuery.i18n.properties plugin can access the properties files, BUT, they need to be web accessible, and in most cases they aren't.

So what I've done is moved the properties files into a separate module which gets packaged up and included as a dependency for the other modules that need it, and then unpacked into a spot in the webapp so the javascript can see it.

Another example is http://jira.sakaiproject.org/browse/PRFL-367

cheers,
Steve


On 04/12/2010, at 8:09 AM, Richwine, Brian L wrote:

> Hey, Thanks!
>  
> From: jonespm at gmail.com [mailto:jonespm at gmail.com] On Behalf Of Matthew Jones
> Sent: Friday, December 03, 2010 4:03 PM
> To: Richwine, Brian L
> Cc: accessibility at collab.sakaiproject.org WG (accessibility at collab.sakaiproject.org); sakai-dev Developers (sakai-dev at collab.sakaiproject.org); i18n at collab.sakaiproject.org
> Subject: Re: [Building Sakai] Does Client Side JavaScript Have Access to Internationalization Resource Strings in Sakai 2.x?
>  
> Nuno had written this library jQuery.i18n.properties [1]. It looked pretty nice and looks like a few tools like profile2 uses it to some extent (http://jira.sakaiproject.org/browse/PRFL-486) and it's compatible with the bundles that Sakai uses internally.
>  
> [1] http://codingwithcoffee.com/?p=272
> 
> -Matthew
>  
> On Fri, Dec 3, 2010 at 3:50 PM, Richwine, Brian L <brichwin at indiana.edu> wrote:
> Hi,
>  
> I’m musing over a fix for an accessibility problem where the value attribute of input elements doesn’t include any pronounceable words (like the “|<”, “<”, “>”, and “>|” list paging control buttons). By default, screen reading software doesn’t read punctuation. If configured to read punctuation, a screen-reader would pronounce “|<” as “Vertical Bar less than” which requires the user to do a good bit of thinking to interpret it as “First”.
>  
> I’m musing over a jQuery routine that could replace the input elements with a visually equivalent button element that has the required extra text for a screen-reader so low-vision/blind users can always hear “First”, “Previous”, “Next”, and “Last”.
>  
> It makes we wonder, can a client side JavaScript routine access the i18n resource strings for a tool in Sakai 2.x?
>  
> Thanks,
>   Brian
>  
> Brian Richwine
> Adaptive Technology Support Specialist
> Adaptive Technology and Accessibility Centers
> Indiana University - Bloomington/Indianapolis
> http://iuadapts.indiana.edu
> (812) 856-4112
>  
> 
> _______________________________________________
> 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"
>  
> _______________________________________________
> accessibility mailing list
> accessibility at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/accessibility
> 
> TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20101206/1ac0b290/attachment.html