Snipe-it: All Export document problem with Thai Language (UTF8)

[9xmen007]

At first I would like to say "Big Thank you " for your powerful apps.

Now I implement system successfully. and have some issue.

When I try to export any report with all format. It problem with text encoding in Thai Language. I attached an example for issue.

Thank you again!

[uberbrady]

I was working on a similar problem.

Can you attach the .csv file here, so I can look at it? If there's nothing secret in your export.

If not, can you open your .csv file in a text editor and just replace with 'X' the data that you don't want shared?

If you'd prefer to email me personally a copy of the .csv, we can arrange that too.

[snipe]

I think this is a duplicate of #1023

[9xmen007]

Update!! Only can read in txt format . but problem with excel.
@uberbrady this my csv.

https://app.box.com/s/qyt7ryf9te799gh28egf8gu5v6otujgz

[9xmen007]

Problem resolve;

I open csv file with notepad++ and change encoding from UTF-8 without BOM to UTF-8.
and now can open with excel normally.

Thank you.

[uberbrady]

@9xmen007 Thank you!

And that sounds like a great solution, at least a workaround.

Does this also look correct to you? (I'm sorry, I don't speak or read Thai at all, so I'm just going by looking at it visually).

[uberbrady]

Can you also upload the 'fixed' version? It sounds like we may have to start adding BOM markers to our export files...

[9xmen007]

@uberbrady This correct format for my language.

I send you file with remove bom

https://app.box.com/s/w9f3i93o9bj8wyvkyjzpfssycy5ctn8j

[uberbrady]

Excellent, thank you.

What's actually happening is that you're _adding_ a BOM - I can see it at the start of the file -

od -t x1 ~/Downloads/report.1.csv |head -1
0000000    ef  bb  bf  41  73  73  65  74  20  54  61  67  2c  e0  b8  9c

(EF BB BF is the Byte-Order Marker, the BOM)

This probably makes it so that Excel doesn't panic about the UTF8 that's in the file. Super strange though. Still doesn't work on the Mac, though - but that's Microsoft's fault, not anyone else's (it's a known problem).