Nail Et Caract

[Kramlech]

Bonjour

Je suis en train de faire un script pour surveiller le contenu d'un dossier de mon NAS, script qui doit se terminer par l'envoie d'un mail ...

Pour cela, j'ai donc installé nail par ipkg, mais je butte sur un problème de caractère accentué. Dès que j'ai un tel caractère dans le message à envoyer, nail se plante et me renvoie le message suivant :

Cannot convert from ANSI_X3.4-1968 to iso-8859-1

Invalid or incomplete multibyte or wide character

"/root/dead.letter" 3/91

. . . message not sent.

(pour information, l'envoi de message fonctionne très bien si je n'ai pas d'accent).

Est-ce que quelqu'un aurait une idée pour me sortir de cette impasse ?

Merci

Modifié le 16 novembre 2012 par Kramlech

[Kramlech]

Ma question ne mobilisant pas les foules, je vais la poser autrement :

Quelle solution ai-je pour changer le type de codage d'une chaine de caractères (de type de la commande iconv que je n'ai trouvé ni en natif, ni dans ipkg), ou alors pour transformer tous ces caractères spéciaux en caractères basic ? ....

[psuken]

Hello,

Perso je n'y connais (encore) pas grand chose dans ce genre de commandes.

Est-ce que cette info t'aide ?

Character sets

Mailx normally detects the character set of the terminal using the LC_CTYPE locale setting. If the locale cannot be used appropriately, the ttycharset variable should be set to provide an explicit value. When reading messages, their text is converted to the terminal character set if possible. Unprintable characters and illegal byte sequences are detected and replaced by Unicode substitute characters or question marks unless the print-all-chars is set at initialization time.

The character set for outgoing messages is not necessarily the same as the one used on the terminal. If an outgoing text message contains characters not representable in US-ASCII, the character set being used must be declared within its header. Permissible values can be declared using the sendcharsets variable, separated by commas; mailx tries each of the values in order and uses the first appropriate one. If the message contains characters that cannot be represented in any of the given character sets, the message will not be sent, and its text will be saved to the 'dead.letter' file. Messages that contain NUL bytes are not converted.

Outgoing attachments are converted if they are plain text. If the sendcharsets variable contains more than one character set name, the ~@ tilde escape will ask for the character sets for individual attachments if it is invoked without arguments.

Best results are usually achieved when mailx is run in a UTF-8 locale on a UTF-8 capable terminal. In this setup, characters from various countries can be displayed, while it is still possible to use more simple character sets for sending to retain maximum compatibility with older mail clients.

Source : http://linux.die.net/man/1/nail

[Kramlech]

Merci psuken

Je n'étais pas tombé sur cette doc (google est votre ami, mais parfois, il faut réussir à lui poser la bonne question !....)

En fait le passage important est le suivant :

The character set conversion relies on the iconv(3) function. Its functionality differs widely between the various system environments mailx runs on. If the message 'Cannot convert from a to b' appears, either some characters within the message header or text are not appropriate for the currently selected terminal character set, or the needed conversion is not supported by the system. In the first case, it is necessary to set an appropriate LC_CTYPE locale (e.g. en_US) or the ttycharset variable. In the second case, the sendcharsets and ttycharset variables must be set to the same value to inhibit character set conversion. If iconv() is not available at all, the value assigned to sendcharsets must match the character set that is used on the terminal.

Il suffit donc de mettre les lignes :

set sendcharsets=utf-8

set ttycharset=utf-8

dans le fichier nail.rc pour que tout fonctionne !!!!

Modifié le 16 novembre 2012 par Kramlech