From: oslsachem <oslsachem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 8562@debbugs.gnu.org
Subject: bug#8562: Emacs 23.1 and later don't work in windows 98
Date: Fri, 3 Jun 2011 22:10:05 +0200 [thread overview]
Message-ID: <BANLkTi=V_Mk1oPKGk-TJnZQ=Ko_yamp3OA@mail.gmail.com> (raw)
In-Reply-To: <83pqmve2s2.fsf@gnu.org>
> It could be that more Unicode functions have similar problems, because
> they reside inside unicows.dll on Windows 9X. Could you please look
> up all the functions in w32font.c and w32uniscribe.c whose names end
> with a `W', and see which ones of them are in unicows.dll?
C:\emacs-23.3\src>grep -E -o -h "\<\w+[a-z0-9]+W\>" w32font.c w32uniscribe.c | s
ort | uniq
DrawTextW
ExtTextOutW
GetGlyphOutlineW
GetOutlineTextMetricsW
GetTextExtentPoint32W
GetTextMetricsW
And in a wider search:
C:\emacs-23.3\src>grep -E -o -h "\<\w+[a-z0-9]+W\>" *.c | grep -v
"Elf\|MingW" | sort | uniq
AppendMenuW
DrawTextW
ExtTextOutW
GetFileSecurityW
GetGlyphOutlineW
GetOutlineTextMetricsW
GetTextExtentPoint32W
GetTextMetricsW
ImmGetCompositionStringW
LookupAccountSidW
lstrlenW
Note: The words that begin with Elf are macros, not functions.
I was going to report that the rest of these functions are already
implemented in core system libraries:
==================================================
Function Name : AppendMenuW
Address : 0xbfc010eb
Relative Address : 0x000010eb
Ordinal : 8 (0x8)
Filename : USER32.DLL
Full Path : C:\WINDOWS\SYSTEM\USER32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : DrawTextW
Address : 0xbfc010f4
Relative Address : 0x000010f4
Ordinal : 176 (0xb0)
Filename : USER32.DLL
Full Path : C:\WINDOWS\SYSTEM\USER32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : ExtTextOutW
Address : 0xbff21cb2
Relative Address : 0x00001cb2
Ordinal : 207 (0xcf)
Filename : GDI32.DLL
Full Path : C:\WINDOWS\SYSTEM\GDI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : GetFileSecurityW
Address : 0xbfe8216d
Relative Address : 0x0000216d
Ordinal : 116 (0x74)
Filename : ADVAPI32.DLL
Full Path : C:\WINDOWS\SYSTEM\ADVAPI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : GetGlyphOutlineW
Address : 0xbff2797f
Relative Address : 0x0000797f
Ordinal : 264 (0x108)
Filename : GDI32.DLL
Full Path : C:\WINDOWS\SYSTEM\GDI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : GetTextExtentPoint32W
Address : 0xbff21ed0
Relative Address : 0x00001ed0
Ordinal : 309 (0x135)
Filename : GDI32.DLL
Full Path : C:\WINDOWS\SYSTEM\GDI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : ImmGetCompositionStringW
Address : 0xbfe210a7
Relative Address : 0x000010a7
Ordinal : 25 (0x19)
Filename : IMM32.DLL
Full Path : C:\WINDOWS\SYSTEM\IMM32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : LookupAccountSidW
Address : 0xbfe8217f
Relative Address : 0x0000217f
Ordinal : 173 (0xad)
Filename : ADVAPI32.DLL
Full Path : C:\WINDOWS\SYSTEM\ADVAPI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : lstrlenW
Address : 0xbff77454
Relative Address : 0x00007454
Ordinal : 865 (0x361)
Filename : KERNEL32.DLL
Full Path : C:\WINDOWS\SYSTEM\KERNEL32.DLL
Type : Exported Function
==================================================
But I have stumbled across this comment:
w32menu.c:1505
/* On W9x/ME, unicode menus are not supported, though AppendMenuW
apparently does exist at least in some cases and appears to be
stubbed out to do nothing.[...] */
And then I have checked that both GetTextMetricsW and
GetOutlineTextMetricsW, which caused the system error #120 ("This
function is not supported on this system."), are actually
"implemented" in a core system library along with other of the
previous functions:
==================================================
Function Name : GetOutlineTextMetricsW
Address : 0xbff2795b
Relative Address : 0x0000795b
Ordinal : 286 (0x11e)
Filename : GDI32.DLL
Full Path : C:\WINDOWS\SYSTEM\GDI32.DLL
Type : Exported Function
==================================================
==================================================
Function Name : GetTextMetricsW
Address : 0xbff27952
Relative Address : 0x00007952
Ordinal : 315 (0x13b)
Filename : GDI32.DLL
Full Path : C:\WINDOWS\SYSTEM\GDI32.DLL
Type : Exported Function
==================================================
So, your idea of trying the unicode functions which have been
reimplemented in unicows.dll and seeing if they make a difference
looks very promising.
Greetings,
Osl
next prev parent reply other threads:[~2011-06-03 20:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:55 bug#8562: Emacs 23.1 and later don't work in windows 98 oslsachem
2011-04-27 3:09 ` Eli Zaretskii
2011-05-06 1:38 ` oslsachem
2011-05-06 11:52 ` Eli Zaretskii
2011-05-06 15:28 ` Eli Zaretskii
2011-05-22 21:32 ` oslsachem
2011-05-23 13:43 ` Jason Rumney
2011-05-24 19:31 ` oslsachem
2011-05-23 17:39 ` Eli Zaretskii
2011-05-24 19:32 ` oslsachem
2011-05-24 20:37 ` Eli Zaretskii
2011-05-25 2:01 ` oslsachem
2011-05-25 4:28 ` Eli Zaretskii
2011-05-25 10:53 ` oslsachem
2011-05-25 16:44 ` Eli Zaretskii
2011-05-26 1:50 ` oslsachem
2011-05-27 14:04 ` Eli Zaretskii
2011-05-27 17:22 ` oslsachem
2011-05-27 18:17 ` Eli Zaretskii
2011-05-27 16:13 ` oslsachem
2011-05-27 17:15 ` Eli Zaretskii
2011-05-27 18:33 ` oslsachem
2011-05-27 20:51 ` Eli Zaretskii
2011-05-30 15:12 ` oslsachem
2011-05-30 18:43 ` Eli Zaretskii
2011-05-31 18:16 ` oslsachem
2011-05-31 21:02 ` Eli Zaretskii
2011-05-31 21:04 ` Eli Zaretskii
2011-06-02 23:41 ` oslsachem
2011-06-03 7:10 ` Eli Zaretskii
2011-06-03 8:29 ` Eli Zaretskii
2011-06-03 20:10 ` oslsachem [this message]
2011-06-03 20:51 ` oslsachem
2011-06-03 22:52 ` oslsachem
2011-06-04 7:11 ` Eli Zaretskii
2011-06-05 1:58 ` oslsachem
2011-06-05 3:07 ` Eli Zaretskii
2011-06-05 5:48 ` Eli Zaretskii
2011-06-05 22:32 ` oslsachem
2011-06-07 19:25 ` oslsachem
2011-06-07 20:32 ` Eli Zaretskii
2011-06-08 18:11 ` oslsachem
2011-06-08 20:36 ` Eli Zaretskii
2011-06-12 21:47 ` oslsachem
2011-10-01 11:06 ` Eli Zaretskii
2011-10-26 23:05 ` oslsachem
2011-10-01 11:03 ` Eli Zaretskii
2011-10-26 22:46 ` oslsachem
2011-10-27 14:53 ` Eli Zaretskii
[not found] ` <CADv-x1szHOjvVzg8xAYtZNE4iByugKeQz37SY+-dNVucioB70w@mail.gmail.com>
2011-10-28 10:21 ` Eli Zaretskii
2011-10-28 12:11 ` Eli Zaretskii
2011-10-29 22:24 ` oslsachem
2011-11-04 11:42 ` Eli Zaretskii
2011-11-04 20:59 ` oslsachem
2011-11-04 22:01 ` Eli Zaretskii
2011-10-28 10:10 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=V_Mk1oPKGk-TJnZQ=Ko_yamp3OA@mail.gmail.com' \
--to=oslsachem@gmail.com \
--cc=8562@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).