Testflight: Bug : .txt files with ANSI or UNICODE encoding can not be opened
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Expected behaviour
ANSI or UNICODE .txt files should open
Actual behaviour
.txt files with ANSI or UNICODE encoding do not open.
.txt files with UTF8 encoding open with unreadable characters replacing accentuated characters (é, à for example).
.txt files with UF8 with BOM do open
Steps to reproduce
open a .txt file with ANSI encoding.
Reasoning or why should it be changed/implemented?
It's a bug (or maybe me)
iOS version
12.4 (language is french)
App version
3.00 bêta
Server configuration
Operating system:
FreeBSD
Web server:
Caddy
Database:
MariaDB
PHP version:
7.3
Nextcloud version: (see Nextcloud admin page)
18.0.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with ANSI, Unicode, UTF-8, and UTF-8-with-BOM .txt files on the stated iOS and app versions. Trace the iOS text-file opening path and verify that each encoding opens with accented characters rendered correctly; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100