language-pack.nsi

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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 ...."

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

  1. … 2 more files in changeset.
[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

  1. … 2 more files in changeset.
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

  1. … 1 more file in changeset.
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

  1. … 2 more files in changeset.
Calling sql scripts to update the db with the new languages

  1. … 1 more file in changeset.
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

  1. … 2 more files in changeset.
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

  1. … 1 more file in changeset.
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

Updator now extracts all the xx.xml files required for flahs to $INSTDIR\jboss-4.0.2\server\default\deploy\lams.ear\lams-central.war\flashxml

Great Success! This is nice!

All language files for projects are now unpacking correctly, ie lams_blah/conf/language

Added date string utility so the date can be entered as a string, but can still be compared as a version in the registry in the form yyyy-dd-mm

Uses a date instead of a vertsion to check for newer language pack versions

Added backup functionality, existing language files are zipped to C:\lams\jboss-4.0.2\server\default\deploy\lams.ear\lams-dictionary.jar\backup\

Updator checks for existing newer versions than the current, then applies this version to the registry, it also checks if there is a lams version 2.x installed

Skeleton for the language pack updator

    • -0
    • +218
    ./language-pack.nsi
  1. … 1 more file in changeset.