Re: Iceweasel uses wrong charset

2016-05-13 Thread Vincent Lefevre
On 2016-05-11 12:10:25 +0200, to...@tuxteam.de wrote: > This is happening only on local files? Perhaps FF is expecting that > brain damaged byte order mark to recognize the file as UTF-8? I reported a bug about that in the past: https://bugzilla.mozilla.org/show_bug.cgi?id=1071816 -- Vincent

Re: Iceweasel uses wrong charset

2016-05-13 Thread Vincent Lefevre
On 2016-05-11 11:55:33 +0200, Frédéric Marchal wrote: > On Wednesday 11 May 2016 11:23:56 err...@free.fr wrote: > > Why unicode like utf-8 is not default value in iceweasel ? > > > > (it's time, we are in 2016 now) > > Unicode is the default in firefox/iceweasel. No, the default is windows-1

Re: [partially solved]Re: Iceweasel uses wrong charset

2016-05-12 Thread Rob van der Putten
Hi there Michael Lange wrote: On Wed, 11 May 2016 18:43:50 +0200 Michael Lange wrote: According to this (yet probably dated ) page: http://www-archive.mozilla.org/projects/intl/chardet.html universal_charset_detector might help if it were enabled by default. Just looked at the above p

Re: [partially solved]Re: Iceweasel uses wrong charset

2016-05-11 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 11, 2016 at 06:55:31PM +0200, Michael Lange wrote: > On Wed, 11 May 2016 18:43:50 +0200 > Michael Lange wrote: > > > According to this (yet probably dated ) page: > >http://www-archive.mozilla.org/projects/intl/chardet.html > > univer

[partially solved]Re: Iceweasel uses wrong charset

2016-05-11 Thread Michael Lange
On Wed, 11 May 2016 18:43:50 +0200 Michael Lange wrote: > According to this (yet probably dated ) page: >http://www-archive.mozilla.org/projects/intl/chardet.html > universal_charset_detector might help if it were enabled by default. Just looked at the above page again, and noticed that the

Re: Iceweasel uses wrong charset

2016-05-11 Thread Michael Lange
On Wed, 11 May 2016 16:28:03 +0200 wrote: > There's some hope. Have a look at the intl subcategory in about:config > [1] (especially at intl.locale.matchOS and/or general.useragent.locale), > but also intl.accept.charsets (it is a list, might be prioritized). > I never tested this before, but a

Re: Iceweasel uses wrong charset

2016-05-11 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 11, 2016 at 03:14:39PM +0200, Rob van der Putten wrote: > Hi there > > > to...@tuxteam.de wrote: > > >On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote: [...] > >That's because it has been enshrined by the Unicode Cons

Re: Iceweasel uses wrong charset

2016-05-11 Thread Rob van der Putten
Hi there to...@tuxteam.de wrote: On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote: I actually thought about this. But it just seems crude; vim some.txt ^vufeff :wq It does work though. But I want UTF-8 without a BOM. It is, after all, the default locale. Everyone wan

Re: Iceweasel uses wrong charset

2016-05-11 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote: > Hi there > > > to...@tuxteam.de wrote: [BOM BOM hurrah!] > I actually thought about this. But it just seems crude; > > vim some.txt > ^vufeff > :wq > > It does work though. > B

Re: Iceweasel uses wrong charset

2016-05-11 Thread Rob van der Putten
Hi there to...@tuxteam.de wrote: This is happening only on local files? Perhaps FF is expecting that brain damaged byte order mark to recognize the file as UTF-8? When the data come over HTTP there are other out-of-band hints to communicate the encoding. Try editing the file with some Micros

Re: Iceweasel uses wrong charset

2016-05-11 Thread Richard Owlett
On 5/11/2016 4:58 AM, Rob van der Putten wrote: Hi there Michael Lange wrote: you can try the following: type "about:config" into iceweasel's address bar (without the quotes of course), then type "charset" into the config's search bar. Several options should appear. Look for the key "intl.ch

Re: Iceweasel uses wrong charset

2016-05-11 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 11, 2016 at 11:58:31AM +0200, Rob van der Putten wrote: > Hi there > > > Michael Lange wrote: > > >you can try the following: > > > >type "about:config" into iceweasel's address bar (without the quotes of > >course), then type "charset"

Re: Iceweasel uses wrong charset

2016-05-11 Thread Rob van der Putten
Hi there Michael Lange wrote: you can try the following: type "about:config" into iceweasel's address bar (without the quotes of course), then type "charset" into the config's search bar. Several options should appear. Look for the key "intl.charset.default". Is the value already set to "UTF-

Re: Iceweasel uses wrong charset

2016-05-11 Thread Frédéric Marchal
On Wednesday 11 May 2016 11:23:56 err...@free.fr wrote: > Why unicode like utf-8 is not default value in iceweasel ? > > (it's time, we are in 2016 now) Unicode is the default in firefox/iceweasel. See https://developer.mozilla.org/en-US/docs/Web/Guide/Localizations_and_character_encodings

Re: Iceweasel uses wrong charset

2016-05-11 Thread err404
Why unicode like utf-8 is not default value in iceweasel ? (it's time, we are in 2016 now) signature.asc Description: OpenPGP digital signature

Re: Iceweasel uses wrong charset

2016-05-11 Thread Michael Lange
Hi, On Wed, 11 May 2016 10:55:54 +0200 Rob van der Putten wrote: > Hi there > > > UTF-8 is my default locale. So obviously text files are UTF-8 as well. > So why does iceweasel insist that these are windows-1252? How do I fix > this? you can try the following: type "about:config" into icewea

Re: Iceweasel uses wrong charset

2016-05-11 Thread Frédéric Marchal
On Wednesday 11 May 2016 10:55:54 Rob van der Putten wrote: > Hi there > > > UTF-8 is my default locale. So obviously text files are UTF-8 as well. > So why does iceweasel insist that these are windows-1252? How do I fix this? In about:config, have you changed any of intl.charset.detector or in

Iceweasel uses wrong charset

2016-05-11 Thread Rob van der Putten
Hi there UTF-8 is my default locale. So obviously text files are UTF-8 as well. So why does iceweasel insist that these are windows-1252? How do I fix this? Regards, Rob