HOWTO Translation Directory Structure Specification by Greg Hankins, gregh@sunsite.unc.edu v1.2, 20 January 1997 This document contains the formal directory tree specification for HOWTO translations. It is also available at http://sunsite.unc.edu/gregh/Directory-Structure.html. 1. Translation Location HOWTO Translations will be located at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/translations/. This location has the advantages of: · a fast server, with plenty of disk space and a fast network connection · many mirror sites around the world · CDROM archives are made of sunsite.unc.edu, thus any translations that appear on sunsite.unc.edu also appear on the CDROMs. · sunsite.unc.edu is already on of the leading Linux sites in the world, and is the home site of the English HOWTO project. 2. Formatting Formatting will be done by each translation team. This way, the work is distributed, and each team can freely use language-specific features (for example A4 paper size). 3. Directory Names The directories for each language with be named using the ISO 639 language code , with symlinks in English. For example, German translations would be located at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/translations/de with a symlink to ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/translations/german. 4. Subdirectory Structure The subdirectory structure will be very similar to the English HOWTO directory structure. The top level directory will have gziped plain text versions of the HOWTOs, along with the following subdirectories: · dvi, with gziped DVI versions of the documents · html, with tared and gziped HTML versions of the documents · ps, with gziped PostScript versions of the documents · sgml, with gziped SGML sources of the documents · mini, where "mini" is spelled in the native language, with plain text mini-HOWTO translations Other formats (for example, RTF), maybe be added following the above convention. 5. Informational Files At a minimum, a file named README, or other obvious name should be placed in the top level directory listing translation team contact information, such as names, email addresses, and WWW or FTP sites. Index files may also be included. 6. Updating Translations Translations maybe be updated in the following ways: 1. I can set up a mirror script to mirror the home location of the translations. Each translation team must provide someone to receive the output from the mirror script, and may pick a time that the mirror script will run if they want. 2. A gziped tar file with the correct directory structure of the translation team's archive site, or a gziped tar file with each HOWTO, can be uploaded to ftp://sunsite.unc.edu/pub/incoming/Linux, and I can untar it in the appropriate place.