On Thu, Jan 16, 2014 at 7:28 PM, ISHIKAWA,chiaki ishik...@yk.rim.or.jp 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
On Fri, Jan 17, 2014 at 11:39 AM, Henri Sivonen hsivo...@hsivonen.fi 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
(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
On 2014-01-17 4:39 AM, Henri Sivonen wrote:
On Thu, Jan 16, 2014 at 7:28 PM, ISHIKAWA,chiaki ishik...@yk.rim.or.jp 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
(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
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 makes
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 might
that the time was ripe by now to go over to using UTF-8.
Yes, but now I can't locate the code that I thought I was reading, so
let's ignore this aspect.
* Do we (or gtk) really still support non-UTF-8 platform charset
values on *nix? (MXR turns up so little that it makes me wonder
non-UTF-8 support might
On 11/26/2013 6:37 AM, Henri Sivonen wrote:
On Mon, Nov 25, 2013 at 6:03 PM, Yuri Dario mc6...@mclink.it 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
charset when
saving as HTML Page, complete? For Save As Text I would have thought
that the time was ripe by now to go over to using UTF-8.
* Do we (or gtk) really still support non-UTF-8 platform charset
values on *nix? (MXR turns up so little that it makes me wonder
non-UTF-8 support might have
reserialization like on Mac?
* Is the OS/2 port still alive and supported as an in-tree port? The
latest releases I've seen are 10.x ESR.
* Do we (or gtk) really still support non-UTF-8 platform charset
values on *nix? (MXR turns up so little that it makes me wonder
non-UTF-8 support might have
On Tue, Nov 26, 2013 at 12:46 AM, Henri Sivonen hsivo...@hsivonen.fiwrote:
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
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
charset when
saving as HTML Page, complete? For Save As Text I would have thought
that the time was ripe by now to go over to using UTF-8.
* Do we (or gtk) really still support non-UTF-8 platform charset
values on *nix? (MXR turns up so little that it makes me wonder
non-UTF-8 support might have
14 matches
Mail list logo
