SDF Text Translations |
----------------------

The purpose of this project is to translate key documents authored in English
to various languages used around the world.  This isn't meant to be an all
encompasing project, but a very specific one to deal with these key text files:

what.txt       -    What is SDF?  A high level overview.
newuser.txt    -    An introduction to user commands and features 
newarpa.txt    -    An introduction to ARPA commands and features
newmeta.txt    -    An introduction to MetaARPA commands and features
newdba.txt     -    An introduction to the DBA membership
[...]

The file naming convention for translations should follow:

filename_XX.txt  where 'XX' = the two letter country code where the language
is primarily used.  If there is no country where the language is used, you
might want to reconsider your effort.

[FILE CREATION]
To create a new translation, use your favorite editor using a unique filename
with an .txt extension.  Be sure to include a RCS ID tag at the bottom
of your file, which essentially is:  $Id: README.TXT,v 1.2 2006/09/19 19:20:38 smj Exp $  (take out the backslashes).
Also, make sure the permissions for the file are acceptable for use by
the webserver; ie, "chmod og+r file" or "umask 022" before creating the
file.

Once you have finished editing your first version, save your file and
then run 'ci -u filename' at the shell.  You will be asked for a
description of the file. End with a '.' on a blank line.  This will
add the file to the repository, and leave the file unlocked.

[FILE EDITING]
Editing is open to all MetaARPA members.  Though no formal permission from
the initial author is needed, please be sure that your changes or additions
are necessary or helpful.  Run the 'co -l filename' command at the shell.

  **NOTE** If when using 'co -l' you are told that the file is already locked
           please STOP what you are doing and wait for it to be checked back
           in.  If it does not get checked back in, email the author and
           let them know you want to check out the file and edit it.

This will copy out the file from RCS and allow you to make changes to
it. Once your changes have been made, save your file, double check the
permissions, and then run 'ci -u filename'. It is very important that
you do this and report the changes you've made. The file will be updated
and left ulocked. The file will then be available for others to check
out and revise as needed.

[DISCUSSIONS]
Discussions concerning this project should be posted on the bboard:<TRANSLATE>

$Id: README.TXT,v 1.2 2006/09/19 19:20:38 smj Exp $