[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]

Minutes of ILUGC Meet, 15th July 2000



************************************************************************

                     Minutes of the ILUGC Meet 15th July, 2000

************************************************************************



 The ILUGC met on the 15th Saturday, 2000 without much of agendas.
 Though many of us thought that the meeting will end earlier, it took
 a long and interesting length of time to finish.

 The only planned stuff was a talk on CVS (Concurrent Versioning System)

 by Zameer Ahmed. Zameer started off the speech by quoting the problems
 he had during a project. He explained how cumbersome the task of
 taking backups is.

 The history of the birth of CVS was explained very well. RCS was the
 (supposed) first Version Control System which was made out of a few
 shell scripts.CVS is based on RCS though not a few shell scripts.

 Terms such as checking in, Update, and checking out/commit was
 explained. CVS maintains a source tree on a pserver. The syntax for
 initialising, checking-in, committing, etc., were discussed.

 The method of installing the rpms (and of course, THE pkg of the
 majority of the gang, .deb) were discussed. Some tips on managing
 source development in groups were shared.

 CVS puts the files on the pserver and maintains the versions of the
 files in a directory called CVSROOT. This directory has many files for
 controlling the versions of the files. Locking files, Undeleting files
 and other such misc.  stuff were explained.

 Zameer suggested interested CVSians to check out:

  http://daemonnews.org

 Through out the meet there were Debianistic voices: "Deb Rulezzz!".

 Ravi* was making a lot of noise.

 Swaraj* (not to be mistaken as suraj) was making a lotter more noise!

 After having received a mail on Tamil for KDE, Prabhu requested
 Mr.M.K.Saravanan for giving a talk on Localising KDE for Tamil.
 Almost everyone appreciated the mind-blowing screen shots of the KDE
 Tamil Desktop (TM). MKS explained the Character sets of ASCII.

 ASCII which is designed for Supporting the English (26_uppercase +
 26_Lowercase + 75_other_stuff + 127_Extended_Characters) can barely
 accommodate the Indian Language Character sets. For instance tamil has
 over 260 characters. To overcome this problem, a new character set
 called ISCII, was designed by C-DAC (Centre for Development in Advanced

 Computing). CDAC started their research in this project by assuming
that
 all indian languages were derived from "Brahmi".

 The diversity in Unity of about 10 standards was mentioned. He
explained
 some techniques involved in Producing many chars from the existing kbd
 like Glyphs, Kerning. A lot of humor was seen in his speech. The TAB
 / TAM standards by the govt. were discussed. The  present Unicode is
 cramped because it was submitted by CDAC as soon as the ISCII was
 designed. This was done without the knowledge of the Tamil Nadu State
 Govt. The steps taken by the govt (KaniThamizh Sangam) was explained.

 He emphasised that it is the duty of us linuxians to support the
 "Tamil for KDE" project. All that one needs is to:

  1. obtain the "Akaram" TSCII editor
   (written by Mr. N.Govindasami).
  2. Open the Local Language settings file from the KDE source.
  3. Fill in the Tamil Equivalent for the corresponding english
  text.

 He said that the requisite for joining this project is NOT programming
 skills but ONLY patience.  (-:

 He wanted us to volunteer for localising KDE for Tamil. There were a
few
 volunteers as many of them were not skilled in Tamil. )-:

 See it to believe it. Check out:

  http://members.home.net/gomathiss/kde.html

 Quote of the meet:

  "Perl is a Write-Only Language"
     -Vineet Chaitanya
             (quoted by Mr.M.K.Saravanan)

  -Suraj

















__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

---
Visit our home page at: www.chennailug.org
Send e-mail to 'ilugc-request@xxxxxxxxxxxxxxxxxx' with 'unsubscribe' 
in either the subject or the body to unsubscribe from this list.