code: public int getActualMinimum(int field) {
          int result;
  
          switch (field) {
          case DAY_OF_WEEK:
          case AM_PM:
          case HOUR:
          case HOUR_OF_DAY:
          case MINUTE:
          case SECOND:
          case MILLISECOND:
          case ZONE_OFFSET:
          case DST_OFFSET:
          case DOW_LOCAL:
          case JULIAN_DAY:
          case MILLISECONDS_IN_DAY:
              // These fields all have fixed minima/maxima
              result = getMinimum(field);
              break;
  
          default:
              // For all other fields, do it the hard way....
              result = getActualHelper(field, getGreatestMinimum(field), getMinimum(field));
              break;
          }
          return result;
      }
docs: Returns the minimum value that this field could have, given the current date.
  For most fields, this is the same as {@link #getMinimum getMinimum}
  and {@link #getGreatestMinimum getGreatestMinimum}.  However, some fields,
  especially those related to week number, are more complicated.
  <p>
  For example, assume {@link #getMinimalDaysInFirstWeek getMinimalDaysInFirstWeek}
  returns 4 and {@link #getFirstDayOfWeek getFirstDayOfWeek} returns SUNDAY.
  If the first day of the month is Sunday, Monday, Tuesday, or Wednesday
  there will be four or more days in the first week, so it will be week number 1,
  and <code>getActualMinimum(WEEK_OF_MONTH)</code> will return 1.  However,
  if the first of the month is a Thursday, Friday, or Saturday, there are
  <em>not</em> four days in that week, so it is week number 0, and
  <code>getActualMinimum(WEEK_OF_MONTH)</code> will return 0.
  <p>
  @param field the field whose actual minimum value is desired.
  @return the minimum of the given field for the current date of this calendar
  
  @see #getMinimum
  @see #getGreatestMinimum