Red Hat Bugzilla – Bug 171836
non-english characters in file names in recent documents menu are displayed as squares
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
After closing file whose name contains non-english characters, the entry in File /"Recent Documents" menu is displayed as squares.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create new file
2. Save it, giving it name with non-english characters (I tryed cyrillic and hebrew characters), then close the file
3. Open File/"Recent Documents" menu
Actual Results: Non-english characters in the file name displayed as squares.
Expected Results: File name should be displayed correctly.
This did work in previous version (1.9.125)
Can you attach a tiny sample document with a known "bad" name ?
Created attachment 120453 [details]
file with name in russian
What really matters is a file name and not a content
Created attachment 120455 [details]
working for me
looking ok for me. So...
1) KDE or GNOME ?
2) what's the output of locale ?
This might be a font/glyph substitution thing which depends on what font is
being user for the UI
[pavel@pashar ~]$ locale
The change in behaviour happened after latest openoffice update.
very odd, after you open the document does
a) the title bar have the filename displayed correctly and
b) does file->Properties->general have the filename displayed correctly ?
The title bar is correct, but properties are not.
I wonder if unselecting tools->options->openoffice.org->view->use system font
for user interface makes any difference
It makes. Everything is displayed correctly now, and it also makes things a bit
I wonder if you know what your "normal" gnome system font is ?
Application and Desktop fonts: Sans/10
Window title: Sans Bold/10
This supposed to be a default, I never changed it.
Sans is an alias of course, try
> fc-match --verbose --sort "Sans"
to see what the matches are in order of preference
my "Sans" font is Luxi Sans, and trying "Bitstream Vera Sans" work as well
Sorry, I dont have an fc-match. Which package has it?
BTW, I just tried version 1.9.125 and final (2.0) release downloaded from OOo
site - both display things properly even when "use system font for user
interface" is selected.
Created attachment 121845 [details]
fc4 update of 2.0.1-143.2.1
Created attachment 121846 [details]
Looks ok for me fc-4 with latest update for fc4 like the screenshot, if this
problem persists for you with >= 2.0.1-143.2.1 can you download the fc-match
attached here and run
chmod u+x fc-match
./fc-match --verbose --sort "Sans"
I tried version 2.0.1-0.142.3.1. I hope you meant this version, since I could
not find version 2.0.1-143.2.1 in either updates or updates-testing. This
version actually makes things worse: now the menu is garbled even when "Use
system fonts" is unchecked.
Created attachment 121861 [details]
output of fc-match --verbose --sort "Sans"
ok, that's good output from fc-match. I see that "Sans" matches
So I'd like to get that font for myself to see if that will reproduce things.
Where did it come from ?
> rpm -qf /usr/share/fonts/java/LucidaSansRegular.ttf
the sun jdk ?
Yes, it's sun jdk.
Created attachment 121897 [details]
bzipped font file
2.0.1-143.2.1 from updates still has the problem.
It could be hard to track this one down, Lucida Sans hasn't got the glyphs
needed, so glyph substitution occurs, for some reason it doesn't work for you,
but does for me. You have a large stack of fonts installed which I don't, so
presumably the problem is related to one of them.
I assume that typing the same letters in gedit and setting
edit->preferences->fonts->editor font to "Sans" does work ?
Yes, it works.
I wonder what could be a difference between fedora build and OO.o build, since
version 2.0.1-143 (2.0.1 RC2) downloaded from www.openoffice.org does not have
Upstream doesn't have support for fontconfig glyph replacement, that's the
irony. Not using fontconfig means that upstream OOo cannot handle missing glyphs
as well as redhat OOo can (obviously in general, and not in this case) e.g. for
asian and indic text.
It's real likely that this is part of the bug 180124 problem. Where multi pass
glyph substitution comes unstuck
*** This bug has been marked as a duplicate of 180124 ***