Hi. I've recently updated to Suse 9.3, and my OED2 CDROM software no longer works properly under Wine - the dialog and general system text of the application still displays properly, but the application data, the results lists and definition text, doesn't. Essentially, the problem seems to be that Wine seems to think that this kind of text has to be displayed as small caps. The underlying text is actually correct, if I cut and paste it into Notepad, for example, the text capitalisation upper and lower looks fine (apart from special characters such as phonetics, which don't display). In the OED2 app I get small caps for all lower case and empty box characters for what are really capitals, numerics, and punctuation. The app comes with a set of special TTF fonts provided by the OED, and these font sets are being used. It's just that (for example, in the main text) Plantin Small Caps is being used for display by Wine instead of the normal Plantin font(you can tell it is picking the correct font family up from the letter forms displayed). So Wine is finding the fonts installed by the application, and they are all there and readable (I've checked). It just seems to be insisting on using small caps for some reason - the small caps versions of the fonts are in separate files. I've updated Wine to the most recent version (20050419) and the behaviour is the same. I've run winetools and done all the standard setup stuff, and that hasn't helped either. Anyone got any ideas what I can do to fix? -- Clear skies! Mike Calder.
Am Mon, May 02, 2005 at 02:13:28PM +0100 schrieb Mike Calder:> I've updated Wine to the most recent version (20050419) and the behaviour is > the same. I've run winetools and done all the standard setup stuff, and that > hasn't helped either.Very easy: Downgrade to the version you used before, when all fonts have been displayed correctly. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
On Monday 02 May 2005 17:00, Joachim von Thadden wrote:> Am Mon, May 02, 2005 at 02:13:28PM +0100 schrieb Mike Calder: > > I've updated Wine to the most recent version (20050419) and the behaviour > > is the same. ?I've run winetools and done all the standard setup stuff, > > and that hasn't helped either. > > Very easy: Downgrade to the version you used before, when all fonts > have been displayed correctly. > > Regards > ??????Joachim von ThaddenHmm. I suspect that my problem is one of these interaction things; ?OS:Installation details:Wine code:Wine Installation:application. Just reverting the Wine code is unlikely to hack it. I either need someone knowledgeable to say YYGT(Yes, You Get That) and give me a hint as to what is probably going on with the font handling and what directions may be useful to investigate, or someone knowledgeable to say yes that's probably a bug I should report. I prefer going forwards to going back. -- Clear skies! Mike Calder.
Hi again. More on this one. If I run in Winedbg, on "cont" it halts before user input allowed and gives: WineDbg starting on pid 0xa In 32 bit mode. 0x55a6219e: jmp 0x55a6218d Wine-dbg>cont First chance exception: page fault in 16-bit code (15e7:ad8c). In 16 bit mode. Register dump: CS:15e7 SS:1227 DS:1227 ES:1227 FS:0063 GS:005b IP:ad8c SP:ad80 BP:ad96 FLAGS:0206( - 00 - RIP1) AX:150b BX:0000 CX:0007 DX:0000 SI:1227 DI:0000 Stack dump: 0x1227:0xad80: 73db 1217 ad96 0000 ad8c 15e7 2fcd 00cb 0x1227:0xad90: ae96 08e3 1227 adbb 16b6 11ff 002f adaa 0x1227:0xada0: 1227 adaa 1227 ae96 08e3 150b 0000 0007 0244: sel=1227 base=55981380 limit=0000ff5f 16-bit rw- Backtrace: =>1 0x15e7:0xad8c (0x1227:0xad96) 2 0x11ff:0x16b6 (0x1227:0xadba) 3 0x6811:0xff18 (0x1227:0xadf4) 4 0x11ff:0x1fbf (0x1227:0xae08) 5 0x11ff:0x07d8 (0x1227:0xae1a) 6 0x1217:0x564c (0x1227:0xae30) 7 0x138f:0x00bc (0x1227:0xae5e) 8 0x151f:0x0c2f (0x1227:0xae78) 9 0x1457:0x088f (0x1227:0xaec8) 10 0x1437:0x1358 (0x1227:0xaed8) 11 0x1437:0x18d5 (0x1227:0xaeec) 12 0x1007:0x0000 CallTo16_Ret in kernel32 (0x1227:0xaf26) 13 0x55a87a72 K32WOWCallback16Ex in kernel32 (0x57864190) 14 0x55d400dc in user32 (+0x500dc) (0x578644b8) 15 0x55d47221 CallWindowProc16 in user32 (0x578644e8) 16 0x55d84d6b DispatchMessage16 in user32 (0x5786451c) 17 0x55d03fee in user32 (+0x13fee) (0x5786452c) 18 0x55a889eb __wine_call_from_16_long in kernel32 (0x5786455c) 19 0x1477:0x0c49 (0x1227:0xaf6e) 20 0x1477:0x0e76 (0x1227:0xaf86) 21 0x1217:0x5b05 (0x1227:0xafb0) 22 0x11ff:0x01e8 (0x1227:0xafe2) 23 0x1217:0x5a66 (0x1227:0xb0ca) 24 0x1217:0x8879 (0x1227:0xb0dc) 25 0x1217:0x6532 (0x1227:0x0000) 0x15e7:0xad8c: int $0x2f Wine-dbg> Does this mean anything? -- Clear skies! Mike Calder.
Am Di, Mai 03, 2005 at 10:34:46 +0100 schrieb Mike Calder:> On Monday 02 May 2005 17:00, Joachim von Thadden wrote: > > Am Mon, May 02, 2005 at 02:13:28PM +0100 schrieb Mike Calder: > > > I've updated Wine to the most recent version (20050419) and the behaviour > > > is the same. I've run winetools and done all the standard setup stuff, > > > and that hasn't helped either. > > > > Very easy: Downgrade to the version you used before, when all fonts > > have been displayed correctly. > > > > Regards > > Joachim von Thadden > > Hmm. > > I suspect that my problem is one of these interaction things; OS:Installation > details:Wine code:Wine Installation:application. > > Just reverting the Wine code is unlikely to hack it. > > I either need someone knowledgeable to say YYGT(Yes, You Get That) and give me > a hint as to what is probably going on with the font handling and what > directions may be useful to investigate, or someone knowledgeable to say yes > that's probably a bug I should report.If this is what you think, then you have to provide a lot more informations. For every interacting position you mentioned you have to tell what you changed.> I prefer going forwards to going back.This sounds always nice but in case of Wine going to a previous version is sometimes a step forward! Wine is work in progress and between versions many things may get broken or are in testing. To name it you will have no luck with WinWord with 20050419 as there are redrawing issues that make it nearly unusable. Other programs show similar problems. With the version 20050310 you will not have these issues. Also font problems are very typical to remain in some versions. And note that solving an issue with one version by configuring something does not mean that the next version will work with that approach. By the way: Crossover Office is always more than half a year behind the actual source tree. Like me with the WineTools they prefer to identify the most stable release and use this as a basis until there is another promising release. But they have an advantage over me: They actually make the source so they know when something is experimental and when it is supposed to be stable;-) Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"