Bug 624264 - In the OO window's titlebar, document names with umlauts are not shown correctly in non-UTF8 encodings
Summary: In the OO window's titlebar, document names with umlauts are not shown correc...
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
(Show other bugs)
Version: 14
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-15 10:11 UTC by Joachim Backes
Modified: 2010-08-16 13:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-16 13:02:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Nautilus windows and OO writer window (desktop photo) (95.43 KB, image/jpeg)
2010-08-15 10:11 UTC, Joachim Backes
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenOffice.org 113908 None None None Never

Description Joachim Backes 2010-08-15 10:11:18 UTC
Created attachment 438814 [details]
Nautilus windows and OO writer window (desktop photo)

Description of problem:
When openening a OO document with German "Umlauts" in it's name (by using nautilus with double clicking), the OO shows the umlauts in the document's name in the OO window's title bar in weird manner. The document's name was "Ich hatt ein Vöglein.odt"

Version-Release number of selected component (if applicable):
openoffice.org-writer-3.3.0-4.1.fc14.i686


How reproducible:

always
Steps to Reproduce:
1.See description
2.
3.
  
Actual results:
See description

Expected results:


Additional info:

Comment 1 Caolan McNamara 2010-08-16 08:20:38 UTC
What's the output of...

locale -a

I'm betting that its not a UTF-8 locale

Comment 2 Caolan McNamara 2010-08-16 08:21:11 UTC
sorry, I mean the output of "locale", not "locale -a"

Comment 3 Joachim Backes 2010-08-16 08:29:41 UTC
(In reply to comment #2)
> sorry, I mean the output of "locale", not "locale -a"

locale
=======

LANG=en_US.utf8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C

Comment 4 David Tardon 2010-08-16 08:40:31 UTC
I see it with

LC_ALL=C ooffice

. Also, opening from recent documents doesn't work for such document.

Comment 5 Joachim Backes 2010-08-16 08:59:56 UTC
1.

unset LC_ALL
ooffice 

shows the titelbar and the document itself correct.

2.

This is a standard f14 installation (no tricks)  with german keyboard, and in OO, language is set to german (currency set to german/euro). I think, I should remove the line "LC_ALL=C" from my ~/.bashrc

Comment 6 Joachim Backes 2010-08-16 09:05:05 UTC
(In reply to comment #5)
> 1.
> 
> unset LC_ALL
> ooffice 
> 
> shows the titelbar and the document itself correct.
> 
> 2.
> 
> This is a standard f14 installation (no tricks)  with german keyboard, and in
> OO, language is set to german (currency set to german/euro). I think, I should
> remove the line "LC_ALL=C" from my ~/.bashrc

The same .bashrc line *with* "LC_ALL=C" worked properly in F13 together with OO!

Comment 7 Caolan McNamara 2010-08-16 09:11:59 UTC
Yeah, "C" is a terribly idea if you have files with non-ascii filenames floating about. 

Fixing title bar fix is easy, recently-used not quite so trivial

Comment 8 Joachim Backes 2010-08-16 09:17:01 UTC
I think, I can live with en empty LC_ALL :-)

Comment 9 Caolan McNamara 2010-08-16 13:02:55 UTC
Suggested a patch upstream. Won't fix this in Fedora. non-UTF8 locale settings are definitely un-recommended. Something like LC_ALL=en_US.utf8 might get the desired effect without clobbering utf8

Comment 10 Joachim Backes 2010-08-16 13:14:31 UTC
LC_ALL=de_DE.utf8 does it too.

Thank you.


Note You need to log in before you can comment on or make changes to this bug.