Uses of Package
org.pepstock.charba.client.intl

Packages that use org.pepstock.charba.client.intl

Package	Description
org.pepstock.charba.client.adapters	Contains all classes to interact with date adapters implemented by CHART.JS to be abstract from date time java script library to use.
org.pepstock.charba.client.configuration	Contains all elements to configure a chart instance (know as chart options at instance level).
org.pepstock.charba.client.defaults	Contains all interfaces need to provide defaults values of the chart options.
org.pepstock.charba.client.defaults.chart	Contains the default values of chart options based on type of chart instance.
org.pepstock.charba.client.defaults.globals	Contains the default values of chart options for all chart types (CHART.JS options defaults).
org.pepstock.charba.client.intl	Contains classes in order to use the ECMAScript Internationalization API, which provides language sensitive number formatting, and date and time formatting.
org.pepstock.charba.client.intl.enums	Contains enumerations to use in order to configure the ECMAScript Internationalization API options.
org.pepstock.charba.client.options	Contains all elements to configure charts at global level (know as chart global options).

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.adapters

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.configuration

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.defaults

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.defaults.chart

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.defaults.globals

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.intl

Class and Description
CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.
CLocaleBuilder The builder is used to build instances of CLocale from values configured by the setters. A CLocale object created by a builder is well-formed and can be transformed to a well-formed IETF BCP 47 language and it's also cached.
DateTimeFormatOptions The object configures a date time formatter. See MDN for more details.
DateTimeFormatOptions.DateTimeFormatOptionsFactory Creates a date time format options by a native object and a default values instance.
FormatPart Result of NumberFormat.formatToParts(double) which is containing the locale-specific tokens from which it possible to build custom strings while preserving the locale-specific parts. See MDN for more details.
IsLocaleItem Interface to map the locale item in order to get the name and search the items against the name instead of the value.
Language Enumerates the language identifiers which can be used to create and manage locale.
NumberFormatOptions The object configures a number formatter. See MDN for more details.
NumberFormatOptions.NumberFormatOptionsFactory Creates a number format options by a native object and a default values instance.
Region Enumerates the region or country identifiers which can be used to create and manage locale.
Script Enumerates the standard codes for script identification which can be used to create and manage locale.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.intl.enums

Class and Description
IsLocaleItem Interface to map the locale item in order to get the name and search the items against the name instead of the value.

Classes in org.pepstock.charba.client.intl used by org.pepstock.charba.client.options

Class and Description

CLocale Unicode represents locales with a string, called a locale identifier. The locale identifier consists of a language identifier and extension tags. Language identifiers are the core of the locale, consisting of language, script, and region subtags. Additional information about the locale is stored in the optional extension tags. Extension tags hold information about locale aspects such as calendar type, clock type, and numbering system type. A Unicode BCP 47 locale identifier consists of a language code (optionally) a script code, (optionally) a region (or country) code (optionally) one or more variant codes (optionally) one or more extension sequences See MDN page for more details. LOCALE auto recognition The locale client property can be specified using either a meta tag, as part of the query string in the host page’s URL or from default platform locale. If all cases are specified, the query string takes precedence, then meta data and finally the navigator language.