Open GoogleCodeExporter opened 8 years ago
I can confirm that this patch is working for Cyrillic too
Cheers
Original comment by nchan...@gmail.com
on 23 Jul 2009 at 5:05
I'm using version 2.21 (the most recent) and my line 635 is the following (the
original) :
$val = htmlentities($val);
Till now i have been able to display all the characters (chinese, japanese,
arabic,
cyrillic, etc...) without any problem. The only issue, just discovered, is the
one
reported under the number 39 (Defect Character Encoding in utf-8). here
attached
there is a small program in php that i wrote to dump the excel file. Hope that
it
helps. Bye
Original comment by vve...@hotmail.it
on 28 Jul 2009 at 8:11
Attachments:
HI
I am having similar issue. IN my excel file i have text in different languages
(English, German, Italian, french, Greek, Portuguese, Russian, Chinese,
Japanese and
so on... probably 15 different languages)
Any help is much appreciated.
Original comment by kkv...@gmail.com
on 28 Oct 2009 at 6:21
Fixed in 2.22 at:
http://code.google.com/p/php-excel-reader2/
Original comment by sirsh...@gmail.com
on 19 Jan 2010 at 12:57
Hi
I already used 2.22. But result show funny chinese word. Everyone know what
problem?
result show like that 銷售貨單號碼
Original comment by nayzawli...@gmail.com
on 8 Apr 2010 at 7:44
Might be you need the right header in your output page:
header('Content-type: text/html; charset=utf-8');
Fixed the problem I was having displaying Japanese...
Original comment by gile...@gmail.com
on 13 May 2010 at 4:49
Thank u very much to solve my problem with the help of header....
Original comment by noname.n...@gmail.com
on 29 Jan 2011 at 7:53
header('Content-type: text/html; charset=utf-8'); i also use this but still got
same issue of this kind of language 銷售貨單號碼
Original comment by kalsooml...@gmail.com
on 11 Sep 2014 at 6:49
$excel = new PhpExcelReader;
$excel->setOutputEncoding("utf-8");
just set setOutputEncoding("utf-8"); where you are creating the excel reader
object
Original comment by 1212nik...@gmail.com
on 15 Sep 2014 at 11:37
Original issue reported on code.google.com by
enera...@gmail.com
on 14 Jul 2009 at 8:57Attachments: