Issue 15330 - Incorrect display of Word & Powerpoint file name in title bar
Summary: Incorrect display of Word & Powerpoint file name in title bar
Status: CLOSED WONT_FIX
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@ui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-05 15:29 UTC by pmjd
Modified: 2003-06-16 15:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pmjd 2003-06-05 15:29:43 UTC 
Tested in both Writer and Impress but not a problem in Calc. When a Word 2000 or
Word 97 file has been opened in Writer, the title bar doesn't display the
correct file name. Instead Writer displays a random piece of text from the
document as the file name. In Impress any opened Powerpoint 2000 or 97 file
simply says no slide title instead.

Aside from that keep up the excellent work!
Comment 1 stefan.baltzer 2003-06-06 12:01:28 UTC 
That'a feature of OO: In case the file has a title in the document
properties, this title is shown in the title bar instead of the
physical file name. If there is no title, the physical file name is shown.

MS Words tends to set the first words typed in the document as
document title. That's "their" feature ;-) And - of course - this
title is imported and taken as document title, thus shown in OO's
title bar.

NEQ (next expected question...:) Why doing it differently?
Imagine a centralized pool of documents in a company, for some reason
all files have to have "8.3" Names. The physical title "TEMPL_58.sxw"
is less informative than a title like "Fax template for international
incvoice".

Not a defect. Set to "WontFix".
Comment 2 stefan.baltzer 2003-06-06 12:02:28 UTC 
Closed.
Comment 3 prgmgr 2003-06-16 15:41:36 UTC 
*** Issue 12717 has been marked as a duplicate of this issue. ***