Project

General

Profile

Bug #6266

iso-8859-1 to UTF-8

Added by saen acro about 1 month ago. Updated about 1 month ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
Start date:
2023-04-23
Due date:
% Done:

0%

Estimated time:
Found in version:
ANY
Affected Versions:

Description

Lot of early code of TVH is in iso-8859-1 encoding
Representation of some character's in iso-8859-1,
with is not possible to be represented to other regions.
Converting to UTF-8 is necessary.

Github show them correct but on user system not.


Files

History

#1

Updated by Flole Systems about 1 month ago

  • Status changed from New to Invalid

Opening source files with wrong encoding is not a bug.

#2

Updated by saen acro about 1 month ago

Flole Systems wrote:

Opening source files with wrong encoding is not a bug.

It is problem, if your localization is not iso-8859-1.

if not BUG name it Optimization

#3

Updated by Flole Systems about 1 month ago

Again: If you open a file with the wrong encoding that's your fault. That "but report" can be submitted to every project out there, and they'll close it just like this. If you want to take care of making sure all files have the same encoding I can track it as feature request and assign you to it though.

#4

Updated by saen acro about 1 month ago

Flole Systems wrote:

Again: If you open a file with the wrong encoding that's your fault. That "but report" can be submitted to every project out there, and they'll close it just like this. If you want to take care of making sure all files have the same encoding I can track it as feature request and assign you to it though.

There is no such thing as opening with wrong encoding

Unfortunately you don't seem to realize that your computer is set with western european settings,
and you think the whole world is set with those.
Believe me, it's not like that in reality

Same is valid for teletext and regional settings on tv

Number Description Covers
8859-1 Latin 1 North America, Western Europe, Latin America, the Caribbean, Canada, Africa.
8859-2 Latin 2 Eastern Europe.
8859-3 Latin 3 SE Europe, Esperanto, miscellaneous others.
8859-4 Latin 4 Scandinavia/Baltics (and others not in ISO-8859-1).
8859-5 Latin/Cyrillic The Cyrillic alphabet. Bulgarian, Belarusian, Russian and Macedonian.
8859-6 Latin/Arabic The Arabic alphabet.
8859-7 Latin/Greek The modern Greek alphabet and mathematical symbols derived from the Greek.
8859-8 Latin/Hebrew The Hebrew alphabet.
8859-9 Latin/Turkish The Turkish alphabet. Same as ISO-8859-1 except Turkish characters replace Icelandic.
8859-10 Latin/Nordic Nordic alphabets. Lappish, Nordic, Eskimo.
8859-15 Latin 9 (Latin 0) Similar to ISO-8859-1 but replaces some less common symbols with the euro sign and some other missing characters.
2022-JP Latin/Japanese 1 The Japanese alphabet part 1.
2022-JP-2 Latin/Japanese 2 The Japanese alphabet part 2.
2022-KR Latin/Korean 1 The Korean alphabet.
#5

Updated by saen acro about 1 month ago

More clear than this

#6

Updated by saen acro about 1 month ago

8859-1 Flole Systems
8859-5 Флоле Системс

#7

Updated by Flole Systems about 1 month ago

saen acro wrote:

There is no such thing as opening with wrong encoding

There is. I can select in my IDE which encoding the file has. If I select the wrong one the file is messed up, but that's entirely my fault then. If your IDE doesn't allow setting the encoding you should contact the support from your IDE and raise it as feature request/bug report there. Good IDEs even detect it automatically in most cases.

I'm not going to argue about this with you, if you want to change it feel free to submit a PR.

Also available in: Atom PDF