Strict Standards: Only variables should be passed by reference in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/gettext.php on line 66

Strict Standards: Only variables should be passed by reference in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/gettext.php on line 66

Strict Standards: Only variables should be passed by reference in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/gettext.php on line 66

Strict Standards: Only variables should be passed by reference in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/gettext.php on line 66

Strict Standards: Only variables should be passed by reference in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/gettext.php on line 66
beates blog » 2011 » März
Skip to Content »

beates blog » archive for
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
März, 2011


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

 Fast Food


  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    März 24th, 2011

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    12:26 pm

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions-formatting.php on line 76

Nach über 4 Monaten habe ich vor kurzem den ersten Burger hier gegessen. Weil gerade nichts besseres auf unserem Weg lag hat MCDohf mal wieder etwas Geld von uns bekommen, und ich hab mir nen Quarterpounder ausgesucht. ¼-Pfünder sind in England und Nordamerika als größere Version der Standardburger ziemlich beliebt und ein echter Klassiker. Auf dem europäischen Festland nennt sich der „Burger Royal mit Käse“, weil das metrische System unter einem viertel Pfund Hackfleisch eine andere Menge alter Milchkuh versteht als der Queen das mal vorschwebte. Wer “Pulp Fiction” gesehen hat weiß das. Wer sich etwas besser mit MC Donalds auskennt weiß auch, dass der “Royal TS” kein Quarterpounder ist, sondern eine gepimpte Version davon. Das “TS” steht für “Tomate und Salad”.

Ehrlich gesagt hätte ich mir das sparen können, auch Beates Chicken MC Nuggets waren für die Füße. Ich dachte der Konzern hätte weltweit ein einheitliches Angebot und gleiche Qualität, aber die kanadische Version erschien uns wie ein billiger Abklatsch.

Beim nächsten Heißhunger auf Fast-Food sollten wir uns vielleicht wieder etwas stramm kanadisches aussuchen und eine Poutine essen. Das ist ein pervers klingende Mischung aus Fritten, Käse und Bratensoße, die es hier in zig Varianten und an quasi jeder Ecke gibt. Schmeckt gut! Ich werde wohl nie in die Verlegenheit kommen, aber sollte ich mir wirklich mal einen Winterspeck anfressen müssen werden Poutines sicher ein fester Bestandteil meiner Ernährung werden J

[Achim]


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

 Zeitumstellung


  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    März 15th, 2011

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    1:21 pm

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions-formatting.php on line 76

Heute wurde in Nordamerika die Umstellung auf Sommerzeit durchgeführt. Entgegen unseren Erwartungen spricht man hier nicht von „summer time“, sondern von „daylight saving time“.

Bis Ende April beträgt der Zeitunterschied nach Deutschland nicht mehr wie üblich 6 Stunden, sondern nur noch 5 Stunden. Seit 1996 wird nicht mehr wie in Europa üblich am letzten Aprilwochenende und am letzten Wochenende im Oktober umgestellt, sondern am zweiten Sonntag im März und am ersten Sonntag im November. Sollte sich herausstellen, dass durch die Ausweitung der Sommerzeit keine Energie eingespart wird, kann auf das europäische System zurückgestellt werden. Die derzeitige Regelung ist also nur vorläufig.

Russland verkündete vor kurzem bei der Sommerzeit zu bleiben, um die Umstellungsprobleme in Zukunft zu vermeiden. Diese betrifft nicht nur Menschen, bekanntlich geben Kühe nach den beiden Zeitumstellungen jedes Jahr weniger Milch. Eine Universität hier in Ontario hat außerdem herausgefunden, dass Morgen für PKWs ein 17% größeres Unfallrisiko herrscht als an gewöhnlichen Montagen.

Sehr interessant war es für mich zu lesen, dass die alte Zeiteinteilung ohne Umstellung auf Sommerzeit hier in Nordamerika alles andere als eine große Tradition hat. Bis 1883 hatte jeder Ort seine eigene Zeitzone, in der um 12 Uhr Mittag die Sonne exakt im Süden stand. Das war damals fast problemlos durchzuführen, nur für Zugreisende muss dieser Zustand die Hölle auf Erden gewesen sein. Deswegen gab es an vielen Bahnstationen 2 Uhren. Eine war auf Lokalzeit, eine auf Bahnzeit eingestellt. 1883 unterteilten dann die Eisenbahnen den Kontinent in 4 Zeitzonen. Diese setzten sich durch, wenn auch zum Teil gegen erheblichen Widerstand. Einige Gemeinden beschlossen damals gar trotzig die Beibehaltung ihrer Zeitzone.

Bereits 1916 führten im 1. Weltkrieg die Mittelmächte unter Führung Deutschlands die Sommerzeit ein, um z.B. Kohle zu sparen. Die Kriegsgegner der Entente und Russland zogen 1917 nach, die USA 1918. Ab dann ging dieser Virus um die Welt, seit der Ölkrise der 70-er Jahre mit großem Einfluss auf die Nordhalbkugel. Das nördlichste Land das noch nie damit experimentiert hat ist Afghanistan.

Hier in Kanada sind übrigens die Rebellen von 1883 immer noch präsent. Die Sommerzeit wird von einigen Teilen Quebecs und Saskatchewans nicht mitgetragen. Auch in einigen Gemeinden von Ontario, British-Columbia und anderen Bundesstaaten hält man sich nicht an die üblichen zeitlichen Gepflogenheiten. Die Varianten und Gründe sind so unterschiedlich und vielfältig, dass ich darüber einen eigenen Artikel schreiben könnte. Manche bleiben bei der Sommerzeit, andere übernehmen eine angrenzende Zeitzone oder bleiben bei der Winterzeit. Verstehen kann ich das ja, wenn kleine Gemeinden sich an die Zeitzone des angrenzenden Bundeslandes halten, weil sie im Einzugsbereich großer Städte liegen. Aber warum die anderen ihre zeitliche Extrawurst braten kann ich Euch wirklich nicht sagen.

Aber wie bezeichneten es die Amis im kalten Krieg, wenn etwas wirklich keinen Sinn machte? “Just to confuse the Russians” :-)

[Achim]


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32

 Mal wieder das Wetter


  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    März 12th, 2011

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions.php on line 32
    2:36 pm

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/19/d29432735/htdocs/morlings/beatesblog/wp-includes/functions-formatting.php on line 76

In Deutschland wird es wärmer, der Frühling meldet sich an. Hier in Toronto wird es ebenfalls wärmer, leider fühlt sich das aber ziemlich suboptimal an. Seit Anfang Dezember hatten wir ja tagsüber zumeist -2 bi -10 Grad. Dank der Lage am See sehr stabil, also ohne große Temperaturschwankungen. Dadurch konnte sich auch die bekennende Frostbeule Beate wirklich gut an den Winter anpassen, zeitweise war es ihr sogar zu warm wenn wir mal knapp über 0 Grad hatten. Hier in Toronto kann man also mit dem kanadischen Winter wirklich leben.

Zuletzt wurde es aber wärmer, und damit auch unangenehmer. Schneeregen, tief hängende Wolken, so dass man von unserem Balkon nicht mal mehr den ca. 3 Kilometer entfernten CN Tower (ehemals Skytower) sehen kann.

Ein perfektes Wetter also um schön drinnen zu bleiben, Cappuccino oder heiße Schokolade zu schlürfen und „8000“ von Extrawelt zu hören. Tagelang. Denn das Wetter bleibt erst mal so. Wer das Lied nicht kennt, hier ist der Link: http://www.youtube.com/watch?v=ho7gIr69UkQ

[Achim]