| Author |
 Topic  |
|
|
Nathan
Help Moderator
USA
7664 Posts |
 Posted - 15 April 2002 : 14:23:27
|
bozden, I am curious about this software. Will it work for mod language packs, or even non-snitz language packs?
 Nathan Bales
Snitz Exchange | Do's and Dont's< |
|
|
Deleted
deleted
4116 Posts |
Posted - 15 April 2002 : 16:08:05
|
It is not mature enough. Currently it is in alpha 02 version. It only deals with Snitz langpacks. I would not call it a good software, I just use it for automation of my tasks (so that the computer works for me - not the other way). It is based on Access 2000 database working on Access 2002. Without the following it would be impossible to deal 10s of language packs.
Note: The following is valid for v1a002
TABLES:
LCID: Keeps all locale related info (date, time, currency, calendar etc)
VERSIONS: International Snitz Versions (v4x) with descriptions, links etc
LANGPACKS: Langpacks related to the versions and LCID's, their update status, translators etc.
VVVV_NNNN: Tables for languages for version VVVV and LCID=NNNN, includes records for language variables (so its not feasible, but this is required)
LINKS: Important links with descriptions on localization and globalization
FUNCTIONALITY:
* View/Edit LCID table
* View/Edit VERSION table
* View/Edit LANGPACKS table
* Ofcourse the above also in hierarchical manner
* Report differences between two versions (e.g. v4b03 and v4b04)
* Check/Report/Import a language file (nowadays it must be in original format)
* Export a final language file (for being used in v4b04)
* Identify Language File (to what version it belongs), report differences, accept if there is an exact fit.
* Auto create database related code to be used in v4's setup procedures (create table for all supported databases, select-option etc). This will ease the programming with whenever a change in the LCID database structure occurs.
* View/Edit LINKS table
In the near future I'll add some more features whenever they are needed.
I can say, that with little changes it can be adopted for MOD language packs. It will not work for non-snitz ones. I even have problems with UTF-8 encoded files.
But I repeat again: It's not mature enough.
Think Pink
==> Start Internationalization Here< |
 |
|
|
fatum
Junior Member
Belgium
281 Posts |
|
|
Nathan
Help Moderator
USA
7664 Posts |
Posted - 16 April 2002 : 00:01:12
|
quote:
It will not work for non-snitz ones
I was thinking that its a great idea. It might have the potential to become an independant open souce project if in the future it could be parted from its Snitz-specificness.
For now though, its getting the job done 
Nathan Bales
Snitz Exchange | Do's and Dont's< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 16 April 2002 : 05:20:02
|
quote:
quote:
It will not work for non-snitz ones
I was thinking that its a great idea. It might have the potential to become an independant open souce project if in the future it could be parted from its Snitz-specificness.
For now though, its getting the job done
Nathan Bales
Snitz Exchange | Do's and Dont's
Is there a more "global" definition for language resources. If you also take other programming languages into account, I can think of too many "standarts".
Think Pink
==> Start Internationalization Here< |
|
|
| |
Topic |
|
Forum Locked
