Does anyone know where IE 5.5/6.0 localized resources are stored?

[Scott Smith]

Hi,

We're trying to localize an IE plug-in that relies on the exact text of
certain IE menu items and buttons (the IDs used for menu items and toolbar
buttons aren't constants in IE for some reason, so we had to fall back on
string matching to locate these).

Identifying the proper strings is easy to do in English; just look at the
menu item and copy the exact string into a string constant in our code.

We need to get these menu and button strings for each language that we plan
to support, however. We could just install each different language version,
and look at the menu items and buttons, but... for languages such as
Chinese, Korean, Japanese, etc., it's very difficult to find the exact
Unicode characters based upon what you see on the screen.

It would be best if we could just extract the Unicode strings by loading the
executable or DLL into Visual Studio as resources. Unfortunately, so far
we've been unable to locate the DLL or executable where these resources are
stored.

Does anyone know where these menu/string resources are, or how I can track
them down?

Any help much appreciated!

-Scott

[Igor Tandetnik]

Scott Smith <scottse...@NO-SPAM.hotmail.com> wrote:
> It would be best if we could just extract the Unicode strings by
> loading the executable or DLL into Visual Studio as resources.

Look at c:\windows\system32\shdoclc.dll . I believe it is what you are
looking for.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925

[Scott Smith]

That's it! Thanks Igor!

-Scott

"Igor Tandetnik" <itand...@mvps.org> wrote in message
news:etgv7SKa...@TK2MSFTNGP02.phx.gbl...

[Jesper Holmberg [msft]]

Hi,

I'm Jesper Holmberg and I work in the Windows localization team at Microsoft.

Note that string matching is very fragile. The translations may change at
any point in time, without notice. It is likely that there are plenty of
inconsistencies between IE5.5 and IE6.0 for various languages, and even
between different Service Packs. Even things that have shipped aren't
necessarily safe - in fact, in Swedish IE7 we just made a major terminology
change which may be back-propped to previous IE versions.

Please consider if there's a better way than relying on string matching.

--
Mvh,
Jesper Holmberg
http://blogs.msdn.com/jesperh

Detta inlägg publiceras i befintligt skick och innebär inga garantier eller
rättigheter i övrigt.