Forum › Forums › New users › New Users and General Questions › txt encoding
Tagged: encoding detect convert
- This topic has 24 replies, 7 voices, and was last updated Feb 25-5:43 pm by andfree.
-
AuthorPosts
-
February 22, 2023 at 10:09 am #100308Member
sybok
::@andfree:
Well, that’s embarrassing. I cannot find the option mentioned in the link (from May 2020) in my LO 7.4.5.
Encoding option is clearly present when importing a file into a LO Calc.February 22, 2023 at 11:21 am #100316Member
zblsv
::I’ve got this:
echo 4fDv9PHd8OXpCurh9OHq8d7s7enz5wrz+evn7dzx6eEK4fXu5+zd7efyCurh9OHt3Ov58+fyCuM= | base64 -d | iconv -f ISO-8859-7 -t utf-8αποτρέπει κατακρήμνιση σωληνάρια αυξημένης κατανάλωσηςWhich is translated to this:
prevent precipitation tubules increased consumptionSo, try
iconv -f ISO-8859-7 -t utf-8 -c -o mg-greek.txt mg.txt
more mg-greek.txtWords are carried away by the wind...
February 22, 2023 at 5:59 pm #100356Member
marcelocripe
::Hello andfree.
I suspect it’s a problem with missing fonts in antiX. Because I have the same problem, several languages are replaced by unrecognizable characters, especially languages that are not derived from Latin.
When I have a text file “.txt” in “pt_BR” language that was created in Windows Notepad and I have to open it in antiX, I first try to open it with Leafpad, if it doesn’t work I try to open it with Writer from LibreOffice, so I can copy the text and paste it into a new “.txt” file created by Leafpad in antiX.
– – – – –
Olá andfree.
Eu desconfio que seja um problema de falta de fontes no antiX. Porque eu tenho o mesmo problema, pois vários idiomas são substituídos por caractereses irreconhecíveis, em especial dos idiomas que não são devivados do latim.
Quando eu tenho um arquivo de texto “.txt” em idioma “pt_BR” que foi criado no bloco de notas do Windows e tenho que abrir no antiX, eu tento primeiro abrir com o Leafpad, se não funcionar eu tento abrir com o Writer do LibreOffice, assim eu consigo copiar o texto e colar em um novo arquivo “.txt” criado pelo Leafpad no antiX.
February 24, 2023 at 5:53 am #100511Memberandfree
::Thanks for the replies.
When I have a text file “.txt” in “pt_BR” language that was created in Windows Notepad and I have to open it in antiX, I first try to open it with Leafpad, if it doesn’t work I try to open it with Writer from LibreOffice, so I can copy the text and paste it into a new “.txt” file created by Leafpad in antiX.
In my case, none of these tries worked.
I cannot find the option mentioned in the link (from May 2020) in my LO 7.4.5.
Encoding option is clearly present when importing a file into a LO Calc.This is the case for my LO 7.4.5.1, too.
echo 4fDv9PHd8OXpCurh9OHq8d7s7enz5wrz+evn7dzx6eEK4fXu5+zd7efyCurh9OHt3Ov58+fyCuM= | base64 -d | iconv -f ISO-8859-7 -t utf-8
αποτρέπει
κατακρήμνιση
σωληνάρια
αυξημένης
κατανάλωσηςThat’s right.
iconv -f ISO-8859-7 -t utf-8 -c -o mg-greek.txt mg.txt
more mg-greek.txtIt works. Many thanks.
February 24, 2023 at 9:07 am #100521MemberRobin
::iconv -f ISO-8859-7 -t utf-8
Great it works finally for you. What zblsv succeeded with was exactly what I had suggested originally:
or try some of the ISO-8859-x encodings.
Windows is like a submarine. Open a window and serious problems will start.
February 24, 2023 at 9:24 am #100522Memberandfree
::What zblsv succeeded with was exactly what I had suggested originally
You are right. Unfortunately, I had tried it in a different (wrong?) way:
$ iconv --from-code=ISO-8859-1 --to-code=ISO-8859-7 mg.txt > mg1.txt iconv: illegal input sequence at position 0Thanks for your help.
- This reply was modified 2 months, 2 weeks ago by andfree.
February 24, 2023 at 10:03 am #100525MemberRobin
::(wrong?) way:
Yes. You want utf-8 as output (–to-code= or -t) on antiX. And you have to run the input (–from-code= or -f) through the avialable encodings, in order to check out whether one of them applies to your file. Then you’d have ended up with the very encoding zblsv has succeeded with.
No problem, we are all here to learn constantly.
Windows is like a submarine. Open a window and serious problems will start.
February 25, 2023 at 6:00 am #100611Memberandfree
::Thanks, again.
You want utf-8 as output (–to-code= or -t) on antiX. And you have to run the input (–from-code= or -f) through the avialable encodings
You are right, again. I had tried all the ISO-8859-x series of encodings as output, not as input. Instead, this worked:
$ iconv --from-code=ISO-8859-7 --to-code=utf-8 mg.txt > mg1.txtI wonder if zblsv tried one after another the ISO-8859-x series of encodings as input or he ended up with ISO-8859-7 another way.
- This reply was modified 2 months, 2 weeks ago by andfree.
February 25, 2023 at 12:44 pm #100626Member
zblsv
::I wonder if zblsv tried one after another the ISO-8859-x series of encodings as input or he ended up with ISO-8859-7 another way.
I have taken note of your words about the Greek language. ISO-8859-7 is the Greek encoding. Now I don’t remember any utility that could detect the language (by vowels and syllables) for decoding from the ISO-8859 series. Therefore I have been to translate… Excuse my Yandex-English.
Words are carried away by the wind...
February 25, 2023 at 5:43 pm #100636Memberandfree
-
AuthorPosts
- You must be logged in to reply to this topic.