Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plain text files not interpreted as Unicode #13

Closed
ghost opened this issue Dec 14, 2016 · 18 comments
Closed

Plain text files not interpreted as Unicode #13

ghost opened this issue Dec 14, 2016 · 18 comments
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Dec 14, 2016

When uploading a plain text file encoded as Utf8 to a Next Cloud instance and opening it in the app, it gets partially unreadable.

The default encoding for text files should be Utf8.

@marinofaggiana
Copy link
Member

please @joelmeyerhamme attachment a example test file.

@ghost
Copy link
Author

ghost commented Dec 15, 2016

The attached Utf8 encoded file containing ä gets interpreted as ä in ISO Latin 1.
test.txt

@marinofaggiana
Copy link
Member

i see :
2016-12-15 17-04-13 3154

@ghost
Copy link
Author

ghost commented Dec 15, 2016

The bug appears to be specific to the .md file ending for Markdown. Haven't thought of that, sorry for not including it in the initial comment.

@marinofaggiana
Copy link
Member

oh Yes, true.

@rakekniven
Copy link
Member

rakekniven commented Apr 4, 2017

Did some tests.

Created three textfiles. Their names should explain everything. You will see screenshots for each file as well.

test-ansi.txt
test-utf8-wo-bom.txt
test-utf8-w-bom.txt

OK
2017-04-04 08-19-48 6185

OK
2017-04-04 08-19-54 6186

The UTF-8 file withoud BOM fails.
2017-04-04 08-19-59 6187

@KeiOtori
Copy link

KeiOtori commented Jul 25, 2017

I have the same issue here: after opening file content in UTF-8, viewer looks weird.
But i can copy broken text, and paste it into other app - there i see it in correct form.

Here is my example:

  • What i was supposed to see:
    default

  • What i really see:
    2017-07-25 11-32-11-1

My test file is attached, it is encoded in UTF-8, but in iOS app it is misinterpreted as Windows-1252 / CP-1252 (??)
TestingEncoding.txt

EDIT:
Oh, just found it out: if i manually convert this file from UTF-8 to UTF-8-BOM (in terms of notepad++, adding BOM char to the file?) - everything works and looks great. Maybe the issue is incorrect detection of encoding for UTF files without BOM?

@marinofaggiana
Copy link
Member

Thanks @KeiOtori I make a test

marinofaggiana added a commit that referenced this issue Jul 26, 2017
@marinofaggiana marinofaggiana added this to the v2.17.6 milestone Jul 26, 2017
@marinofaggiana
Copy link
Member

fixed.

@rakekniven
Copy link
Member

@marinofaggiana This is working AFAICS, or?

@marinofaggiana
Copy link
Member

yes.

@binss
Copy link

binss commented May 26, 2018

@marinofaggiana I still have this issue when I open the markdown(.md) file, but txt file display well

I have file test.md with content:

你好
こんにちは
hello

It seem wrong as md file:

img_248535134340-1

but good as txt file

img_ae44e2b432ba-1

EDIT:

The test.md is encoded in UTF-8. When I transform it to UTF-8 with BOM, It seems good.

@uiharu-s
Copy link

uiharu-s commented May 30, 2018

May I ask why this issue is closed? I’m still encountering this issue in the latest published version (2.20.8), specifically md with East Asian characters getting misencoded.

Edit: I see it’s included in a milestone, sorry

@rakekniven
Copy link
Member

The issues is about plain text files with file extension txt.
Could you please try to copy your file and change extension md to txt and give some feedback?

@binss
Copy link

binss commented May 30, 2018

When I change extension to txt, it shows correctly. I guess it maybe a decode problem for md extension file with plain text.

marinofaggiana pushed a commit that referenced this issue May 30, 2018
@marinofaggiana
Copy link
Member

@binss try with the next beta 2.21.0.00016

@rakekniven
Copy link
Member

rakekniven commented May 30, 2018

@marinofaggiana Bugfixing for feature release?

Is this related with #471

@marinofaggiana marinofaggiana modified the milestones: v2.17.6, v2.21.0 May 31, 2018
@ldesgrange
Copy link

Hi,

I still have a variant of this issue (but much less important). If I create a UTF-8 text file on my computer then in iOS app (2.22.2.2):

  • synchronize
  • when opening it shows the file correctly
  • when editing the encoding is fine too
  • save
  • file shows with the wrong encoding
  • going back to the folder and reopening the file shows it fine again.

So it looks like that only the view after saving the file has a wrong encoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants