[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mercurial
Subject:    Fwd: A proposal on solve encoding problem on Windows.
From:       Mike Meyer <mwm () mired ! org>
Date:       2011-10-21 16:11:58
Message-ID: CAD=7U2BncByoRAKYTiHMShUJfhsu5XbgNDT06jbJo-EQZmpsgA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Sigh. Not sure this made it to the list, as it only went to the google
groups address, which claims it bounced it. Sorry if you see it twice.


---------- Forwarded message ----------
From: Mike Meyer <mwm@mired.org>
Date: Fri, Oct 21, 2011 at 8:50 AM
Subject: Re: A proposal on solve encoding problem on Windows.
To: mercurial_general@googlegroups.com


On Fri, Oct 21, 2011 at 1:37 AM, Andrey <py4fun@gmail.com> wrote:

> So what happens when I create and check in a file that uses a non-ascii
>> file name encoded in something other than utf8 on a Unix box and you try and
>> check it out on your windows box?
>>
> Your local Mercurial client on your Unix box shall be aware which encoding
> should used for the file
>

Sure, if you change the Unix clients as well, then this isn't a problem. But
the proposal on the table - and the one I was responding to, which you
failed to quote - was that only the Windows behavior be fixed, and that the
behavior on Linux systems *not* change. That behavior is not encoding aware,
which is why the answer to this question is of interest.

I can't see this proposal going forward until this question is answered.

   <mike

[Attachment #5 (text/html)]

Sigh. Not sure this made it to the list, as it only went to the google groups \
address, which claims it bounced it. Sorry if you see it \
twice.<div><br></div><div><br><div class="gmail_quote">---------- Forwarded message \
                ----------<br>
From: <b class="gmail_sendername">Mike Meyer</b> <span dir="ltr">&lt;<a \
href="mailto:mwm@mired.org">mwm@mired.org</a>&gt;</span><br>Date: Fri, Oct 21, 2011 \
                at 8:50 AM<br>Subject: Re: A proposal on solve encoding problem on \
                Windows.<br>
To: <a href="mailto:mercurial_general@googlegroups.com">mercurial_general@googlegroups.com</a><br><br><br>On \
Fri, Oct 21, 2011 at 1:37 AM, Andrey <span dir="ltr">&lt;<a \
href="mailto:py4fun@gmail.com" target="_blank">py4fun@gmail.com</a>&gt;</span> \
wrote:<div class="gmail_quote"> <blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <blockquote class="gmail_quote" \
style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
class="gmail_quote"><div>So what happens when I create and check in a file that uses \
a non-ascii file name encoded in something other than utf8 on a Unix box and you try \
and check it out on your windows box?</div>

</div></blockquote><div>Your local Mercurial client on your Unix box shall be aware \
which encoding should used for the file</div></blockquote><div><br></div><div>Sure, \
if you change the Unix clients as well, then this isn&#39;t a problem. But the \
proposal on the table - and the one I was responding to, which you failed to quote - \
was that only the Windows behavior be fixed, and that the behavior on Linux systems \
*not* change. That behavior is not encoding aware, which is why the answer to this \
question is of interest.</div>

<div><br></div><div>I can&#39;t see this proposal going forward until this question \
is answered.</div><div><br></div><font color="#888888"><div>   &lt;mike</div><div> \
</div></font></div> </div><br></div>



_______________________________________________
Mercurial mailing list
Mercurial@selenic.com
http://selenic.com/mailman/listinfo/mercurial


[prev in list] [next in list] [prev in thread] [next in thread]