libcore.icu.TimeZoneNames java code examples

Add the Codota plugin to your IDE and get smart completions

private void myMethod () {
 DateTime d =new DateTime()
DateTimeFormatter formatter;String text;formatter.parseDateTime(text)
Object instant;new DateTime(instant)
Smart code suggestions by Codota
}

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

Reactive rest calls using spring rest template
requestLocationUpdates (LocationManager)
onCreateOptionsMenu (Activity)
getApplicationContext (Context)
VirtualMachine (com.sun.tools.attach)
A Java virtual machine. A VirtualMachine represents a Java virtual machine to which this Java vir
BufferedImage (java.awt.image)
The BufferedImage subclass describes an java.awt.Image with an accessible buffer of image data. All
ResultSet (java.sql)
An interface for an object which represents a database table entry, returned as the result of the qu
SortedSet (java.util)
A Set that further provides a total ordering on its elements. The elements are ordered using their C
Stack (java.util)
The Stack class represents a last-in-first-out (LIFO) stack of objects. It extends class Vector with
JFileChooser (javax.swing)

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