win_installer

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
finish page prompts user to restart LAMS so the effects of the language pack can take effect

updated the build.txt for the language pack to include instructions for updating the DictionarydateCreated row in the lams_configuration table

the section to install the language pack (the only section) is now compulsory

Cosmetic change, the 'branding test near the bottom of each installer page no longer displays "Nullsoft installer version....." but instead "Lams-Language-pack ...."

updates the Dictionary date created row in lams_configuration with the lates date of the language pack

Added in the Language-Pack-BUILD.txt which describes the steps needed to compile and run the language pack, also changed the date for the language pack for 20/12/2006

    • -0
    • +17
    ./Language-Pack-BUILD.txt
These files no longer in use, they were from earlier failed attempts to insert into the database

[LI-35] Now language-pack.nsi finally updates the rows in lams_supported_local with the correct utf-8 values, thanks to a non-procedural sql sript that Fiona made, which can be run in ant

    • -0
    • +47
    ./src/updateLocales.sql
encoding for insertLocale.sql changed to utf-8 and cleaned up

Enabled registry ckecks an updates

Changed the language pack to not use the sql procedures at all, because they do not seem to work in NSIS or ant, instead, the rows are updated from within the nsis code, and there is a list called languages.txt that contains all the current languages in the form:

[language_iso_code]-[country_iso_code]-[description]-[direction]

The language.txt file and the language-pack.nsi must be encoded with utf-8

Changed the language pack to not use the sql procedures at all, because they do not seem to work in NSIS or ant, instead, the rows are updated from within the nsis code, and there is a list called languages.txt that contains all the current languages in the form:

[language_iso_code]-[country_iso_code]-[description]-[direction]

The language.txt file and the language-pack.nsi must be encoded with utf-8

LI-38: Changed the function .inInstFail so it only dletes the files created by the failed installation (not retained files) and it removes the db which was made by teh failed install

Unable to use nsExec::ExecToStack when there is redirection involved. ie: nsExec::ExecToStack mysql < insertlocale.sql

Have to use ant instead, which is fairly annoying

Unable to use nsExec::ExecToStack when there is redirection involved. ie: nsExec::ExecToStack mysql < insertlocale.sql

Have to use ant instead, which is fairly annoying

    • -0
    • +18
    ./src/LanguagePack.xml
Now this actually works, inserts the language valuse if they dont already exist, however it will fail if the number of languages surpass 127, because the locale_id is a tinint(4) and will only go up to 127

undo of changes made by an accidental commit

Calling sql scripts to update the db with the new languages

Procedure to update locales table in database, calls insertlocalses repeatedly until all languages have been covered

To add a new language, you nee only to add a line:

insertLocal(language_iso_code, country_iso_code, description, direction)

sql code (for language pack) for a procedure to insert locales into the lams_supported_local if they dont already exist.

This procedure is called by updateLocales.sql

sql code (for language pack) for a procedure to insert locales into the lams_supported_local if they dont already exist.

This procedure is called by updateLocales.sql

    • -0
    • +18
    ./src/insertlocale.sql
Procedure to update locales table in database, calls insertlocalses repeatedly until all languages have been covered

To add a new language, you nee only to add a line:

insertLocal(language_iso_code, country_iso_code, description, direction)

    • -0
    • +32
    ./src/updatelocales.sql
Updater now unpacks all the llid language files for comlex activities into their respective folders

All that is needed now is SQL procedures to add rows to the lams_supported_locale where the matching language doesnt exist

Then we're done for teh language pack

Now have names for all the llid file folders

Now have names for all the llid file folders

Can now get multiple rows from the database using an array utility i found on the net. All that is needed now is to make the correct llid directories and put the required language files in

Oh, and update the database with the new language files

Finally found a way around the sql database query problem, now i can get single values from the db for the llid, still havent thought of a way to get multiple entries

Adding in a java program, to try and adress the database access problem through NSIS

    • -0
    • +55
    ./src/SQLQueryGenerator.java
Adding in a java program, to try and adress the database access problem through NSIS

    • binary
    ./src/SQLQueryGenerator.class
Working on finding a way to get the locations for the llid folders from the database in NSIS, will probably need to use a array header for NISIS