Lines Matching refs:pattern
30 * a pattern which just includes the desired fields and lengths. The generator
31 * will return the "best fit" pattern corresponding to that skeleton.
36 * fields in a pattern, in order, since we have that internally.
41 * Opaque type for a date/time pattern generator object.
49 * because some fields are merged for the date/time pattern generator.
145 * Get the best pattern matching the input skeleton. It is guaranteed to
149 * It uses a stateful pattern parser which is set up for each generator object,
156 * The skeleton is a pattern containing only the variable fields.
160 * The best pattern found from the given skeleton.
174 * Get a unique skeleton from a given pattern. For example,
178 * It uses a stateful pattern parser which is set up for each generator object,
184 * @param pattern input pattern, such as "dd/MMM".
185 * @param length the length of pattern.
195 const UChar *pattern, int32_t length,
200 * Get a unique base skeleton from a given pattern. This is the same
207 * It uses a stateful pattern parser which is set up for each generator object,
213 * @param pattern input pattern, such as "dd/MMM".
214 * @param length the length of pattern.
224 const UChar *pattern, int32_t length,
229 * Adds a pattern to the generator. If the pattern has the same skeleton as
230 * an existing pattern, and the override parameter is set, then the previous
233 * conflicting pattern.
239 * @param pattern input pattern, such as "dd/MMM"
240 * @param patternLength the length of pattern.
243 * @param conflictingPattern Previous pattern with the same skeleton.
254 const UChar *pattern, int32_t patternLength,
260 * An AppendItem format is a pattern used to append a field if there is no
262 * and there is no matching pattern internally, but there is a pattern
263 * matching "yyyyMMMd", say "d-MM-yyyy". Then that pattern is used, plus the
266 * pattern is "d-MM-yyyy, G".
268 * There are actually three available variables: {0} is the pattern so far,
275 * @param value pattern, such as "{0}, {1}"
333 * The date time format is a message format pattern used to compose date and
335 * by the date pattern and {1} will be replaced by the time pattern.
343 * for those two skeletons, so the result is put together with this pattern,
348 * message format pattern, here {0} will be replaced by the date
349 * pattern and {1} will be replaced by the time pattern.
371 * fractional seconds. For example, suppose that the input pattern is
372 * "hhmmssSSSS", and the best matching pattern internally is "H:mm:ss", and
373 * the decimal string is ",". Then the resulting pattern is modified to be
398 * Adjusts the field types (width and subtype) of a pattern to match what is
399 * in a skeleton. That is, if you supply a pattern like "d-M H:m", and a
400 * skeleton of "MMMMddhhmm", then the input pattern is adjusted to be
405 * It uses a stateful pattern parser which is set up for each generator object,
411 * @param pattern Input pattern
412 * @param patternLength the length of input pattern.
415 * @param dest pattern adjusted to match the skeleton fields widths and subtypes.
424 const UChar *pattern, int32_t patternLength,
431 * Call udatpg_getPatternForSkeleton() to get the corresponding pattern.
457 * Get the pattern corresponding to a given skeleton.
462 * @param pLength pointer to the length of return pattern.
463 * @return pattern corresponding to a given skeleton.
