1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292
|
.. -*- mode: rst; encoding: utf-8 -*-
===============
Date Formatting
===============
.. contents:: Contents
:depth: 2
.. sectnum::
When working with date and time information in Python, you commonly use the
classes ``date``, ``datetime`` and/or ``time`` from the `datetime`_ package.
Babel provides functions for locale-specific formatting of those objects in its
``dates`` module:
.. _`datetime`: http://docs.python.org/lib/module-datetime.html
.. code-block:: pycon
>>> from datetime import date, datetime, time
>>> from babel.dates import format_date, format_datetime, format_time
>>> d = date(2007, 4, 1)
>>> format_date(d, locale='en')
u'Apr 1, 2007'
>>> format_date(d, locale='de_DE')
u'01.04.2007'
As this example demonstrates, Babel will automatically choose a date format
that is appropriate for the requested locale.
The ``format_*()`` functions also accept an optional ``format`` argument, which
allows you to choose between one of four format variations:
* ``short``,
* ``medium`` (the default),
* ``long``, and
* ``full``.
For example:
.. code-block:: pycon
>>> format_date(d, format='short', locale='en')
u'4/1/07'
>>> format_date(d, format='long', locale='en')
u'April 1, 2007'
>>> format_date(d, format='full', locale='en')
u'Sunday, April 1, 2007'
Pattern Syntax
==============
While Babel makes it simple to use the appropriate date/time format for a given
locale, you can also force it to use custom patterns. Note that Babel uses
different patterns for specifying number and date formats compared to the
Python equivalents (such as ``time.strftime()``), which have mostly been
inherited from C and POSIX. The patterns used in Babel are based on the
`Locale Data Markup Language specification`_ (LDML), which defines them as
follows:
A date/time pattern is a string of characters, where specific strings of
characters are replaced with date and time data from a calendar when formatting
or used to generate data for a calendar when parsing. […]
Characters may be used multiple times. For example, if ``y`` is used for the
year, ``yy`` might produce "99", whereas ``yyyy`` produces "1999". For most
numerical fields, the number of characters specifies the field width. For
example, if ``h`` is the hour, ``h`` might produce "5", but ``hh`` produces
"05". For some characters, the count specifies whether an abbreviated or full
form should be used […]
Two single quotes represent a literal single quote, either inside or outside
single quotes. Text within single quotes is not interpreted in any way (except
for two adjacent single quotes).
For example:
.. code-block:: pycon
>>> d = date(2007, 4, 1)
>>> format_date(d, "EEE, MMM d, ''yy", locale='en')
u"Sun, Apr 1, '07"
>>> format_date(d, "EEEE, d.M.yyyy", locale='de')
u'Sonntag, 1.4.2007'
>>> t = time(15, 30)
>>> format_time(t, "hh 'o''clock' a", locale='en')
u"03 o'clock PM"
>>> format_time(t, 'H:mm a', locale='de')
u'15:30 nachm.'
>>> dt = datetime(2007, 4, 1, 15, 30)
>>> format_datetime(dt, "yyyyy.MMMM.dd GGG hh:mm a", locale='en')
u'02007.April.01 AD 03:30 PM'
The syntax for custom datetime format patterns is described in detail in the
the `Locale Data Markup Language specification`_. The following table is just a
relatively brief overview.
.. _`Locale Data Markup Language specification`: http://unicode.org/reports/tr35/#Date_Format_Patterns
Date Fields
-----------
+----------+--------+--------------------------------------------------------+
| Field | Symbol | Description |
+==========+========+========================================================+
| Era | ``G`` | Replaced with the era string for the current date. One |
| | | to three letters for the abbreviated form, four |
| | | lettersfor the long form, five for the narrow form |
+----------+--------+--------------------------------------------------------+
| Year | ``y`` | Replaced by the year. Normally the length specifies |
| | | the padding, but for two letters it also specifies the |
| | | maximum length. |
| +--------+--------------------------------------------------------+
| | ``Y`` | Same as ``y`` but uses the ISO year-week calendar. |
| +--------+--------------------------------------------------------+
| | ``u`` | ?? |
+----------+--------+--------------------------------------------------------+
| Quarter | ``Q`` | Use one or two for the numerical quarter, three for |
| | | the abbreviation, or four for the full name. |
| +--------+--------------------------------------------------------+
| | ``q`` | Use one or two for the numerical quarter, three for |
| | | the abbreviation, or four for the full name. |
+----------+--------+--------------------------------------------------------+
| Month | ``M`` | Use one or two for the numerical month, three for the |
| | | abbreviation, or four for the full name, or five for |
| | | the narrow name. |
| +--------+--------------------------------------------------------+
| | ``L`` | Use one or two for the numerical month, three for the |
| | | abbreviation, or four for the full name, or 5 for the |
| | | narrow name. |
+----------+--------+--------------------------------------------------------+
| Week | ``w`` | Week of year. |
| +--------+--------------------------------------------------------+
| | ``W`` | Week of month. |
+----------+--------+--------------------------------------------------------+
| Day | ``d`` | Day of month. |
| +--------+--------------------------------------------------------+
| | ``D`` | Day of year. |
| +--------+--------------------------------------------------------+
| | ``F`` | Day of week in month. |
| +--------+--------------------------------------------------------+
| | ``g`` | ?? |
+----------+--------+--------------------------------------------------------+
| Week day | ``E`` | Day of week. Use one through three letters for the |
| | | short day, or four for the full name, or five for the |
| | | narrow name. |
| +--------+--------------------------------------------------------+
| | ``e`` | Local day of week. Same as E except adds a numeric |
| | | value that will depend on the local starting day of |
| | | the week, using one or two letters. |
| +--------+--------------------------------------------------------+
| | ``c`` | ?? |
+----------+--------+--------------------------------------------------------+
Time Fields
-----------
+----------+--------+--------------------------------------------------------+
| Field | Symbol | Description |
+==========+========+========================================================+
| Period | ``a`` | AM or PM |
+----------+--------+--------------------------------------------------------+
| Hour | ``h`` | Hour [1-12]. |
| +--------+--------------------------------------------------------+
| | ``H`` | Hour [0-23]. |
| +--------+--------------------------------------------------------+
| | ``K`` | Hour [0-11]. |
| +--------+--------------------------------------------------------+
| | ``k`` | Hour [1-24]. |
+----------+--------+--------------------------------------------------------+
| Minute | ``m`` | Use one or two for zero places padding. |
+----------+--------+--------------------------------------------------------+
| Second | ``s`` | Use one or two for zero places padding. |
| +--------+--------------------------------------------------------+
| | ``S`` | Fractional second, rounds to the count of letters. |
| +--------+--------------------------------------------------------+
| | ``A`` | Milliseconds in day. |
+----------+--------+--------------------------------------------------------+
| Timezone | ``z`` | Use one to three letters for the short timezone or |
| | | four for the full name. |
| +--------+--------------------------------------------------------+
| | ``Z`` | Use one to three letters for RFC 822, four letters for |
| | | GMT format. |
| +--------+--------------------------------------------------------+
| | ``v`` | Use one letter for short wall (generic) time, four for |
| | | long wall time. |
| +--------+--------------------------------------------------------+
| | ``V`` | Same as ``z``, except that timezone abbreviations |
| | | should be used regardless of whether they are in |
| | | common use by the locale. |
+----------+--------+--------------------------------------------------------+
Time-zone Support
=================
Many of the verbose time formats include the time-zone, but time-zone
information is not by default available for the Python ``datetime`` and
``time`` objects. The standard library includes only the abstract ``tzinfo``
class, which you need appropriate implementations for to actually use in your
application. Babel includes a ``tzinfo`` implementation for UTC (Universal
Time).
For real time-zone support, it is strongly recommended that you use the
third-party package `pytz`_, which includes the definitions of practically all
of the time-zones used on the world, as well as important functions for
reliably converting from UTC to local time, and vice versa:
.. code-block:: pycon
>>> from datetime import time
>>> from pytz import timezone, utc
>>> dt = datetime(2007, 04, 01, 15, 30, tzinfo=utc)
>>> eastern = timezone('US/Eastern')
>>> format_datetime(dt, 'H:mm Z', tzinfo=eastern, locale='en_US')
u'11:30 -0400'
The recommended approach to deal with different time-zones in a Python
application is to always use UTC internally, and only convert from/to the users
time-zone when accepting user input and displaying date/time data, respectively.
You can use Babel together with ``pytz`` to apply a time-zone to any
``datetime`` or ``time`` object for display, leaving the original information
unchanged:
.. code-block:: pycon
>>> british = timezone('Europe/London')
>>> format_datetime(dt, 'H:mm zzzz', tzinfo=british, locale='en_US')
u'16:30 British Summer Time'
Here, the given UTC time is adjusted to the "Europe/London" time-zone, and
daylight savings time is taken into account. Daylight savings time is also
applied to ``format_time``, but because the actual date is unknown in that
case, the current day is assumed to determine whether DST or standard time
should be used.
.. _`pytz`: http://pytz.sourceforge.net/
Localized Time-zone Names
-------------------------
While the ``Locale`` class provides access to various locale display names
related to time-zones, the process of building a localized name of a time-zone
is actually quite complicated. Babel implements it in separately usable
functions in the ``babel.dates`` module, most importantly the
``get_timezone_name`` function:
.. code-block:: pycon
>>> from pytz import timezone
>>> from babel import Locale
>>> from babel.dates import get_timezone_name
>>> tz = timezone('Europe/Berlin')
>>> get_timezone_name(tz, locale=Locale.parse('pt_PT'))
u'Hor\xe1rio Alemanha'
You can pass the function either a ``datetime.tzinfo`` object, or a
``datetime.date`` or ``datetime.datetime`` object. If you pass an actual date,
the function will be able to take daylight savings time into account. If you
pass just the time-zone, Babel does not know whether daylight savings time is
in effect, so it uses a generic representation, which is useful for example to
display a list of time-zones to the user.
.. code-block:: pycon
>>> from datetime import datetime
>>> dt = tz.localize(datetime(2007, 8, 15))
>>> get_timezone_name(dt, locale=Locale.parse('de_DE'))
u'Mitteleurop\xe4ische Sommerzeit'
>>> get_timezone_name(tz, locale=Locale.parse('de_DE'))
u'Deutschland'
Parsing Dates
=============
Babel can also parse date and time information in a locale-sensitive manner:
.. code-block:: pycon
>>> from babel.dates import parse_date, parse_datetime, parse_time
.. note:: Date/time parsing is not properly implemented yet
|