Re: Policy Weekly Issue #4/10: Filesystem location of non-english documentation files

[Christophe Le Bars <clebars@teaser.fr>]

**On 24 Oct, CS (Christian Schwarz) wrote:
CS>Policy suggestion
CS>
CS>In continuation of this policy I suggest to keep all documentation files
CS>in one place: /usr/doc/<pkg>. In case of non-english docs, the files would
CS>be placed into a subdirectory /usr/doc/<pkg>/LANG_<locale>

I only view disadvantages with this solution:

a) users can't change the directory to their own <language>
   documentations tree.

b) no gains, since users who change the directory to /usr/doc/<pkg>
   already find non-english documentations with the links:
	/usr/doc/<pkg>/<language> -> /usr/doc/LANG/<language>/<pkg>

c) /usr/doc/LANG/<language> policy is much more the
   continuation of the classic /usr/man/<language> or
   /usr/X11R6/lib/X11/<language> filesystem policy.

d) we must change again all packages with non-english docs ;-)

CS>The locale string can have the form <language> or <language>_<territory>. 
CS>It is the maintainers job to decide which form to be used for a specific
CS>documentation file. 

I'm not sure that we need <territory>...

CS>The LANG_ prefix is used to reduce the possibility of a file name
CS>conflict.  (I don't think an extra LANG/ directory is appropriate here.) 
CS>
CS>Any program/script that needs to access documentation files mechanically
CS>should search for the files in the following directories (in exactly this
CS>order): 
CS>
CS>     /usr/doc/<pkg>/LANG_<language>_<territory>/
CS>     /usr/doc/<pkg>/LANG_<language>/
CS>     /usr/doc/<pkg>/

I prefer this order:

   [ /usr/doc/LANG/<language>_<territory>/<pkg>/ ]
     /usr/doc/LANG/<language>/<pkg>/
     /usr/doc/<pkg>/

-- 
       Christophe Le Bars - clb@alcove.fr - clebars@debian.org 
1000110101011100101011000110101011100101010001101010111001010101000110
           Utilisez Debian! - http://www.teaser.fr/~clebars
            Linux dans l'entreprise - http://www.alcove.fr