search

chokkarg / worktime

Automatically exported from code.google.com/p/worktime
0 stars 0 forks source link

Export file is not UTF-8 and misses BOM (screws up Russian and Hebrew export files) #100

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.exporting the file that has hebrew writings cout out as gibrish

What is the expected output?

What do you see instead?

What version of the product are you using (check the about screen for the
version or version number)?

Please provide any additional information below.

Original issue reported on code.google.com by shay.nah...@gmail.com on 16 Mar 2012 at 6:09

GoogleCodeExporter commented 8 years ago 
Thanks for your report!

What exactly goes wrong?
Is there an error somewhere during the creation of the report or is it just the 
file that is not-readable?

Could you provide me some files?
First of all the backup file (you can create it through 'Preferences' -> 
'Backup & Resotre', this saves a file to your SD-card (in 
/sdcard/worktime-backup/
And secondly if this issue is about unreadable exported (csv) files can you 
also attach those?

If (for privacy issues) you do not want or cannot attach the files on this page 
you can send them to me at dirkvranckaert@gmail.com

It's important for me to have the backup file so that I can reproduce the issue 
on one of my devices in order to be able to fix it!

Also what version of the application are you using?

Original comment by dirkvran...@gmail.com on 17 Mar 2012 at 8:49

GoogleCodeExporter commented 8 years ago 
Reply by mail from user (with attachment of export file):

I'm using the latest version of the app.
There is no error during the creation of the file and the file is created just 
fine... 
but, when i load the file in excel, I cant see hebrew letters but rather some 
king of strange Greek letters.

I've incountered with problems like this in the past...I believe it's a problem 
due to language encoding (just like in html, where you have to specify in which 
language you want to decode the file later - so when you write the file you
have to tell android in what language to write it.

Original comment by dirkvran...@gmail.com on 19 Mar 2012 at 7:15

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 19 Mar 2012 at 7:15

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 19 Mar 2012 at 7:27

GoogleCodeExporter commented 8 years ago 
This issue is fixed now.
Problem was that no UTF-8 encoding was applied and that the BOM (Byte Order 
Mark) should be set on the file.

Original comment by dirkvran...@gmail.com on 30 Mar 2012 at 7:28

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r423.

Original comment by dirkvran...@gmail.com on 30 Mar 2012 at 7:31

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 15 May 2012 at 9:30

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 15 May 2012 at 9:38

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 15 May 2012 at 9:50

GoogleCodeExporter commented 8 years ago

Original comment by dirkvran...@gmail.com on 15 May 2012 at 9:55