Bug 150567 - LibreOffice is showing unreadable file names it the name uses Arabic or Persian characters.
Summary: LibreOffice is showing unreadable file names it the name uses Arabic or Persi...
Status: RESOLVED DUPLICATE of bug 125995
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.0.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-23 18:49 UTC by Morteza
Modified: 2022-08-26 14:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screen Shot of the problem in start screen. (242.38 KB, image/png)
2022-08-23 18:50 UTC, Morteza
Details
Screen Shot of the problem in Writer's title bar. (26.01 KB, image/png)
2022-08-23 18:51 UTC, Morteza
Details
macOS start center (680.23 KB, image/png)
2022-08-26 14:08 UTC, Michael Warner
Details
macOS title bar (205.73 KB, image/png)
2022-08-26 14:08 UTC, Michael Warner
Details
About LibreOffice Screenshot (154.41 KB, image/png)
2022-08-26 14:27 UTC, Morteza
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Morteza 2022-08-23 18:49:39 UTC
Description:
If I save a file with Arabic or Persian Name or the file I open have these characters LibreOffice shows unreadable characters for file name in title bar or selection page.



Actual Results:
Wrong display of file name in Persian and Arabic.

Expected Results:
Correct display of file name in Persian and Arabic.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Morteza 2022-08-23 18:50:40 UTC
Created attachment 181983 [details]
Screen Shot of the problem in start screen.
Comment 2 Morteza 2022-08-23 18:51:26 UTC
Created attachment 181984 [details]
Screen Shot of the problem in Writer's title bar.
Comment 3 Mike Kaganski 2022-08-24 05:28:05 UTC
Looks like UTF-8 displayed as ISO 8859-1.
Comment 4 ⁨خالد حسني⁩ 2022-08-25 15:46:45 UTC
This seems like a mis-configured system, the title bar is handled by the window manager not LibreOffice and it shows the same issue.
Comment 5 Mike Kaganski 2022-08-25 15:51:01 UTC
Do the files show OK in the system file manager?
Comment 6 ⁨خالد حسني⁩ 2022-08-25 17:19:57 UTC
(In reply to Mike Kaganski from comment #5)
> Do the files show OK in the system file manager?

So it is a LibreOffice issue after all. I think this and bug 145758 should be duplicates of bug 125995.
Comment 7 ⁨خالد حسني⁩ 2022-08-25 17:22:08 UTC
(In reply to خالد حسني from comment #6)
> (In reply to Mike Kaganski from comment #5)
> > Do the files show OK in the system file manager?
> 
> So it is a LibreOffice issue after all. I think this and bug 145758 should
> be duplicates of bug 125995.

Though we probably need a screenshot of About LibreOffice from Morteza to see what locale is used.
Comment 8 Michael Warner 2022-08-26 14:08:07 UTC
Created attachment 182040 [details]
macOS start center
Comment 9 Michael Warner 2022-08-26 14:08:46 UTC
Created attachment 182041 [details]
macOS title bar
Comment 10 Michael Warner 2022-08-26 14:11:24 UTC
no repro in:
Version: 7.4.0.2 / LibreOffice Community
Build ID: 1512ce97d7ed39dce3121f7e15651fd8895f950e
CPU threads: 10; OS: Mac OS X 12.5; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

FWIW
Comment 11 Morteza 2022-08-26 14:27:03 UTC
Created attachment 182042 [details]
About LibreOffice Screenshot
Comment 12 Morteza 2022-08-26 14:27:55 UTC
(In reply to Mike Kaganski from comment #5)
> Do the files show OK in the system file manager?

yes they are ok in any file manager I use.
Comment 13 Morteza 2022-08-26 14:29:01 UTC
(In reply to خالد حسني from comment #7)
> (In reply to خالد حسني from comment #6)
> > (In reply to Mike Kaganski from comment #5)
> > > Do the files show OK in the system file manager?
> > 
> > So it is a LibreOffice issue after all. I think this and bug 145758 should
> > be duplicates of bug 125995.
> 
> Though we probably need a screenshot of About LibreOffice from Morteza to
> see what locale is used.

I attached the screenshot.
Also I live booted to fedora35 and title bar was ok in there.
Comment 14 Mike Kaganski 2022-08-26 14:38:56 UTC
(In reply to خالد حسني from comment #6)
> (In reply to Mike Kaganski from comment #5)
> > Do the files show OK in the system file manager?
> 
> So it is a LibreOffice issue after all. I think this and bug 145758 should
> be duplicates of bug 125995.

bug 125995 looks very relevant; but being not very familiar with Linux system locale and encoding, I feel is a bit different.

In bug 125995, Jan-Marek likely used a system with a different locale, and explicitly set locale to C when starting LibreOffice. That likely made *encoding* used by LibreOffice different from what was used elsewhere in the system.

In this bug (and bug 145758, to which this bug is definitely a duplicate), likely C is the *system* locale; and reading the mention of "LANG=C.UTF-8" in bug 125995, I wonder what is the system *encoding* used on these systems, such that LibreOffice obviously uses ASCII/ISO 8859-1, and other tools use UTF-8? Is there a wrong detection of system encoding for Linux?
Comment 15 ⁨خالد حسني⁩ 2022-08-26 14:49:22 UTC
(In reply to Mike Kaganski from comment #14)
> (In reply to خالد حسني from comment #6)
> > (In reply to Mike Kaganski from comment #5)
> > > Do the files show OK in the system file manager?
> > 
> > So it is a LibreOffice issue after all. I think this and bug 145758 should
> > be duplicates of bug 125995.
> 
> bug 125995 looks very relevant; but being not very familiar with Linux
> system locale and encoding, I feel is a bit different.
> 
> In bug 125995, Jan-Marek likely used a system with a different locale, and
> explicitly set locale to C when starting LibreOffice. That likely made
> *encoding* used by LibreOffice different from what was used elsewhere in the
> system.
> 
> In this bug (and bug 145758, to which this bug is definitely a duplicate),
> likely C is the *system* locale; and reading the mention of "LANG=C.UTF-8"
> in bug 125995, I wonder what is the system *encoding* used on these systems,
> such that LibreOffice obviously uses ASCII/ISO 8859-1, and other tools use
> UTF-8? Is there a wrong detection of system encoding for Linux?

Both are definitely duplicates.

AFAIK, there is no way to detect locale encoding other than parsing the locale name, and C locale has traditionally not been a UTF-8 encoding. To fix there immediate issue, both reporters should use a locale that is explicitly UTF-8, e.g. en_US.UTF-8 or fa_IR.UTF-8.

*** This bug has been marked as a duplicate of bug 125995 ***