Re: [COOT] americanisms in 0.6.1....
I think it should be in pig-latin Gloria From: Miguel Ortiz Lombardia To: COOT@JISCMAIL.AC.UK Date: 01/28/2010 03:30 PM Subject: Re: [COOT] americanisms in 0.6.1 Sent by: Mailing list for users of COOT Crystallographic Software I don't know if this will be a long discussion or not, but now that is there I have also my own thoughts to share with anyone wanting to read beyond this line. Researchers begin as students. Students are essentially formed in their mother language and I hope it keeps like that for the good. Very often it's only afterwards that they/we learn the lingua franca of science, and I mean it, because one may have some base of this broken English we (non-native and some native English speakers) talk in science, but our base is often out of tune with the real use we make of English. When you teach a student about the use of a program you often find yourself also teaching that particular English slang. Or they have to spend a significant amount of time to learn it themselves. Think also about this: as Kevin said, not so long ago Latin was the language of science and philosophy. Sooner than what we may think, Chinese might earn its place in that hall of fame. What then, if the best program ever for whatever task we carry out is only available in Chinese? Translating programs is fortunately infinitely easier than translating poetry. It can be undertaken as a collaborative task, requiring a limited amount of time from anyone participating. And it enriches both the users and the program. Needless to say, English is not my first language, not even the second one... Miguel Le 28 janv. 2010 à 14:24, Johan Turkenburg a écrit : > Maybe I will get away with this one, as English is not my first language. > > I think translating interfaces/programs is a gimmick: at the end of > the day, scientists (people!) need to be able to talk to each other, > so need a common language. This happens to be English (at the moment). > So we better all practice it as much as possible. > > (don't let this be the start of a long discussion, it's just a thought) > > Johan > > On 28 January 2010 10:50, Paul Emsley wrote: >> Kevin Cowtan wrote: >>> >>> Ezra Peisach wrote: >>> I move that the names in the scheme scripts be changed to the american names and that a new script "British.scm" be put in place. >>> >>> Well, that's just crazy talk. The scripting interface should clearly use >>> the established language of science, which transcends national boundaries >>> and has been the lingua franca for the bulk of the history of science. >>> >>> I therefore propose that Coot scripting interface be translated to Latin. >>> >>> There may be some technical neologisms which do not yet have appropriate >>> Latin equivalents. I'm sure these people will be glad to help... >>> >>> http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm >>> >> >> At some stage I (at least) would like to have the GUI translated into >> various languages. We have a start for Spanish and French and I'd like >> others, for example Chinese, Japanese and Portuguese, So we'll be putting >> out a call for translators later (Latin_Vatican is a possibility). No time >> to look at this before next year though. >> >> Paul. >> > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- Miguel Architecture et Fonction des Macromolécules Biologiques (UMR6098) CNRS, Universités d'Aix-Marseille I & II Case 932, 163 Avenue de Luminy, 13288 Marseille cedex 9, France Tel: +33(0) 491 82 55 93 Fax: +33(0) 491 26 67 20 e-mail: miguel.ortiz-lombar...@afmb.univ-mrs.fr Web: http://www.pangea.org/mol/spip.php?rubrique2
Re: [COOT] americanisms in 0.6.1....
I don't know if this will be a long discussion or not, but now that is there I have also my own thoughts to share with anyone wanting to read beyond this line. Researchers begin as students. Students are essentially formed in their mother language and I hope it keeps like that for the good. Very often it's only afterwards that they/we learn the lingua franca of science, and I mean it, because one may have some base of this broken English we (non-native and some native English speakers) talk in science, but our base is often out of tune with the real use we make of English. When you teach a student about the use of a program you often find yourself also teaching that particular English slang. Or they have to spend a significant amount of time to learn it themselves. Think also about this: as Kevin said, not so long ago Latin was the language of science and philosophy. Sooner than what we may think, Chinese might earn its place in that hall of fame. What then, if the best program ever for whatever task we carry out is only available in Chinese? Translating programs is fortunately infinitely easier than translating poetry. It can be undertaken as a collaborative task, requiring a limited amount of time from anyone participating. And it enriches both the users and the program. Needless to say, English is not my first language, not even the second one... Miguel Le 28 janv. 2010 à 14:24, Johan Turkenburg a écrit : > Maybe I will get away with this one, as English is not my first language. > > I think translating interfaces/programs is a gimmick: at the end of > the day, scientists (people!) need to be able to talk to each other, > so need a common language. This happens to be English (at the moment). > So we better all practice it as much as possible. > > (don't let this be the start of a long discussion, it's just a thought) > > Johan > > On 28 January 2010 10:50, Paul Emsley wrote: >> Kevin Cowtan wrote: >>> >>> Ezra Peisach wrote: >>> I move that the names in the scheme scripts be changed to the american names and that a new script "British.scm" be put in place. >>> >>> Well, that's just crazy talk. The scripting interface should clearly use >>> the established language of science, which transcends national boundaries >>> and has been the lingua franca for the bulk of the history of science. >>> >>> I therefore propose that Coot scripting interface be translated to Latin. >>> >>> There may be some technical neologisms which do not yet have appropriate >>> Latin equivalents. I'm sure these people will be glad to help... >>> >>> http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm >>> >> >> At some stage I (at least) would like to have the GUI translated into >> various languages. We have a start for Spanish and French and I'd like >> others, for example Chinese, Japanese and Portuguese, So we'll be putting >> out a call for translators later (Latin_Vatican is a possibility). No time >> to look at this before next year though. >> >> Paul. >> > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- Miguel Architecture et Fonction des Macromolécules Biologiques (UMR6098) CNRS, Universités d'Aix-Marseille I & II Case 932, 163 Avenue de Luminy, 13288 Marseille cedex 9, France Tel: +33(0) 491 82 55 93 Fax: +33(0) 491 26 67 20 e-mail: miguel.ortiz-lombar...@afmb.univ-mrs.fr Web: http://www.pangea.org/mol/spip.php?rubrique2 smime.p7s Description: S/MIME cryptographic signature
Re: [COOT] Transforming maps
(transform-map-using-lsq-matrix 1 "A" 1 200 0 "A" 1 200 2 (molecule-centre 1) 10) All seems to go fine, except that the map matches correctly only part of the transformed molecule, and it looks like when the map is extended by symmetry, things fail Yes, the transformed map only makes sense 10A around the centre of molecule 1. Make sense, but it does not quite do the correct thing. If I use: (read-pdb "test.pdb") (read-pdb "reference.pdb" ) (auto-read-make-and-draw-maps "test.mtz") (transform-map-using-lsq-matrix 1 "A" 118 349 0 "A" 118 349 2 (molecule-centre 1) 10) (set-rotation-centre 34.0726.71 0.6102)# centre of molecule 1 the result is: http://www-cryst.bioc.cam.ac.uk/node/199 (corrected permssions, sorry about that) This is centred on the point around which the map is created (based on coot output), and you can see clearly density is lacking from one side of the image, very close to the centre. I am sure there is trivial solution to this, but I can't think of it now. Use a bigger radius? Dynamically set the position to which you transform maps? Dynamically? Me? That would be great. Can I centre on a residue or calculate a centre from a set of atoms? Also, is the lsq matrix from the transform-map-using-lsq-matrix stored anywhere, and can I use it for other transformations? (handle-read-ccp4-map "my.map" 0) Aah, of course. Thanks. Marko _ Marko Hyvonen Department of Biochemistry, University of Cambridge ma...@cryst.bioc.cam.ac.uk http://www-cryst.bioc.cam.ac.uk/groups/hyvonen tel:+44-(0)1223-766 044/760 468 mobile: +44-(0)7796-174 877 fax:+44-(0)1223-766 002 --
Re: [COOT] americanisms in 0.6.1....
This will be so much fun :) As a native of Riga I volunteer to work on Latvian version of coot. Hey, it will probably have as many users as the Latin version, by order of magnitude. Cheers, Ed. On Thu, 2010-01-28 at 10:50 +, Paul Emsley wrote: > At some stage I (at least) would like to have the GUI translated into > various languages. We have a start for Spanish and French and I'd > like > others, for example Chinese, Japanese and Portuguese, So we'll be > putting out a call for translators later (Latin_Vatican is a > possibility). No time to look at this before next year though. > > Paul. > > -- Edwin Pozharski, PhD, Assistant Professor University of Maryland, Baltimore -- When the Way is forgotten duty and justice appear; Then knowledge and wisdom are born along with hypocrisy. When harmonious relationships dissolve then respect and devotion arise; When a nation falls to chaos then loyalty and patriotism are born. -- / Lao Tse /
Re: [COOT] Macros in COOT--use VB to write python code
Is my understanding correct that what Wes describes can be accomplished in the following three steps: 1. Apply CHAINSAW using sequence alignment 2. fill-partial-residues 3. fit-protein (optional) Seems to me that moving chainsaw step into coot will not save much time (if at all). Cheers, Ed. On Thu, 2010-01-28 at 10:10 +, Paul Emsley wrote: > Goodness, sounds like fun. > > Coot does have an align&mutate function of course, but you don't get to > fiddle with the sequence alignment - Coot uses its own alignment [1]. > My understanding is that should be fine for ~70% sequence identity or > better. My feeling though is that it is not widely used. So my question > to the community is: Is there a need to be able to use an alignment > rather than simply a target sequence? > > Thanks, > > Paul. > > [1] courtesy of mmdb > > > Wes Ozarowski wrote: > > > > Dear Andrew, > > > > Since I don't have the time to learn python fully and because > > there is not too many of examples of python scripting available for > > Coot, thus I use my expertise of VB to help me write the correct > > syntax for python script. then paste it into notepad and run it as a > > python script from Coot's GUI. > > > > For example I will paste an amino acid sequence of homologous > > proteins from ClustalW into an excel spreadsheet, then using VB to > > write a program that will put each amino acid into it's own > > spreadsheet cell as separate objects with some fancy colors ( as color > > codes) to make it pretty. Now, I can do all sorts of analyses of these > > sequences, like find the ones that are non-homologous between two > > proteins, put them in a table, let VB write the python syntax for > > "goto" and "mutate_autofit " of all these specific amino acids, paste > > it into notepad and "wala !" i have automation. That is ,I can goto > > (thus observe visually the mutational changes for oddballs) and > > mutate_autofit about 300 amino acids in about 10 min, rather than > > spending hours doing it manually. > > > >Wes > > > > > > > > > > > > > > In a message dated 1/19/2010 10:56:53 A.M. Central Standard Time, > > and...@mrc-lmb.cam.ac.uk writes: > > > > Having worked with O for many years I am only now getting serious > > with > > COOT. There are a couple of things that I would like to do that > > don't > > seem to be available (as far as I can tell), but which may well be > > possible using Macros. > > > > Unfortunately a quick Google has not revealed anything about how to > > use macros in COOT, but a colleague suggested they need to be > > written > > in Python or another language that I had not heard of before. > > > > So my first question is where can I find a low level description of > > how to write macros with some examples (I know nothing about Python, > > except that it is fashionable) ? > > > > There are specifically two things I want to be able to do: > > > > 1. Do an LSQ superposition using specified residues in multiple > > chains > > (superposing one oligomer on another). > > > > 2. To do a LSQ superposition of a homologous structure onto my > > working > > structure using +/- N residues about the current position, where N > > is > > a variable (not essential, could be fixed) and the current > > position is > > the last residue that I clicked on. > > > > Thanks > > > > Andrew > > -- Edwin Pozharski, PhD, Assistant Professor University of Maryland, Baltimore -- When the Way is forgotten duty and justice appear; Then knowledge and wisdom are born along with hypocrisy. When harmonious relationships dissolve then respect and devotion arise; When a nation falls to chaos then loyalty and patriotism are born. -- / Lao Tse /
Re: [COOT] americanisms in 0.6.1....
Maybe I will get away with this one, as English is not my first language. I think translating interfaces/programs is a gimmick: at the end of the day, scientists (people!) need to be able to talk to each other, so need a common language. This happens to be English (at the moment). So we better all practice it as much as possible. (don't let this be the start of a long discussion, it's just a thought) Johan On 28 January 2010 10:50, Paul Emsley wrote: > Kevin Cowtan wrote: >> >> Ezra Peisach wrote: >> >>> >>> I move that the names in the scheme scripts be changed to the american >>> names and that a new script "British.scm" be put in place. >>> >> >> Well, that's just crazy talk. The scripting interface should clearly use >> the established language of science, which transcends national boundaries >> and has been the lingua franca for the bulk of the history of science. >> >> I therefore propose that Coot scripting interface be translated to Latin. >> >> There may be some technical neologisms which do not yet have appropriate >> Latin equivalents. I'm sure these people will be glad to help... >> >> http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm >> > > At some stage I (at least) would like to have the GUI translated into > various languages. We have a start for Spanish and French and I'd like > others, for example Chinese, Japanese and Portuguese, So we'll be putting > out a call for translators later (Latin_Vatican is a possibility). No time > to look at this before next year though. > > Paul. >
Re: [COOT] americanisms in 0.6.1....
Translating coot? With google, that's a doddle! /French/: foulque f /Spanish: /focha /Portuguese: /galeirão :) On 28/01/2010 10:50, Paul Emsley wrote: Kevin Cowtan wrote: Ezra Peisach wrote: I move that the names in the scheme scripts be changed to the american names and that a new script "British.scm" be put in place. Well, that's just crazy talk. The scripting interface should clearly use the established language of science, which transcends national boundaries and has been the lingua franca for the bulk of the history of science. I therefore propose that Coot scripting interface be translated to Latin. There may be some technical neologisms which do not yet have appropriate Latin equivalents. I'm sure these people will be glad to help... http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm At some stage I (at least) would like to have the GUI translated into various languages. We have a start for Spanish and French and I'd like others, for example Chinese, Japanese and Portuguese, So we'll be putting out a call for translators later (Latin_Vatican is a possibility). No time to look at this before next year though. Paul.
Re: [COOT] Transforming maps
Marko Hyvonen wrote: Hello cooters. I am trying to compare multiple structures of similar proteins, in different crystal forms, and to transform the maps in a script using "transform-map-using-lsq-matrix" command. But I am stuck with few problems. This part of the script is essentially as follows: (no-coot-tips) (set-run-state-file-status 0) (read-pdb "new.pdb") (read-pdb "reference.pdb" ) (auto-read-make-and-draw-maps "test.mtz") (transform-map-using-lsq-matrix 1 "A" 1 200 0 "A" 1 200 2 (molecule-centre 1) 10) All seems to go fine, except that the map matches correctly only part of the transformed molecule, and it looks like when the map is extended by symmetry, things fail Yes, the transformed map only makes sense 10A around the centre of molecule 1. . See http://www-cryst.bioc.cam.ac.uk/node/199 I am not authorized. I am sure there is trivial solution to this, but I can't think of it now. Use a bigger radius? Dynamically set the position to which you transform maps? Also, I can't seem to find the command how to read a (ccp4) map into coot using a script. http://www.biop.ox.ac.uk/coot/doc/coot.html#Read-Maps (handle-read-ccp4-map "my.map" 0) All I can see is how to read it from the menu, but not the scripting command. Ideally I'd read in just a small map carved around the area of interest (and then saved). To carve out a bit of map, put a water (say) in a new molecule at the centre of the region (make a note of its molecule-number) (mask-map-by-molecule map-number water-molecule-number 1) for some value of map-number and water-molecule-number. Paul.
[COOT] Transforming maps
Hello cooters. I am trying to compare multiple structures of similar proteins, in different crystal forms, and to transform the maps in a script using "transform-map-using-lsq-matrix" command. But I am stuck with few problems. This part of the script is essentially as follows: (no-coot-tips) (set-run-state-file-status 0) (read-pdb "new.pdb") (read-pdb "reference.pdb" ) (auto-read-make-and-draw-maps "test.mtz") (transform-map-using-lsq-matrix 1 "A" 1 200 0 "A" 1 200 2 (molecule-centre 1) 10) All seems to go fine, except that the map matches correctly only part of the transformed molecule, and it looks like when the map is extended by symmetry, things fail. See http://www-cryst.bioc.cam.ac.uk/node/199 I am sure there is trivial solution to this, but I can't think of it now. Also, I can't seem to find the command how to read a (ccp4) map into coot using a script. All I can see is how to read it from the menu, but not the scripting command. Ideally I'd read in just a small map carved around the area of interest (and then saved). And if someone has a working example on how to do this with ccp4, I'd be interested to hear. thanks, Marko _ Marko Hyvonen Department of Biochemistry, University of Cambridge http://www-cryst.bioc.cam.ac.uk/groups/hyvonen --
Re: [COOT] coot 0.6.1 and libldap-2.2.so.7 at Fedora10
Thanks Paul! coot-Linux-i386-fedora-10-gtk2-python worked straight away... Cheers, Martin __ Martin Moche, Ph.D., M.Sc. Senior scientist Karolinska Institutet MBB/SGC Scheeles väg 2 171 77 Stockholm Sweden Phone: +46-8-524 868 43 Mob: +46-733-229327 Fax: +46-8-524 868 68 martin.mo...@ki.se - Original Message - From: Paul Emsley Date: Thursday, January 28, 2010 11:01 am Subject: Re: coot 0.6.1 and libldap-2.2.so.7 at Fedora10 To: COOT@JISCMAIL.AC.UK > Hi Martin, > > Martin Moche wrote: > > Dear Coot Users, > > > > I am trying to run, coot-0.6.1-binary-Linux-i386-fedora-4-gtk2, > at my > > Fedora10 Linux machine... > > > > > Eeek - Stop right there! The correct solution is to use the Fedora > 10 > binary. > > ... which seems not to to be in place yet... > > OK, it is now, please look here for binaries: > > http://www.ysbl.york.ac.uk/~emsley/software/binaries/stable/ > > > Paul. >
Re: [COOT] americanisms in 0.6.1....
Kevin Cowtan wrote: Ezra Peisach wrote: I move that the names in the scheme scripts be changed to the american names and that a new script "British.scm" be put in place. Well, that's just crazy talk. The scripting interface should clearly use the established language of science, which transcends national boundaries and has been the lingua franca for the bulk of the history of science. I therefore propose that Coot scripting interface be translated to Latin. There may be some technical neologisms which do not yet have appropriate Latin equivalents. I'm sure these people will be glad to help... http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm At some stage I (at least) would like to have the GUI translated into various languages. We have a start for Spanish and French and I'd like others, for example Chinese, Japanese and Portuguese, So we'll be putting out a call for translators later (Latin_Vatican is a possibility). No time to look at this before next year though. Paul.
Re: [COOT] Macros in COOT--use VB to write python code
Goodness, sounds like fun. Coot does have an align&mutate function of course, but you don't get to fiddle with the sequence alignment - Coot uses its own alignment [1]. My understanding is that should be fine for ~70% sequence identity or better. My feeling though is that it is not widely used. So my question to the community is: Is there a need to be able to use an alignment rather than simply a target sequence? Thanks, Paul. [1] courtesy of mmdb Wes Ozarowski wrote: Dear Andrew, Since I don't have the time to learn python fully and because there is not too many of examples of python scripting available for Coot, thus I use my expertise of VB to help me write the correct syntax for python script. then paste it into notepad and run it as a python script from Coot's GUI. For example I will paste an amino acid sequence of homologous proteins from ClustalW into an excel spreadsheet, then using VB to write a program that will put each amino acid into it's own spreadsheet cell as separate objects with some fancy colors ( as color codes) to make it pretty. Now, I can do all sorts of analyses of these sequences, like find the ones that are non-homologous between two proteins, put them in a table, let VB write the python syntax for "goto" and "mutate_autofit " of all these specific amino acids, paste it into notepad and "wala !" i have automation. That is ,I can goto (thus observe visually the mutational changes for oddballs) and mutate_autofit about 300 amino acids in about 10 min, rather than spending hours doing it manually. Wes In a message dated 1/19/2010 10:56:53 A.M. Central Standard Time, and...@mrc-lmb.cam.ac.uk writes: Having worked with O for many years I am only now getting serious with COOT. There are a couple of things that I would like to do that don't seem to be available (as far as I can tell), but which may well be possible using Macros. Unfortunately a quick Google has not revealed anything about how to use macros in COOT, but a colleague suggested they need to be written in Python or another language that I had not heard of before. So my first question is where can I find a low level description of how to write macros with some examples (I know nothing about Python, except that it is fashionable) ? There are specifically two things I want to be able to do: 1. Do an LSQ superposition using specified residues in multiple chains (superposing one oligomer on another). 2. To do a LSQ superposition of a homologous structure onto my working structure using +/- N residues about the current position, where N is a variable (not essential, could be fixed) and the current position is the last residue that I clicked on. Thanks Andrew
Re: [COOT] coot 0.6.1 and libldap-2.2.so.7 at Fedora10
Hi Martin, Martin Moche wrote: Dear Coot Users, I am trying to run, coot-0.6.1-binary-Linux-i386-fedora-4-gtk2, at my Fedora10 Linux machine... Eeek - Stop right there! The correct solution is to use the Fedora 10 binary. ... which seems not to to be in place yet... OK, it is now, please look here for binaries: http://www.ysbl.york.ac.uk/~emsley/software/binaries/stable/ Paul.
[COOT] coot 0.6.1 and libldap-2.2.so.7 at Fedora10
Dear Coot Users, I am trying to run, coot-0.6.1-binary-Linux-i386-fedora-4-gtk2, at my Fedora10 Linux machine... At startup I got this message: daffy-mochma 7% coot COOT_PREFIX is /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2 /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real: error while loading shared libraries: libldap-2.2.so.7: cannot open shared object file: No such file or directory coot-exe: "/net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real" coot-version: /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real: error while loading shared libraries: libldap-2.2.so.7: cannot open shared object file: No such file or directory platform: /bin/uname core: #f No core file found. No debugging This is not helpful. Please turn on core dumps before sending a crash report ## coot startup end ### However I seem to have newer versions on this the ldap library? [r...@daffy lib]# ls -l libldap* lrwxrwxrwx 1 root root 20 Mar 24 2009 libldap-2.4.so.2 -> libldap-2.4.so.2.2.0 -rwxr-xr-x 1 root root 269100 Oct 15 2008 libldap-2.4.so.2.2.0 lrwxrwxrwx 1 root root 22 Mar 24 2009 libldap_r-2.4.so.2 -> libldap_r-2.4.so.2.2.0 -rwxr-xr-x 1 root root 291248 Oct 15 2008 libldap_r-2.4.so.2.2.0 Is there a package I can install to obtain all libraries required for coot 0.6.1? I have tried to copy the libldap-2.2.so.7 from another machine and placed it in /usr/lib however then I got...the following startup message daffy-mochma 1% coot COOT_PREFIX is /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2 /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real: error while loading shared libraries: libssl.so.5: cannot open shared object file: No such file or directory coot-exe: "/net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real" coot-version: /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real /net/fileserver/xtal/graphics/coot-Linux-i386-fedora-4-gtk2/bin/coot-real: error while loading shared libraries: libssl.so.5: cannot open shared object file: No such file or directory platform: /bin/uname core: #f No core file found. No debugging This is not helpful. Please turn on core dumps before sending a crash report ## coot startup end ### so now I miss libssl.so.5 instead... How to proceed? Cheers, Martin __ Martin Moche, Ph.D., M.Sc. Senior scientist Karolinska Institutet MBB/SGC Scheeles väg 2 171 77 Stockholm Sweden Phone: +46-8-524 868 43 Mob: +46-733-229327 Fax: +46-8-524 868 68 martin.mo...@ki.se
Re: [COOT] americanisms in 0.6.1....
Ezra Peisach wrote: I move that the names in the scheme scripts be changed to the american names and that a new script "British.scm" be put in place. Well, that's just crazy talk. The scripting interface should clearly use the established language of science, which transcends national boundaries and has been the lingua franca for the bulk of the history of science. I therefore propose that Coot scripting interface be translated to Latin. There may be some technical neologisms which do not yet have appropriate Latin equivalents. I'm sure these people will be glad to help... http://www.vatican.va/roman_curia/institutions_connected/latinitas/documents/index_en.htm
