[WG: I18N & L10N] Problem with i18n in Citations Helper

[Jim Eng]

I spoke too soon.  It took more than 24 hours after Google picked up the latest changes in our Google Sakaibrary registry, but they did take effect eventually.  Attached is a screenshot of some search results where test2.umich.edu was used as the server key.  The unicode characters came through just fine.  Daniel Merino sent me screenshots of a page of results with links in Spanish with links labeled "Importar al MiAulario".  I think this lays to rest our concerns about being able to use non-ascii characters in registering a system with Google.

Thanks for all the help, David, Beth, Daniel and others.

Jim
 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: google-unicode.png
Type: image/png
Size: 303697 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/i18n/attachments/20101111/b7d43406/attachment-0001.png 
-------------- next part --------------


On Nov 10, 2010, at 9:43 AM, Jim Eng wrote:

> Hi David,
> 
> It appears that Google is blocking anything except ascii characters in the labels for the links to import citations into Sakai.  That includes non-ascii unicode characters and ampersand-secaped characters, as near as I can tell.  I want to do another test next week to get better verification of that (or better yet, to find a way to accomplish this).  Here are the test cases I had hoped might work:
> 
> test2.umich.edu | ???
> test4.umich.edu | T&S ñalå
> test5.umich.edu | ?n?c?de?
> test6.umich.edu | ???????
> test7.umich.edu | ???????
> 
> When we use those keys, Google leaves out the "Import into Sakai" link entirely.  
> 
> If anyone has any suggestions about how we might sneak non-ascii characters through the checks Google is doing, I'd be glad to hear them.  Otherwise I will report back in about a week about my further testing.  
> 
> To put this in context, nobody has asked yet for us to include a label in a language that requires non-ascii characters.  I am trying to figure this out so we will know how to do it when that happens.  If we can't find a way to do that, we may need to require that this be ascii only.  
> 
> Thanks.
> 
> Jim