mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl and legacy win32 apps through wine
Date: Tue, 17 Nov 2015 16:02:49 -0500	[thread overview]
Message-ID: <20151117210248.GC3818@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151117132115.02be8539@r2lynx>

On Tue, Nov 17, 2015 at 01:21:15PM +0700, Рысь wrote:
> Hello.
> 
> I came to need to run few legacy win32 apps in wine (2d programs of
> specific nature).
> 
> I had built wine myself which links with musl fine.
> 
> These programs are Russian only. They do not have English fallback or
> any other translated versions. Their texts are of cp1251 encoding.
> 
> I unable to read them because they are garbled probably because they
> are converted to utf-8 implicitly. However if I set LC_ALL=ru_RU.UTF-8,
> wine own translation is shown as expected - I see clear Russian
> translation. Only those legacy programs are in trouble.
> 
> Is there a way to tell Wine or to emulate it cp1251 encoding? Maybe I
> could modify Wine somehow to convert texts to proper UTF-8? I did not
> found Wine uses iconv or something like that inside it's source.
> 
> I only need Wine for these few programs. I now running a chroot with
> debian glibc and wine as a temporary solution.

I'm not really familiar with how Wine emulates the Windows locale
system, but if I remember right from when I once used it for QQ (which
needed a legacy Chinese locale), it ties the emulated locale to the
host locale. If so this is of course really problematic since the host
locale on a modern system always uses UTF-8 encoding and legacy
Windows apps never use/expect it. Probably some hack is needed on the
Wine side to work around this but I'm not sure what it would look
like.

Rich


  reply	other threads:[~2015-11-17 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  6:21 Рысь
2015-11-17 21:02 ` Rich Felker [this message]
2015-11-18  2:45   ` Рысь
2015-11-18  6:32     ` Рысь
2015-11-18 16:24       ` Rich Felker
2015-11-18 16:34         ` Рысь

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151117210248.GC3818@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).