English translation "Route Editor"
- Carsten Hölscher
- Administrator
- Beiträge: 33799
- Registriert: 04.07.2002 00:14:42
- Wohnort: Braunschweig
- Kontaktdaten:
- Carsten Hölscher
- Administrator
- Beiträge: 33799
- Registriert: 04.07.2002 00:14:42
- Wohnort: Braunschweig
- Kontaktdaten:
-
- Beiträge: 708
- Registriert: 04.12.2002 20:44:14
- Wohnort: Zwijndrecht (NL)
- Kontaktdaten:
-
- Beiträge: 1044
- Registriert: 18.01.2004 12:51:32
- Aktuelle Projekte: Objektbau in LOD0, Fahrpult, new adventures in VHDL
- Wohnort: EPD
I just stumbled across this topic when browsing through the forums
after quite some time now, and I noticed your problems with
changing dialogues. Here's another suggestion:
whenever a window is being created, either an application window
or a dialogue box, it's layout and text is neither hard-coded into
the program executable file nor into the windows system. Instead,
a window's component layout, it's menu layout , menu items, a few
basic text strings like default error messages and even the glyphs
used for tool bars like those in the route editor are stored within the
executable file as character data. When the window is actually being
shown on the screen, these strings/image data/layout data/whatever
are being transformed into a visible window by the VCL, the Visual
Component Library. Windows itself relies on the VCL as well, i.e. all
those little animations you see when moving or copying a file are
stored within a DLL library file. So maybe you should check the
following: the EXE and DLL files are editable, which means that you
might even open ZUSI's executable with a resource editor and change
all the menu items to your language without needing the source code.
My guess is that the ZUSI installation might have supplied you with
some system file, maybe included in Delphi in which ZUSI was coded,
which contains the string values used by the VCL in some of the
standard windows dialogues. You might want to download a small
program called ResHack which is free and can be found here:
http://www.users.on.net/johnson/resourcehacker/
and have a look at files
C:\windows\system32\stdvcl32.dll
C:\windows\system32\stdvcl40.dll
(change C:\windows to whatever your windows folder is,
the sub-directory is system32 for Win2000 and XP, system
for 98 and ME)
I noticed that these files are language-neutral, which might be a reason
why the system isn't complaining about them or why it doesn't matter
which language you choose.
Here's a screenshot to show you what I'm talking about:
As I said, this is just a suggestion what *might* have happened,
as I've had trouble with mixed-language systems before and began
to look for the files in which the relevant data are stored. Maybe there
are some other locations where the German language strings might
come from, i.e. the file C:\windows\explorer.exe contains all the
strings used in the actual windows desktop shell. In explorer.exe,
you'll find all those things like the captions "run...", "shutdown" and
similar items from the start menu which cannot be found in the registry.
ATTENTION: BE CAREFUL WHEN OPENING SYSTEM FILES IN A RESOURCE
EDITOR. Maybe you should just try to find the bug without changing
anything, and restore the exchanged file from a CD or from another
computer running the same windows version.
I hope this hint might lead you to the source of the faulty dialouges...
Regards,
Immo
after quite some time now, and I noticed your problems with
changing dialogues. Here's another suggestion:
whenever a window is being created, either an application window
or a dialogue box, it's layout and text is neither hard-coded into
the program executable file nor into the windows system. Instead,
a window's component layout, it's menu layout , menu items, a few
basic text strings like default error messages and even the glyphs
used for tool bars like those in the route editor are stored within the
executable file as character data. When the window is actually being
shown on the screen, these strings/image data/layout data/whatever
are being transformed into a visible window by the VCL, the Visual
Component Library. Windows itself relies on the VCL as well, i.e. all
those little animations you see when moving or copying a file are
stored within a DLL library file. So maybe you should check the
following: the EXE and DLL files are editable, which means that you
might even open ZUSI's executable with a resource editor and change
all the menu items to your language without needing the source code.
My guess is that the ZUSI installation might have supplied you with
some system file, maybe included in Delphi in which ZUSI was coded,
which contains the string values used by the VCL in some of the
standard windows dialogues. You might want to download a small
program called ResHack which is free and can be found here:
http://www.users.on.net/johnson/resourcehacker/
and have a look at files
C:\windows\system32\stdvcl32.dll
C:\windows\system32\stdvcl40.dll
(change C:\windows to whatever your windows folder is,
the sub-directory is system32 for Win2000 and XP, system
for 98 and ME)
I noticed that these files are language-neutral, which might be a reason
why the system isn't complaining about them or why it doesn't matter
which language you choose.
Here's a screenshot to show you what I'm talking about:
As I said, this is just a suggestion what *might* have happened,
as I've had trouble with mixed-language systems before and began
to look for the files in which the relevant data are stored. Maybe there
are some other locations where the German language strings might
come from, i.e. the file C:\windows\explorer.exe contains all the
strings used in the actual windows desktop shell. In explorer.exe,
you'll find all those things like the captions "run...", "shutdown" and
similar items from the start menu which cannot be found in the registry.
ATTENTION: BE CAREFUL WHEN OPENING SYSTEM FILES IN A RESOURCE
EDITOR. Maybe you should just try to find the bug without changing
anything, and restore the exchanged file from a CD or from another
computer running the same windows version.
I hope this hint might lead you to the source of the faulty dialouges...
Regards,
Immo
- Carsten Hölscher
- Administrator
- Beiträge: 33799
- Registriert: 04.07.2002 00:14:42
- Wohnort: Braunschweig
- Kontaktdaten:
-
- Beiträge: 1044
- Registriert: 18.01.2004 12:51:32
- Aktuelle Projekte: Objektbau in LOD0, Fahrpult, new adventures in VHDL
- Wohnort: EPD
This was supposed to be a suggestion where to look for the
source of the problem rather than a direct pointer.
I intended to say that not only these files, but any file that contains
string table resources might contain the German strings assuming
that changing of the regional settings has no effect on them and
that they can not be found in the system registry. None of the programs
I ever wrote in Delphi required any other file than the EXE to be
copied when distributed to another computer, and as I don't have the
full version, I don't know whether Zusi comes with any kind of re-
distributable system files like some kind of run-time environment or
DLL libraries or whatever.
source of the problem rather than a direct pointer.
I intended to say that not only these files, but any file that contains
string table resources might contain the German strings assuming
that changing of the regional settings has no effect on them and
that they can not be found in the system registry. None of the programs
I ever wrote in Delphi required any other file than the EXE to be
copied when distributed to another computer, and as I don't have the
full version, I don't know whether Zusi comes with any kind of re-
distributable system files like some kind of run-time environment or
DLL libraries or whatever.
Zuletzt geändert von ImmoBirnbaum am 29.09.2004 21:34:22, insgesamt 2-mal geändert.
- Carsten Hölscher
- Administrator
- Beiträge: 33799
- Registriert: 04.07.2002 00:14:42
- Wohnort: Braunschweig
- Kontaktdaten: