| Author |
 Topic  |
|
Deleted
deleted
4116 Posts |
 Posted - 26 February 2002 : 12:46:57
|
Hi all,
During the transformation from v3.4 to v4.0, the language data will change to some extend. It will be not efficient to keep track of the added/deleted/changed language strings by hand and by to many people.
For the process of v49b04 I started to program an Access based utility to cover all locale related info and keep ALL language data for ALL translated LCID values.
This utility will:
* Import info in LangNNNN.asp files
* Keep track of changes
* Find un-translated strings
* Record versioning info
* Use industry standart localization data for further development stages (date-time formats, etc)
* Re-generate new LangNNNN.asp files automatically and upon request
* ...
Please ZIP and send your LangPackNNNN.ZIP files (if no GIF files are ready, only LangNNNN.asp file) -whatever their status is- to my e-mail address ASAP.
Thank you.
Think PinkPost v40b03 Patches
Edited by - bozden on 20 April 2002 08:58:11< |
|
|
n/a
deleted
593 Posts |
Posted - 26 February 2002 : 15:25:44
|
quote:
Hi all,
During the transformation from v3.4 to v4.0, the language data will change to some extend. It will be not efficient to keep track of the added/deleted/changed language strings by hand and by to many people.
For the process of v49b04 I started to program an Access based utility to cover all locale related info and keep ALL language data for ALL translated LCID values.
This utility will:
* Import info in LangNNNN.asp files
* Keep track of changes
* Find un-translated strings
* Record versioning info
* Use industry standart localization data for further development stages (date-time formats, etc)
* Re-generate new LangNNNN.asp files automatically and upon request
* ...
Please ZIP and send your LangPackNNNN.ZIP files (if no GIF files are ready, only LangNNNN.asp file) -whatever their status is- to my e-mail address ASAP.
Thank you.
Think PinkPost v40b03 Patches
Hi Bozden,
Lang1041.asp is sent to you.
The latest revision: 02/25/02.
Graphics not included. (Ones submitted by Seahorse remain as is)
LeoRat
Edited by - bozden on 20 April 2002 09:01:57< |
 |
|
|
Deleted
deleted
4116 Posts |
Posted - 26 February 2002 : 20:29:02
|
Till now I get:
LangPack1031 (Deutsch-Du and Deutsch-Sie)
Lang1041.asp (Japanese with utf8)
Thank you.
Think PinkPost v40b03 Patches< |
|
|
|
seahorse
Senior Member
USA
1075 Posts |
Posted - 26 February 2002 : 21:44:10
|
quote:
Lang1041.asp is sent to you.
The latest revision: 02/25/02.
Graphics not included. (Ones submitted by Seahorse remain as is)
LeoRat
LeoRat,
You beat me to it. .
Bozden,
I was going to send you the 1041 file, but since LeoRat beat me to it, I'm just sending you the graphics files.
Regards,
Ken
===============
The greatest tragedy is a child without a loving parent.< |
|
|
|
Deleted
deleted
4116 Posts |
|
|
Deleted
deleted
4116 Posts |
|
|
fatum
Junior Member
Belgium
281 Posts |
Posted - 28 February 2002 : 16:47:39
|
Bodzen,
The Dutch langpack is on its way.
Bodzen, I just resent the langpack, this time updated to patch003.
Dutch support forum | version4 beta3 Dutch testsite
Edited by - fatum on 28 February 2002 17:05:52< |
|
|
|
Nathan
Help Moderator
USA
7664 Posts |
Posted - 28 February 2002 : 18:12:57
|
Bozden, I think alot of folks made their languages packs then left  for example. . . the russian lang pack. You might have to find their threads and follow their downloads.
Nathan Bales - Romans 15:13
---------------------------------
Snitz Exchange | Mod Resource< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 28 February 2002 : 19:42:49
|
Hmm. What would be if these forums get closed? The problem is: First v40b04 then v4.0f will be prepared and will include some language packs. Somebody has to keep them up2date this time or a bit later. I cannot update the Russian LangPack like most of us.
The workgroup methodology I proposed was just for this. If one goes away, the others will remain, new members will join: A virtually fault tolerant system.
Some of the people applied v40b02 or v40b03 to their site and are happy with it. I'm sure they will come back to upgrade, and they have to upgrade their LangPacks also. I just hope they will come back. The e-mail list and the subscriptions both are dead, so we can just hope.
Look at: INQUIRY: Status of LangPacks
They are all near completion. I'll try to e-mail them individually.
Think PinkPost v40b03 Patches< |
|
|
|
n/a
deleted
593 Posts |
Posted - 28 February 2002 : 22:52:09
|
Bozden,
I am sending you a Shift-JIS lang1041.asp....Seashorse agrees on the point mentioned below and this is consistent with our discussion elesewhere...
---------
Seahorse,
I uploaded Shift-JIS lang1041.asp as well.
Reasons: Previous R1.3 is set to utf-8 (65001) within the file and code page is set to utf-8 in saving the file (saved as UTF8 file). All langxxx.asp (including English) were saved as utf8 fiels which were installed at i2AsiaForum (a production/testing site).
I just played with Shift-JIS Lang1041 but saved in a normal ANSI code (1251). This was installed along with English-US (code set to Normal ANSI)saved in Normal ANSI Code. I uploaded both to Brinkster, and run setup.asp and checked how it goes. They work fine. As long as it is "bilingual" it works well...meaning there is only one char encoding style used for "JA".
The site shows the previous unicode text showing naturally in unicode char rendering/representation, and Shift-JIS in shift-jis encoding ... two encoding schemes for a particular language cannot be displayed properly as noted before.
So, for implementing Forum in an orthodox approach of having a language specific web Forum page by language selection, it is fine...although there is still an issue of design to tie with a single multilingual database which obviously is the case with Snitz2000 (meaning, at present, Forum shows everything!!!! So if you have a mixed language combo of "national" encoding schemes, then, some shows up corrupted and have to go through switching of browser encoding option to view them correctly....and different browser render encoding slightly different, and so on...)
So, here is my 2 cents: for 1041 languge packs - as done for German, ideally it is good to have unicode version, shift-JIS version, Shift-JIS w/single byte support version, and EUC version prepared so that whichever encoding scheme visitors use in editing text/message can do that. Obviously, this confirms to a standard browser encoding selection, but will be defaulted to whatever encoding implemented in Forum.
As you asked for SHIFT-JIS, which obviously is the most common encoding scheme in Japan, it will make sense to pack different flavors of lang1041...
It's up in
http://www.geocities.com/tosakko2001/1041ShiftJ.zip
I haven't really checked through "compatibility" with post40b03patch003 but if you can verify, it will be good.
As for handling different flavors of particular language packs...should probably check with Bozden.
May send ShiftJIS version 1041 to Bozden as well.
leorat....
----------------
I will take a break on this item and also a QA testing...getting HTTP500 internal server error on my site and cannot get to it.
I amy do EUC and Shift-JIS single byte stuff when I get to it...but given new release seems to be coming up shortly, perhaps just stick with UTF8 Unicode and Shift-JIS for lang1041 for now.
Best,
leorat
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 02 March 2002 : 19:25:01
|
bozden,
Do you have a limit date for this? I'm creating a lang pack for european portuguese. Started now, can finish it in a couple of days. Is that OK?
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 03 March 2002 : 10:02:29
|
quote:
Do you have a limit date for this? I'm creating a lang pack for european portuguese. Started now, can finish it in a couple of days. Is that OK?
I'm preparing a Access 2000 based "software" called LangPackManager, which will be crutial in later upgrading tasks (especially for 3.4=>40b04). Even in the few (4) packages I get, the first alpha version found some mistakes. If you prepare a langpack which is v40b03patch003 compatible, it will help a lot. The software will automatically delete langvars, add langvars and report any changes automatically thereafter.
Think PinkPost v40b03 Patches< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 03 March 2002 : 13:31:00
|
quote:
quote:
Do you have a limit date for this? I'm creating a lang pack for european portuguese. Started now, can finish it in a couple of days. Is that OK?
I'm preparing a Access 2000 based "software" called LangPackManager, which will be crutial in later upgrading tasks (especially for 3.4=>40b04). Even in the few (4) packages I get, the first alpha version found some mistakes. If you prepare a langpack which is v40b03patch003 compatible, it will help a lot. The software will automatically delete langvars, add langvars and report any changes automatically thereafter.
Think PinkPost v40b03 Patches
Ok, I'm taking care of it now. I'll finish it as soon as I can.
Just to be sure, what exactly does v40b03patch003 compatible mean? I downloaded 4.0b03 in November and this week I downloaded a file named AllPost40b03patches.zip. Is it correct to think that by using the files resulting from updating my original version files with these patches I'll make my langpack v40b03patch003 compatible?
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 03 March 2002 : 15:36:27
|
Just make sure that the file date of the All*.zip is about the same as the latest patch. The language file in that patch003 and in that file also has the same data. Use it as the "latest version".
Think PinkPost v40b03 Patches< |
|
|
|
tutzauer
Starting Member
Panama
28 Posts |
Posted - 03 March 2002 : 23:14:17
|
Hi,
I'm new to this forum. I hope that you will forgive my butting in.
I was reading about updating the language files for future updates of snitz international. This is where the rubber meets the road.
Some ideas that occurred to me:
1. Deleted variables are minor problems..just rem them out in the language file.
2. Changed text or new text variables are not so easy.
a. To prevent delays they will need an immediate value before language files have been revised by the subject matter experts.
b. For control a standard must be developed to identify changes.
For example: suppose a variable is deleted in version xx. A solution might be to rem out the old variable with the comment 'Deleted in version xx .
For example: suppose a variable is added in version xx. New comment line are added to the language files stating the version and the change i.e. 'VERSION XX NEW VARIABLES i.e. 'VERSION XX CHANGED VARIABLES. Under each title would be the variable line with an ENGLISH LANGUAGE VALUE and comment. This would accomplish several things
1) The latest version language file could be adapted to any previous version.
2) The new/changed variables would be associated and grouped by version number in the language file (easy to find). The old value would be remed out with 'VALUE CHANGED IN VERSION XX (again easy to find)
3) The program would still run reasonably well until an official language file was released.
4) Each individual forum administrator could have translations made locally until an official version is released (no delay to the upgrade release).
5) All language files can be immediately updated for new/changed with a simple copy and paste operation...ready for the subject matter experts to modify. The REMs can be added by the individual language workgroups. The extra variables will not cause any big problems and the changed variables should end up with the last values added at the bottom of the file until the REMs are added. Actually the REMs probably don't have much value except for debugging. Although I think it is a good idea to keep track of changes until the smoke clears.
3. When a final (locked down) version of the language files is released, the remed lines can be removed and the new/changed variables can be placed in their normal place according to the original system of ordering the variables. The preliminary language files could contain a comment line at the top stating 'PRELIMINARY RELEASE OF LANGUAGE FILE LANG10XX.ASP FOR SNITZ INTERNATIONAL VERSION sf2k_vXX_bXX In the 'final' language files this comment line would be replaced with 'FINAL RELEASE OF LANGUAGE FILE LANG10XX.ASP FOR SNITZ INTERNATIONAL VERSION sf2k_vXX_bXX
If you have already thought this through, please forget the above.
If not, comments please
Jack Tutzauer< |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 04 March 2002 : 07:50:34
|
Valuable ideas . Basically I want to keep langpacks for all versions (including future releases). I'll keep the data for "publicly released" versions, but not bugfixes.
ForumVersion_LCID
I will take 1033 data as a base. If you keep data for v40b03 and v40b04, a routine can compare them to find what is deleted, what is added, what is changed. Once that info is compiled for 1033, the translators will be informed so that they can make the necessary changes. After they make the changes that file will be quality (technical) checked again before release.
Currently the record structure is formed, I have the routines to import and export LangNNNN.asp files. Now I'm writing the Q-check and reporting part.
I'm also compiling a full set of locale specific settings such as number, currency, calendar formats and thinking on how I will inforporate these to the main forum code (admin sections mainly).
Whenever I'm a bit further, I will share an alpha version with you. Currently the header of a language file will contain the following:
'#################################################################################
'############################## LANGUAGE RESOURCE FILE ###########################
'## For more information please read LangReadMe.txt in the related forum version
'## GENERATED BY: Snitz LangPackManager v1.0 alpha 001 on 02.03.2002 02:38:09
'############################### LANGUAGE INFO ###################################
'## LOCALE NAME :
'## ENGLISH LANGUAGE NAME :
'## LOCAL LANGUAGE NAME :
'## LCID DECIMAL :
'## LCID HEXADECIMAL :
'############################### VERSION INFO ####################################
'## FORUM COMPATIBILITY :
'## LANGUAGE FILE SUBVERSION :
'## LANGUAGE DATA DATED :
'## DATA COLLECTED BY :
'## INIT. TRANSLATION DATED :
'## LAST. UPDATE :
'## TRANSLATED BY :
'## CHECKED BY :
'############################### OTHER INFO ######################################
'##
'##
'#################################################################################
Any comments will be very much appreciated.
Think PinkPost v40b03 Patches< |
|
|
|
Topic |
|
Forum Locked
