pkh@vap.vi.ri.cmu.edu (Ping Kang Hsiung) (10/24/88)
I got Eugene Miya's bib files over the weekend. There are some notations used in the files that I don't understant: 1. Some \(em or (em in the %J field. What these mean? (and why they don't have the closing ")".) 2. In the key field, there are some numbers: %K I3m educational computing %K I3m mechanical engineering computing %K I35 modeling systems How do I interpretate/user these I3m, I35 numbers? 3. Some acronyms: CGF, CAMP, ISATA. They are not defined in the files. Thanks.
eugene@eos.UUCP (Eugene Miya) (10/25/88)
In article <3384@pt.cs.cmu.edu> pkh@vap.vi.ri.cmu.edu (Ping Kang Hsiung) writes: >I got Eugene Miya's bib files over the weekend. There are some >notations used in the files that I don't understant: > >1. Some \(em or (em in the %J field. What these mean? >(and why they don't have the closing ")".) > >2. In the key field, there are some numbers: > %K I3m educational computing > %K I3m mechanical engineering computing > %K I35 modeling systems >How do I interpretate/user these I3m, I35 numbers? > >3. Some acronyms: CGF, CAMP, ISATA. They are not defined in the files. Oops! Sorry. I got other mail on this. I forgot all about them. The BACKSLASH macros are troff-isms. There are tools like deroff to take them out or r2bib to convert things into bibTeX. These macros are 4 characters in size \(em is a slightly longer dash. They aren't a significant problem, write sed filter. The I fields are ACM Classification codes. You can either get them from ACM Computing Reviews (blue and white things, that most don't get) or you can get the hardcopy versions of these bibliographies (they have the CR classification scheme for graphics). The acronyms are unfortunately a long term problems. We can get a table to use use U. AZ's bib program to fill them out. I hope you are all finding some use of this stuff. We NEED people around the country to help us update this. There are earlier years. Also new papers are being written all the time. They have to get entered (even finding them is hard). I don't deserve the credit, I'm only pissed off that I have to read queries over and over. The credit belongs to the crew of Bay Area ACM/SIGGRAPH working on this project. (other volunteers are welcome: especially key entry help) Another gross generalization from --eugene miya, NASA Ames Research Center, eugene@aurora.arc.nasa.gov resident cynic at the Rock of Ages Home for Retired Hackers: "Mailers?! HA!", "If my mail does not reach you, please accept my apology." {uunet,hplabs,ncar,decwrl,allegra,tektronix}!ames!aurora!eugene "Send mail, avoid follow-ups. If enough, I'll summarize."