Question: What did many existing computer systems that relied on time zones need because of the DST rule changes?

Answer: upgrades

Changes to DST rules cause problems in existing computer installations. <hl> For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by corporate information technologists. <hl>

Changes to DST rules cause problems in existing computer installations. For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the <hl> upgrades <hl> consumed a significant effort by corporate information technologists.


Question: In addition to calendaring programs, what kind of programs were most impacted by the changes?

Changes to DST rules cause problems in existing computer installations. For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by corporate information technologists.

Answer: email

Changes to DST rules cause problems in existing computer installations. <hl> For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by corporate information technologists. <hl>

Changes to DST rules cause problems in existing computer installations. For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on <hl> email <hl> and calendaring programs; the upgrades consumed a significant effort by corporate information technologists.


Question: Which professionals bore the brunt of the effort to upgrade systems affected by time changes?

Answer: corporate information technologists

Changes to DST rules cause problems in existing computer installations. <hl> For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by corporate information technologists . <hl>

Changes to DST rules cause problems in existing computer installations. For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by <hl> corporate information technologists <hl>.

For example, the 2007 change to DST rules in North America required many computer systems to be upgraded, with the greatest impact on email and calendaring programs; the upgrades consumed a significant effort by <hl> corporate information technologists <hl> .


Question: What system of time do some applications use so they won't have problems with time changes?

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display.

Answer: UTC

<hl> Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. <hl> Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display.

Some applications standardize on <hl> UTC <hl> to avoid problems with clock shifts and time zone differences. Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display.


Question: By using UTC, applications get out of adjusting to changes around clock shifts and what other factor?

Answer: time zone differences

<hl> Some applications standardize on UTC to avoid problems with clock shifts and time zone differences . <hl> Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display.

Some applications standardize on UTC to avoid problems with clock shifts and <hl> time zone differences <hl>. Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display.

Some applications standardize on UTC to avoid problems with clock shifts and <hl> time zone differences <hl> .


Question: In addition to individual applications, what modern systems that control the basic functions of a computer typically use UTC?

Answer: operating systems

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. <hl> Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display. <hl>

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. Likewise, most modern <hl> operating systems <hl> internally handle and store all times as UTC and only convert to local time for display.


Question: Where do computers usually use UTC?

Answer: internally

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. <hl> Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display. <hl>

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. Likewise, most modern operating systems <hl> internally <hl> handle and store all times as UTC and only convert to local time for display.


Question: What time would a computer probably use for the clock display?

Answer: local time

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. <hl> Likewise, most modern operating systems internally handle and store all times as UTC and only convert to local time for display. <hl>

Some applications standardize on UTC to avoid problems with clock shifts and time zone differences. Likewise, most modern operating systems internally handle and store all times as UTC and only convert to <hl> local time <hl> for display.


Question: Where do most systems go to get the data they use to calculate local time?

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as zoneinfo.

Answer: the IANA time zone database

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. <hl> Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as zoneinfo. <hl>

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. Many systems in use today base their date/time calculations from data derived from <hl> the IANA time zone database <hl> also known as zoneinfo.


Question: What two specific points of data do systems need to figure out to get local time?

Answer: date/time

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. <hl> Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as zoneinfo. <hl>

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. Many systems in use today base their <hl> date/time <hl> calculations from data derived from the IANA time zone database also known as zoneinfo.


Question: What's another name for the IANA database?

Answer: zoneinfo

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. <hl> Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as zoneinfo . <hl>

However, even if UTC is used internally, the systems still require information on time zones to correctly calculate local time where it is needed. Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as <hl> zoneinfo <hl>.

Many systems in use today base their date/time calculations from data derived from the IANA time zone database also known as <hl> zoneinfo <hl> .


Question: The IANA database works by connecting names to what information about the location?

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

Answer: historical and predicted clock shifts

<hl> The IANA time zone database maps a name to the named location's historical and predicted clock shifts . <hl> This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

The IANA time zone database maps a name to the named location's <hl> historical and predicted clock shifts <hl>. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

The IANA time zone database maps a name to the named location's <hl> historical and predicted clock shifts <hl> .


Question: IANA, or zoneinfo, updates are installed as a part of what ordinary function when changes to DST policy are made?

Answer: system maintenance

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. <hl> When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance . <hl> In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary <hl> system maintenance <hl>. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary <hl> system maintenance <hl> .


Question: What environment variable defines a location's name?

Answer: TZ

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. <hl> In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. <hl> In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the <hl> TZ <hl> environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.


Question: What format is used to store internal time in systems that use zoneinfo?

Answer: timezone-independent epoch time

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. <hl> Internal time is stored in timezone-independent epoch time ; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display. <hl>

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "tztab" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in <hl> timezone-independent epoch time <hl>; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

Internal time is stored in <hl> timezone-independent epoch time <hl> ; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.


Question: What's the name of the HP database that's similar to IANA but not compatible with it?

Answer: tztab

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. <hl> This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's " tztab " database is similar but incompatible. <hl> When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

The IANA time zone database maps a name to the named location's historical and predicted clock shifts. This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's "<hl> tztab <hl>" database is similar but incompatible. When temporal authorities change DST rules, zoneinfo updates are installed as part of ordinary system maintenance. In Unix-like systems the TZ environment variable specifies the location name, as in TZ=':America/New_York'. In many of those systems there is also a system-wide setting that is applied if the TZ environment variable isn't set: this setting is controlled by the contents of the /etc/localtime file, which is usually a symbolic link or hard link to one of the zoneinfo files. Internal time is stored in timezone-independent epoch time; the TZ is used by each of potentially many simultaneous users and processes to independently localize time display.

This database is used by many computer software systems, including most Unix-like operating systems, Java, and the Oracle RDBMS; HP's " <hl> tztab <hl> " database is similar but incompatible.


Question: Less sophisticated systems might just support a TZ value with one start rule and how many end rules?

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps.

Answer: one

<hl> Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. <hl> For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps.

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most <hl> one <hl> start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps.


Question: When must TZ values be changed on an older system?

Answer: whenever DST rules change

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. <hl> Such a TZ value must be changed whenever DST rules change , and the new value applies to all years, mishandling some older timestamps. <hl>

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed <hl> whenever DST rules change <hl>, and the new value applies to all years, mishandling some older timestamps.

Such a TZ value must be changed <hl> whenever DST rules change <hl> , and the new value applies to all years, mishandling some older timestamps.


Question: What does the TZ value EST5EDT,M3.2.0/02:00,M11.1.0/02:00 specify?

Answer: time for the eastern United States starting in 2007

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. <hl> For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007 . <hl> Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps.

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies <hl> time for the eastern United States starting in 2007 <hl>. Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps.

For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies <hl> time for the eastern United States starting in 2007 <hl> .


Question: What years will a new TZ value apply to?

Answer: all years

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. <hl> Such a TZ value must be changed whenever DST rules change, and the new value applies to all years , mishandling some older timestamps. <hl>

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed whenever DST rules change, and the new value applies to <hl> all years <hl>, mishandling some older timestamps.

Such a TZ value must be changed whenever DST rules change, and the new value applies to <hl> all years <hl> , mishandling some older timestamps.


Question: What's might a new TZ value mishandle when it changes with new DST rules?

Answer: older timestamps

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. <hl> Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some older timestamps . <hl>

Older or stripped-down systems may support only the TZ values required by POSIX, which specify at most one start and end rule explicitly in the value. For example, TZ='EST5EDT,M3.2.0/02:00,M11.1.0/02:00' specifies time for the eastern United States starting in 2007. Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some <hl> older timestamps <hl>.

Such a TZ value must be changed whenever DST rules change, and the new value applies to all years, mishandling some <hl> older timestamps <hl> .


Question: Similar to systems using zoneinfo, Microsoft Windows calculates DST by doing what?

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

Answer: specifying the name of a location

<hl> As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location , and the operating system then consults a table of rule sets that must be updated when DST rules change. <hl> Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by <hl> specifying the name of a location <hl>, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by <hl> specifying the name of a location <hl> , and the operating system then consults a table of rule sets that must be updated when DST rules change.


Question: When does the table of rule sets the Windows operating system uses have to be updated?

Answer: when DST rules change

<hl> As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change . <hl> Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated <hl> when DST rules change <hl>. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated <hl> when DST rules change <hl> .


Question: If your computer runs Vista, what's the maximum number of start and end rules you can have for each time zone setting?

Answer: two

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. <hl> Windows Vista supports at most two start and end rules per time zone setting. <hl> In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most <hl> two <hl> start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.


Question: If located in Canada somewhere where DST is observed, a system running Vista might mishandle time stamps that are older than what year?

Answer: 1987

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. <hl> In a Canadian location observing DST, a single Vista setting supports both 1987 –2006 and post-2006 time stamps, but mishandles some older time stamps. <hl> Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both <hl> 1987 <hl>–2006 and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

In a Canadian location observing DST, a single Vista setting supports both <hl> 1987 <hl> –2006 and post-2006 time stamps, but mishandles some older time stamps.


Question: On a system running Windows older than Vista, locations in Canada observing DST would only reliably support time stamps from after what year?

Answer: 2006

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. <hl> In a Canadian location observing DST, a single Vista setting supports both 1987– 2006 and post-2006 time stamps, but mishandles some older time stamps. <hl> Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

As with zoneinfo, a user of Microsoft Windows configures DST by specifying the name of a location, and the operating system then consults a table of rule sets that must be updated when DST rules change. Procedures for specifying the name and updating the table vary with release. Updates are not issued for older versions of Microsoft Windows. Windows Vista supports at most two start and end rules per time zone setting. In a Canadian location observing DST, a single Vista setting supports both 1987–<hl> 2006 <hl> and post-2006 time stamps, but mishandles some older time stamps. Older Microsoft Windows systems usually store only a single start and end rule for each zone, so that the same Canadian setting reliably supports only post-2006 time stamps.

In a Canadian location observing DST, a single Vista setting supports both 1987– <hl> 2006 <hl> and post-2006 time stamps, but mishandles some older time stamps.


Question: What single year did Windows 95 use to apply rules to Israel's time changes?

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

Answer: 1995

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. <hl> Windows 95 used rules correct for 1995 only, causing problems in later years. <hl> In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for <hl> 1995 <hl> only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.


Question: Because the schedule in Israel was always changing, what did Microsoft do with the release of Windows 98?

Answer: marked Israel as not having DST

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. <hl> In Windows 98, Microsoft marked Israel as not having DST , forcing Israeli users to shift their computer clocks manually twice a year. <hl> The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft <hl> marked Israel as not having DST <hl>, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

In Windows 98, Microsoft <hl> marked Israel as not having DST <hl> , forcing Israeli users to shift their computer clocks manually twice a year.


Question: How often would Israeli users running Windows 98 need to manually adjust the time on their machines to stay current?

Answer: twice a year

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. <hl> In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year . <hl> The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually <hl> twice a year <hl>. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually <hl> twice a year <hl> .


Question: What law regulated the rules for time shifts in Israel according to the Jewish calendar?

Answer: The 2005 Israeli Daylight Saving Law

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. <hl> The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. <hl> Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. <hl> The 2005 Israeli Daylight Saving Law <hl> established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to the Gregorian calendar.


Question: Although the schedule in Israel became predictable after 2005, there were still problems in Windows until Israel adjusted DST to what calendar in 2013?

Answer: the Gregorian calendar

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. <hl> In 2013, Israel standardized its daylight saving time according to the Gregorian calendar . <hl>

These limitations have caused problems. For example, before 2005, DST in Israel varied each year and was skipped some years. Windows 95 used rules correct for 1995 only, causing problems in later years. In Windows 98, Microsoft marked Israel as not having DST, forcing Israeli users to shift their computer clocks manually twice a year. The 2005 Israeli Daylight Saving Law established predictable rules using the Jewish calendar but Windows zone files could not represent the rules' dates in a year-independent way. Partial workarounds, which mishandled older time stamps, included manually switching zone files every year and a Microsoft tool that switches zones automatically. In 2013, Israel standardized its daylight saving time according to <hl> the Gregorian calendar <hl>.

In 2013, Israel standardized its daylight saving time according to <hl> the Gregorian calendar <hl> .


Question: What does Microsoft Windows use internally for its real-time clock?

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

Answer: local time

<hl> Microsoft Windows keeps the system real-time clock in local time . <hl> This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

Microsoft Windows keeps the system real-time clock in <hl> local time <hl>. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

Microsoft Windows keeps the system real-time clock in <hl> local time <hl> .


Question: Not using UTC, Windows can't multi boot with different versions of itself like you'd need to do to use what kind of disk?

Answer: a rescue boot disk

Microsoft Windows keeps the system real-time clock in local time. <hl> This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk . <hl> This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with <hl> a rescue boot disk <hl>. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with <hl> a rescue boot disk <hl> .


Question: As opposed to providing support for users to have unique time zone settings, Windows will only allow for what?

Answer: a single system-wide setting

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. <hl> This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting . <hl> In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only <hl> a single system-wide setting <hl>. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.

This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only <hl> a single system-wide setting <hl> .


Question: In what year did Microsoft imply that they would be making changes to support RealTimeIsUniversal in a step towards compatibility with UTC?

Answer: 2008

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. <hl> In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. <hl> Since then at least two fixes related to this feature have been published by Microsoft.

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In <hl> 2008 <hl> Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least two fixes related to this feature have been published by Microsoft.


Question: Since 2008, at least how many times has Microsoft released fixes for the RealTimeIsUniversal feature?

Answer: two

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. <hl> Since then at least two fixes related to this feature have been published by Microsoft. <hl>

Microsoft Windows keeps the system real-time clock in local time. This causes several problems, including compatibility when multi booting with operating systems that set the clock to UTC, and double-adjusting the clock when multi booting different Windows versions, such as with a rescue boot disk. This approach is a problem even in Windows-only systems: there is no support for per-user timezone settings, only a single system-wide setting. In 2008 Microsoft hinted that future versions of Windows will partially support a Windows registry entry RealTimeIsUniversal that had been introduced many years earlier, when Windows NT supported RISC machines with UTC clocks, but had not been maintained. Since then at least <hl> two <hl> fixes related to this feature have been published by Microsoft.


Question: What file system do recent Windows versions use?

The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

Answer: NTFS

<hl> The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. <hl> However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

The <hl> NTFS <hl> file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).


Question: Under NTFS, what does Windows use for file time stamps in storage?

Answer: UTC

<hl> The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. <hl> However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

The NTFS file system used by recent versions of Windows stores the file with a <hl> UTC <hl> time stamp, but displays it corrected to local—or seasonal—time. However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).


Question: What file system do most removable devices use?

Answer: FAT

The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. <hl> However, the FAT filesystem commonly used on removable devices stores only the local time. <hl> Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. However, the <hl> FAT <hl> filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).


Question: What time will a file be set to if it's copied from the hard disk onto other media?

Answer: current local time

The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. However, the FAT filesystem commonly used on removable devices stores only the local time. <hl> Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the current local time . <hl> If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

The NTFS file system used by recent versions of Windows stores the file with a UTC time stamp, but displays it corrected to local—or seasonal—time. However, the FAT filesystem commonly used on removable devices stores only the local time. Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the <hl> current local time <hl>. If the time adjustment is changed, the timestamps of the original file and the copy will be different. The same effect can be observed when compressing and uncompressing files with some file archivers. It is the NTFS file that changes seen time. This effect should be kept in mind when trying to determine if a file is a duplicate of another, although there are other methods of comparing files for equality (such as using a checksum algorithm).

Consequently, when a file is copied from the hard disk onto separate media, its time will be set to the <hl> current local time <hl> .


Question: What phrase describes keeping adjusted summer hours year-round?

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

Answer: permanent daylight saving time

<hl> A move to " permanent daylight saving time " (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. <hl> Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to "<hl> permanent daylight saving time <hl>" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to " <hl> permanent daylight saving time <hl> " (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus.


Question: Proponents of permanent DST say it has all the advantages of regular DST without the issues some people have from what bi-annual occurrences?

Answer: time shifts

<hl> A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts ) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. <hl> Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to "permanent daylight saving time" (staying on summer hours all year with no <hl> time shifts <hl>) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to "permanent daylight saving time" (staying on summer hours all year with no <hl> time shifts <hl> ) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus.


Question: In year-round DST, would sunrise happen early or late compared to most places?

Answer: late

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. <hl> However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. <hl> Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively <hl> late <hl> sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.


Question: During what time period did Russia use permanent DST?

Answer: 2011 to 2014

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. <hl> Russia switched to permanent DST from 2011 to 2014 , but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014. <hl>

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter, that year-round DST entails. Russia switched to permanent DST from <hl> 2011 to 2014 <hl>, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

Russia switched to permanent DST from <hl> 2011 to 2014 <hl> , but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.


Question: In what season in areas observing permanent daylight saving time will it stay dark the latest in the morning?

Answer: winter

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. <hl> However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in winter , that year-round DST entails. <hl> Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

A move to "permanent daylight saving time" (staying on summer hours all year with no time shifts) is sometimes advocated, and has in fact been implemented in some jurisdictions such as Argentina, Chile, Iceland, Singapore, Uzbekistan and Belarus. Advocates cite the same advantages as normal DST without the problems associated with the twice yearly time shifts. However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in <hl> winter <hl>, that year-round DST entails. Russia switched to permanent DST from 2011 to 2014, but the move proved unpopular because of the late sunrises in winter, so the country switched permanently back to "standard" or "winter" time in 2014.

However, many remain unconvinced of the benefits, citing the same problems and the relatively late sunrises, particularly in <hl> winter <hl> , that year-round DST entails.


Question: In which direction do countries like Russia and Argentina shift their time zones that could be considered all-year DST?

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Answer: westward

<hl> Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward , in effect observing DST year-round without complications from clock shifts. <hl> For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones <hl> westward <hl>, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones <hl> westward <hl> , in effect observing DST year-round without complications from clock shifts.


Question: About how many minutes does Saskatoon, Saskatchewan stay ahead of mean solar time?

Answer: 67

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. <hl> For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. <hl> Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about <hl> 67 <hl> minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.


Question: What time does Saskatoon observe all year long?

Answer: Central Standard Time

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. <hl> For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. <hl> Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is <hl> Central Standard Time <hl> (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.


Question: Places like northeast India that shift time zones to the east could be considered to be observing what kind of DST?

Answer: negative DST

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. <hl> Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST . <hl> The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing <hl> negative DST <hl>. The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions.

Conversely, northeast India and a few other areas skew time zones eastward, in effect observing <hl> negative DST <hl> .


Question: What year did Ireland and the UK give up on their permanent DST experiment?

Answer: 1971

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. <hl> The United Kingdom and Ireland experimented with year-round DST from 1968 to 1971 but abandoned it because of its unpopularity, particularly in northern regions. <hl>

Xinjiang, China; Argentina; Chile; Iceland; Russia and other areas skew time zones westward, in effect observing DST year-round without complications from clock shifts. For example, Saskatoon, Saskatchewan, is at 106°39′ W longitude, slightly west of center of the idealized Mountain Time Zone (105° W), but the time in Saskatchewan is Central Standard Time (90° W) year-round, so Saskatoon is always about 67 minutes ahead of mean solar time, thus effectively observing daylight saving time year-round. Conversely, northeast India and a few other areas skew time zones eastward, in effect observing negative DST. The United Kingdom and Ireland experimented with year-round DST from 1968 to <hl> 1971 <hl> but abandoned it because of its unpopularity, particularly in northern regions.


Question: Places like Spain and parts of France effectively go by DST in the winter but add what in the summer?

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and Central European Midsummer Time for details.

Answer: an extra hour

<hl> Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. <hl> Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and Central European Midsummer Time for details.

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with <hl> an extra hour <hl> in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and Central European Midsummer Time for details.


Question: During the summer in Nome, about how many hours ahead of the sun do they set their clocks?

Answer: three

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. <hl> Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. <hl> Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and Central European Midsummer Time for details.

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and <hl> three <hl> in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and Central European Midsummer Time for details.


Question: What term was used in Britain for double daylight saving time?

Answer: Double Summer Time

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. <hl> Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as " Double Summer Time ". <hl> See British Double Summer Time and Central European Midsummer Time for details.

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "<hl> Double Summer Time <hl>". See British Double Summer Time and Central European Midsummer Time for details.

Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as " <hl> Double Summer Time <hl> ".


Question: What's a third name for double daylight saving time or Double Summer Time used in Europe?

Answer: Central European Midsummer Time

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". <hl> See British Double Summer Time and Central European Midsummer Time for details. <hl>

Western France, Spain, and other areas skew time zones and shift clocks, in effect observing DST in winter with an extra hour in summer. Nome, Alaska, is at 165°24′ W longitude, which is just west of center of the idealized Samoa Time Zone (165° W), but Nome observes Alaska Time (135° W) with DST, so it is slightly more than two hours ahead of the sun in winter and three in summer. Double daylight saving time has been used on occasion; for example, it was used in some European countries during and shortly after World War II when it was referred to as "Double Summer Time". See British Double Summer Time and <hl> Central European Midsummer Time <hl> for details.


Question: What does RIBA stand for?

Answer: Royal Institute of British Architects

<hl> The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971. <hl>

The <hl> Royal Institute of British Architects <hl> (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971.


Question: What is the goal of RIBA?

Answer: the advancement of architecture

<hl> The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971. <hl>

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for <hl> the advancement of architecture <hl> under its charter granted in 1837 and Supplemental Charter granted in 1971.


Question: When was RIBA founded?

Answer: 1837

<hl> The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971. <hl>

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in <hl> 1837 <hl> and Supplemental Charter granted in 1971.


Question: When was RIBA's founding document expanded?

Answer: 1971

<hl> The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971 . <hl>

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in <hl> 1971 <hl>.

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in <hl> 1971 <hl> .


Question: In what country does RIBA mainly operate?

Answer: United Kingdom

<hl> The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the United Kingdom , but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971. <hl>

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the <hl> United Kingdom <hl>, but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971.

The Royal Institute of British Architects (RIBA) is a professional body for architects primarily in the <hl> United Kingdom <hl> , but also internationally, founded for the advancement of architecture under its charter granted in 1837 and Supplemental Charter granted in 1971.


Question: What was Riba's first name?

Originally named the Institute of British Architects in London, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.

Answer: Institute of British Architects in London

<hl> Originally named the Institute of British Architects in London , it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey. <hl>

Originally named the <hl> Institute of British Architects in London <hl>, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.

Originally named the <hl> Institute of British Architects in London <hl> , it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.


Question: In what year was the Institute of British Architects founded?

Answer: 1834

<hl> Originally named the Institute of British Architects in London, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey. <hl>

Originally named the Institute of British Architects in London, it was formed in <hl> 1834 <hl> by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.


Question: In what city was the Institute of British Architects located?

Answer: London

<hl> Originally named the Institute of British Architects in London , it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey. <hl>

Originally named the Institute of British Architects in <hl> London <hl>, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.

Originally named the Institute of British Architects in <hl> London <hl> , it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.


Question: In terms of profession, what were people like Philip Hardwick, William Adams Nicholson and Thomas de Grey?

Answer: Architects

<hl> Originally named the Institute of British Architects in London, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey. <hl>

Originally named the Institute of British <hl> Architects <hl> in London, it was formed in 1834 by several prominent architects, including Philip Hardwick, Thomas Allom, William Donthorne, Thomas Leverton Donaldson, William Adams Nicholson, John Buonarotti Papworth, and Thomas de Grey, 2nd Earl de Grey.


Question: What caused the change of the Institute's name?

After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in 1892. In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.

Answer: the grant of the royal charter

<hl> After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in 1892. <hl> In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.

After <hl> the grant of the royal charter <hl> it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in 1892. In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.


Question: What was removed from the Royal Institute's name?

Answer: the reference to London

<hl> After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in 1892. <hl> In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.

After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping <hl> the reference to London <hl> in 1892. In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.


Question: When was the mention of London removed from the Royal Institute's name?

Answer: 1892

<hl> After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in 1892 . <hl> In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.

After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in <hl> 1892 <hl>. In 1934, it moved to its current headquarters on Portland Place, with the building being opened by King George V and Queen Mary.

After the grant of the royal charter it had become known as the Royal Institute of British Architects in London, eventually dropping the reference to London in <hl> 1892 <hl> .