Open GoogleCodeExporter opened 9 years ago
That looks pretty good, but please identify the specific wine bug
report for each applied workaround, and use the w_workaround_wine_bug
function to announce it, e.g.
if w_workaround_wine_bug 29636 "Installing native riched20 to work around crash bug"
then
w_call riched20
fi
Original comment by daniel.r...@gmail.com
on 17 Sep 2013 at 1:58
Thanks, but how can I find these bug ID?
Original comment by hillwood...@gmail.com
on 17 Sep 2013 at 3:05
Try the recipe on a clean wineprefix without any of those workarounds.
If it works, you're done.
Otherwise, if it crashes or otherwise misbehaves, search
http://bugs.winehq.org/ for the symptom.
If you find it, great; otherwise file a wine bug, and say which winetrick works
around it.
Do that workaround first, with that bug number.
Repeat until the app is working.
Original comment by daniel.r...@gmail.com
on 17 Sep 2013 at 3:13
Update patch
Original comment by hillwood...@gmail.com
on 17 Sep 2013 at 3:52
Attachments:
That's much better. I'll clean up the remaining indent problems, test, and
commit tonight.
I may also try to find two or three word descriptions (e.g. "chinese chat
program")
for those who are unfamiliar with the apps, too.
Original comment by daniel.r...@gmail.com
on 17 Sep 2013 at 4:09
TM 2009 and 2013 are also chat program.THS(同花顺) is a stock market program.
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 1:32
The attached patch fixes some whitespace problems, uses lowercase letters for
verb names, and corrects the bug number for mfc42.
Do all of these apps work in Wine? Which version did you test with?
QQGame seems to crash at the end of install, and maybe whenever starting
up any app in that bottle, with wine-1.7.1-158.
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 3:51
Attachments:
QQGame works fine in wine 1.7.1. I am sorry that I don't install old version in
my system, so i don't know the status that QQGame works in old wine. QQ and TM
can work in 1.6 version and higner, THS can work in 1.5 version and higner. I
didn't test THS in 1.4 version.
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 1:31
Please not set sha1sum check for THS! The install file would be updated every
day! The sha1sum check would cause install error.
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 2:15
OK, here's a draft that doesn't check the sum for THS.
When I run the THS installer, I get garbage instead of characters
in the first screen of the installer. What's the best way
to see the real characters there? I tried a few things, but nothing helped.
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 3:06
Attachments:
Do you mean there are many unrecognized characters in first screen? Oh, it must
copy simsum.ttc from windows to install in system to fix. This font cannot be
install by winetricks, but most Chinese users know how to do. Need i mail
this font to you?
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 3:32
No, thanks. I can download it myself. But it's not a free font
( http://www.microsoft.com/typography/fonts/font.aspx?FMID=1646 ).
Is there a way to display that text without buying or pirating a font?
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 3:46
I asked the author of http://wiki.winehq.org/FontReplacements to comment.
(I did try the patch mentioned there, without success.
I also tried copying simsun.ttc into ~/.fonts; that didn't help, either.)
https://github.com/bhuztez/configs-and-scripts/blob/master/fedora-wine-qq.sh
is an interesting script; it's the first one I've seen in a while that sources
winetricks. It kind of adds a verb for installing QQ2009, including
using simsun.ttc. Doesn't work now, since it was written for an old winetricks,
but I updated its load_fakesimsun... no joy.
At this point I'd settle for *any* way of seeing the text on the first screen
of any of these installers. Is there a simple recipe I can follow somewhere?
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 4:08
You can try to import this file to regedit, it work fine in openSUSE.
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 4:23
Attachments:
Didn't seem to help. WINEDEBUG=+fonts shows that my copied simsun.ttc is
found at least once:
trace:font:freetype_SelectFont Chosen: L"SimSun" L"Regular"
(L"/home/dank/.local/share/wineprefixes/ths/dosdevices/c:/windows/Fonts/simsun.t
tc"/(nil):0)
but I'm still not seeing chinese.
Maybe I should take a step backwards and try a very simple test.
In a clean wineprefix, what is the recipe for seeing Chinese text
in the File menu of wine's notepad? I tried
rm -rf ~/.wine
LANG=zh_CN wine notepad
but still saw English.
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 4:31
Why do you try to switch your account language to Chinese?
Original comment by hillwood...@gmail.com
on 18 Sep 2013 at 4:40
I'm just looking for the simplest way to get Wine to display chinese text.
Original comment by daniel.r...@gmail.com
on 18 Sep 2013 at 6:04
Why not just w_call cjkfonts ?
I've added a patch for it, and it works for me
(but there is a small problem: all fonts would looks the same)
Original comment by litimetal
on 19 Sep 2013 at 12:06
rm -rf ~/.wine
winetricks cjkfonts
wine notepad
does not show me chinese menus, nor does it let me paste chinese text.
Original comment by daniel.r...@gmail.com
on 19 Sep 2013 at 12:09
Interesting.
rm -rf ~/.wine
winetricks cjkfonts
wine notepad
The menu is in English, but I can type/paste Chinese.
Then LANG=zh_CN notepad
and menu became Chinese
Original comment by litimetal
on 19 Sep 2013 at 12:47
My system is Ubuntu 13.04, installed with English as the system language,
and I'm using wine built from source on that system.
I may be running into http://bugs.winehq.org/show_bug.cgi?id=30245
What OS and wine are you using? Did you build wine from source yourself,
or are you using a patched version built by someone else?
Original comment by daniel.r...@gmail.com
on 19 Sep 2013 at 2:31
My system is Fedora 19, installed with English
I built my wine from source: wine-1.7.1-208-g10251e5
WINETRICKS_VERSION=20130707
PS My locale:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Original comment by litimetal
on 19 Sep 2013 at 2:37
Garbage is fixed, please try this patch.
Original comment by hillwood...@gmail.com
on 20 Sep 2013 at 2:45
Attachments:
What's your winetricks version? I should have had fixed this problem.
Original comment by litimetal
on 20 Sep 2013 at 2:52
20130707
Original comment by hillwood...@gmail.com
on 20 Sep 2013 at 2:54
But I can't apply your patch, because winetricks has been modified.
I think you'd better go to http://code.google.com/p/winetricks/source/checkout
to get the svn version of winetricks(now is 20130919)
Original comment by litimetal
on 21 Sep 2013 at 1:02
Attachments:
It seem that svn version have fixed this problem.
Original comment by hillwood...@gmail.com
on 21 Sep 2013 at 5:55
Well, let's go back to your patch.
I think you can solve the problem now with 'w_call cjkfont'
Would you please re-send a patch?
To Dan Kegel: You said you can't type Chinese. I think it is another problem
caused by your computer's config. How about open another issue? Or you send me
an e-mail about it?
Original comment by litimetal
on 21 Sep 2013 at 8:48
Patch update.
Original comment by hillwood...@gmail.com
on 21 Sep 2013 at 2:51
Attachments:
With (a slightly corrected version of) Hillwood's latest patch, I can
see the chinese text properly.
I've added qqintl to the list so I can test more easily, too.
I'll commit it soon, just waiting for my QQ registration to come through :-)
Original comment by daniel.r...@gmail.com
on 21 Sep 2013 at 4:14
After testing qqgame for a while, I figured it wasn't stable enough;
it puts up crash dialogs on every start of wine.
Looking at the ths verb, I would like to understand the need for wininet a bit
more.
Looking at the tm2009 verb, I would like to understand the need for ie8 a bit
more.
But the qq2012 verb looks good (after a correction or two), and I added
a qqintl verb (after filing a few bug reports).
I'll attach the remaining draft ths / tm2009 patch for your reference.
Original comment by daniel.r...@gmail.com
on 21 Sep 2013 at 5:50
Committed as r1063
r1063 | daniel.r.kegel | 2013-09-21 10:46:28 -0700 (Sat, 21. Sep 2013) | 1 Zeile
qq2012, qqintl: new verbs (based on patch by Hillwood Yang_
Original comment by daniel.r...@gmail.com
on 21 Sep 2013 at 5:52
I don't suggest to use winegecko instead of ie8 which be auto installed by wine
first start, It could make TM and QQ unstable, TM and QQ would crash while
opening chat window or chat logs. So ie8 is better than winegecko.
Original comment by hillwood...@gmail.com
on 22 Sep 2013 at 1:17
I agree with you.
winetricks ie8 is a good way to workaround bug 29638
I think 'cjkfonts' is necessary for QQIntl, too, as some people may use QQIntl
but communicate in Chinese.
Also, I think 'msxml3' is necessary to workaround bug 33612
Original comment by litimetal
on 22 Sep 2013 at 2:06
I think 'cjkfonts' is not necessary, there is not Chinese interface in QQIntl.
Original comment by hillwood...@gmail.com
on 22 Sep 2013 at 2:23
I'm happy to add ie7 as a workaround, but I need a good repeatable bug first.
I don't think I've seen exactly bug 29638 in qqintl.
But while testing qqintl, I ran into a repeatable crash when clicking the
settings icon. The log looked like http://bugs.winehq.org/show_bug.cgi?id=30083
and ie7 worked around it, so I added this:
+ if w_workaround_wine_bug 30083 "Installing native ie7 to avoid crash in
settings and other dialogs"
+ then
+ w_call ie7
+ fi
to qqintl. (I tend to use ie7 since I suspect, but haven't checked, that ie8
is bigger / fatter / buggier.)
I haven't found a good recipe to make qq2009 crash yet, so I haven't added
a similar workaround for that yet.
I haven't been able to get into a chat group, so I can't reproduce 33612.
I agree that cjkfonts should only be added if the interface needs it.
Original comment by daniel.r...@gmail.com
on 22 Sep 2013 at 2:55
Original issue reported on code.google.com by
hillwood...@gmail.com
on 17 Sep 2013 at 1:47Attachments: