Topic Summary - Displaying 7 post(s). Click here to show all
Posted by: Dandello Posted on: Sep 23rd, 2017 at 10:05pm
I'll just use English for the Mod sections I need here until you get caught up.
Posted by: pyragony54 Posted on: Sep 23rd, 2017 at 2:35pm
Please do not go too fast. I'm not finished with the German files yet. Well, I still need a week. Then the mods have to be made synonymous yes and finally I have two German languages.
Posted by: Dandello Posted on: Sep 22nd, 2017 at 12:46pm
We're gaining on it.
It's been forever since anyone took a hard look at Setup.pl and there's at least one more form item that needs to go in. (I took it out and now realize it probably needs to go back in. Oh well. : )
Once that's handled I can go back to working on the Mods and templates needed for this site, and the Mods Rucola wants. THEN this site gets converted to 2.7 (finally). Here I'll have an error log to catch more bugs with.
Posted by: pyragony54 Posted on: Sep 22nd, 2017 at 5:36am
I just downloaded Build 1903. Still much work, but looks very good.
Posted by: Dandello Posted on: Sep 20th, 2017 at 3:25pm
Okay - getting proper multilingual support for Setup.pl is going to require rethinking how the additional Language Packs get installed.
Current thoughts:
Have all the translated Setup language files in their own folder and then the new admin installs the full language pack using YaBMod before going to Convert.
Have the admin install the additional Language packs the old fashioned way - by copying the files into the Language/* folder and Setup.pl and/or Settings_Main.pm creating the Lang.lng (or the data in Lang.lng gets put into Settings.pm) I think this would require that the 'language name' info be put into a .txt file in the Language/* folder so YaBB can find it.
Thoughts? Suggestions?
Posted by: Dandello Posted on: Sep 19th, 2017 at 1:05pm
Posted by: Dandello Posted on: Sep 16th, 2017 at 2:43pm
I'm going through Setup.pl for multi-language support and realized that although YaBB uses all those paths stored in Paths.pm, only the YaBB main url, and the url and path to the yabbfiles, actually need to inputted into Setup.pl. All the other paths are 'hardcoded'.
So expect some serious simplification when I get done with Setup.pl. (Countered, of course, with complexification with adding language hashes.)