home *** CD-ROM | disk | FTP | other *** search
- ******************************************************************************
- ** ViNCEd localization package **
- ** **
- ** © 1990-1997 THOR-Software **
- ** Version 40.50 **
- ** **
- ** All the restrictions of the THOR-Software licence apply to this package **
- ** read the VNC.guide to find out more about this licence **
- ******************************************************************************
-
- This is the localization package for THOR's ViNCEd shell editor.
-
- Since at the time of writing ViNCEd, I had no access to the commodore
- standard localization tools, ViNCEd's locale is setup by a private program,
- called CreateCatalog. There are many pro's and con's about this program,
- and propably even more con's than pro's, but at least it is freely dis-
- tributable (only the licence apply), and it is sometimes more flexible
- than the standard tool. Besides this program, which can be found in the
- "bin" foulder, an assembler is needed. The prepared scripts are setup for
- Frank Wille's PhxAss, which is also freely available at the AmiNet, but
- is not included in this package cause my licence does not apply to it.
- However, each other assembler will work as well, with some minimal changes.
- Copy it to the "bin" folder, where CreateCatalog is located.
-
- Besides the assembler, no assembly language knowledge is needed, all you
- need to do is to change some strings in the files.
-
-
- A word about the CreateCatalog tool: It usually takes only one input file,
- the .construct file. This file has two purposes and can be read thanks to
- the unique CreateCatalog syntax by both the shell and CreateCatalog itself.
- First, it is a shell script that has to be executed with the Execute command
- to build the complete catalog. Second, it acts as a command file for
- CreateCatalog, which may contain the localized strings, plus some comments
- plus links to files with more strings. So don't worry if something seems
- to miss: The .construct file is good enough and contains all information.
-
-
- Here's a step-by-step instruction how to localize ViNCEd:
-
-
- 1) Download the PhxAss assembler package from AmiNet. Only one file from
- this distribution is needed, namely the "PhxAss" command. Place it in the
- bin folder of this directory, near the CreateCatalog tool.
-
-
- 2) Add an assign VL: to this drawer. This is not needed permanently, only for
- the time of localization.
-
- >assign VL: ""
-
-
-
- 3) Edit the "sys.construct" file, follow the instructions there. You need to change
- the name of the language, and some requester texts. The english versions of the
- strings are present there as well. It contains one empty string - leave it
- alone and DON'T REMOVE it.
-
-
- 4) Edit the "sys1.asm" file. This one contains a structure encoded in
- assembly language which is used by the ViNCEd menu builder. Only the strings
- between double quotes "..." need to be translated there. Don't forget to
- include your name and the language at the marked position, since people want
- to know who did the work. Also read the instructions in this file.
-
- 5) Now build the locale. Only one command should suffer:
-
- >Execute VL:sys.construct
-
- The complete locale database will be put into your RAM: drawer and will be
- called "VNC.sys.catalog". Create a subdirectory "VNC" in your catalog
- drawer "LOCALE:CATALOGS/<language>" and copy this file there.
-
- 6) Now edit the "prefs.construct" file. It contains all strings for the
- prefs editor "SetVNC". This time, no assembler intermediate files are
- needed, since every string is in the constructor. The only thing worth
- remembering is:
-
- The first character of a line determinates the meaning of a line:
- A blank (or TAB) or a semicolon ";" are used to introduce a comment line.
- These lines are ingored by CreateCatalog (and form the shell script).
- A ' (apostrophe) is an actual string that is put into the locate database.
- Only these lines must be translated.
- A # (hash mark) line sets the string counter to a specific value. Do not
- edit these lines.
-
- Since all the catalog creators are taken from the german localization, the
- current strings in the locale database are german. Don't mind about this,
- I always added the english original version of the string ON TOP of the
- german version, plus some information when this string is used.
-
-
- 7) Build the catalog by one command:
-
- >Execute VL:prefs.construct
-
-
- A file "VNC.prefs.catalog" should appear in the RAM drawer.
-
-
- 8) Copy this file to LOCALE:Catalogs/<language>/VNC.
-
-
- 9) Setup the language with the prefs editor "Locale" of the workbench.
- Open a ViNCEd window and open the prefs editor. Check if your localization
- looks properly: Check for example if some of your strings are too long
- and leak over the boundaries of the gadgets. Usually the size of the menu
- is adapted from the strings in it, however a very big menu may look ugly
- again. It might happen that your first try is not very con-vince-ing, so
- write down the strings that caused the problems and correct them.
- Repeat steps 3 to 12 until the result is acceptable.
-
-
- 10) If you like, update the installer script of the ViNCEd package.
- If you don't know how to do this, just translate the english or german
- strings in there, and send me the translated version.
-
-
- 11) If you have still plenty of time (I don't expect this do be done ;-)
- translate the guide. This is maybe a lot of work, two weeks of typing...
- ;-) Well, as I said, unless you've plenty of time....
-
-
- 12) If you're finally happy with your translations, don't forget to mail
- them to my address so I can put them into the next release of ViNCEd. Here's
- my mail address:
-
- thor@math.tu-berlin.de
-
- Please send the locale databases (plus the installer, plus the guide) as
- an uuencoded lha archive to this address. If you have trouble with
- CreateCatalog, please let me know, too.
-
-
- Thanks a lot for your work,
- Thomas
-
-