Strict Standards: Redefining already defined constructor for class wpdb in /homepages/10/d212871047/htdocs/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/10/d212871047/htdocs/wp-includes/cache.php on line 389

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

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

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

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

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

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

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

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

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

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

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

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-includes/theme.php on line 507

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/dofollow.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /homepages/10/d212871047/htdocs/wp-includes/wp-db.php:52) in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 1088

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/simpletagging/simpletagging.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 41

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 44

Deprecated: Function ereg() is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/tantan_reports.php on line 39

Deprecated: Function ereg() is deprecated in /homepages/10/d212871047/htdocs/wp-content/plugins/tantan/version-check.php on line 201

Strict Standards: Non-static method NAVT::wp_bootstrap() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 1743

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

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method NAVT::init() should not be called statically in /homepages/10/d212871047/htdocs/wp-includes/plugin.php on line 160

Strict Standards: Non-static method NAVT::install_check() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 112

Strict Standards: Non-static method NAVT::get_option() should not be called statically in /homepages/10/d212871047/htdocs/wp-content/plugins/wordpress-navigation-list-plugin-navt/app/navt.php on line 173
accents mal-aimés du courrier électronique communaute de noctambules
Warning: Creating default object from empty value in /homepages/10/d212871047/htdocs/wp-content/themes/dkret2/header.php on line 45

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/kses.php on line 511

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/10/d212871047/htdocs/wp-includes/functions.php on line 14

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/10/d212871047/htdocs/wp-includes/functions.php on line 23

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/10/d212871047/htdocs/wp-includes/functions.php on line 25

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/10/d212871047/htdocs/wp-includes/functions.php on line 27

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/10/d212871047/htdocs/wp-includes/functions.php on line 28

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/10/d212871047/htdocs/wp-includes/functions.php on line 14

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/10/d212871047/htdocs/wp-includes/functions.php on line 23

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/10/d212871047/htdocs/wp-includes/functions.php on line 25

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/10/d212871047/htdocs/wp-includes/functions.php on line 27

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/10/d212871047/htdocs/wp-includes/functions.php on line 28

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 568

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-content/plugins/polls/polls.php on line 577

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/10/d212871047/htdocs/wp-includes/formatting.php on line 74

ACCENTS MANQUANT DANS LES MAILS

Pourquoi les accents sont les mal-aimés du courrier électronique ?
Ne nous le cachons pas, l’e-mail est à l’origine américain. Et outre-atlantique, les caractères accentués ne courent pas les rues. Ce qui explique que les concepteurs du mail aient “oublié” de prendre en compte les accents.

Pourquoi Internet ne peut-il pas prendre en compte les accents ?
On va passer par une petite explication technique.
Sur Internet, on ne transmet pas directement les caractères. On associe à chacun un code en binaire - exactement comme un code barre formé de traits fins et de traits épais - et c’est ce code qui circule sur Internet.
Le nom du code originel (celui qui n’aime pas les accents), c’est le code ASCII (ou US-ASCII). Grâce à lui, chaque caractère (a, b, c, …, A, B, C, 0,1,2, …,$, #, etc.) est associé à un code sur 7 bits, c’est à dire un code formé de 7 barres.

Ce codage sur 7 bits ne peut répertorier que 128 caractères.
Faisons les comptes : 10 chiffres (de 0 à 9), 26 lettres minuscules, 26 lettres majuscules, une dizaine de signes de ponctuation, des caractères exotiques (&, #, \, $, %) et des caractères spéciaux (retour-chariot, etc)… il ne reste plus assez de cases libres dans les 128 pour introduire nos accents.

Alors comment va-t-on caser nos accents ?
Une seule solution : ajouter une barre (1 bit) pour pouvoir répertorier davantage de caractères. Passer de 7 bits à 8 bits permet en effet d’accepter le double de caractères (de 128 à 256).

Alors ça y est c’est bon ?
Non hélas ! Le courrier électronique est à l’origine basé sur le protocole SMTP, qui ne gère que le code à 7 bits. Et le protocole à 8 bits qui lui succède, l’ESMTP, n’est pas encore installé sur tous les serveurs (on ne peut pas changer tout le système du jour au lendemain) ! Donc, pour pouvoir faire passer des codes à 8 bits dans un système de codes à 7 bits, il faut ruser !

C’est quoi la ruse ?
Coder. C’est à dire trafiquer un peu le message pour qu’il puisse passer sans problème à travers les mailles du filet. Deux principaux systèmes de codage cohabitent, au sein d’un ensemble appelé MIME :

* Le Quoted-Printable
Les caractères accentués sont remplacés par des signes = suivis du code hexadécimal du caractère (par exemple =E9 pour “é”…). L’ensemble du message ne contient donc plus que des caractères 7 bits et passe sans encombres à travers les différentes passerelles du Net. A l’arrivée, le logiciel de messagerie fait l’opération inverse.
* Le Base64
Les caractères 8 bits sont codés sur 6 bits : un groupe de 3 octets (soit 24 bits) devient ainsi 4 ensembles de 6 bits, les 6 bits représentant un sous-ensemble de l’US-ASCII : A-Z, a-z, +, /, et =. Là aussi, l’ensemble du message passe sans encombres à travers les différentes passerelles du Net.

Si vous ne codez pas votre message, celui-ci est envoyé au format 8 bits
Les caractères accentués ne sont alors pas convertis et sont envoyés tels quels. Cette méthode comporte des risques. En cas de rencontre avec une (vieille) passerelle 7 bits, vous pouvez avoir plusieurs cas de figure :

* le message est converti en Quoted-Printable (cas le plus fréquent).
* le message est converti en base 64.
* les accents du message sont transformés par des caractères faisant partie du jeu de caractère 7 bits.
* Les accents du message sont remplacés par des caractères exotiques (Ä, Æ, š, etc.) Ceci se produit quand le jeu de caractères par défaut n’est pas le même sur les deux machines (iso-8859-1, 8859-2…).

Je fais comment en pratique ?
Il faut plusieurs conditions pour que les accents “passent”.
1. que votre logiciel de courrier et celui de votre correspondant supportent le MIME (Quoted printable et Base 64) et soient correctement configurés
2. que tous les routeurs (ordinateurs qui font circuler l’information) entre votre machine et la sienne n’y soient pas trop allergiques.

Source www.arobase.org

PARCOURS ET FONCTIONNEMENT MAILS
STOCKAGE DU COURRIER
LES PROTOCOLES
STANDARD MIME
WEBMAILS GRATUITS

Comment surfer sur Internet ?
Ce dossier va vous permettre de parfaitement connaitre les bonnes références pour surfer vite et bien. Vous étudierez les moteurs de recherche, les annuaires, ainsi que les bases de données !
Vive le web rapide et efficace !

Sécuriser son pc
Ici, vous trouverez toutes les solutions contre les agressions extérieures, pour maintenir son pc en bon état de fonctionnement. Vous protéger de toutes les agressions du web: vers, virus, chevaux de troie et autres spywares. Pour combattre au quotidien ces attaques sur Internet et les moyens de s’en protéger…

Hardware, le matériel informatique
Retrouvez tous les éléments physiques informatiques, pouvant appartenir à un ordinateur, du moniteur…à la mémoire vive

Lexique-glossaire informatique
Voici un petit lexique destiné à mieux connaître la signification des principaux termes employés dans le jargon informatique…Vous pouvez rechercher une définition particulière en utilisant l’index thématique. Tous les termes de A à Z.

aucun
Olivier

Ecrire un commentaire








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/10/d212871047/htdocs/wp-content/plugins/math-comment-spam-protection/math-comment-spam-protection.classes.php on line 77

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/10/d212871047/htdocs/wp-content/plugins/math-comment-spam-protection/math-comment-spam-protection.classes.php on line 163