Just a thought, but maybe the admins can put the languagefiles on sourceforge together with the snitz files.
Like this there is a centralized place to find the files and you won't have the problem of having several language files on the net, with nobody knowing which one is the latest version.
Fatum ------------------- Boves Luci The best Belgian student club<
I cannot think of a kind of "quality control" the language files. It can cause some problems with several versions of language files (different versions for different beta versions) being distributed officially. E.g. we will add a lot of strings with v3.4 (i.e. v40b04)...
What I was thinking was, to include the up-to-date language files with the next beta version as LangPacks (i.e. with v40b04)... Inbetween, I have to do a technical quality control on headers and number of lines (no string missing)...
quote: I cannot think of a kind of "quality control" the language files. It can cause some problems with several versions of language files (different versions for different beta versions) being distributed officially. E.g. we will add a lot of strings with v3.4 (i.e. v40b04)...
I agree. I suggest for the <= 3.3 versions that the translator include a meta tag in one of the .asp (to be determined by the moderator?) with version of snitz, version of language and name and e-mail address of the translator.
quote: What I was thinking was, to include the up-to-date language files with the next beta version as LangPacks (i.e. with v40b04)... Inbetween, I have to do a technical quality control on headers and number of lines (no string missing)...
The same goes for the language packs. Discussion of translated terms, together with which version is under review, should take place on an appropriate forum on the Snitz forum site.
Forum Locked
Posted - 13 January 2002 : 12:48:25
