Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 584

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 584

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 584

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 584

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 603

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 702

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 702

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 702

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 702

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/44/d152788678/htdocs/wordpress/wp-includes/classes.php on line 727

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/44/d152788678/htdocs/wordpress/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/44/d152788678/htdocs/wordpress/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-includes/theme.php on line 576

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/exec-php.php on line 22

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/manager.php on line 34

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/manager.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/manager.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/admin.php on line 42

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/admin.php on line 48

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/admin.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/admin.php on line 50

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/ajax.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/cache.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/exec-php/includes/cache.php on line 42

Strict Standards: Non-static method InSeriesInternal::compat_hooks() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 944

Strict Standards: Redefining already defined constructor for class ngg_Tags in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/nextgen-gallery/lib/nggallery.lib.php on line 479

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method DuplicateSidebarWidgets::load() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 311

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method DuplicateSidebarWidgets::register() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 311

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/44/d152788678/htdocs/wordpress/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 90

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGenerator::Enable() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 311
Les Enfants de l’Ô » Mémoire de poisson rouge…
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method InSeriesInternal::insert_doc_rel_links() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 311

Strict Standards: Non-static method InSeries::adv_CurrentSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 858

Strict Standards: Non-static method InSeriesInternal::get_current_series_id() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series.php on line 131

Strict Standards: Non-static method InSeriesInternal::get_series_hint() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 142

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 134

Strict Standards: Non-static method InSeriesInternal::get_the_ID() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 147

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 147

Strict Standards: Non-static method InSeriesInternal::PostToSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 152

Strict Standards: Non-static method InSeriesInternal::GetPostSeriesCachedResults() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 323

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 325

Strict Standards: Non-static method InSeriesInternal::get_entry_table_name() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 330

Strict Standards: Non-static method InSeriesInternal::get_table_name() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 117

Les Enfants de l\'Ô

de l\'écriture à la publication


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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33

Mémoire de poisson rouge…

Un article de Vanessa du Frat
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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
21 juillet 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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
1:06

Category Icon

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method InSeriesInternal::in_series_linker_content_filter() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 163

Strict Standards: Non-static method InSeriesInternal::get_the_ID() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 881

Strict Standards: Non-static method InSeries::adv_PostToSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 881

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series.php on line 486

Strict Standards: Non-static method InSeriesInternal::PostToSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series.php on line 490

Strict Standards: Non-static method InSeriesInternal::GetPostSeriesCachedResults() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 323

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 325

La mémoire de poisson rouge, c’est LE truc à ne pas avoir quand on écrit une grande saga familiale super compliquée qui se déroule sur plusieurs générations. Vous vous rappelez mon post précédent, celui dans lequel je désespérais de trouver une bonne solution pour mes settings temporels ? Figurez-vous qu’en faisant du rangement dans mon appartement, je suis tombée sur une vieille version des Enfants de l’Ô. Un truc qui faisait bien pitié (et non, je ne mettrai pas d’extrait. Cette version, heureusement, n’a jamais été diffusée nulle part !). Sauf que, dans le truc en question, j’avais nommé mes mois. Et là, je me suis souvenue qu’il y a au moins dix ans, j’avais eu le même problème, les mêmes questionnements, et que j’avais créé un calendrier.

Des fois, je me mettrais des baffes. Bref, reste encore le problème des années. Et puis je ne sais pas si je vais garder mon “ancien” calendrier (qui est plutôt simple et pas des masses original vu que j’avais calqué l’année sur l’année astrale, avec les mois qui portaient les noms de signes du zodiaque), ou en faire un nouveau. De toute manière, pour ne pas m’embêter, les mois n’auront pas de noms dans les petits settings temporels en début de chapitre, et je n’utiliserai mon calendrier que de manière purement anecdotique de temps à autre dans le bouquin.

Ah, et j’avais aussi fait une carte de ma planète, avec les continents, la population, le climat, et toute une chronologie. A cette époque, j’étais partie passer 10 mois en Autriche pour un séjour linguistique et je m’ennuyais grave ^^ Maintenant, faudrait m’attacher à une table pendant deux jours avec juste un bloc-note et un crayon pour que je refasse quelque chose du genre…


Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method InSeriesInternal::in_series_linker_content_filter() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-includes/plugin.php on line 163

Strict Standards: Non-static method InSeriesInternal::get_the_ID() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 881

Strict Standards: Non-static method InSeries::adv_PostToSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 881

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series.php on line 486

Strict Standards: Non-static method InSeriesInternal::PostToSeries() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series.php on line 490

Strict Standards: Non-static method InSeriesInternal::GetPostSeriesCachedResults() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 323

Strict Standards: Non-static method InSeriesInternal::make_int() should not be called statically in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/in-series/in-series-internal.php on line 325



      Partager sur Facebook

      Partager sur Twitter.

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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

Ceci est l'article n°186 du blog et il a été posté il y a
Deprecated: Function eregi() is deprecated in /homepages/44/d152788678/htdocs/wordpress/wp-includes/gettext.php on line 294
1102 jours.



2 commentaires pour “Mémoire de poisson rouge…”

    1
    Ephy
    le
    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

    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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
    1 octobre 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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

    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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
    12:31

    God, comme je te comprends XD Le nombre de fois que j’ai relu mes anciens textes pour tomber sur une info qui me fait dire “QUOI? J’avais inventé CA? Mais c’est une super idée!!” XDDDD
    Il me faudrait presque un avatar “poisson rouge” XD

    2
    eirinna
    le
    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

    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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
    3 octobre 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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 19

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 28

    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/44/d152788678/htdocs/wordpress/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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 32

    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/44/d152788678/htdocs/wordpress/wp-includes/functions.php on line 33
    1:01

    Coucou Ness,

    Avec un peu de retard, je voudrais apporter ma pierre à tes problèmes de calendrier.
    D’abord, le calendrier basé sur le zodiaque me semble une mauvaise idée : les constellations sont toutes des “dessins” qui relient des étoiles qui n’ont parfois rien avoir les unes avec les autres et surtout qui ne sont visibles que de la Terre. Donc sur une autre planète, on en verrait d’autres, différentes.
    J’ai lu l’entrée précédente et ses commentaires. Je pense qu’un compte à partir de la guerre ou de la colonisation de la planète serait logique, pour marquer la coupure. Ensuite, je plussoie le fait que les calendrier révolutionnaires n’ont jamais pris : la semaine de sept jours est trop ancrée. Les soviets aussi s’y sont heurté quand ils ont voulu supprimer la dimanche.
    Changer ou nom les noms de mois, c’est toi qui vois. Une façon simple serait qu’ils les appellent premier, deuxième, etc. C’est de là que proviennent nos septembre, octobre, novembre, décembre, respectivement septième, huitième, neuvième et dixième mois de l’année (qui commençait deux mois plus tard, début mars).
    Dernier truc, j’adore les chapeau de chapitre (c’est comme ça qu’on nomme les mémoire du mage bidule en début).

Laisser un commentaire

XHTML: Vous pouvez utiliser ces tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

O: :blush: :cry: :embarrassed: :heart: :idea: :love: :nerd: :confused: :shocked: :silly: :P :yawn: :angry: :coffea: :depressed: :tired: :horrified: :kiss: :X :drunk: :shy: :sad: :sleep: :bad: ;) :blackheart: :cool: :evil: :D :lol: :sick: :fever: :pinkheart: :hardthinking: :) :good: :pray:


Warning: Illegal string offset 'solo_subscribe' in /homepages/44/d152788678/htdocs/wordpress/wp-content/plugins/subscribe-to-comments/subscribe-to-comments.php on line 304

S'abonner sans commenter