It's not general because within Jmol there are over 225 references to
.toLowerCase() and over 150 to .toUpperCase(), and any of these are
potential problems in that regard, not just that one script or scripts in
general. And I think it is not possible to do this in JavaScript without an
explicit
yes, short of redesigning all the code references of .toLowerCase() and
.toUpperCase() just for our friends in Turkey, there's not much we can do
about this.
On Wed, Jun 4, 2014 at 1:36 AM, Angel Herráez angel.herr...@uah.es wrote:
Yes, I had read about such a problem.
The issue is, however,
Bob, I think you are not getting my point.
I think this happens because there is an upercase ID text in the source
code of that gotoligand function.
For some reason, Jmol goes later to convert that to lowercase.
But if the gotoligand function had just lowercase id, then I believe no
harm
would
yes, OK, but that's not a general solution. I suppose that happens in Java
and JavaScript?
On Wed, Jun 4, 2014 at 2:20 PM, Angel Herráez angel.herr...@uah.es wrote:
Bob, I think you are not getting my point.
I think this happens because there is an upercase ID text in the source
code of
Dear Bob,
You're going to love this bug report. It's thrilling!
I was today demonstrating the new PDB ligand pocket view that uses the
contact command. Guess what... it breaks in Turkish computers, nothing is
displayed but the standard protein rendering.
I think I have tracked down the issue.
Yes, that makes sense. Funny that we just talked about this.
string.lowerCase() apparently chokes with Turkish.
Go figure.
Bob
On Tue, Jun 3, 2014 at 2:13 PM, Angel Herráez angel.herr...@uah.es wrote:
Dear Bob,
You're going to love this bug report. It's thrilling!
I was today
here it is:
http://mattryall.net/blog/2009/02/the-infamous-turkish-locale-bug
On Tue, Jun 3, 2014 at 3:21 PM, Robert Hanson hans...@stolaf.edu wrote:
Yes, that makes sense. Funny that we just talked about this.
string.lowerCase() apparently chokes with Turkish.
Go figure.
Bob
On
