libcore.icu.TimeZoneNames java code examples

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

String[][] zoneStrings = TimeZoneNames.getZoneStrings(locale);
String result = TimeZoneNames.getDisplayName(zoneStrings, getID(), daylightTime, style);
if (result != null) {
  return result;

/**
 * Gets zone strings, initializing them if necessary. Does not create
 * a defensive copy, so make sure you do so before exposing the returned
 * arrays to clients.
 */
synchronized String[][] internalZoneStrings() {
  if (zoneStrings == null) {
    zoneStrings = TimeZoneNames.getZoneStrings(locale);
  }
  return zoneStrings;
}

/**
 * Append a representation of the time zone of 'calendar' to 'buffer'.
 *
 * @param count the number of z or Z characters in the format string; "zzz" would be 3,
 * for example.
 * @param generalTimeZone true if we should use a display name ("PDT") if available;
 * false implies that we should use RFC 822 format ("-0800") instead. This corresponds to 'z'
 * versus 'Z' in the format string.
 */
private void appendTimeZone(StringBuffer buffer, int count, boolean generalTimeZone) {
  if (generalTimeZone) {
    TimeZone tz = calendar.getTimeZone();
    boolean daylight = (calendar.get(Calendar.DST_OFFSET) != 0);
    int style = count < 4 ? TimeZone.SHORT : TimeZone.LONG;
    if (!formatData.customZoneStrings) {
      buffer.append(tz.getDisplayName(daylight, style, formatData.locale));
      return;
    }
    // We can't call TimeZone.getDisplayName() because it would not use
    // the custom DateFormatSymbols of this SimpleDateFormat.
    String custom = TimeZoneNames.getDisplayName(formatData.zoneStrings, tz.getID(), daylight, style);
    if (custom != null) {
      buffer.append(custom);
      return;
    }
  }
  // We didn't find what we were looking for, so default to a numeric time zone.
  appendNumericTimeZone(buffer, count, generalTimeZone);
}

Javadoc

Provides access to ICU's time zone name data.

Most used methods

getDisplayName
Returns the appropriate string from 'zoneStrings'. Used with getZoneStrings.
getZoneStrings
Returns an array of time zone strings, as used by DateFormatSymbols.getZoneStrings.

Popular in Java

Start an intent from android
compareTo (BigDecimal)
orElseThrow (Optional)
Return the contained value, if present, otherwise throw an exception to be created by the provided s
onCreateOptionsMenu (Activity)
BigInteger (java.math)
An immutable arbitrary-precision signed integer.FAST CRYPTOGRAPHY This implementation is efficient f
Collections (java.util)
This class consists exclusively of static methods that operate on or return collections. It contains
Date (java.util)
A specific moment in time, with millisecond precision. Values typically come from System#currentTime
LinkedList (java.util)
Doubly-linked list implementation of the List and Dequeinterfaces. Implements all optional list oper
SortedMap (java.util)
A map that has its keys ordered. The sorting is according to either the natural ordering of its keys
AtomicInteger (java.util.concurrent.atomic)
An int value that may be updated atomically. See the java.util.concurrent.atomic package specificati
Top 17 Free Sublime Text Plugins

How to useTimeZoneNames in libcore.icu

Best Java code snippets using libcore.icu.TimeZoneNames (Showing top 20 results out of 315)

How to use
TimeZoneNames
in
libcore.icu