This document serves as a "how-to-use" document for the external translation
tool provided as part of DPSLang, from now on "DPSLangX". I'm very concerned
about being clear, since external translators are not supposed to be familiar
with programming at all. Therefore, if you don't find this document clear
enough, please e-mail me at "ddemarco@dpsautomation.com"


1) Purpose of DPSLangX
----------------------
DPSLangX is provided as an aid to external translators who don't have Delphi
or any other Borland tools. Typically, a software developer will use DPSLang
from the Delphi ITE to create an internationalization database, setup its
configuration, choose a set of translation languages, filter out unimportant
strings, and so on. After that, the task of actually translating resources is
tackled by an external translator, someone who ideally doesn't have to know a
thing about Delphi.
Bearing that in mind, I created DPSLangX wich will hopefully serve as a very
easy-to-use tool, with a very small footprint, and which doesn't need any
setup or installation programs.


2) How to send DPSLangX to your external translator
---------------------------------------------------
In order to enable your translator to do his part of the job, you will need to
send him/her the following things:
a) DPSLang.exe (included in this zip file)
b) Your internationalization file (the file with the "int" extension).
c) The packages needed to start DPSLang.exe (see section 4 for details)
d) Any other design-time packages you would like to include (see section 4 for
   details)
I recommend you to zip all of this files together (spanning them across
multiple disks if necessary), and e-mail them to your translator.


3) How external translators use this software
---------------------------------------------
External translators will usually receive the files mentiones in the previous
section, as sent by the developer. In order to start translating, translators
should:
a) Copy all files received to a single folder (It's a good idea to create a new
   folder, in order not to mix these files with other ones).
b) Start DPSLangX.exe by double-clicking on it.
d) From the "Options" menu, select "Packages..." and then click on the "Add"
   button. Select all files shown, and click Ok. Click "Close" to close the
   packages window.
c) From the "File" menu, select "Open", and then pick the file with the "int"
   extension (usually it will be the only one shown)
d) You're ready to go. You can start translating now.
e) When you finish translating (or if you want to send your "work-in-progress"
   back to the developer, simply e-mail him/her the file with the "int"
   extension.


4) The use of packages
----------------------
In order for DPSLangX to work, the following packages must be sent to the
translator:
- rtl60.bpl
- vcl60.bpl
- dbrtl60.bpl
- vcldb60.bpl
- dsnap60.bpl
- bdertl60.bpl
- designide60.bpl
- visualclx60.bpl
- webdsnap60.bpl
- xmlrtl60.bpl
- inet60.bpl
- inetdb60.bpl
- vclx60.bpl
Please note that DPSLangX.exe *WILL NOT WORK* if these files are not present.

Also, you might want to include other packages (because you want your external
translator to work on previews too), and those should also be included.
Here's a brief list of other packages you might need to include, depending on
different component types you use.
- To use the standard components: enclose "dclstd60.bpl"
- To use legacy Windows 3.1 components: "dcl31w60.bpl" & "dclstd60.bpl"
- To use database access (BDE): dclbde60.bpl, dclstd60.bpl, dcldb60.bpl,
  dbx60.bpl & designdgm60.bpl
I'll complete this list as I have more time. you can figure out what packages
are needed by entering DPSLangX.exe and trying to preview your forms.




