Location: PHPKode > scripts > LanguageSys > languagesys/doc/en/migration.htm
  <link rel="stylesheet" href="inline.css" />
  <div id="body">
  <h1>Migrating from LanguageSys 1.0.0 to 1.0.2</h1>
   To migrate from LanguageSys 1.0.0 to 1.0.2 you just have to re-precompile the precompiled
   language files. This is because of the new method was implemented to access the precompiled
   language files which isn't comaptible with the old precompiled language files. Also the
   new precompiled language files arn't compatible with older versions of LanguageSys.<br />
   The normal language files (not precompiled) are not affected, so you do not have to
   change anything else.
  <h1>Migration from LanguageSys 1.0.2 to 1.1.1</h1>
   To migrate from LanguageSys 1.0.2 to 1.1.1 you just have to rename the language files.
   This is because the POSIX locale codes are not longer of use as in 1.0.2, now LanguageSys
   uses tags as defined by the <a href="http://www.faqs.org/rfcs/rfc1766.html" lang="en" target="_blank">RFC 1766</a>.
   This has some advantages, eg. you can use more diferent languages than before and nearly all combinations are possible.
   Additional to this it is more compatible with other protocolls, eg the HTTP protocoll, focused on the language identification.<br />
   To get the language files working with LanguageSys 1.1.1 you just can replace the underscore in the names of the language files by an hyphen.
   So, en_GB migrates to en-GB.<br />
   <i>Tipp: Because of general tags like en_EN are not longer possible, you now can use JUST the languages name, for example you can name this file "en.ini" instead of "en_EN.ini".</i><br />
   Also this affects the use= tag inside of the language files, so if a language file referres to an other, you have to replace
   the value of the use= tag with the new name of the language file.<br />
   Other positions are not affected by this release, so you do not have to change anything else.
Return current item: LanguageSys