Re: Support for non-UTF-8 platform charset

2014-01-17 Thread Zack Weinberg
On 2014-01-17 4:39 AM, Henri Sivonen wrote: On Thu, Jan 16, 2014 at 7:28 PM, ISHIKAWA,chiaki wrote: I found that TB generates during its execution UTF-8 file path name strings WITHOUT BOM and still contain supposedly a valid UTF8 path name. I'm pretty sure that file system paths on Linux are

Re: Support for non-UTF-8 platform charset

2014-01-17 Thread ISHIKAWA,chiaki
(Sorry for top-posting.) Dear Henri Sivonen, Thank you for lucid explanation. I am trying to understand the details and am pondering inserting a few more dumps to figure out the answers to your newly raised questions. I will report my finding RSN. Thank you again. Your comment clears up a lot

Re: Support for non-UTF-8 platform charset

2014-01-17 Thread Henri Sivonen
On Fri, Jan 17, 2014 at 11:39 AM, Henri Sivonen wrote: > All this use of iconv is sad, yes. I wouldn't be opposed to dropping > the iconv code paths and using the OS X / Android code (that assumes > that operating system's file system APIs always take UTF-8) for all > *nix platforms. Filed: https

Re: Support for non-UTF-8 platform charset

2014-01-17 Thread Henri Sivonen
On Thu, Jan 16, 2014 at 7:28 PM, ISHIKAWA,chiaki wrote: > (2014/01/16 12:22), Zack Weinberg wrote: >> >> On 2013-11-26 5:40 AM, Neil wrote: >>> >>> Henri Sivonen wrote: >>> On Windows, do we really need to pay homage to the pre-NT legacy when doing Save As? How about we just use UTF-8 fo

Re: Support for non-UTF-8 platform charset

2014-01-16 Thread ISHIKAWA,chiaki
(2014/01/16 12:22), Zack Weinberg wrote: On 2013-11-26 5:40 AM, Neil wrote: Henri Sivonen wrote: On Windows, do we really need to pay homage to the pre-NT legacy when doing Save As? How about we just use UTF-8 for "HTML Page, complete" reserialization like on Mac? You'll need a BOM, of cour

Re: Support for non-UTF-8 platform charset

2014-01-15 Thread Zack Weinberg
On 2013-11-26 5:40 AM, Neil wrote: Henri Sivonen wrote: On Windows, do we really need to pay homage to the pre-NT legacy when doing Save As? How about we just use UTF-8 for "HTML Page, complete" reserialization like on Mac? You'll need a BOM, of course. (MXR turns up so little that it make

Re: Support for non-UTF-8 platform charset

2013-11-26 Thread Simon Montagu
On 11/25/2013 01:46 PM, Henri Sivonen wrote: > Questions: > > * On Windows, do we really need to pay homage to the pre-NT legacy > when doing Save As? How about we just use UTF-8 for "HTML Page, > complete" reserialization like on Mac? Do you mean Save As Text? Do we really use the platform char

Re: Support for non-UTF-8 platform charset

2013-11-26 Thread Ted Mielczarek
On 11/26/2013 6:37 AM, Henri Sivonen wrote: > On Mon, Nov 25, 2013 at 6:03 PM, Yuri Dario wrote: >> the OS/2 port is alive, we already have a beta release for 17.x and a >> more current version will follow. > Does this work all happen in forked repositories, such as > https://github.com/bitwisewor

Re: Support for non-UTF-8 platform charset

2013-11-26 Thread Henri Sivonen
On Mon, Nov 25, 2013 at 7:47 PM, Simon Montagu wrote: (Replying to @smontagu.org, instead of netscape.com just in case.) > Do you mean Save As Text? Do we really use the platform charset when > saving as HTML Page, complete? For Save As Text I would have thought > that the time was ripe by now t

Re: Support for non-UTF-8 platform charset

2013-11-26 Thread Neil
Henri Sivonen wrote: On Windows, do we really need to pay homage to the pre-NT legacy when doing Save As? How about we just use UTF-8 for "HTML Page, complete" reserialization like on Mac? You'll need a BOM, of course. (MXR turns up so little that it makes me wonder non-UTF-8 support migh

Re: Support for non-UTF-8 platform charset

2013-11-25 Thread Simon Montagu
On 11/25/2013 01:46 PM, Henri Sivonen wrote: > Questions: > > * On Windows, do we really need to pay homage to the pre-NT legacy > when doing Save As? How about we just use UTF-8 for "HTML Page, > complete" reserialization like on Mac? Do you mean Save As Text? Do we really use the platform char

Re: Support for non-UTF-8 platform charset

2013-11-25 Thread Karl Tomlinson
Henri Sivonen writes: > On *nix platforms, it's not clear to me what exactly the platform > charset is used for these days. An MXR search turns up surprisingly > little. > * Do we (or gtk) really still support non-UTF-8 platform charset > values on *nix? (MXR turns up so little that it makes me

Re: Support for non-UTF-8 platform charset

2013-11-25 Thread Yuri Dario
Hi, > * Is the OS/2 port still alive and supported as an in-tree port? The > latest releases I've seen are 10.x ESR. the OS/2 port is alive, we already have a beta release for 17.x and a more current version will follow. -- Bye, Yuri Dario /* * OS/2 open source software * http://

Re: Support for non-UTF-8 platform charset

2013-11-25 Thread Robert O'Callahan
On Tue, Nov 26, 2013 at 12:46 AM, Henri Sivonen wrote: > We have a concept of platform charset that goes back to pre-NT > Windows, Mac OS Classic, OS/2 and pre-UTF-8 *nix platforms. This > concept gets in the way of doCOMtaminating old code to use only new > facilities in mozilla::dom::EncodingUti

Support for non-UTF-8 platform charset

2013-11-25 Thread Henri Sivonen
We have a concept of platform charset that goes back to pre-NT Windows, Mac OS Classic, OS/2 and pre-UTF-8 *nix platforms. This concept gets in the way of doCOMtaminating old code to use only new facilities in mozilla::dom::EncodingUtils. These days, on Mac and Android, we say the platform charset