lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Unexpected character in file history


From: Greg Chicares
Subject: Re: [lmi] Unexpected character in file history
Date: Mon, 17 Oct 2016 16:13:52 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.3.0

On 2016-10-15 12:20, Vadim Zeitlin wrote:
> On Sat, 15 Oct 2016 00:04:25 +0000 Greg Chicares <address@hidden> wrote:
> 
> GC> [I have little to add (at the bottom), but the entire original message
> GC> is relevant context, so I haven't trimmed it.]
> GC> 
> GC> On 2016-06-15 21:16, Greg Chicares wrote:
> GC> > On 2016-06-15 18:46, Vadim Zeitlin wrote:
> GC> >> On Tue, 14 Jun 2016 21:38:40 +0000 Greg Chicares <address@hidden> 
> wrote:
> GC> >> 
> GC> >> GC> On 2016-06-14 20:39, Vadim Zeitlin wrote:
> GC> >> GC> > On Mon, 13 Jun 2016 13:39:29 +0000 Greg Chicares 
> <address@hidden> wrote:
> GC> >> GC> > 
> GC> >> GC> > GC> When I pull down the "File" menu, history now looks like 
> this:
> GC> >> GC> > GC>   1 □quote.cns
> GC> >> GC> > GC>   2 □quote2.cns
> GC> >> GC> > GC> I'm not sure the square character is unicode "WHITE SQUARE"
> GC> > 
> GC> > [...it's actually 'LEFT-TO-RIGHT EMBEDDING' (U+202A)...]
> ...
> GC> I see the same thing using 'wine'
> 
>  This doesn't really surprise me, I know that older versions of Windows (up
> to XP SP2) didn't handle this character correctly/specially and it's not
> unreasonable to suppose that Wine code hasn't been updated yet. Of course,
> with Wine being open source, I could make sure of it by examining its
> sources and, maybe, even fix the problem -- but I'm still not sure if it's
> worth doing it.

No, I don't think it's worthwhile.

BTW, I experimented with using 'winecfg' to change the "Windows Version"
from xp to 7 and 8. They all display U+202A in the file history. With xp,
lmi's input dialog is rendered correctly; with 7 or 8, it is not (it's
maximized by default, but the pushbuttons at the bottom are truncated,
and resizing the tabbed dialog doesn't make them visible). Apparently
there's some low-hanging fruit, which we could pluck if fixing 'wine'
were our goal; but that cannot be our goal here and now.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]