DOCSLIB.ORG

Civicrm Localization

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Civicrm Localization Blog FAQ Documentation Forums Issue Tracker IRC CiviCRM Localisation Added by Piotr Szotkowski , last edited by Piotr Szotkowski on Jun 04, 2009 Introduction User Language (Translations) Other Localisation Settings Date Formats Date Format Examples Countries and Provinces Postal Address Formatting Currency and Monetary Display Formats Helping with CiviCRM Localisations How it Works Translating CiviCRM's Drupal Menu Items Web -based Localisation Offline Translation Localisation forums and "crm -translators" Mailing List (see also http://wiki.civicrm.org/confluence/display/CRMDOC/Localization ) Introduction One of our goals is to make CiviCRM as usable as possible - which means get it fully localised into any languages that our users find useful and make CiviCRM configurable in all the places that are locale-dependent. To achieve this, CiviCRM uses gettext for text localisation and configuration options for date/money/address formats and the like. This approach assures that CiviCRM should be easily localisable into wide variety of languages (also the ones using non-Latin scripts/alphabets). This page explains how to set up CiviCRM to run in one of the other supported languages and how to contribute new and/or updated translations into new languages back to CiviCRM. Applies to Version 1.6 or Later This documentation is applicable to CiviCRM v1.6 or later. For prior versions, check this page . User Language (Translations) CiviCRM has been translated into a number of different languages. These translations are contributed by community members - so your first step is to determine if a complete translation exists for the current version by visiting the Translation Server home page . If you find a completed translation, note the locale code of the translation, and continue with the steps below to configure your installation. Otherwise, check the section on Helping with CiviCRM Localisations below. Locale Codes Locale codes consist of the language abbreviation followed by the country abbreviation. For example, en_US is the code for the United States English locale, while fr_CA is the Canadian French locale. To configure CiviCRM to use an existing translation: 1. Download the translations distribution - civicrm-<version>-l10n.tar.gz - from the CiviCRM Sourceforge downloads site . This tarball contains all files for the latest available translations. 2. Uncompress the tarball and you will see a directory called civicrm, containing two subdirectories called l10n and sql. The l10n directory containsa set of sub-directories named using their locale codes. (Example: the Canadian French translation files will located in /civicrm/l10n/fr_CA) 3. Copy this l10n directory, together with all its subdirectories into your civiCRM codebase root directory. (note if creating the l10n folder manually it should be ell-ten-n, not capital-I-ten-n) - For Joomla this would be site_root/administrator/components/com_civicrm/civicrm . So if you wanted the en_GB language it would look like this site_root/administrator/components/com_civicrm/civicrm/l10n/en_GB/ - For Drupal this would be site_root/modules/civicrm . So if you wanted the en_GB language it would look like this site_root/modules/civicrm/l10n/en_GB/ 4. Login to CiviCRM (as a user with "administer CiviCRM permissions"). 5. Go to Administer CiviCRM » Global Settings » Localisation 6. You should now be able to see and select all the localization options in the Default Language and Monetary Locale drop-down menus. If you don't, and instead can just see the default 'English (USA)' option, check the preceding steps as the drop-down options are set by the directories under your l10n directory. Also be sure to confirm that the l10n directory is correctly named as l10n (that is: el-ten-en and not eye-ten-en). 7. The other settings on this page are described below. You can review them and adjust as needed. Be sure to save your changes when you're done. Your CiviCRM screens should now appear in the selected language. If the underlying server has the proper locale generated, the full and abbreviated month and day names will also be localised properly. Any text that has NOT been translated in the translation files will appear in the default English language. If you see English text after setting a different language, you may need to add to the translation. Refer to the section on Helping with CiviCRM Localisations below. Other Localisation Settings Date Formats One of the aspects of localisation is the display and input format for dates. By default, CiviCRM displays the dates using the American formats, but this can be modified to match your preferred formats. You can define the formats for the following types of date display: Complete Date and Time (dates that contain year, month, day and time) Complete Date (dates that contain year, month and day) Month and Year Year Only Date Formats Use POSIX Sequence Codes Date formats are specified using the standard POSIX % -prepended sequences . You should review these formatting codes and the Date Formatting Examples below before attempting to modify the date formats. 1. Login to CiviCRM (as a user with "administer CiviCRM permissions"). 2. Go to Administer CiviCRM » Global Settings » Date Formatting 3. Update formatting patterns as needed and Save your changes. Date Format Examples The default American format for Complete Date and Time is: %B %E%f, %Y %l:%M %P ...which, for the date of 2005-07-13, gets expanded to 'July 13th, 2005 2:26 PM'. European users might want to redefine this to: %E %B %Y, %k:%M ...which would display '13 July 2005, 14:26' instead (note the switch from 12-hour to 24-hour clock and dropping of the AM/PM display). The default American format for Complete Date is %B %E%f, %Y ...which, for the date of 2005-07-13, gets expanded to 'July 13th, 2005'. Typical European settings would have this format changed; it could look like this: %E %B %Y ...which would get expanded to '13 July 2005' (or '13 lipiec 2005' if user language is set to Polish - pl_PL). The Date Input Field formatting options define the order of the date and date-time drop-downs in various CiviCRM forms (for example, contact's birth date or scheduled meetings' date-times): The default layouts are: Complete Date and Time: %b %d %Y, %I : %M %P Complete Date: %b %d %Y These defaults provide the user with six drop-downs: abbreviated month name (%b), day (%d), year (%Y), 12-hour-clock hour (%I), minute (%M) and an AM/PM selector (%P). European users might want to redefine these to: Complete Date and Time: %d %b %Y, %H : %M Complete Date: %d %b %Y Which would display the day before the abbreviated month, switch to 24-hour-based hour drop-down (%H) and drop the AM/PM selector. Countries and Provinces The installed CiviCRM database contains both an ISO 3166 -1-compliant list of countries, and a ful, ISO 3166 -2-compliant list of provinces (states, departments, voivodships, etc.). You can configure the selections provided in address input fields for your installation (based on the geographic distribution of the address records you plan on storing). You can: Set a Default Country . This country will be selected by default when entering new addresses. Limit the list of Available Countries offered in Country drop-down lists on address input forms. Limit the Countries whose States and Provinces are offered on address input forms. 1. Login to CiviCRM (as a user with "administer CiviCRM permissions"). 2. Go to Administer CiviCRM » Global Settings » Localisation 3. Update the fields in the Contact Address Fields - Selection Values section as needed and Save your changes. Postal Address Formatting In various countries, postal addresses are written differently. CiviCRM allows you to modify the default United States format to meet the requirements of your installation. This option is best explained by example. The American default looks like this: Default Address Format {street_address} {supplemental_address_1} {supplemental_address_2} {city}{, }{state_province}{ }{postal_code} {country} The general rules are as follows: Every { ...token... } will be replaced with the token 's value (keeping anything else inside the curly braces intact). If the value of a given token is missing, the whole { ... } construct will be dropped. Any { non-token } construct will be turned into non-token if, after tokens are replaced, it has content on both sides (i.e., it will be dropped if on the beginning or end of any line). If there's no city , { city}{, }{state_province}{ } {postal_code } will turn first into { , }California{ }12345 and then into California 12345 . If, after token replacements, there are any consecutive { non-token } constructs, the first one's contents will replace the whole series. For example, if there's no state_province , { city}{, }{state_province}{ }{postal_code } will first turn into San Francisco{, }{ }12345 and then into San Francisco, 12345 . For example, Polish users, who usually don't write the vovidoship names in the address, might want to change the Address Formatting to: Address Format without Province {street_address} {supplemental_address_1} {supplemental_address_2} {postal_code}{ }{city} {country} # Login to CiviCRM (as a user with "administer CiviCRM permissions"). 1. Go to Administer CiviCRM » Global Settings » Address Settings 2. Update formatting patterns as needed and Save your changes. Currency and Monetary Display Formats CiviCRM currently supports a single currency per site. The default currency is USD, but you can select the appropriate currency for your site under Global Settings. You can also control the way that monetary values are displayed - both the number format and the arrangement of currency symbols relative to the amount. The 'look' of the numeric value (amount) depends on the selected Monetary Locale setting. As with User Language, thiis setting takes a locale (like 'en_US', 'de_DE' or 'pl_PL') and asks the underlying operating system to format the amount accordingly: Monetary Locale Examples The amount of 1234567 dollars and 89 cents will be displayed as '1,234,567.89' with an 'en_US' locale, as '1.234.567,89' with a 'pl_PL' one and as '12,34,567.89' with an 'en_IN' one.
Load more

Recommended publications
  • Download the Specification
    Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 November 2020 Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 Copyright © 2014, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
    [Show full text]
  • Potranslator Documentation Release 1.1.5
    potranslator Documentation Release 1.1.5 SekouD Nov 01, 2018 Contents 1 potranslator 3 1.1 Supported Languages..........................................3 1.2 Quick Start for auto-translation with potranslator............................6 1.3 Basic Features..............................................7 1.4 Optional features.............................................7 1.5 Installation................................................8 1.6 Commands, options, environment variables...............................8 1.7 License..................................................9 1.8 Original..................................................9 1.9 CHANGES................................................9 2 Installation 11 2.1 Stable release............................................... 11 2.2 From sources............................................... 11 3 Usage 13 3.1 From a Python program......................................... 13 3.2 Commands, options, environment variables............................... 13 4 Package Api Documentation for potranslator 17 4.1 API Reference for the classes in potranslator.potranslator.py...................... 17 5 Contributing 19 5.1 Types of Contributions.......................................... 19 5.2 Get Started!................................................ 20 5.3 Pull Request Guidelines......................................... 21 5.4 Tips.................................................... 21 5.5 Deploying................................................ 21 6 Credits 23 6.1 Development Lead...........................................
    [Show full text]
  • Open Source License and Copyright Information for Gplv3 and Lgplv3
    Open Source License and Copyright Information for GPLv3/LGPLv3 Dell EMC PowerStore Open Source License and Copyright Information for GPLv3/LGPLv3 June 2021 Rev A02 Revisions Revisions Date Description May 2020 Initial release December 2020 Version updates for some licenses, and addition and deletion of other components June, 2021 Version updates for some licenses, and addition and deletion of other components The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2020-2021 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [6/1/2021] [Open Source License and Copyright Information for GPLv3/LGPLv3] [Rev A02] 2 Dell EMC PowerStore: Open Source License and Copyright Information for GPLv3/LGPLv3 Table of contents Table of contents Revisions............................................................................................................................................................................. 2 Table of contents ...............................................................................................................................................................
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]
  • Design and Implementation of an End-User Programming Software System to Create and Deploy Cross-Platform Mobile Mashups
    Degree Project Design and implementation of an end-user programming software system to create and deploy cross-platform mobile mashups Sandra Kaltofen 2010-11-09 Subject: Computer Science Level: Bachelor Course code: DA3003 Abstract Significant changes in mobile computing are continuously influenced by the enhanced features of mobile devices and software applications. The release of open platforms that allow the creation of advanced mobile applications are the triggers for recent developments with regard to the topics of end-user mobile application frameworks and mobile mashup creation. Inspired by these efforts, this thesis identifies some of the problems in this field and presents a solution for a cross-platform end-user programming software system that enables the creation of mobile mashups. Keywords: Android, Cross-platform mobile frameworks, Google Web Toolkit, iPhone, Java, JavaScript, Mashups, Mobile mashups, Web 2.0 APIs, Web development frameworks ii Table of Contents 1 Introduction ................................................................................................................ 1 1.1 Definition of the problem .................................................................................... 3 1.2 Structure of the thesis .......................................................................................... 3 1.3 Delimitations ....................................................................................................... 4 2 State of the art............................................................................................................
    [Show full text]
  • C/C++ Compile Guide
    WizFi630S Guide C/C++ Compile Guide (Version 1.0.0) © 2019 WIZnet Co., Ltd. All Rights Reserved. For more information, please visit our website at http://www.wiznet.io/ © Copyright 2019 WIZnet Co., Ltd. All rights reserved. 1 WizFi630S Guide Document Revision History Date Revision Changes 2019-11-25 1.0 Release © Copyright 2019 WIZnet Co., Ltd. All rights reserved. 2 WizFi630S Guide Contents 1. Overview ................................................................................................................. 4 2. Download ................................................................................................................ 4 2.1 Prerequisites .................................................................................................. 4 2.2 Packages for Building Environment .......................................................... 4 2.3 OpenWRT Firmware Repository................................................................. 6 2.4 Menuconfig .................................................................................................... 7 3. Write C Code........................................................................................................... 7 3.1 Helloworld ...................................................................................................... 7 3.2 Make the Environment Script .................................................................... 8 4. Cross Compile ......................................................................................................... 8 4.1
    [Show full text]
  • Enhancing Open-Source Localization
    San Jose State University SJSU ScholarWorks Master's Projects Master's Theses and Graduate Research 2010 Enhancing open-source localization Farzana Forhad San Jose State University Follow this and additional works at: https://scholarworks.sjsu.edu/etd_projects Part of the Computer Sciences Commons Recommended Citation Forhad, Farzana, "Enhancing open-source localization" (2010). Master's Projects. 57. DOI: https://doi.org/10.31979/etd.5kf8-9ykm https://scholarworks.sjsu.edu/etd_projects/57 This Master's Project is brought to you for free and open access by the Master's Theses and Graduate Research at SJSU ScholarWorks. It has been accepted for inclusion in Master's Projects by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. Enhancing open-source localization CS298 Report Enhancing open-source localization A Writing Project Presented to The Faculty of computer Science San Jose State University In Partial Fulfillment of the Requirement for the Degree Master of Science By Farzana Forhad May 2010 - 1 - Enhancing open-source localization CS298 Report © 2010 Farzana Forhad - 2 - Enhancing open-source localization CS298 Report APPROVED FOR THE DEPARTMENT OF COMPUTER SCIENCE Dr. Chris Pollett Dr. Robert Chun Frank Butt - 3 - Enhancing open-source localization CS298 Report ABSTRACT Pootle is a web portal which is designed to be a web translation tool. We can run Pootle like an internet server and run a local copy on an intranet. Pootle has a user friendly interface which ensures better quality and easier translation of projects. Users can log into the Pootle and create their own projects under any language, and they can also add or retrieve any language from any project or any project from any language.
    [Show full text]
  • If Loop in Unix Shell Script Examples
    If Loop In Unix Shell Script Examples Flin remains merging: she bays her plica fumigating too resistively? Denticulate and old-established Harvie never cross-sections deridingly when Job invalid his focussing. In-and-in Bentley plebeianizing munificently or yarns dithyrambically when Wynton is isobaric. This type of unix shell A Unix shell or both a command interpreter made a programming language. You jump to swallow a little between check and statement. If ear is no existing variable, simply sit them. If possible example that first file to be processed is programc the puppet will expand. UK on bash if statement with array passport risk my application. You have modified version will be looping in localstorage so on your system, a false condition can we have. Yes there are often loops, unix shell script! The example shell? Bash IF Syntax & Examples Tutorial Kart. Without this capability, so assignments to this variable have no effect. We shall learn about the syntax of if statement and get a thorough understanding of it with the help of examples. First cell's just rise at the example given case and fang a goto statement in story that maybe you choose a. How deeply your loop examples are converted files can be looping? Introduction to if. Kill ring into words and letters and in unix shell and osx in if performance, loop in script if there is discussed in groups of. The loop through a numeric operations on ibm kc alerts notifies you might think that did not append a digit. From chart above examples of the conditional statement if, those need shell! Instead, here time will teach a quick method, this use does talk matter.
    [Show full text]
  • SIME Installation and Configuration Manual
    SIME Installation and Configuration Manual Version 1.0 August 2015 1 Contents Introduction .................................................................................................................................................. 3 Target audience ........................................................................................................................................ 3 Scope of this document ............................................................................................................................ 3 What is NOT covered in this manual ........................................................................................................ 3 Software Stack .......................................................................................................................................... 3 Linux Installation ........................................................................................................................................... 4 Hardware Requisites ................................................................................................................................. 4 Operating System ...................................................................................................................................... 4 Database Server ........................................................................................................................................ 4 Web Server...............................................................................................................................................
    [Show full text]
  • R 3.1 Open Source Packages
    R 3.1 Open Source Packages Package Version Purpose accountsservice 0.6.15-2ubuntu9.3 query and manipulate user account information acpid 1:2.0.10-1ubuntu3 Advanced Configuration and Power Interface event daemon adduser 3.113ubuntu2 add and remove users and groups apport 2.0.1-0ubuntu12 automatically generate crash reports for debugging apport-symptoms 0.16 symptom scripts for apport apt 0.8.16~exp12ubuntu10.27 commandline package manager aptitude 0.6.6-1ubuntu1 Terminal-based package manager (terminal interface only) apt-utils 0.8.16~exp12ubuntu10.27 package managment related utility programs apt-xapian-index 0.44ubuntu5 maintenance and search tools for a Xapian index of Debian packages at 3.1.13-1ubuntu1 Delayed job execution and batch processing authbind 1.2.0build3 Allows non-root programs to bind() to low ports base-files 6.5ubuntu6.2 Debian base system miscellaneous files base-passwd 3.5.24 Debian base system master password and group files bash 4.2-2ubuntu2.6 GNU Bourne Again Shell bash-completion 1:1.3-1ubuntu8 programmable completion for the bash shell bc 1.06.95-2 The GNU bc arbitrary precision calculator language bind9-host 1:9.8.1.dfsg.P1-4ubuntu0.16 Version of 'host' bundled with BIND 9.X binutils 2.22-6ubuntu1.4 GNU assembler, linker and binary utilities bsdmainutils 8.2.3ubuntu1 collection of more utilities from FreeBSD bsdutils 1:2.20.1-1ubuntu3 collection of more utilities from FreeBSD busybox-initramfs 1:1.18.5-1ubuntu4 Standalone shell setup for initramfs busybox-static 1:1.18.5-1ubuntu4 Standalone rescue shell with tons of built-in utilities bzip2 1.0.6-1 High-quality block-sorting file compressor - utilities ca-certificates 20111211 Common CA certificates ca-certificates-java 20110912ubuntu6 Common CA certificates (JKS keystore) checkpolicy 2.1.0-1.1 SELinux policy compiler command-not-found 0.2.46ubuntu6 Suggest installation of packages in interactive bash sessions command-not-found-data 0.2.46ubuntu6 Set of data files for command-not-found.
    [Show full text]
  • SECUMOBI SERVER Technical Description
    SECUMOBI SERVER Technical Description Contents SIP Server 3 Media Relay 10 Dimensioning of the Hardware 18 SIP server 18 Media Proxy 18 Page 2 of 18 SIP Server Operatingsystem: Debian https://www.debian.org/ Application: openSIPS http://www.opensips.org/ OpenSIPS is built and installed from source code. The operating system is installed with the following packages: Package Description acpi displays information on ACPI devices acpi-support-base scripts for handling base ACPI events such as the power button acpid Advanced Configuration and Power Interface event daemon adduser add and remove users and groups anthy-common input method for Japanese - common files and dictionary apt Advanced front-end for dpkg apt -utils APT utility programs aptitude terminal-based package manager (terminal interface only) autopoint The autopoint program from GNU gettext backup -manager command -line backup tool base-files Debian base system miscellaneous files base-passwd Debian base system master password and group files bash The GNU Bourne Again SHell bc The GNU bc arbitrary precision calculator language binutils The GNU assembler, linker and binary utilities bison A parser generator that is compatible with YACC bsdmainutils collection of more utilities from FreeBSD bsdutils Basic utilities from 4.4BSD-Lite build -essential Informational list of build -essential packages busybox Tiny utilities for small and embedded systems bzip2 high-quality block-sorting file compressor - utilities ca-certificates Common CA certificates console-setup console font and keymap
    [Show full text]
  • Learning the Bash Shell, 3Rd Edition
    1 Learning the bash Shell, 3rd Edition Table of Contents 2 Preface bash Versions Summary of bash Features Intended Audience Code Examples Chapter Summary Conventions Used in This Handbook We'd Like to Hear from You Using Code Examples Safari Enabled Acknowledgments for the First Edition Acknowledgments for the Second Edition Acknowledgments for the Third Edition 1. bash Basics 3 1.1. What Is a Shell? 1.2. Scope of This Book 1.3. History of UNIX Shells 1.3.1. The Bourne Again Shell 1.3.2. Features of bash 1.4. Getting bash 1.5. Interactive Shell Use 1.5.1. Commands, Arguments, and Options 1.6. Files 1.6.1. Directories 1.6.2. Filenames, Wildcards, and Pathname Expansion 1.6.3. Brace Expansion 1.7. Input and Output 1.7.1. Standard I/O 1.7.2. I/O Redirection 1.7.3. Pipelines 1.8. Background Jobs 1.8.1. Background I/O 1.8.2. Background Jobs and Priorities 1.9. Special Characters and Quoting 1.9.1. Quoting 1.9.2. Backslash-Escaping 1.9.3. Quoting Quotation Marks 1.9.4. Continuing Lines 1.9.5. Control Keys 4 1.10. Help 2. Command-Line Editing 2.1. Enabling Command-Line Editing 2.2. The History List 2.3. emacs Editing Mode 2.3.1. Basic Commands 2.3.2. Word Commands 2.3.3. Line Commands 2.3.4. Moving Around in the History List 2.3.5. Textual Completion 2.3.6. Miscellaneous Commands 2.4. vi Editing Mode 2.4.1.
    [Show full text]