## Updating from v1 to v2

The following changes were made to the Language package between v1 and v2.

### Class methods non-static

The `Language` and `Text` classes have been refactored to follow an object oriented approach instead of using static methods.
Instantiating the `Text` class requires a `Language` instance to be injected.

The `Text::_()` method remains static and will proxy to the object oriented API as long as a Language instance is
available via `Language::getInstance()`.

### Language requires base path to be defined

In v1, applications were required to define a `JPATH_ROOT` constant for the base path to search for languages in. In 2.x,
you are required to pass the base path as the first parameter in the `Language` constructor (and getInstance() method).

### _QQ_ constant removed

The `_QQ_` constant was previously an allowed escape sequence for quotes in language files.  Support for this constant
has been removed. Double quotes in files should either be escaped (`\"`) or HTML encoded (`"`) (if displayed in an
HTML context).

### Language::_ and Text::_ deprecated

The `_` method in `Language` and `Text` has been deprecated in favor of `translate`.

### Language::getInstance() removed

The `getInstance()` method in `Language` has been removed.  Use `LanguageFactory::getLanguage()` instead.

### Language::setLanguage() removed

The `setLanguage()` method in `Language` has been removed.  A new Language instance in the new language should be instantiated
instead.

### Stemmer::getInstance() removed

The `getInstance()` method in `Stemmer` has been removed.  Use `LanguageFactory::getStemmer()` instead.

### Text::alt() signature changed

The `alt()` method's signature has had a backward compatibility breaking change.  A `$parameters` parameter has been added and is
now the third parameter in the method signature.  This affects calls to the method which included the `$jsSafe` and
`$interpretBackSlashes` parameters.

### Text::script() removed

The `script()` method in `Text` has been removed, as well as support for the internal JavaScript store.  Downstream applications
should implement this feature if needed.

### Methods for CMS Search Component

The methods `getUpperLimitSearchWord`, `getSearchDisplayedCharactersNumber`, `getLowerLimitSearchWord` and `getIgnoredSearchWords`
have all been removed as well as the associated methods to get and set their callback functions. These should be implemented
by the user if required.

### LocaliseInterface
A `LocaliseInterface` has been introduced as a standard way to set the way to set functions for `Language::getPluralSuffixes()`
and `Language::transliterate()`. Both of these must now be set in the language's localise.php file (this was possible in
version 1 however could optionally could have callback functions set if such a file didn't exist).

Localise files now MUST implement the LocaliseInterface to be recognised. An base class is available and is suitable for
many Western Languages.