mandag 8. desember 2003, 19:25, skrev Kurt Gramlich:
dear friends
i am missing
developer.skolelinux.no/security.html.no
could somebody translate the english version to norway?
Regards
Kurt
Has been done today. Twice over!
I did security.html.nb, Tommy Gildseth made security.html.no. (I believe mine is better.) Regarding the .no postfix, how does this translate to Norwegian Bokmål and Nynorsk? I believe we should rather use .nb and .nn, but might be wrong. What about the browsers set to only accept .no?
Harald Thingelstad wrote:
mandag 8. desember 2003, 19:25, skrev Kurt Gramlich:
dear friends
i am missing
developer.skolelinux.no/security.html.no
could somebody translate the english version to norway?
Regards
Kurt
Has been done today. Twice over!
I did security.html.nb, Tommy Gildseth made security.html.no. (I believe mine is better.)
If you want to use Unicode(UTF-8), you have to specify this in the HTML document, as a <meta> element, or have the server send the correct content-type header. If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Tommy
tirsdag 9. desember 2003, 17:03, skrev Tommy Gildseth:
If you want to use Unicode(UTF-8), you have to specify this in the HTML document, as a <meta> element, or have the server send the correct content-type header. If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Tommy
Which leads us to our next question: With Apache overriding the document settings (as has been discussed) I see three options: 1) Have Apache override everything to iso8859-1 (as I've heard this is for now), we need every document to be up to that standard. As Debian and other distros end up with UTF-8 as standard (this is entirely possible with Debian testing right now, as you see), iso8859-1 everywhere will end up as a hassle. We've got only Sámi needing UTF-8 right now, but expect that to change with internationalization. 2) Have Apache override everything to UTF-8. Move the hassle to current users. Problem decreases with time, but will be a big one right now. 3) Turn off that default setting in Apache, and have every page to set its own charset.
Are things really this bad, or is there some easier way out.
Harald
On Tue, Dec 09, 2003 at 05:03:39PM +0100, Tommy Gildseth wrote:
If you want to use Unicode(UTF-8), you have to specify this in the HTML document, as a <meta> element, or have the server send the correct content-type header. If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Are you sure? I believe the browser will always follow the meta tags of the docyment, if present, as this is a way to override the system wide settings of the server. Would be silly the other way around (- or give less capabilities), and I believe this is not well defined in a RFC, while meta tags are well defined.
best regards Keld
Keld Jørn Simonsen wrote:
On Tue, Dec 09, 2003 at 05:03:39PM +0100, Tommy Gildseth wrote:
If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Are you sure? I believe the browser will always follow the meta tags of the docyment, if present, as this is a way to override the system wide settings of the server. Would be silly the other way around (- or give less capabilities), and I believe this is not well defined in a RFC, while meta tags are well defined.
As I said, this is the behaviour I have experienced that Mozilla has. I haven't tested it with other browsers, so I couldn't really tell if the same goes for Opera and IE etc.
Tommy
Wednesday, December 10. b. 2003 23:37, Tommy Gildseth don čállet:
Keld Jørn Simonsen wrote:
On Tue, Dec 09, 2003 at 05:03:39PM +0100, Tommy Gildseth wrote:
If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Are you sure? I believe the browser will always follow the meta tags of the docyment, if present, as this is a way to override the system wide settings of the server. Would be silly the other way around (- or give less capabilities), and I believe this is not well defined in a RFC, while meta tags are well defined.
As I said, this is the behaviour I have experienced that Mozilla has. I haven't tested it with other browsers, so I couldn't really tell if the same goes for Opera and IE etc.
Tommy
I have experienced the same thing. I uploaded some utf-8 pages to d.s.n/ ~albbas/. The pages had the meta-utf-8 thingie defined, but the pages displayed the latin1 version of the utf-8 characters. I tested with mozilla 1.5 and konqueror 3.1.4.
søn, 14.12.2003 kl. 19.58 skrev Børre Gaup:
Wednesday, December 10. b. 2003 23:37, Tommy Gildseth don čállet:
Keld Jørn Simonsen wrote:
On Tue, Dec 09, 2003 at 05:03:39PM +0100, Tommy Gildseth wrote:
If the server already sends ISO-8859-1/15 as the content-type, the browser(at least Mozilla) will prefer this over what is specified in the HTML document.
Are you sure? I believe the browser will always follow the meta tags of the docyment, if present, as this is a way to override the system wide settings of the server. Would be silly the other way around (- or give less capabilities), and I believe this is not well defined in a RFC, while meta tags are well defined.
As I said, this is the behaviour I have experienced that Mozilla has. I haven't tested it with other browsers, so I couldn't really tell if the same goes for Opera and IE etc.
This is what you can expect, for it is indeed what the standards mandate. Which means setting the encoding server-wide is not such a good idea. After all, latin-1 is supposed to be assumed when no encoding is specified. For us, latin-1 is an acceptable _fallback_, but we want utf-8 on many of our pages.
I have experienced the same thing. I uploaded some utf-8 pages to d.s.n/ ~albbas/. The pages had the meta-utf-8 thingie defined, but the pages displayed the latin1 version of the utf-8 characters. I tested with mozilla 1.5 and konqueror 3.1.4.
Ask "drift" to disable the default encoding in httpd.conf. It is not needed, and causes a lot of trouble.
Tysdag 9. desember 2003 14:43 skreiv Harald Thingelstad:
Regarding the .no postfix, how does this translate to Norwegian Bokmål and Nynorsk? I believe we should rather use .nb and .nn, but might be wrong. What about the browsers set to only accept .no?
It's possible to make .nb (or .nn) an alias for .no, using the AddLanguage directive in httpd.conf. In the VirtualHost section for i18n.skulelinux.no, we use "AddLanguage no .nn". The result is that browsers requesting .no get .nn instead.
It would probably be a good idea to use this technique throughout the site.
Regards, Gaute Hvoslef Kvalnes