Hi,
thanks for your interest in GLPI.
A similar bug report could be found here :
http://www.glpi-project.org/forum/viewtopic.php?id=22834
The proposed solution : replace \w by \p{L}
Could you test it and validate the proposed solution ?
For the second problem, you are right about addslashes.
Thanks for all.
Regards
Le 02/02/2011 16:08, Denis Linvinus a écrit :
Hi GLPI team!
i'm migrating from 0.72.2 to 0.78.2, because almost all my patches was
included in this release,
but again utf8 problems :)
There is my favorite template, it indicate that followup is private
only if that is true
##FOREACHfollowups##
[##followup.date##] Новый ответ по заявке ##lang.followup.author##
##followup.author## ##IFfollowup.isprivate=Да##
##lang.followup.isprivate## ##ENDIFfollowup.isprivate## :
##followup.description##
##ENDFOREACHfollowups##
But it will not works because \w in regexp support only latin symbols.
This bug can be easily resolved if use .*?
notificationtemplate.class.php_utf8.patch
Second problem with mailgate and ticket,
when creating new ticket from email, with empty email subject,
ticket subject creating from mail body with limiting to 70 utf8 chars,
but! if at place 69-71 was \\n then ticket subject will contain
incorret text which will cause error in mysql
Error posted there http://pastebin.com/DqTFCX8u
Look at \\n *\\\*',\'yyyyyyyy...@xxxx.ru
Possible solution, but i'm not sure at 100%
ticket.class.php_slashes_problem.patch
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
