• Introduction
• Overview
• Why does Noda Time exist?
• Installation
• Core
• Core concepts
• Choosing (and converting) between types
• Core types quick reference
• Recipes
• Design philosophy and conventions
• Migrating from 1.x to 2.0
• Migrating from 2.x to 3.0
• Text
• Text handling
• Patterns for Duration values
• Patterns for Offset values
• Patterns for Instant values
• Patterns for LocalTime values
• Patterns for LocalDate values
• Patterns for LocalDateTime values
• Patterns for OffsetDateTime values
• Patterns for ZonedDateTime values
• Patterns for Period values
• Patterns for OffsetDate values
• Patterns for OffsetTime values
• Patterns for AnnualDate values
• Patterns for YearMonth values
• Advanced
• Date and time arithmetic
• Range of valid values
• BCL conversions
• Serialization
• Calendars
• Week years
• Threading
• Trivia
• Library
• Unit testing with Noda Time
• Updating the time zone database
• Mono support
• Limitations of Noda Time
• Current roadmap

Patterns for OffsetTime values

The OffsetTime type supports the following patterns:

Standard Patterns

The following standard patterns are supported:

• G: General invariant ISO-8601 pattern, to second precision. This corresponds to the custom pattern HH':'mm':'sso<G>. This is the default format pattern.
• o: Extended invariant ISO-8601 pattern, to nanosecond precision. This corresponds to the custom pattern HH':'mm':'ss;FFFFFFFFFo<G>.

Custom Patterns

The custom format patterns for the local time part of the value are the same as the custom patterns for LocalTime.

There is an additional specifier for the offset. The "o" specifier must always be followed by a pattern for Offset within angle brackets. The pattern may be a standard pattern or a custom pattern. For example, a pattern of HH:mm o<G> might produce output of "16:23 Z" or "16:23 +01".

To use culture-specific standard time patterns in a custom OffsetTime pattern, use the "l" specifier, followed by a pattern for LocalTime within angle brackets. The pattern may be a standard pattern or a custom pattern. For example, a pattern of l<T> o<+HH:mm> might produce output of "16:23:52 +01:00".