swdyh / goodbye_chatwork

Chatwork(chatwork.com) log downloader
MIT License
67 stars 24 forks source link

help about character corruption #6

Open adofe-ask opened 8 years ago

adofe-ask commented 8 years ago

HI, thanks for this great gem. We are using Japanese in the chatwork, the log generated was character corruption. (the content and files both) How can I fix it by my own? or any function may be apply to solve this problem? Thanks you.

hirokishirai commented 8 years ago

@adofe-ask Please give us source characters and result characters(corrupted logs). If you have other informations help this issue, they also please.

And which plan do you use?

adofe-ask commented 8 years ago

We are using ChatWork. Becasue of company secret I can't give you the source. Just pick one of the corrupted photo file here 90066904_ Thanks a lot

hirokishirai commented 8 years ago

@adofe-ask Sorry, I can't Investigate logical destruction images.

Could you try the following flow?

  1. Create a new group chatroom with only you(You can create from '+' button is upper part of the left side menu).
  2. Post some messages with no secret informations to group chatroom that you created in japanese.
  3. Export logs from group chatroom that you created with goodbye_chatwork gem.
hirokishirai commented 8 years ago

@adofe-ask

# Check room_id of group chat that you created
$ goodbye_chatwork -i example@example.com -p your_password
# Export logs
$ goodbye_chatwork -i example@example.com -p your_password -e room_id
hirokishirai commented 8 years ago

@adofe-ask Have you solved your question?

adofe-ask commented 8 years ago

not solve yet ... these days are busy.... will export logs on monday thanks a lot

ghost commented 7 years ago

@adofe-ask Do you still have this problem?

ghost commented 7 years ago

@adofe-ask Hi. În japan, some people have same issue on windows PC. Is your PC windows?

swdyh commented 7 years ago

I fixed the option when saving the download file, so please try out the new version.

I have not prepared the environment in which the problem occurs, so I can not confirm if this problem has been fixed