With spip 2.0.3 and 2.0.5 I found taht if I configure the character set to ISO-8859-1
and not utf8 I can't write article at all !!!
In fact, if i write a text when i save it I loose all the text after the first accented vocal like "è" or "è".
I've just checked and I see this too.
I've added some calls to spip_log() to an installation of SPIP 2.0.5 on my development server and the texte field is correct (I used "This is a tést") all the way to the call to spip_mysql_query() (called from spip_mysql_update(), sql_update(), modifier_contenu(), revision_article(), articles_set(), action_editer_article_dist() called by the browser). It still truncates the field at the first "é", though.
Updating the database manually with the mysql command line or phpMyAdmin both work fine, so I've got not idea what SPIP is doing wrong.
Hi,
I need to transfer an old site in ISO-8859-1 in spip,
and I would like ti use the plugin Article PDF...
thanks for your tèst
2009/3/6 Thomas Sutton <thomas@bouncingorange.com>
Hi mmmx,
On 06/03/2009, at 1:05 AM, mmmx wrote:
Hi,
on spip dev they said I had to write here.
With spip 2.0.3 and 2.0.5 I found taht if I configure the character set to ISO-8859-1
and not utf8 I can't write article at all !!!
In fact, if i write a text when i save it I loose all the text after the first accented vocal like "è" or "è".
I've just checked and I see this too.
I've added some calls to spip_log() to an installation of SPIP 2.0.5 on my development server and the texte field is correct (I used "This is a tést") all the way to the call to spip_mysql_query() (called from spip_mysql_update(), sql_update(), modifier_contenu(), revision_article(), articles_set(), action_editer_article_dist() called by the browser). It still truncates the field at the first "é", though.
Updating the database manually with the mysql command line or phpMyAdmin both work fine, so I've got not idea what SPIP is doing wrong.
It seems you can change this row in spip_meta
charset_sql_connexion iso-8859-1
YES!!!
this helps…
Can you explain me why?
This is strange…
this field contains the charset used by MySQL to communicate with PHP. Normally, it’s automatically calculated.
Maybe a bug hadn’t changed this value correctly during a transfert / update. Maybe your web hosting service had changed it’s configuration without warning you, and SPIP hadn’t detected this change.
.Gilles
And have I to set the ‹ impt › field to ‹ non › or ‹ oui › ?