1. Richard et.al. did a great job in v3.4, and v4 will be based on it of course.


2. I first started to keep up with the changes in early development stages but I gave up.


3. As a test run, I started to compare-update one file (active.asp) and found out that it will take too much time. (See: http://forum.snitz.com/forum/topic.asp?TOPIC_ID=22240 )


4. We decided to repeat the string collection process which absolutely takes less time. In v3.4 there are group changes in language strings because file name changes, file-splits etc (See: http://forum.snitz.com/forum/topic.asp?TOPIC_ID=24401 ). For this purpose (to make the upgrade of Language packs easier and to verify LangPack compatibility) I wrote a program on Access (I call it LangPackManager, see: http://forum.snitz.com/forum/topic.asp?TOPIC_ID=23558 ). This will evolve and will ease the group changes in variable naming.


5. Lately I tried to convert some of the stable files (%3.3 of all done), and saw it will also need careful steps because of the existing language packs. We have to log all these variable changes once, and LangPackManager will do it for N language files. Only new/modified strings will need to be translated. The necessary steps will be reported by the LangPackManager automatically. Thus, this task must be done by one person only (any volunteer?).


6. Because of the previous point, having v4b03.003 compatible LangPacks is crucial.


7. The actual start will be just after the advent of v3.4final.


8. There will be no ETA announced for v4.0final. The next step is v4.0beta04, which will be compatible with v3.4, including some fixes (if any) and some (major?) code and database changes/ additions related to internationalization. After fixing v4b04 issues, v4b05 will contain everything that is planned. Then, v4.0final will come out with all required fixes and N Language Packs (N depends on you).


9. So there *is* a plan for evaluation, and ETA will not be tomorrow . But this is just a plan, lets see what life brings to us.

quote:

---

Lately I tried to convert some of the stable files (%3.3 of all done), and saw it will also need careful steps because of the existing language packs. We have to log all these variable changes once, and LangPackManager will do it for N language files. Only new/modified strings will need to be translated. The necessary steps will be reported by the LangPackManager automatically. Thus, this task must be done by one person only (any volunteer?).
Think PinkPost v40b03 Patches

---

quote:

---

Originally posted by ruirib


I would like to help in some way. Not sure what you meant about this and I do have some time limitations. But I'd like to help.

---

quote:

---

Originally posted by Nathan

I will also put my name forward.

---