Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

Package: www.debian.org Followup-For: Bug #791506 Control: retitle -1 [www.debian.org] Release notes are translated per-language, not per-locale > Content negotiation works well: if you have pt-BR and pt locales enabled in > browser, and go to https://www.debian.org/releases/bu

Processed: Re: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

Processing control commands: > retitle -1 [www.debian.org] Release notes are translated per-language, not > per-locale Bug #791506 [www.debian.org] [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page Changed Bug title to '[www.debian.org] R

Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

Hello Content negotiation works well: if you have pt-BR and pt locales enabled in browser, and go to https://www.debian.org/releases/bullseye/releasenotes you are presented a "pt" translation of the page (because there is no pt-br translation of that page) and thus the links to

Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

, then the page is negotiated to a fallback language (en-based with my browser settings). Is it possible that content-negotiation is only enabled currently for two-character language codes, and not for country+locale combinations? Thank you, James

Bug#789377: marked as done (www.debian.org: update browsers section in content negotiation page (cn.wml))

Your message dated Tue, 29 Mar 2016 17:27:47 + with message-id <e1akxqh-0002tf...@moszumanska.debian.org> and subject line Debian WWW CVS commit by holger-guest fixes #789377 has caused the Debian Bug report #789377, regarding www.debian.org: update browsers section in content negotiatio

Re: Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)

Hi, Holger Wansing wrote: > Please find the new patch attached, and the resulting html file. > Just committed. Holger -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0 " J E

Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)

uage Obviously, not everyone in the world uses the same language. As the web grows it is becoming more common to find pages that are available in multiple languages. A standard was therefore introduced, called content negotiation, that allows a person to set the language(s) they prefer to receive documents

Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)

On Sat, Mar 26, 2016 at 4:55 AM, Holger Wansing wrote: > If noone objects, I will commit it shortly. Galeon should be removed, it is dead for a long time. There appears to be some missing space after the Voyager and IBrowse sections. I would suggest putting the W3C link at the very top since

Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)

irefox). > - renaming "Chromium" to "Chrome and Chromium" > - removing the workaround for a bug in Konqueror (bug fixed in 2008) > - sorting browsers alphabetically > - adding W3C page about content negotiation, as suggested by pabs > > > There is a patch attached

Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

Hi, Marcelo Santana wrote: > Please could anybody verify why the CN doesn't work properly for the > Release Notes web page[1] with pt_BR language? > > [1]https://www.debian.org/releases/stable/releasenotes > > Explaining better, although I have my browser configured

Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page

Package: www.debian.org Severity: wishlist Tags: l10n Hi there. Please could anybody verify why the CN doesn't work properly for the Release Notes web page[1] with pt_BR language? [1]https://www.debian.org/releases/stable/releasenotes Explaining better, although I have my browser configured

Re: improve content negotiation page

On Fri, Jun 19, 2015 at 10:07 PM, Stéphane Blondon wrote: - remove old browsers (Netscape 3 and 4, old versions of Firefox). - rename Chromium to Chrome and Chromium - sort browsers alphabetically Sounds good, I think we should also link to this page:

Bug#789377: www.debian.org: update browsers section in content negotiation page (cn.wml)

and Chromium - removing the workaround for a bug in Konqueror (bug fixed in 2008) - sorting browsers alphabetically - adding W3C page about content negotiation, as suggested by pabs There is a patch attached to this message to do it. -- Stéphane Index: cn.wml

Re: improve content negotiation page

2015-06-20 9:24 GMT+02:00 Paul Wise p...@debian.org: On Fri, Jun 19, 2015 at 10:07 PM, Stéphane Blondon wrote: I can send a patch or report it in the BTS if you want. I would suggest sending a patch to the BTS. Done. It's bug #789377. Have a nice day -- Stéphane -- To UNSUBSCRIBE, email

improve content negotiation page

Hello, with the previous question on the mailing list about changing language preference in the browser, I read https://www.debian.org/intro/cn#howtoset page and I think we could improve the browsers section (Setting the preferred language in a browser): - remove old browsers (Netscape 3 and 4,

Content negotiation broken on www.de.debian.org

Package: mirrors Severity: minor On Fri, Jul 20, 2007 at 11:38:26AM +0200, Alexander Schmehl wrote: * Holger Wansing [EMAIL PROTECTED] [070719 23:10]: I noticed that content negotiation is not working (or not working correctly) at least for german on www.debian.de, while on www.debian.org

Re: Content negotiation on www.debian.de

Hi! * Holger Wansing [EMAIL PROTECTED] [070719 23:10]: I noticed that content negotiation is not working (or not working correctly) at least for german on www.debian.de, while on www.debian.org it works fine: www.debian.de is displayed in english, while www.debian.org is shown in german

Content negotiation on www.debian.de

Hello, I noticed that content negotiation is not working (or not working correctly) at least for german on www.debian.de, while on www.debian.org it works fine: www.debian.de is displayed in english, while www.debian.org is shown in german (as it is configured here in iceweasel, so

Re: Content negotiation - ICS Calendar files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/2006 11:01 AM, Jutta Wrage wrote: [...] Okay, it is a bug in the browsers, too, that I cannot change that (as far as I know). But _no_ web server with normal web pages should prefer delivering ICS calendar files instead of HTML pages.

Re: Content negotiation - ICS Calendar files

On Fri Mar 03, 2006 at 23:25:21 -0300, Felipe Augusto van de Wiel (faw) wrote: On 03/03/2006 05:16 PM, Jutta Wrage wrote: I noticed a probple with content negotiation on the event pages. If I visit any link on http://www.nl.debian.org/events/2006/ I always get the ics file. That's

Re: Content negotiation - ICS Calendar files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 04.03.2006 um 03:25 schrieb Felipe Augusto van de Wiel (faw): That's strange, accessing the above link via Mozilla and Mozilla Firefox (both from etch) show me the HTML. I tried using www.nl, www.us, www.br, www.de and just www. All

Re: Content negotiation - ICS Calendar files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2006 05:16 PM, Jutta Wrage wrote: Hi! Hey Jutta, :) I noticed a probple with content negotiation on the event pages. If I visit any link on http://www.nl.debian.org/events/2006/ I always get the ics file. That's strange

Re: Content negotiation - ICS Calendar files

On Saturday 04 March 2006 03:25, Felipe Augusto van de Wiel (faw) wrote: I noticed a probple with content negotiation on the event pages. If I visit any link on http://www.nl.debian.org/events/2006/ I always get the ics file. That's strange, accessing the above link via Mozilla

Re: Content negotiation - ICS Calendar files

* Felipe Augusto van de Wiel (faw) [EMAIL PROTECTED] [2006-03-03 23:25] : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2006 05:16 PM, Jutta Wrage wrote: Hi! Hey Jutta, :) I noticed a probple with content negotiation on the event pages. If I visit any link on http

Debian web sites and content negotiation

[Please CC me as I am not on -www] Is there any possible way to have pages on the Debian website set a cookie if the user explicitly selects a language and then continue to use that language as long as the cookie is valid? I ask because occasionally I will get annoyed by the website when I start

Re: Debian web sites and content negotiation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 30.10.2005 um 00:52 schrieb Roberto C. Sanchez: Is there any possible way to have pages on the Debian website set a cookie if the user explicitly selects a language and then continue to use that language as long as the cookie is valid? That

Re: Debian web sites and content negotiation

[Please CC me as I am not on -www] On Sun, Oct 30, 2005 at 01:14:19AM +0200, Jutta Wrage wrote: Am 30.10.2005 um 00:52 schrieb Roberto C. Sanchez: Is there any possible way to have pages on the Debian website set a cookie if the user explicitly selects a language and then continue to

Content negotiation on www.debian.org do not work again

Content negotiation on www.debian.org do not work (at least for Ukrainian; I always get pages in English). It was working some time ago. -- Eugeniy Meshcheryakov Kyiv National Taras Shevchenko University Information and Computing Centre http://icc.univ.kiev.ua signature.asc Description

Re: Content negotiation on www.debian.org do not work again

On Thu, Sep 22, 2005 at 08:21:59PM +0300, Eugeniy Meshcheryakov wrote: Content negotiation on www.debian.org do not work (at least for Ukrainian; I always get pages in English). It was working some time ago. Should be fixed tomorrow after the next reload of the apache.conf (www.debian.org

content negotiation does not work on www.debian.org?

Hello, It looks like content negotiation does not work for me when using www.debian.org (192.25.206.10). It works with www.(ua|nl).debian.org, so browser settings are correct. It worked also with main server in the past. Regards, -- Eugeniy Meshcheryakov Kyiv National Taras Shevchenko

Re: www.it.debian.org lost content negotiation

On Sat, Jan 22, 2005 at 01:40:10AM +0100, Giuseppe Sacco wrote: Subject says it all: the page always start in english. I verified this to be the case. Would one of you please investigate? -- Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact

Re: www.it.debian.org lost content negotiation

On Mon, Jan 24, 2005 at 01:40:29AM +0100, Marco d'Itri wrote: On Jan 24, Matt Kraai [EMAIL PROTECTED] wrote: Subject says it all: the page always start in english. I verified this to be the case. Would one of you please investigate? How? The configuration looks right to me:

Re: Content negotiation information

On 6/11/2004, Marcin Orda [EMAIL PROTECTED] wrote: How to set the default document language I've included such a link (to your website as a temporary solution) on my website just for a quick solution. The question is: would you mind me using some portions of the information you put in that

Content negotiation information

Hi, I'm just putting together my website http://www.securityshells.com mainly for my private use, i.e. job seeking, posting news, sharing photos, etc. Ispired by debian.org ;) I've been fiddling a bit with Apache content negotiation. At the bottom of every page you have a following link How

Re: Problem with content negotiation at www.de.debian.org

* Tommi Vainikainen [EMAIL PROTECTED] [2004-08-10 20:56]: I couldn't remember where to find contact person for particular mirror, but www.de.debian.org has problems with content negotiation. I've set content negotiation to accept primary finnish and secondary english. This works for other

Re: Problem with content negotiation at www.de.debian.org

On Wed Aug 11, 2004 at 11:36:41 +0200, Gerfried Fuchs wrote: * Tommi Vainikainen [EMAIL PROTECTED] [2004-08-10 20:56]: I couldn't remember where to find contact person for particular mirror, but www.de.debian.org has problems with content negotiation. I've set content negotiation

Problem with content negotiation at www.de.debian.org

Hi, I couldn't remember where to find contact person for particular mirror, but www.de.debian.org has problems with content negotiation. I've set content negotiation to accept primary finnish and secondary english. This works for other web sites (such as www.debian.org), but at de mirror content

Re: content negotiation problems?

* Reinier van Kleij [EMAIL PROTECTED] [2003-11-27 11:19]: i navigating the debian website in english but a lot of links give back pages in norwegian! even the report bug page (http://www.debian.org/Bugs/Reporting), that's why i use this email to report the bug... Due to a server compromise

content negotiation problems?

dear maintainer, i navigating the debian website in english but a lot of links give back pages in norwegian! even the report bug page (http://www.debian.org/Bugs/Reporting), that's why i use this email to report the bug... some of the pages that are in norwegian:

Re: content negotiation

with the benefit of content-negotiation while the later requires to link just to foo. The former would e.g. allow files with basically the same name but different content type (like, foo.html vs. foo.png), the later unfortunately doesn't allow this posibility. But appart from that shortcome

content negotiation

Hello. I'm a member of Debian User Group Bulgaria, and we're currently trying to resolve a content_negotiation problem with our mirror (www.bg.debian.org), which appears to be servering without considering browsers preferences. The apache configuration seems absolutly ok to us, but a strange

Content negotiation for slovene doesn't work

We're very happy to see the slovene version of the pages on-line. Looks great. But there seems to be a problem with content negotiation for slovene. There probably needs to be a line containing AddLanguage sl .sl in the apache config file. z.

Re: Content negotiation for slovene doesn't work

On Fri, Jan 31, 2003 at 06:37:30PM +0100, Zoran Obradovic wrote: We're very happy to see the slovene version of the pages on-line. Looks great. But there seems to be a problem with content negotiation for slovene. There probably needs to be a line containing AddLanguage sl .sl

Content Negotiation Konqueror

Hi, in http://www.debian.org/intro/cn.html Konqueror is not listed. In Konqueror you can set Languages by usually editing: ~/.kde/share/config/kio_httprc and adding an option like this: Languages=es,en,fr More info here: http://dot.kde.org/1001290684/1001334187/ Javier Gómez Sierras

Bug#157734: request to support a wee bit of guesswork in content negotiation

Package: apache Severity: wishlist Version: 1.3.* Hi, When a user requests en-us, en-gb, en-au, en-ca or some other variant of en, and Apache can't find a file in that variant of English, it doesn't try simply en, but continues parsing the Accept-Language list. For example: % wget -q

Bug#131978: marked as done (content negotiation link in devel/website/translating)

Your message dated Sun, 3 Feb 2002 21:39:19 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#131978: content negotiation link in devel/website/translating has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

content negotiation on debian

Hi, Just curious how debian web pages does content negotiation for language. As I see some php source for html pages, links like index.en.html exists. This lookd like include index.$language_preferences[$i].php; trick. On the other hand, there is httpd.conf -- Apache HTTP server configuration

Re: content negotiation on debian

On Sat, Feb 02, 2002 at 01:02:50AM -0800, Osamu Aoki wrote: Just curious how debian web pages does content negotiation for language. Please see http://www.jp.debian.org/devel/website/content_negotiation -- 2. That which causes joy or happiness.

Bug#131978: content negotiation link in devel/website/translating

Package: www.debian.org Severity: minor In the lower section of Linkname: Translating Debian web pages URL: http://www.debian.org/devel/website/translating Date: Sat, 02 Feb 2002 16:51:02 GMT Last Mod: Mon, 28 Jan 2002 00:51:18 GMT there is a link to the content negotiation

the 'smallest variant' apache content negotiation problem is gone

Hi, I just noticed this in http://www.apache.org/dist/httpd/CHANGES_1.3 [...] Changes with Apache 1.3.21 [...] *) Modified mod_mime and mod_negotiation to prevent mod_negotiation from serving any multiview variant containing one or more 'unknown' filename extensions. In PR #8130,

Content negotiation not working with ISO-8859-15

If I set in Mozilla Language preferences ISO-8859-15 (euro charset) as my prefered charset content-negotiation will not work: Navigator sends: Accept-Charset: ISO-8859-15, utf-8; q=0,667, *; q=0,667 Accept-Language: es, en; q=0,500 Apache sends: English page (used httpush http

Updates to /etc/apache/srm.conf for content negotiation

The following shows all the languages that should currently be listed in /etc/apache/srm.conf for a site serving the Debian web pages. Keeping this list up to date will minimize the number of people that receive the wrong language. If you have any questions, feel free to ask on

Re: country codes and content negotiation

On Fri, 25 Aug 2000, James A. Treacy wrote: This is about as bad as using symlinks. Maybe worse since we can easily automate the symlinks during the build and messing around with a type-map files would be a royal pain. I don't see why. It should be fairly easy to add a type-map entry target

country codes and content negotiation

translations are added. E.g., contact.en.html contact.en-us.html - contact.en.html contact.en-uk.html - contact.en.html contact.html - contact.en.html (this is needed, as it is the default when content negotiation fails) Any other ideas? -- James (Jay

Bug#61889: marked as done (www.debian.org: www.dk.debian.org does no longer support content negotiation)

:51 - Received: by peter.intern.opera.no (Postfix, from userid 1000) id 1F047BA806; Thu, 6 Apr 2000 09:42:56 +0200 (CEST) From: [EMAIL PROTECTED] Subject: www.debian.org: www.dk.debian.org does no longer support content negotiation To: [EMAIL PROTECTED] X-Mailer: bug 3.2.10 Message-Id

Bug#61889: www.debian.org: www.dk.debian.org does no longer support content negotiation

Package: www.debian.org Version: 2406 Severity: normal For some reason, www.dk.debian.org has dropped content negotiation, and does only serve English pages by default. Also, internal links no longer work, since it does not understand to complete the URLs by adding .xx.html

No content negotiation in releases/stable

While accessing http://www.debian.org/releases/stable/i386/install I received the english version of the manual, instead of the spanish one which is also available (in install.es.html). It seems that content negotiation is not working in this directory ¿any idea? Regards

Bug#37870: marked as done (www.debian.org: Content negotiation for Danish fubar'ed)

Your message dated Sat, 16 Oct 1999 00:00:45 -0400 with message-id [EMAIL PROTECTED] and subject line Content negotiation for Danish fubar'ed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

finally some action on the content negotiation problems with apache

After months with no response, I finally got mail from someone at apache about the bug I filed regarding problems with content negotiation. mod_negotiation was updated and extended for our forthcoming 1.3.4 release. Additionally a DefaultLanguage directive has been added to Apache

Re: finally some action on the content negotiation problems with apache

On Tue, Dec 29, 1998 at 10:55:48PM -0500, James A. Treacy wrote: After months with no response, I finally got mail from someone at apache about the bug I filed regarding problems with content negotiation. What problem are you talking about? -- Mike

Re: finally some action on the content negotiation problems with apache

On Wed, Dec 30, 1998 at 11:41:58AM +0300, Michael Sobolev wrote: On Tue, Dec 29, 1998 at 10:55:48PM -0500, James A. Treacy wrote: After months with no response, I finally got mail from someone at apache about the bug I filed regarding problems with content negotiation. What problem are you

important: file names and content negotiation

This is something people need to consider when setting up web pages when content negotiation is enabled. It is important enough that we should switch the was we name our files. You need to be careful when there are multiple files with the same base and different mime types. This is because

RE: important: file names and content negotiation

-BEGIN PGP SIGNED MESSAGE- Fine with me... it's even suggested this way in the apache docs... On 06-Nov-98 James A. Treacy wrote: Does anyone have any objections to my changing all the files created by wml to be of the form file.lang.html?

Re: important: file names and content negotiation

I should have mentioned that I'll wait until the translations have all converted to the new sytle. That way all I have to do is to go into each language directory, make some changes in Make.common and remake all the pages. Everything converted in one fell swoop. Jay Treacy

Content negotiation and expires..

For some oddball reason I suspect that content negotiation or some such is causing apache to insert an expires immediately header in the output.. Is this really necessary?? It makes the page uncachable. Jason

Re: Content negotiation and expires..

On Wed, Oct 14, 1998 at 06:39:38PM -0600, Jason Gunthorpe wrote: On Thu, 15 Oct 1998, Martin Schulze wrote: Perhaps the reason is that proxies don't care about the accepted languages? Hrm.. Sounds like a problem with the http spec.. It doesn't seem like it is that simple. If the proxie

Re: Content Negotiation in Netscape 3.04

Reading app-default file of Netscape 3.04 I found: ! You can ask HTTP (Web) servers for documents in your preferred language ! by setting the Accept-Language header. It is a comma-separated list of ! languages or language/region pairs. For example, if you would prefer to ! see documents in

Content negotiation in MSIE

Jay: | Now all we need is for someone to write in with directions for doing | this for IE. Any IE users out there (who are willing to admit it)? I have been informed that it is (kind of) impossible to change the preferred language in IE. The only solution is to install a WinXX localised to your

Re: Content Negotiation in Netscape 3.04

Since you might appreciate this :) Preferred Languaje in linx # PREFERRED_LANGUAGE is the language in MIME notation (e.g., en, # fr) which will be indicated by Lynx in its Accept-Language headers # as the preferred language. If available, the document will be # transmitted in that

Content Negotiation in Netscape 3.04

Reading app-default file of Netscape 3.04 I found: ! You can ask HTTP (Web) servers for documents in your preferred language ! by setting the Accept-Language header. It is a comma-separated list of ! languages or language/region pairs. For example, if you would prefer to ! see documents in

Re: Current status of content negotiation

Hi! Hmmm - what have i to do in my apache configuration ? As an example, this is what I have at home in my access.conf Directory /home/treacy/public_html Options Multiviews /Directory That doesnt work - IMHO, because it doesnt follow the Symbolic-Links (for example to the

Re: Current status of content negotiation

Hi! James A.Treacy [EMAIL PROTECTED] wrote: www.us.debian.org not working. Mike told me he set it up, but I just checked and it doesn't appear to work. I didn't have any way to test it. What should I look at to know if it is working? Easy. Try

Current status of content negotiation

How's the current status of content negotiation for the web pages? Debian JP has translated some of the important pages. But neither completed nor released yet. If someone is actually working, I'll ask some volunteers to make JP version up-to-date so that we can release them to the public

Re: Current status of content negotiation

Georg Hitsch wrote: Hmmm - what have i to do in my apache configuration ? As an example, this is what I have at home in my access.conf Directory /home/treacy/public_html Options Multiviews /Directory Just change the directory to the one containing the web pages. It might be necessary

Re: content negotiation for language in web pages

As I suspected when I started this discussion about content negotiation, it is not proving easy to get all the mirrors to switch to using it. It isn't that anyone has refused, it's just that I've only received 3 responses so far and there are 9 mirrors. As it's been almost a week, I'll send more

Re: content negotiation for language in web pages

On Wed, Feb 04, 1998 at 03:11:54PM -0500, James A.Treacy wrote: As I suspected when I started this discussion about content negotiation, it is not proving easy to get all the mirrors to switch to using it. It isn't that anyone has refused, it's just that I've only received 3 responses so far

Re: content negotiation for language in web pages

I am somehow reluctant to believe that CN will bring that much trouble for anyone. We are propably ignoring anyone who doesn't run apache, but that's the minority;) I don't think anyone will object. It's simply getting their attention long enough to get them to make the

Re: content negotiation for language in web pages

There are some people who feel content negotiation should be used for every page (I'm not sure why. Once CN has you using your preferred language, what difference does it make). I'd like their comments on this scheme (repeated below). It should be used for every page. A WWW site

Re: content negotiation for language in web pages

Hi, James == James A Treacy [EMAIL PROTECTED] writes: James The big problem with this is that it all hinges on every server James supporting content negotiation (CN from here on in). We don't James control the mirrors so it's a big problem. Without content James negotiation, you run

Re: content negotiation for language in web pages

Pardon me for being dense, but it is not any worse than the current situation, is it? I mean, we have the default language at the moment. Though we can't mandate content negotiation on mirror servers, we can suggest that they do so; don't most modern servers support CN quite easily

Re: content negotiation for language in web pages

Aaargh. This content negotiation (CN) has some annoying quirks. After re-reading the apache manual it appears we don't have a lot of choice. from the apache manual: The effect of MultiViews is as follows: if the server receives a request for /some/dir/foo, if /some/dir has MultiViews enabled

Re: content negotiation for language in web pages

On Fri, Jan 30, 1998 at 01:12:06AM -0500, James A.Treacy wrote: This makes it quite difficult to have pages that work with both servers that do and do not support CN. Pages can do the following: 1. pages reference foo. Works great on a CN server. Doesn't work at all on a non-CN server.

Re: content negotiation for language in web pages

On Fri, Jan 30, 1998 at 01:12:06AM -0500, James A.Treacy wrote: Aaargh. This content negotiation (CN) has some annoying quirks. After re-reading the apache manual it appears we don't have a lot of choice. Don't give up hope yet. How about creating type-maps for all the files

Re: content negotiation for language in web pages

side, all would be swell with urls referencing just foo -- but then again it would break non-CN mirrors. This is getting ugly. I'll do some testing with .html.langs tomorrow. Maybe something is possible.. There are some people who feel content negotiation

Re: content negotiation for language in web pages

On Thu, Jan 29, 1998 at 02:23:20PM -0500, James A.Treacy wrote: 3. Similar to 2, but each language references the pages in its language, e.g. index.html.de would reference vendors.html.de . At the main page the user would get a language (either by content negotiation

Re: content negotiation for language in web pages

. That way, mirrors will pick up all the .html.langs and _also_ .html (the English version). 1. If a user references .html.lang, all will work as planned. 2. If he references .html, and the mirror does content-negotiation, he will get the language he wants