CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Localisation issue on install
Pages: [1]

Author Topic: Localisation issue on install  (Read 735 times)

Upperholme

  • Administrator
  • Ask me questions
  • *****
  • Posts: 568
  • Karma: 8
    • MC3
  • CiviCRM version: 4.x
  • CMS version: Drupal 6.x/7.x, Wordpress, Joomla
Localisation issue on install
February 08, 2012, 04:43:42 am
I think I've reported this before with previous versions, but no harm in flagging it up again in relation to 4.1 with the goal of getting it fixed.

When doing a new install, the user is presented with the installation screen (sample attached) that provides a summary of lots of useful information, the fields to set the DB credentials, and so on. It also includes, under "Other Settings", a line about the language of basic data, providing the user with a drop-down menu. thus menu has only one option available (US English), and the text goes on to explain that by downloading and installing the l10n files other languages can be "added here".

This seems to be a clear statement that by installing the l10n files other languages will be made available to the installer, and will appear in the drop-down menu. In reality, installing the l10n files, as described in the wiki at http://wiki.civicrm.org/confluence/display/CRMDOC41/CiviCRM+Localisation has no effect. The only installation language available remains US English.

Whilst not critical, as Localisation can be done post installation, in my view the installation process should be flawless if it is not to confuse new adopters of CiviCRM who will be more likely to be confused and concerned with oddities such as this. It's as much a marketing issue as it is a technical one.

In terms of what happens with the templates_c directory there seems to be some confusion also. Upon the default install, the templates_c directory includes a single sub-directory, entitled not unreasonably en_US. After the install, having localised the installation to the UK options, there is still only one sub-directory in templates_c. however, looking inside the en_US directory, a new directory appears called en_GB. Would it not be better/clearer if the en_GB directory was at the same level as the en_US directory in templates_c? Again, not critical, but a usability issue.
Graham Mitchell
http://mc3.coop

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Localisation issue on install

This forum was archived on 2017-11-26.