/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /* * This file is part of the LibreOffice project. * * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. * * This file incorporates work covered by the following license notice: * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed * with this work for additional information regarding copyright * ownership. The ASF licenses this file to you under the Apache * License, Version 2.0 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ #ifndef __com_sun_star_lang_Locale_idl__ #define __com_sun_star_lang_Locale_idl__ #include //============================================================================= module com { module sun { module star { module lang { //============================================================================= // DocMerge from xml: struct com::sun::star::lang::Locale /** object represents a specific geographical, political, or cultural region.

An operation that requires a Locale to perform its task is called locale-sensitive and uses the Locale to tailor information for the user. For example, displaying a number is a locale-sensitive operation; the number should be formatted according to the customs/conventions of the user's native country, region, or culture.

Because a Locale object is just an identifier for a region, no validity check is performed. If you want to see whether particular resources are available for the Locale, use the XLocale::getAvailableLocales method to ask for the locales it supports.

Note: When you ask for a resource for a particular locale, you get the best available match, not necessarily precisely what you asked for. For more information, see XResourceBundle.

Each implementation that performs locale-sensitive operations allows you to get all the available objects of that type. Use the XLocale interface to set the locale.

*/ published struct Locale { // DocMerge from xml: field com::sun::star::lang::Locale::Language /** specifies an ISO Language Code.

These codes are the lower-case two-letter codes as defined by ISO-639. You can find a full list of these codes at a number of sites, such as:
http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt.

If this field contains an empty string, the meaning depends on the context.

*/ string Language; //------------------------------------------------------------------------- // DocMerge from xml: field com::sun::star::lang::Locale::Country /** specifies an ISO Country Code.

These codes are the upper-case two-letter codes as defined by ISO-3166. You can find a full list of these codes at a number of sites, such as:
http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html.

If this field contains an empty string, the meaning depends on the context.

*/ string Country; //------------------------------------------------------------------------- // DocMerge from xml: field com::sun::star::lang::Locale::Variant /** contains a variant of the locale; codes are vendor and browser-specific.

For example, use WIN for Windows, MAC for Macintosh, and POSIX for POSIX. Wherever there are two variants, separate them with an underscore, and put the most important one first. For example, a traditional Spanish collation might construct a locale with parameters for language, country and variant as: "es", "ES", "Traditional_WIN".

*/ string Variant; }; //============================================================================= }; }; }; }; #endif /* vim:set shiftwidth=4 softtabstop=4 expandtab: */