Imre Posted September 25, 2018 Posted September 25, 2018 Members 0 1 post Posted September 12 Importing non English text only (txt) file does not import characters not present in the English alphabet.
walt.farrell Posted September 25, 2018 Posted September 25, 2018 Can you supply a sample text file as an attachment? -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Imre Posted September 27, 2018 Author Posted September 27, 2018 I attached the original Affinity file and the pdf version of it. HU_text_only_import.afpub HU_text_only_import.pdf
walt.farrell Posted September 27, 2018 Posted September 27, 2018 Thanks, but I was particularly interested in the original of the .txt file you imported, as you said the error is with the import. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Imre Posted September 28, 2018 Author Posted September 28, 2018 This is the txt file I used. Hungarian_test.txt
walt.farrell Posted September 28, 2018 Posted September 28, 2018 Thanks, Imre. Your problem seems to be that Publisher is expecting a file encoded as UTF-8 but your file is encoded as ANSI. Here's a version of your file converted to a UTF-8 encoding, and it imports correctly into Publisher for me, at least for all the characters I checked. This is probably a bug in Publisher's detection of file encoding. I've had some experience with that, and it can be tricky to figure out a good algorithm until you've seen this kind of problem once Hungarian_test-utf8.txt -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Imre Posted October 2, 2018 Author Posted October 2, 2018 Thank a lot. You are right I have saved an UTF-8 tetxt file mysels and it worked fine. Hopefully the fina version will be smarter.
pdussart Posted October 3, 2018 Posted October 3, 2018 Imre, This is not an issue of Publisher. ANSI is limited versus UTF-8. American versus global. I think it is advisable to use UTF8, especially regarding accents and special chararcters, when you exchange docments between different applications. Email, Web screens, prints and electronic documents are better supported through UTF8. What you see on one side looks the same on the other side. There are a lot of variants of ANSI which makes its management even more complicated See for instance http://www.differencebetween.net/technology/protocols-formats/difference-between-ansi-and-utf-8/ Regards, Philippe
walt.farrell Posted October 3, 2018 Posted October 3, 2018 7 hours ago, pdussart said: This is not an issue of Publisher. I will respectfully have to disagree. While it may not be possible 100% of the time to properly "guess" a file's encoding, there are techniques that will let a program get very close, and that would have dealt with Imre's file successfully and allowed Publisher to detect it as an ANSI-encoded file. Notepad++ on Windows, for example, handled his file properly, recognizing the encoding and getting the characters correct. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Gnobelix Posted October 3, 2018 Posted October 3, 2018 On 9/25/2018 at 8:50 PM, Imre said: Importing non English text only (txt) file does not import characters not present in the English alphabet. Hello Imre, the text that you have provided, I can open without problems. I am not sure if it is displayed correctly, since I have no knowledge in Hungarian language. I am using Windows 10 as OS. Cheers Affinity Photo 2.6: Affinity Photo 1.10.6: Affinity Designer 2.6: Affinity Designer 1.10.6: Affinity Publisher 2.6: Affinity Publisher 1.10.6: Windows 11 Pro (Version 24H2 Build (26100.3915)
Imre Posted October 3, 2018 Author Posted October 3, 2018 Thanks a lot. It displays correctly. I also played with the text and if I save the tyt file with UTF-8 coding, it works fine always.
Recommended Posts