Created attachment 182250 [details] Error opening file It's impossible to open any file named in Arabic. See attached image and file. Version: 7.3.5.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 7.3.5-3 Calc: threaded Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-3-MANJARO (64-bit) Graphics Platform: X11
Created attachment 182251 [details] Test file
(In reply to medmedin2014 from comment #1) > Created attachment 182251 [details] > Test file It seems the file that I uploaded with Arabic name, when you download it from this bugs platform it comes modified with wrong encoding and creates a random non readable filename.
Created attachment 182253 [details] Test file 2 Here it's zipped to avoid encoding change in filename.
Are you saying it only doesn't open with LO and that it opens with some other program?
Works fine for me with: Version: 7.3.6.1 (x64) / LibreOffice Community Build ID: 92b673af3a5e8f7cf4716be88dfaca424612f244 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Version: 7.4.1.1 (x64) / LibreOffice Community Build ID: 0a046a10cbf1679eea5538bd3ab63156caa3a036 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Please test with a clean profile, Menu/Help/Restart in Safe Mode
(In reply to m.a.riosv from comment #5) > Please test with a clean profile, Menu/Help/Restart in Safe Mode The bug is reported on Linux (Manjaro KDE) not on Windows.
(In reply to Timur from comment #4) > Are you saying it only doesn't open with LO and that it opens with some > other program? Yes, the file can be opened on Linux (Manjaro KDE) using Calibre E-Book viewer and WPS and even Ark (zipper/unzipper tool).
I don't know what I need in Linux to even see Arabic file name.
(In reply to Timur from comment #8) > I don't know what I need in Linux to even see Arabic file name. Simply use Noto Sans as system font, it has wide range support for many languages.
It seems the problem is not related to only Arabic script, but it also happens with Hebrew, Thai, Russian and Japanese.
(In reply to medmedin2014 from comment #9) > (In reply to Timur from comment #8) > > I don't know what I need in Linux to even see Arabic file name. > Simply use Noto Sans as system font, it has wide range support for many > languages. It needs something more to get it proper as in your screenshot.
Created attachment 182280 [details] Font settings (In reply to Timur from comment #11) > It needs something more to get it proper as in your screenshot. I don't know, but here's my font configuration with installed font packages.
Let's try with Hossein of TDF, please see.
Created attachment 182358 [details] i attached screenshot for proof
NOT REPRODUCIBLE Steps Followed: 1.read the problems faced in previous versions and other OS 2.open my version of Libre Office 3.Create a new file with arabic letters 4.i opened the file in my system 5.no error in my file while opening that file. that file has no error in our environment and also it will acquire both arabic and non arabic language . ENVIRONMENT:LibreOffice 7.4.0.3 release/win_X64_msi
Created attachment 182371 [details] Can Open file Non Latin Laguage Step1-open libre office file Step2-Upload some Contant Step3-And save the Documents in non latin language Step4- You can open that document Environment libre office curent vertion-6.4.7.2 linux mint curent vertion-21
Back to reporter to find out the cause.
(In reply to Sundaravadivel G from comment #17) > ENVIRONMENT:LibreOffice 7.4.0.3 release/win_X64_msi The problem happens on Linux not Windows.
(In reply to Pradeep M from comment #18) > Environment > libre office curent vertion-6.4.7.2 > linux mint curent vertion-21 We are talking about LibreOffice 7.3.5.2, your installed version is too old. Can you re-test with 7.4 or even with the dev version 7.5.0.0.alpha0+
I changed the OS field to Linux due to Comment 0, Comment 18, and Comment 20.
(In reply to Timur from comment #13) > Let's try with Hossein of TDF, please see. I tried to open this file on my Ubuntu Linux, and it was OK: /home/hossein/عربي/فارسی.odt In my test with loading from "file > open", drag an drop, and also command line, the file was loaded without any problem. It was not reproducible with: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: de57562e3b11b64d95344a4ebaaf53607e7bc373 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I suggest you to open the file with drag/drop, and check if you can open the file. On the other hand, somehow similar problem was happening when setting the locale to C, but with a different error message: "The operation on ... was started with an invalid parameter." $ LANG=C instdir/program/soffice Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: de57562e3b11b64d95344a4ebaaf53607e7bc373 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (C); UI: en-US Calc: threaded I think this is a locale/encoding problem in a part of your system. Are you sure you are using UTF-8 everywhere? Another thing to test: Can you see if this setting has any effect on the problem? Options > General > Open/Save Dialogs > [ ] Use LibreOffice dialogs
Hello medmedin2014, I am setting the bug status to NEEDINFO, because more information about your system settings (language, locale, etc.) is needed to understand the cause of the problem. Information from LibreOffice about dialog is useful (as you provided it), but it is not enough to further follow the cause of the problem. Please respond to the questions in comment 23. With the current details, the problem is not reproducible for me.
(In reply to Hossein from comment #23) > On the other hand, somehow similar problem was happening when setting the > locale to C, but with a different error message: "The operation on ... was > started with an invalid parameter." After opening "/etc/locale.gen" I found that my previous selected entry "en_US.UTF-8 UTF-8" was disabled (commented), I don't how it ended like that, may be due to last upgrades it was reset to that configuration without prompting. After enabling that entry and rerun "sudo locale-gen" on terminal all worked again like it was before. Thanks for your precious help.
I wonder, though... could we possibly detect cases where it is _likely_ that this is what's happening (e.g. getting an empty filename, getting a filename with stand-in characters, or spaces, etc.) and give a more verbose warning suggesting this may be the cause of the problem?