-
-
Notifications
You must be signed in to change notification settings - Fork 899
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
Comments
please @joelmeyerhamme attachment a example test file. |
The attached Utf8 encoded file containing |
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. |
oh Yes, true. |
Did some tests. Created three textfiles. Their names should explain everything. You will see screenshots for each file as well. |
I have the same issue here: after opening file content in UTF-8, viewer looks weird. Here is my example: My test file is attached, it is encoded in UTF-8, but in iOS app it is misinterpreted as Windows-1252 / CP-1252 (??) EDIT: |
Thanks @KeiOtori I make a test |
fixed. |
@marinofaggiana This is working AFAICS, or? |
yes. |
@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:
It seem wrong as md file: but good as txt file EDIT: The test.md is encoded in UTF-8. When I transform it to UTF-8 with BOM, It seems good. |
Edit: I see it’s included in a milestone, sorry |
The issues is about plain text files with file extension txt. |
When I change extension to txt, it shows correctly. I guess it maybe a decode problem for md extension file with plain text. |
@binss try with the next beta 2.21.0.00016 |
@marinofaggiana Bugfixing for feature release? Is this related with #471 |
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):
So it looks like that only the view after saving the file has a wrong encoding. |
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.
The text was updated successfully, but these errors were encountered: