frePPLev2.0
open source Production PLanning
  • Home
  • Documentation
    • Getting started
    • Modeling guide
    • User guide
    • Installation guide
    • Developer guide
    • FAQ
  • C++ API

Internationalization

This section contains some notes on topics relevant for the internationalization.

  1. It is highly recommended to use UTF-8 as the encoding of character data.
    Using it consistently for your locale, XML-files and databases helps in avoiding headaches and sleepless nights.

  2. When creating a database for the Django user interface, make sure the character encoding properly support utf-8.
    When using MySQL, this is easiest done by setting the database parameter “default character set” to “utf-8″ and “default collate” to “utf8_general_cs”. Another pitfall when using frePPLe with MySQL is that the string comparison in some MySQL collations is case insensitive, which frePPLe always handles data strings in a case sensitive way.
    When using Oracle, this is controlled through the database “character set” and “national character set”.
    PostgreSQL provides the ‘encoding’ setting on the database.
    SQLite is unicode-ready by default.

  3. Xerces-C will transcode the input XML data from the input encoding (typically specified with a <?xml version="1.0" encoding="UTF-8" ?> header line) to the locale of your *nix shell or Windows environment.
    Xerces-C has intrinsic support for ASCII, UTF-8, UTF-16 (Big/Small Endian), UTF-32(Big/Small Endian), EBCDIC code pages IBM037, IBM1047 and IBM1140 encodings, ISO-8859-1 (aka Latin1) and Windows-1252.
    This means that it can parse input XML files in these encodings. For more exotic encodings a special configuration and compilation is required: see the Xerces-C documentation for more details.

  4. Internally frePPLe stores string data in the locale of your environment: see the documentation on the setlocale C function.
    For most modern Linux distributions the default setting is a UTF-8 encoded locale, meaning that every unicode character can be represented. The environment variable LC_ALL can be used to specify a suitable locale.
    On windows the default locale is some ANSI default codepage (which can represent a limited set of characters only).

  5. When exporting data out of frePPLe, no data conversion to specific encodings is done.
    All output will be in the locale of your environment.

  6. FrePPLe internally uses byte-based string manipulation routines, not character-based.
    For UTF-8 encoding and the single-byte codepages this works fine, but with multi-byte encodings such UTF-16 and UTF-32 this won’t work any more. Such encodings are NOT supported by frePPLe.
    • Getting started
    • Modeling guide
      • Simplified domain model
      • Detailed domain model
      • Environment variables
      • Python interpreter
      • Global parameters
      • Buffer
      • Calendar
      • Customer
      • Demand
      • Flow
      • Item
      • Load
      • Location
      • Operation
      • Suboperation
      • Operationplan
      • Problem
      • Resource
      • SetupMatrix
      • Skill
      • Resource skill
      • Solver
      • Extension modules
        • Forecast module
        • REST web service module
        • Linear programming solver module
        • OpenERP connector module
    • User guide
      • Main features
      • Supported browsers
      • Getting around
        • Logging in
        • Logging out
        • Changing password
        • Navigation
          • Menu bar
          • Jump search
          • Context menus
          • Browser bookmarks
        • Filtering data
        • Sorting data
        • Selecting time buckets
        • Exporting data
        • Importing data
        • User preferences
        • User permissions and roles
      • Screens
        • Data input
        • Supply Path / Where Used
        • Comments
        • History – Audit trail
        • Plan analysis
          • Problem report
          • Constraint report
          • Inventory report
          • Inventory detail report
          • Resource report
          • Resource Gantt report
          • Resource detail report
          • Operation report
          • Operation detail report
          • Demand report
          • Demand detail report
          • Demand Gantt report
          • Forecast report
          • Performance indicator report
        • Execute
      • Batch commands
        • manage.py (manage.exe on Windows)
        • frepple (frepple.exe on Windows)
        • freppleservice.exe (Windows only)
    • Installation guide
      • Windows installer
      • Compiling on Windows
      • Linux binary packages
      • Compiling on Linux
      • Compiling on debian-based linux
      • Compiling on Red Hat based Linux
      • Compiling from the subversion source code repository
      • Running the VMWare virtual machine
      • Other platforms
      • Configuring the user interface
      • Configuring multiple models in the user interface
      • Configuring as a Python extension module
    • FAQ
    • Developer guide
      • Code structure
      • Class diagram
      • Solver
        • Solver features
        • Planning algorithm
          • Top level loop
          • Demand solver
          • Buffer solver
          • Flow solver
          • Load solver
          • Operation solver
          • Resource solver
        • Cluster and level algorithm
      • Extension modules
      • Version control
      • Style guide
      • Portability
      • Security
      • Internationalization
      • Translating the user interface
      • Adding or customizing a report
      • Unit tests
        • buffer_procure_1
        • calendar
        • callback
        • cluster
        • constraints_combined_1
        • constraints_combined_2
        • constraints_leadtime_1
        • constraints_material_1
        • constraints_material_2
        • constraints_material_3
        • constraints_material_4
        • constraints_resource_1
        • constraints_resource_2
        • constraints_resource_3
        • constraints_resource_4
        • constraints_resource_5
        • datetime
        • deletion
        • demand_policy
        • flow_alternate_1
        • flow_alternate_2
        • flow_effective
        • forecast_1
        • forecast_2
        • forecast_3
        • forecast_4
        • forecast_5
        • forecast_6
        • jobshop
        • load_alternate
        • load_effective
        • lpsolver_1
        • multithreading
        • name
        • operation_alternate
        • operation_available
        • operation_effective
        • operation_pre_post
        • operation_routing
        • pegging
        • problems
        • python_1
        • python_2
        • python_3
        • safety_stock
        • sample_module
        • scalability_1
        • scalability_2
        • scalability_3
        • setup_1
        • setup_2
        • skill
        • xml
        • xml_remote
    • License
      • GNU Affero General Public License
      • GNU Free Documentation License
    • Third party add-ons
  • Copyright © 2010-2013 frePPLe bvba