Page History

Scope

• The JobScheduler

...

This means that Unicode-characters sent to stdout or stderr by scripts or programs executed by JobScheduler will be shown correctly.

All other texts, e.g.:

• provides very limited support for Unicode.
• The product suite is moving towards Unicode and therefore the components provide different levels of support.
• The below information states the extent of Unicode support per component.

JobScheduler Engine

Job Objects

• Internally the JobScheduler works with the ISO-8859-1 encoding (Latin1) on all platforms.
• External files for job objects (jobs, job chains, orders, schedules etc.) can be submitted with

  • the ISO-8859-1 encoding

    Code Block
    language xml title Encoding sample collapse true
    <?xml version="1.0" encoding="ISO-8859-1"?> <job title="JITL Job for JobScheduler Advanced Data Exchange" order="yes" stop_on_error="no"> ... </job>

  • the UTF-8 encoding if the characters used are in the range of Unicode 0-127
    

    Code Block
    language xml title Encoding sample collapse true
    <?xml version="1.0" encoding="UTF-8"?> <job title="JITL Job for JobScheduler Advanced Data Exchange" order="yes" stop_on_error="no"> ... </job>

     

  • provided that the characters used are in scope of the JobScheduler XSD schema that limits the allowed characters. The XSD schema is available with the file ./config/scheduler.xsd and restricts characters to the pattern: [\n\r\t -~ -ÿ]*

File Order Sources

• For file name characters the same restrictions apply as for job objects.

stdout/stderr and Logging

• Characters that are outside of the above indicated scope for job objects are arbitrarily converted to ISO-8859-1.

JOE - Job Editor

• JOE creates job object files exclusively with ISO-8859-1 encoding.
• JOE can read job object files with the UTF-8 encoding and ISO-8859-1 encoding within the limits for job objects as stated above. 
• JOE relies on the fact that the file encoding corresponds to the XML header.

JID - JobScheduler Integrated Dashboard

• JID makes use of the JobScheduler database, it does not use use the JobScheduler daemon as a source of information.
• Technically JID is capable to process UTF-8 encodings, however, as the JobScheduler writes characters with UTF-8 encoding within the limits for job objects as stated above, therefore JID does not receive a more extended UTF-8 character set.

JOC - JobScheduler Operations Centre

• JOC receives answers by the XML API from JobScheduler. Such answers are UTF-8 encoded within the limits for job objects as stated above .
• Technically JOC should be capable to work with a complete UTF-8 encoding.

Relationship with Internationalization

• Starting from future Unicode support then improved internationalization will be in scope.
• As of now texts such as

• • error messages, warnings and info messages,
  • GUI texts,
  • log file entries,
  • help messages and tooltip texts
  • are
• error-, warning and info messages,
• GUI-texts,
• log-file entries,
• help- and tooltip-texts
...
are in currently (April 2013)
• • available in English and German only.

...

• A major topic on the JobScheduler road-map is the translation of all texts.
  • To this end the internationalization (i18n) of the GUIs

...

• • and translation (localization, L11n) of the interface texts

...

• • are in progress.
  • See How to make a localized version of JOE and other JobScheduler components

 Note that JOE (the JobScheduler Object Editor), which is used to create the xml-configuration for JS Objects, will create the xml-files with an encoding of ISO-8859-1. To use Unicode, this encoding has to be changed to UTF-8.