[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: `boot-floppies' documentation naming conventions?



On Sun, Mar 19, 2000 at 03:29:05AM -0800, Karl M. Hegbloom wrote:
> 
> >>>>> "Debian" == Debian Bug Tracking System <owner@bugs.debian.org> writes:
> 
>     Debian> Processing commands for control@bugs.debian.org:
>     >> reassign 58638 boot-floppies
>     Debian> Bug#58638: The documentation in disks-i386 is not available in other languages
>     Debian> Bug reassigned from package `ftp.debian.org' to `boot-floppies'.
> 
>  This reminds me...  Not only do we need to ensure that the
>  non-english documentation gets installed by our `make release'
>  target, we need to make sure that the file names are of the correct
>  form so that content negotiation will function correctly.
> 
>  Yesterday was the first time I read anything about that...  What I
>  learned is that with Apache "Options Multiviews", a file named like
>  "name.html.en" will be found when "name.html" is requested, but a
>  name like "name.en.html" will not, unless `mod_rewrite' is used...(?)
> 
>  Can you clue me in?  What should we be naming the documentation files
>  like so that things will function correctly on
>  <URL:http://http.us.debian.org/debian> and others?
> 
Please name file using the convention foo.lang.html . We decided on that
format instead of foo.html.lang because apache can get confused on the
mime type. Local links should be relative and only name the file base,
e.g. foo. 

On a related note, is boot-floppies responsible for the files in
releases/{slink,potato}/? There are a number of problems with links there
and I need to know who to forward problems/bugs to (and there are currently
a LOT of broken links). If I had access to the source, I'd even be willing
to fix problems with the links.

In the future, could you send mail directly to debian-www? We'd combine
webmaster and debian-www, but webmaster occasionally gets mail not meant
for public consumption.

-- 
James (Jay) Treacy
treacy@debian.org


Reply to: