From ucgadkw at UK.AC.UCL Sat Dec 5 10:36:13 1992 From: ucgadkw at UK.AC.UCL (Dominik Wujastyk) Date: Sat, 05 Dec 92 10:36:13 +0000 Subject: new copy of Indhist on INDOLOGY fileserver Message-ID: <161227015553.23782.10265429205084030836.generated@prod2.harmonylists.io> Anand Raman's program Indhist, which was lodged at the INDOLOGY fileserver recently was somehow truncated. Anand has kindly provided a new copy, and it has now been installed at Liverpool. The original was a listpunched shar file; since this probably sounds a bit arcane to many Indologists, I have repacked it as a ZIP file, which is XXencoded. This should be easier to deal with for most members. Indhist is a Unix program which, when invoked, prints a random paragraph or more of historical text on India, from a large database of such quotes. Thanks, Anand! I append the readme.1st file below, for those who wish to know more. Dominik # readme.1st, Introduction and Preliminary notes on Indhist # anand v raman, 30 Aug 1992 Welcome to Indhist ~~~~~~~~~~~~~~~~~~ DEDICATION ~~~~~~~~~~ I would like to dedicate Indhist to the memory of my grandfather, Sri S.K. Srinivasan, who kept his word and never died. The purpose of Indhist is not to glorify Indian heritage beyond recognition. Nor is it to encourage a certain kind of arrogant chauvinism. On the contrary, it is to show that the great Indian civilization, like the Chinese and Ethiopian before it, was no more profound a civilization than any other, and certainly not any more than the mighty European, but on the other hand, no less either. UNPACKING INDHIST ----------------- When you unpack the shell archive, you should find the following files in it: 0. Indhist1.0/readme.1st : This file 1. Indhist1.0/readme.2nd : Essay 1 2. Indhist1.0/readme.3rd : Essay 2 3. Indhist1.0/INSTALL : Makes the binaries, installs, etc. 4. Indhist1.0/Indhist : Executable + Database 5. Indhist1.0/fifo : Shell script for a named pipe 6. Indhist1.0/Indhist.8 : Indhist manual page 7. Indhist1.0/random.c : C program to generate a random number 8. Indhist1.0/getopt.c : C program to parse options to shell script INSTALLATION NOTES: ------------------- After unpacking Indhist and verifying its contents, you are almost ready to go. If everything went well, you should find a directory called Indhist1.0 in your current directory. Change into that directory and type INSTALL (all upper case) and answer the few questions it asks you. INSTALL will place all the requisite binaries in the right places for you. The manual page will not be installed. You must do that yourself. (If you can handle shell scripts, it might help to look into INSTALL to see if you need to tailor it a little before you run it. Strictly speaking this shouldn't be necessary.) When INSTALL completes, you are ready to use Indhist or fifo. You may want to read the Manual page on them before you start. If your pager cannot detect nroff documents and automatically invoke nroff for you, you may have to type nroff -man Indhist.8 | more Also read the section in this document on troubleshooting Indhist for most of the common problems you could encounter. HOW TO USE INDHIST AND FIFO --------------------------- When Indhist is run, it prints a random record from its database (See the manual page on Indhist for more details on this). In that sense it functions somewhat similar to the program fortune (ucb). You can include a call to Indhist from within your .login script, so one random record is printed out every time you login or alternatively in your .logout so you can read it while logging out. You can even include a call to Indhist in both .login and .logout if you love India so much, but be careful not to be mistaken for a chauvinist. Using fifo, you can create named pipes on the filesystem. Then each time the named pipe is opened, it delivers a new record. Your named pipe could be called .plan and placed in your home directory, so each time someone fingers you it prints a new record (Note that some finger daemons are clever enough to not look at .plans that are fifos), or you could call your fifo .signature. This is strongly discouraged. Most mailers and news posters implicitly append this file to *any* posting you make so you could end up posting a note about Indian history to soc.culture.brazil, or what's even worse, to comp.unix.wizards. To save you flames, I'd suggest you stay away from calling your fifo signature. The default name for the fifo is .signature.indhist. This works just as well and most editors allow you to include files within other files. Since you have to edit Mail and News articles before posting them, it is just one small step to append this file to the end of your article before you send it off. This way you even get to know which record you're tagging on to your signature. Beware! some records in Indhist are over 20 lines in length, so if you let a program handle the record insertion independently, you could be flamed for posting a signature that is many times bigger than what you had to say in your article. If this doesn't suit you because you usually mail or post off the fly using cat |, then you probably don't care too much for fellow net users anyway, so a few flames won't bother you. I've noticed that emacs seems to include 0 bytes when you try inserting a fifo into your document. This can be bypassed, however. You can run the Indhist or fifo command within an inferior shell and include its contents into the emacs buffer. To do this, type M-x shell-command. Then type in either one of: Indhist fifo cat .signature.indhist (if the fifo already exists) Then you can yank the contents of the buffer *Shell Command Output* into your current buffer. The emacs manual will tell you how to do that. TROUBLESHOOTING: ---------------- 1. Indhist I'm assuming that you have sh(1) sed(1) and expr(1) which are all part of a basic UNIX distribution on your system. If you don't, then there's no use going any further, Indhist simply won't run. If you do, there's no reason why Indhist won't work. However, to be on the safe side, maybe you can check the permissions on the script Indhist and whether Indhist is in a directory that is part of your PATH environment variable. - 1.a) Indhist prints less than random records: If you find that that the records that Indhist prints are more or less sequentially selected from the database, (In practice there's no way of finding this out unless you keep running Indhist in rapid succession continuously, which is strongly discouraged) then probably the random command must be failing for some reason; the script has been using expr(1) which yields less than random numbers. It shouldn't really matter as long as you abide by my suggestions and use Indhist sparingly. But if you want really random records and want them soon after each other, then you must look at fixing the small random binary, the details of which I won't go into here. - 1.b) Indhist doesn't work unless the full path name is given: Under UNIX System V, if you let the shell select Indhist from the PATH and run it from any directory other than the current one, it prints the following two lines and exits: Can't open Indhist Can't open Indhist This happens because /bin/sh under Sys V substitues $0 by the name of the program being run without tacking on the path to it. So sed complains about not being able to open Indhist which, of course, is not where $0 says it is. To fix this, you must edit Indhist and change `$0' in the statement db=$0 to be the actual pathname for Indhist. For example, you might need to change it to be db=$HOME/bin/Indhist. 2. fifo Fifo is a slightly larger script than Indhist. So it is likely you may encounter some more problems with it. For a start, you must ensure that you have the following programs if fifo is to function properly: 1. getopt (also supplied with this package) 2. test 3. cat 4. mknod 5. true 6. echo Now, if you don't have getopt on your system, you could compile up the Public domain one which I picked up from an anonymous ftp site and am distributing with this package. It is by Rich Salz of Mirror Systems (rs at mirror.tmc.com). If you like, you may even write your own or pick up one from your favorite ftp site. It should be compiled and made available from a directory in your PATH. If you used INSTALL to install Indhist, you shouldn't need to worry about this as it will ensure you have a working copy of getopt. - 2.a) Catting fifo sometimes prints more than one record: If this happens, then edit the file fifo and uncomment the line containing the sleep near the very end of the script. That will fix it. - 2.b) I've got my fifo set up, but catting it just seems to hang: Remember that fifos are almost the same as pipes. You cannot write into a fifo on one machine and try to read what you wrote on another machine where the fifo is made available via NFS. In order to read a fifo that had just been written into, you must have performed the write on the same machine you are reading the fifo from. If that's not why the cat hangs, then you must make sure you have the fifo process in your background. To check this, type ps -x. On my system the ps output looks like this: PID TT STAT TIME COMMAND 6717 p0 I 0:04 -tcsh (tcsh) 6990 p0 S 0:00 sh fifo -df 6995 p0 S 0:00 sh fifo -df 7005 p0 R 0:00 ps -x If you don't see the two lines showing your fifo processes, then they're probably dead, which explains why your named pipe is silent. Maybe someone (a superuser) killed your daemon's when you were out, or your .logout is setup to automatically kill all your processes when you log out. In any case you can get it going again by typing fifo -df - 2.c) finger seems to ignore my .plan file set up to be a fifo Finger(1) could ignore the .plan file and keep printing "No plan." under two circumstances. The first is if your .plan is inaccessible to the world. Check the permissions on the .plan file and your home directory. "ls -ld . .plan" should print something like: drwxr-x--x 26 ARaman 1536 Jun 2 18:09 . prw-r--r-- 1 ARaman 0 Jun 2 17:32 .plan In most cases, this can be fixed by just setting the mode on these files using chmod(1). Try typing "chmod 751 ." and "chmod 644 .plan". That should fix it. If it doesn't, then it is probable that the finger(1) daemon on your system requires .plan to be a regular file. You can check this out quickly by creating a regular file for your plan with the same permissions as your fifo and then running finger. There's nothing much you can do if this is the case. - 2.d) Inappropriate error messages are printed when fifo is run: Sometimes, meaningless error messages have been seen to occur when running fifo. Most commonly these are stty complaints about unsupported operations etc. Vijay Rangarajan (vijay at ncsa.uiuc.edu) has traced these problems to being caused by /usr/ucb/which (called near the very beginning of fifo) that sources your ~/.cshrc file. If this happens, the fix he suggests is that you move your stty settings from your .cshrc file into your .login file. - 2.e) fifo -d keeps printing `cat' error messages: Remember that fifos don't get along too well with NFS. What's worse, some cats don't return proper exit statii to their shells when their writes fail. I know this happens at least on our Pyramid. So the only way you can sometimes tell if fifo has gone bonkers is if you see a recurrent message on your screen that goes cat: output write error when fifo is operating as a daemon. This only happens if fifos are not supported across your NFS and the directory you chose to keep your fifo happens to be NFS mounted from some other hetergenous host. I haven't been able to fix this problem, but I managed to get a cat in the pipeline so if something goes wrong, at least the cat will squeal. The only thing you can do if this happens is to get the pid of the fifo process and kill it. You probably want to do this in a hurry, so remember that ps(1) usually won't show up daemon processes. You must specify the -x switch to ps(1). This means you can't run the fifo, but you still have Indhist. Alternatively, you could try making your fifo on a locally mounted disk. Also, I don't detach the daemon from the control tty. I thought of supplying another binary that does the ioctl call to do this, but realized it wasn't worth the trouble. Most of us aren't running /bin/sh anyway, so keyboard signals don't get propagated to child processes. HOW TO GET THE MOST OUT OF INDHIST: ----------------------------------- The following tips may be helpful in prolonging the enjoyment you get out of Indhist. * Please read the essays distributed along with Indhist. They reflect some of the sentiments which have directly gone into the making of Indhist. However, remember that Indhist will still be useful even if you don't agree with these essays. * Never print more than a few records a day. * Never open the data file and read its contents. * Don't use records from Indhist in your signatures for articles or mail not related to Indian culture. * Don't edit Indhist to doctor any of the records. HOW TO CONTRIBUTE: ------------------ You can contribute to Indhist in various ways. The first of these, of course, is to popularize it among your Indian friends, especially the younger ones who have prematurely lost touch with the Indian civilization, and get them to use it. Also: 1) You can help add to the existing database in Indhist. Since I'm volunteering to distribute the package, you can mail me the records, and if the record seems appropriate enough to go into the database, I'll make sure it is put in and your name added to the list of contributors. You should get a general feel of what kind of historical notes I hope to include in Indhist after a few weeks of using it. Generally, I place a greater value in historical observations about a country by a person not also of that same country. This is not because they may be any more objective or accurate, but because such observations are usually easier to defend against a charge of `delusions of grandeur.' That is why I haven't included any observations regarding India from Basham, although his book abounds with many of them. 2) You can help port the program to environments it currently doesn't run on. You can perhaps write a PC version of Indhist, (I realize that fifos cannot be implemented on the PC) 3) Arrange for Indhist to be made available via anonymous ftp. You must provide me with some publically readable disk space I can write the latest versions into. 4) Suggest improvements to Indhist and give me some feedback about it. 5) Notify me of any bugs you happen to discover in Indhist. (It seems in ancient India, if a chemist should discover a new poison, he will be punished for it unless he also discovers an antidote. I won't be so demanding. I'll be happy if you can just notify me of the bugs, but happier if you fix them and send me the fixes.) 6) Send little notes of appreciation to the people in the list of contributors when the list has grown longer, assuming of course, you like certain aspects of Indhist. LIST OF CONTRIBUTORS: --------------------- Programs: ~~~~~~~~~ Indhist (Unix shell script) anand v raman (A.Raman at massey.ac.nz) fifo (Unix shell script) anand v raman (A.Raman at massey.ac.nz) indhist (PC executable) any takers? indhist (VMS executable) any takers? getopt (Unix binary) Rich Salz (rs at mirror.tmc.com) random (Unix binary) anand v raman (A.Raman at massey.ac.nz) Essays: ~~~~~~~ 1) I really dread the day we Indians turn out to be like the Chinese - anand v raman (A.Raman at massey.ac.nz) 2) The problem of the destitute East - anand v raman (A.Raman at massey.ac.nz) Databases: ~~~~~~~~~~ Indhist (Indian History): Records 0-51 (McCrindle's translations) - anand v raman (A.Raman at massey.ac.nz) Acknowledgements: ~~~~~~~~~~~~~~~~~ I would like to extend my sincere gratitude to the following people who volunteered to test out Indhist and its essays at various stages of its development: Vijay Rangarajan (vijay at ncsa.uiuc.edu) Sri Vidya (vidya at toru.isor.vuw.ac.nz) Shankar Vaidya Nathan (shankarv at microsoft.com) Sree Kumar (kumar at csc.wcc.govt.nz) Thanks are also due to everybody who encouraged the development of this project. My not mentioning them here individually is solely due to space restrictions and in no way belittles their valuable contribution to Indhist. I also hope that none will be the least inclined to attribute the bugs in Indhist to those whose help I have acknowledged. From narain at EDU.BU.BU-PUB Sun Dec 6 00:00:08 1992 From: narain at EDU.BU.BU-PUB (narain at EDU.BU.BU-PUB) Date: Sat, 05 Dec 92 19:00:08 -0500 Subject: indhist Message-ID: <161227015554.23782.18421106510648114107.generated@prod2.harmonylists.io> hi, I read through the indhist message, but i did not find any executable files and databases....can anyone please explain how to get these??(do i need to ftp these from some site?) thanks, narain. From ucgadkw at UK.AC.UCL Sun Dec 6 17:56:41 1992 From: ucgadkw at UK.AC.UCL (Dominik Wujastyk) Date: Sun, 06 Dec 92 17:56:41 +0000 Subject: indhist Message-ID: <161227015556.23782.1092838228865204012.generated@prod2.harmonylists.io> On Dec 5, 7:00pm, Narain wrote: > I read through the indhist message, but i did not find any executable > files and databases....can anyone please explain how to get these??(do i > need to ftp these from some site?) The file I sent out was just the readme file. The whole package is available from the INDOLOGY fileserver at Liverpool. Send the message "get indhist xxe" to the address "listserv at liverpool.ac.uk" and the package will be returned to you as email. Then you need to run it through the program XXdecode, followed by unZIP. Then you will have to run the Install routine. For me, on an AIX host, this worked smoothly, and made an Indhist executable for me in a matter of minutes. NB Indhist is currently written for Unix, and doesn't work on Macs or DOS PCs. Dominik From vilok at CA.BNR Mon Dec 7 14:56:00 1992 From: vilok at CA.BNR (Vilok (V.) Kusumakar) Date: Mon, 07 Dec 92 14:56:00 +0000 Subject: indhist Message-ID: <161227015557.23782.10738946358396334034.generated@prod2.harmonylists.io> In message "Re: indhist", you write: >"get indhist xxe" to the address "listserv at liverpool.ac.uk" and the >package will be returned to you as email. Then you need to run >it through the program XXdecode, followed by unZIP. Then you I have heard of uudecode/encode but not XXencode ? My workstation running HP-UX 8.0 does not have it. I tried uudecode but it doesn't work. What is XXencode ? Where can I get XXencode from ? Also I don't have zip/unzip. Can somebody also get indhist converted to uuencode + compressed ? I thought these are the two more commonly available mailing and compression programs. > >Dominik --------------- Vilok Kusumakar OSI Protocols for tomorrow...... vilok at bnr.ca Bell-Northern Research, Ltd. Phone: (613) 763-2273 P.O. Box 3511, Station C Fax: (613) 765-4777 Ottawa, Ontario, K1Y 4H7 From vilok at CA.BNR Mon Dec 7 22:11:00 1992 From: vilok at CA.BNR (Vilok (V.) Kusumakar) Date: Mon, 07 Dec 92 22:11:00 +0000 Subject: uuencoded version of indhist ... Message-ID: <161227015559.23782.18043604627111997488.generated@prod2.harmonylists.io> Thanks to Tarun for providing indhist in compressed, uuencoded format. BUT... I tried the following but couldn't get indhist to install properly. 1. uudecoded the file (Note: it gave me message "Short file" !!) 2. uncompress ind.tar.Z 3. tar xvf on ind.tar This created a directoy "ind" with only *one* file "INSTALL" in it. I ran INSTALL and it completed by saying that installation is complete but I couldn't find the command anywhere. I think the problem is in tar. It should have created more than one file in directory ind. --------------- Vilok Kusumakar OSI Protocols for tomorrow...... vilok at bnr.ca Bell-Northern Research, Ltd. Phone: (613) 763-2273 P.O. Box 3511, Station C Fax: (613) 765-4777 Ottawa, Ontario, K1Y 4H7 From ucgadkw at UK.AC.UCL Tue Dec 8 10:44:16 1992 From: ucgadkw at UK.AC.UCL (Dominik Wujastyk) Date: Tue, 08 Dec 92 10:44:16 +0000 Subject: indhist Message-ID: <161227015561.23782.15040349840293631667.generated@prod2.harmonylists.io> On Dec 7, 2:56pm, Vilok wrote: > In message "Re: indhist", you write: > >it through the program XXdecode, followed by unZIP. Then you > > I have heard of uudecode/encode but not XXencode ? My workstation > running HP-UX 8.0 does not have it. I tried uudecode but it doesn't > work. What is XXencode ? Where can I get XXencode from ? Also I > don't have zip/unzip. > > Can somebody also get indhist converted to uuencode + compressed ? The XXencode binary-to-ascii conversion replaced UUencode about four years ago as the encoding of choice for robust transmission of files between networks (especially involoving ASCII/EBCDIC gateways). I have used Xxencode because it really solves a lot of problems which people have with Uuencoding. XXen/decode source code is freely available from many sites on the Internet (use archie to find the nearest site). Zip and unzip are also available free from many sites. Again, I refer you to Archie. Zip is a totally standard form of file distribution, far more widely used than compress. I append the C source code for xxdecode. Dominik /* Date: Wed, 13 Jul 88 13:39:20 cdt From: wucs1!wubios!david at uunet.UU.NET (David Camp) Subject: XXENCODE.C and XXDECODE.C Here is the source for XXENCODE and XXDECODE, replacements for UUENCODE and UUDECODE that use a better character set. I use them to transfer files between VM/CMS and my PC and Unix. They were developed by Phil Howard . I adapted them for MS-Dos and VM/CMS. They are public domain. Notice that under VM/CMS, these require the Waterloo C compiler. Under MS-Dos they require the Microsoft C compiler. The usual cc command works under Ultrix. *-------------------------------------------------------------------------* | (314) 362-3635 Mr. David J. Camp | | Room 1108D ^ Box 8067, Biostatistics | | 706 South Euclid < * > Washington University Medical School | | v 660 South Euclid | | Bitnet: david%wubios at wucfua.wustl Saint Louis, MO 63110 | | Internet: david%wubios at wucfua.wustl.edu | *-------------------------------------------------------------------------* -----xxdecode.c----- */ #ifndef lint static char sccsid[] = "@(#)xxdecode.c 5.3 (Berkeley) 4/10/85"; #endif /* * xxdecode [input] * * create the specified file, decoding as you go. * used with xxencode. */ #include #include #ifndef MSDOS #ifndef VMCMS #include #endif /* VMCMS */ #else /* MSDOS */ #include #include #endif /* MSDOS */ #ifndef VMCMS #include #include #else #include #include #include DIR * dir; #define perror(string) fprintf (stderr, "%s\n", string) #endif /* VMCMS */ /* single character decode */ #define DEC(c) ( table[ (c) & 0177 ] ) static char set[] = "+-0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"; static char table[128]; int replace; main (argc, argv) int argc; char * argv []; { FILE *in, *out; int mode; char source [128]; char cdest [128]; char * dest; char * temp; int i; char buf[80]; int did = 0; int replflg = 0; int nameptr = 1; struct stat statbuf; if (argc > 1) { if (strcmp (argv [1], "-r") == 0 || strcmp (argv [1], "-R") == 0) { replflg = 1; nameptr = 2; } } /* input filename */ if (nameptr <= argc - 1) { strcpy (source, argv [nameptr]); #ifdef VMCMS for (i = nameptr + 1; i < argc; i++) { strcat (source, " "); strcat (source, argv [i]); } #endif /* VMCMS */ if ((in = fopen(source, "r")) == NULL) { #ifndef VMCMS perror(source); #else /* VMCMS */ fprintf (stderr, "Cannot open file <%s>\n", source); #endif /* VMCMS */ exit(1); } } else #ifdef VMCMS { fprintf (stderr, "Usage: xxdecode [-r] fn ft [fm] "); fprintf (stderr, "[> fn ft [fm] [(options] (bin]\n"); exit (2); } #else in = stdin; if (isatty (fileno (in)) || argc > 2) { fprintf (stderr, "Usage: xxdecode [-r] [infile]\n"); exit(2); } #endif /* VMCMS */ while (1) { dest = cdest; /* search for header line */ for (;;) { if (fgets(buf, sizeof buf, in) == NULL) { if (! did) { fprintf (stderr, "No begin line\n"); exit (3); } else exit (0); } if (strncmp(buf, "begin ", 6) == 0) { did = 1; break; } } sscanf(buf, "begin %o %s", &mode, dest); /* handle ~user/file format */ if (dest[0] == '~') { #ifndef VMCMS #ifndef MSDOS char *sl; struct passwd *getpwnam(); char *index(); struct passwd *user; char dnbuf[100]; sl = index(dest, '/'); if (sl == NULL) { fprintf(stderr, "Illegal ~user\n"); exit(3); } *sl++ = 0; user = getpwnam(dest+1); if (user == NULL) { fprintf(stderr, "No such user as %s\n", dest); exit(4); } strcpy(dnbuf, user->pw_dir); strcat(dnbuf, "/"); strcat(dnbuf, sl); strcpy(dest, dnbuf); #else dest++; #endif /* MSDOS */ #endif /* VMCMS */ } replace = replflg; if (strcmp (dest, "/dev/stdout") != 0) { #ifdef VMCMS for (i = strlen (dest) - 1; i >= 0 && dest [i] != '/'; i--) dest [i] = toupper (dest [i]); dest = &dest [i + 1]; for (i = 0; dest [i] && dest [i] != '.'; i++) dest [i] = toupper (dest [i]); if (dest [i] == '.') dest [i] = ' '; for (; dest [i] && dest [i] != '.'; i++) ; if (dest [i] == '.') dest [i] = '\0'; #endif /* VMCMS */ if (stat (dest, &statbuf) == 0 && ! replflg) { fprintf (stderr, "File <%s> already exists.\n", dest); fprintf (stderr, "Replace? (Y or N): "); #ifdef VMCMS fprintf (stderr, "\n"); #endif /* VMCMS */ do { fscanf (stdin, "%s", buf); buf [0] = toupper (buf [0]); } while (buf [0] != 'N' && buf [0] != 'Y'); replace = (buf [0] == 'Y'); } else replace = 1; #ifdef VMCMS strcat (dest, " (bin"); #endif /* VMCMS */ } else replace = 1; /* create output file */ if (replace) { fprintf (stderr, "Opening file: %s\n", dest); if (strcmp (dest, "/dev/stdout") == 0) out = stdout; else out = fopen(dest, "w"); #ifdef MSDOS if (setmode (fileno (out), O_BINARY) == -1) { perror ("Cannot open stdout as binary\n"); exit (3); } #endif /* MSDOS */ if (out == NULL) { #ifndef VMCMS perror(dest); #else /* VMCMS */ fprintf (stderr, "Cannot open file <%s>\n", dest); #endif /* VMCMS */ exit(4); } #ifndef VMCMS chmod(dest, mode); #endif /* VMCMS */ } decode(in, out); if (fgets(buf,sizeof (buf), in) == NULL || strcmp (buf, "end\n")) { fprintf(stderr, "No end line\n"); exit(5); } } } /* * copy from in to out, decoding as you go along. */ decode(in, out) FILE *in; FILE *out; { char buf[80]; char *bp; int n; bp=table; /* clear table */ for( n=128 ; n ; --n ) { *(bp++) = 0; }; bp=set; /* fill table */ for( n=64 ; n ; --n ) { table[ *(bp++) & 0177 ] = 64-n; }; for (;;) { /* for each input line */ if (fgets(buf, sizeof buf, in) == NULL) { printf("Short file\n"); exit(10); } n = DEC(buf[0]); if (n <= 0) break; bp = &buf[1]; while (n > 0) { if (replace) outdec(bp, out, n); bp += 4; n -= 3; } } } /* * output a group of 3 bytes (4 input characters). * the input chars are pointed to by p, they are to * be output to file f. n is used to tell us not to * output all of them at the end of the file. */ outdec(p, f, n) char *p; FILE *f; { int c1, c2, c3; c1 = DEC(*p) << 2 | DEC(p[1]) >> 4; c2 = DEC(p[1]) << 4 | DEC(p[2]) >> 2; c3 = DEC(p[2]) << 6 | DEC(p[3]); if (n >= 1) putc(c1, f); if (n >= 2) putc(c2, f); if (n >= 3) putc(c3, f); } /* fr: like read but stdio */ int fr(fd, buf, cnt) FILE *fd; char *buf; int cnt; { int c, i; for (i=0; i: [Elaine Brennan : 6.0405 Rs: Sanscrit and Hungarian E-Texts (2/216)]] Message-ID: <161227015563.23782.8169374187532737202.generated@prod2.harmonylists.io> Cross-posting, for your info. /David Magier Columbia University --------------- Return-Path: Received: by cunixf.cc.columbia.edu (5.59/FCB/jba) id AA10809; Sat, 12 Dec 92 22:55:55 EST Date: Sat, 12 Dec 92 22:55:54 EST From: Anita Lowry To: magier Cc: scottr Subject: [Elaine Brennan : 6.0405 Rs: Sanscrit and Hungarian E-Texts (2/216)] Message-Id: David, FYI. /Anita --------------- Return-Path: Received: from brownvm.brown.edu by cunixf.cc.columbia.edu (5.59/FCB/jba) id AA04939; Fri, 11 Dec 92 20:13:54 EST Message-Id: <9212120113.AA04939 at cunixf.cc.columbia.edu> Received: from BROWNVM.BROWN.EDU by BROWNVM.brown.edu (IBM VM SMTP V2R2) with BSMTP id 0528; Fri, 11 Dec 92 20:07:32 EST Received: from BROWNVM.BITNET by BROWNVM.BROWN.EDU (Mailer R2.08 R208004) with BSMTP id 5066; Fri, 11 Dec 92 15:46:48 EST Date: Fri, 11 Dec 1992 15:12:09 EST Reply-To: Elaine Brennan Sender: "HUMANIST: Humanities Computing" From: Elaine Brennan Subject: 6.0405 Rs: Sanscrit and Hungarian E-Texts (2/216) To: Multiple recipients of list HUMANIST Humanist Discussion Group, Vol. 6, No. 0405. Friday, 11 Dec 1992. (1) Date: Thu, 10 Dec 92 12:00:10 WST (21 lines) From: From: Thomas B. Ridgeway Subject: bject: Re: 6.0397 E-Text Query (1/10) (2) Date: Wed, 9 Dec 1992 16:17 EST (195 lines) From: From: Paul Mangiafico Subject: bject: Sanskrit and Hungarian E-texts (1) -------------------------------------------------------------------- Date: Thu, 10 Dec 92 12:00:10 WST From: Thomas B. Ridgeway Subject: Re: 6.0397 E-Text Query (1/10) John Haviland of Reed enquires re Sanskrit (or Hungarian) e-texts: A small sample of Sanskrit e-texts is available for anonymous ftp from blackbox.hacc.washington.edu in the directory pub/indic (Brihatsamhita, Panini Sutras, Buddhacarita and Saundaryalahari to be specific). These are encoded in the proposed Classical Sanskrit Extended standard for encoding romanized Indic languages. For more discussion on this and related matters, I refer you to the listserv group Indology-l, based at liverpool.ac.uk Tom - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thomas Ridgeway, Director, Humanities and Arts Computing Center/NorthWest Computing Support Center 35 Thomson Hall, University of Washington, DR-10 Seattle, WA 98195 phone: (206)-543-4218 * Ask me about * Internet: ridgeway at blackbox.hacc.washington.edu * Unix TeX * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (2) --------------------------------------------------------------206--- Date: Wed, 9 Dec 1992 16:17 EST From: Paul Mangiafico Subject: Sanskrit and Hungarian E-texts Regarding John Haviland's request for Sanskrit and Hungarian e-texts, I was able to find a few with a quick search in Georgetown University's CPET (Catalogue of Projects in Electronic Text). I have included a list below, beginning with the ten categories under which the data is classified, and followed by info on projects with Sanskrit e-texts and one project with Hungarian e-texts. I hope this information is useful to many HUMANISTs. If you are in search of other e-texts, the Georgetown CPET may be of use to you as well. The CPET database can be accessed via Telnet or modem, or if you send me particulars on what you are looking for I can do a quick search for you and email the results. In any case, if you would like more information on this service, just send me a note. Paul Mangiafico, project assistant Center for Text & Technology Georgetown University pmangiafico at guvax.georgetown.edu **** CATEGORIES OF CLASSIFICATION **** 0. Identifying acronym or short reference. 1. Name and affiliation of operation (with collaborators noted). References to any published description. 2. Contact person and/or vendor with addresses (including telephone and email if possible). 3. Primary disciplinary focus (and secondary interests) [e.g. Literature, Language, Linguistics, Music, Art, etc.]. 4. Focus: time period, location, individual, genre, or medium. 5. Language(s) encoded; [English, French, German, et. al.]. 6. Intended use(s) [e.g. textbank, database, bibliography] with Goal (or statement of purpose) and Size [number of works, or entries, or citations]. 7. Format(s), including choice of sequential text or database excerpts, file formats, analytical programs and programming languages, text markup and encoding schemes, hardware and operating systems, etc. To what extent are the formats consistent throughout the archive? 8. Form(s) of access: if online, what policies? If tape, what track, bpi, block size, labels, parity setting? If diskette, what size and operating system or microcomputer? If CD-ROM, what format? What software is needed for accessing? Is it provided with the package? Availability and price. 9. Source(s) of the archival holdings: encoded in-house, or obtained from elsewhere (where)? Textual authority used for encoding? Titles of the works held, bibliographical information on them. **** PROJECTS WITH SANSKRIT E-TEXTS **** Bamberg (Otto Friedrich Universita%t)/ Thesaurus of Texts in Ancient Indo-European Languages CPET#184 0. THESIETEXT (Thesaurus of Texts in Ancient Indo-European Languages) 1. Thesaurus Indogermanischer Textcorpora; Universitat Bamberg, Germany See Journal "Die Sprache," Vol. 32/2 2. Dr. Jost Gippert Universita%t Bamberg, Orientalistik Postfach 1549 D-W-8600 Bamberg, Germany 3. Literature, language, linguistics, history 4. From beginning of literacy to 17th century; Eurasia 5. Old Indic (Sanskrit), Old Iranian (Avestan, Old Persian), Hittite, Tokharian, Old Germanic, Greek (Ancient), Italic languages, Armenian (Old), and several other I.- E. languages. 6. Textbank 7. Sequential text; encoding scheme of DOS, WordCruncher, and WordPerfect 5.1 8. Access on diskettes, CD-ROM (planned) 9. Encoded by various scholars in different parts of Europe. Hamburg (Univ)/ Sanskrit medical encyclopaedias CPET#191 1. Sanskrit medical encyclopaedias 2. Prof. R.E. Emmerick Iranian Studies University of Hamburg Germany 3. Medicine 4. Caraka, Susruta, Astangahrdaya, Astangasamgraha, and the Siddhasara of Ravigupta 5. Sanskrit Tu%bingen (Seminar fu%r Indologie und Vergleichende Religionswissenschaft)/ Tu%bingen Parana Project CPET#308 1. Tu%bingen Parana Project. Peter Schreiner, Renate So%hnen, Heinrich v. Stietencron. Publications Indicies and Text of the Brahmapurana. Wiesbaden: Harrassowitz [1987] 2. Professor Dr. Heinrich v. Stietencron Seminar fu%r Indologie und Vergleichende Religionswissenschaft Mu%nzgasse 30 D-7400 Tu%bingen Germany Tel. 0049-7071-292675 3. Indology (Indian studies), Sanskrit 4. Classical Hinduism; Puranas, Brahmapurana 5. Sanskrit 6. Published indicies on microfiche; deposit of the input with the Oxford Text Archive has been announced but not yet carried out. The Brahmapurana is a single Sanskrit text with ca. 14000 verses. 7. Straight-forward trans-literation with marking of sandhi, nominal compounds, references; TUSTEP format (ASCII format possible). TUSTEP programs for KWIC-index, reserve index word forms etc. 9. Encoded in-house. Zurich (Univ)/ Sanskrit texts CPET#268 1. Sanskrit texts 2. Prof. Peter Schreiner Abteilung fu%r Indologie Universita%t Zu%rich Ra%mistr. 68 CH-8001 Zu%rich Switzerland tel. 0041-1-2572036 3. Indology, Sanskrit, Hinduism, Indian philosophy 4. Visnupurana, Manu, Sakuntala, Asvaghosa, Buddhacarita, Gaudapada-Karika, Adisesa, Paramarthasara, Bhagavadgita, Narayaniyam, Mahabharata, Svetasvatara-Upanisad. 5. Sanskrit 6. deposit with Oxford Text Archive intended 7. Straight-forward trans-literation with marking of sandhi, nominal compounds, references; TUSTEP format (ASCII format possible). TUSTEP programs for KWIC-index, reserve index word forms etc. 8. Presently none 9. Encoded in-house TX Austin (University of Texas)/ Thesaurus Linguae Sanskritae CPET#101 1. Thesaurus Linguae Sanskritae, University of Texas 2. Prof. R. Lariviere University of Texas Austin, Texas 78712 tel. (512) 471-5811 5. Sanskrit 9. Texts include Mahabharata and Ramayana **** PROJECT WITH HUNGARIAN E-TEXTS **** PA Pittsburgh (Carnegie Mellon Univ)/ CHILDES Database CPET#95 0. CHILDES (Child Language Data Exchange System) 1. Childes Database, Carnegie Mellon Univ See "The Child Language Data Exchange System: An Update," Journal of Child Language, [1990]. Snow, Catherine. "The Child Language Data Exchange System", ICAME Journal (No.14). Bergen, Norway: Norwegian Computing Center [April 1990]. Carterette, E. & Jones, M.H. Informal Speech. Berkeley: University of California Press [1974]. MacWhinney, B. & Snow, C. "The Child Language Data Exchange System", Journal of Child Language (Vol.12, pages 271-296). [1985]. 2. Brian MacWhinney Department of Psychology Carnegie Mellon University Pittsburgh, PA 15213 BITNET: brian at andrew.bitnet Internet: edu%"brian at andrew.cmu.edu" 3. Linguistics; psycholinguistics 4. Transcripts of children's dialogue 5. English, Afrikaans, Danish, Dutch, French, German, Hebrew, Hungarian, Italian, Polish, Slobin, Spanish, Tamil. 6. Database of 40 sets of corpora of parent-child and child- child interactions from children speaking (13 languages in total); the corpora are divided into six major directories: English, non-English, narratives, books, language impairments, and second language acquisition; includes three major tools for child language research: (1) the CHILDES database of transcripts, (2) the CHAT system for transcribing and coding data, and (3) the CLAN programs for analyzing CHAT files; 140 million characters (140 MB). 7. Database excerpts; available on floppies and tapes; detailed coding scheme has been devised and the data are put in that format 8. (Planned) CD-ROM 9. Obtained from researchers From buddha at EDU.STANFORD.LELAND Tue Dec 15 09:29:01 1992 From: buddha at EDU.STANFORD.LELAND (buddha at EDU.STANFORD.LELAND) Date: Tue, 15 Dec 92 01:29:01 -0800 Subject: Subscribing Message-ID: <161227015565.23782.17863785535547700874.generated@prod2.harmonylists.io> How do I subscribe to this list? Yours, Corvin Russell From CXEV at CA.MCGILL.MUSICA Fri Dec 18 17:24:27 1992 From: CXEV at CA.MCGILL.MUSICA (Richard P Hayes) Date: Fri, 18 Dec 92 12:24:27 -0500 Subject: job listing Message-ID: <161227015567.23782.6977891348848263051.generated@prod2.harmonylists.io> Prof. Jan Nattier asked me to forward this to INDOLOGY. If you seek further information on this posting, please contact her by e-mail at jnattier at bronze.ucs.indiana.edu ------------- atra chettavya ------- cut here ----------------------- To all colleagues: Please distribute the following job announcement to those who might be interested. Thank you. INDIANA UNIVERSITY, Bloomington IN 47405. The Dept of Religious Studies invites applications for a one-year visiting position in Sanskrit at the Asst Prof level with the possibility of renewal, depending upon funding and course enrollments. The ability to teach a second Hindu or Buddhist language (e.g., Hindi, Khotanese, Pali, Sogdian, or Tokharian) is an advantage. Appt begins August 1993. Send ltr of application, vita, and 3 ltrs of recommendation by closing date of Feb 15, 1993 to: Sanskrit Search, Dept of Religious Studies, Sycamore Hall 230, Indiana University, Bloomington IN 47405. (FAX 812-855-4687). Indiana University is an Equal Opportunity/Affirmative Action employer. --------- From aklujkar at CA.UBC.UNIXG Sun Dec 20 23:39:26 1992 From: aklujkar at CA.UBC.UNIXG (aklujkar at CA.UBC.UNIXG) Date: Sun, 20 Dec 92 15:39:26 -0800 Subject: Absence from station Message-ID: <161227015569.23782.5922627808299775867.generated@prod2.harmonylists.io> Kindly note that I shall be away on a lecture and research tour from 20 December 1992 to approximately l7 April 1993. I shall be travelling mostly in south and western India. If any of you must get in touch with me (you are at least not encouraged to do so), please write to the following address: c/o Prof. Sarojini Vaidya, Africa House, Adenwala Road, Near King s Circle, Matunga, Bombay 400 019. There is a possibility that on my way back I shall stop in London for a few days. Thank you. -- Ashok Aklujkar, University of B.C., Vancouver. From IEP0PMR at EDU.UCLA.OAC.MVS Tue Dec 22 02:20:00 1992 From: IEP0PMR at EDU.UCLA.OAC.MVS (Patrick McReynolds 3102081070) Date: Mon, 21 Dec 92 18:20:00 -0800 Subject: query Message-ID: <161227015571.23782.2301495628512418830.generated@prod2.harmonylists.io> TO THE DEPTARTMENT OF RELIGIOUS STUDIES INDIANA UNIVERSITY (BLOOMINGTON): Dr. J. Nattier & INDOLOGY DISCUSSION (LIVERPOOL) FROM Fr. Patrick McReynolds (in Indo-European Studies at UCLA) Greetings (& Happy Holidays): This is just an inquiry, since my availability will depend on what my Archbishop in New York may decide in the meanwhile. But I may be available for a post in History of Religions. BA Gonzaga U. (Spokane, WA) 1972 in Theology and Philosophy (with classical course- Latin and Greek) MA Fordham U. (Bronx, NY) 1978 in History of Religions (with courses in Sanskrit, and readings in classical and Buddhist Sanskrit texts) (DD semi-honorary, Independent Catholic U., NY, 1980) CPh UCLA (L.A., CA) 1985 in Indo-European Studies (Interdepartmental Program) (Ph D to be awarded next quarter) I have done extensive work in Sanskrit and especially Vedic here, and have also done course work in Pali and Prakrit languages; and have a reading knowledge of several ancient languages including Old Norse, Greek, Latin, Avestan; and also Lithuanian, Spanish, French and German; and besides the I.E.- Akkadian, Hebrew, and some work in Sumerian. My background is in History of Religions, comparative mythology and so forth (Fr. Thomas Berry at Fordham). And my dissertation (BEFORE YMIR: THE PRIMAL PHASE OF AN INDO-EUROPEAN COSMOGONY) is on a certain aspect of I.E. mythology; with several chapters dealing specifically with Vedic and Indic besides Iranian issues. Jaan Puhvel is the chairman of my committee here. However, I am not much published outside of religious publications of private or limited circulation. I was a contributing translator for THE PLIGHT OF THE SORCERER (Jaan Puhvel, & David Weeks eds.- a translation of a part of Dumezil's Mythe et Epopee); and have had some experience at college level teaching at Fordham, and other experience lecturing thereafter. If you think it might be worth my while to inquire or apply further, please let me know. If not, we will assume you are looking for more of a specialist in Sanskrit or Indic studies, or someone who could make a firmer commitment.... Sincerely, +Patrick McReynolds 801 Levering #3 Los Angeles, CA. 90024 (310 208 1070) From R24340 at EARN.UQAM Tue Dec 22 18:08:47 1992 From: R24340 at EARN.UQAM (Mathieu Boisvert) Date: Tue, 22 Dec 92 13:08:47 -0500 Subject: Edith Nolot Message-ID: <161227015574.23782.984374343840895383.generated@prod2.harmonylists.io> Does anyone know the address and/or phone number of the French scholars Edith Nolot who just published a French translation of the Milindapa%nha? Thank you very much, Mathieu Boisvert Departement des sciences religieuses, Universite du Quebec a Montreal R24340 at UQAM.BITNET.CA