Issue 80866 - font issue in content.xml and style.xml
Summary: font issue in content.xml and style.xml
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-21 00:56 UTC by mathewnanderson
Modified: 2013-08-07 14:38 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 mathewnanderson 2007-08-21 00:56:36 UTC 
The fonts in the content.xml and the style.xml files do not "clean up" when 
they are not in use. If a document in produced in font a, then changed to font 
b, the xml files will have both font a and font b in them. This has been 
reproduced endless times, and is of great consequence when using open office to 
produce massive amounts of documents in an automated fasion. many fonts are 
only available by liscence and should not be appearing in the xml files if they 
are not in use by the associated document.
Comment 1 michael.ruess 2007-08-21 07:17:37 UTC 
Reassigned to ES.
Comment 2 eric.savary 2007-08-22 13:31:43 UTC 
Not so nice... Let's say a cosmetic bug: Those fonts informationare needed by
the undo function 
- a text with font A
- save
--> <style:font-face style:name="A"> in the content.xml
- replace font A with font B
- save
--> <style:font-face style:name="A"> and <style:font-face style:name="B"> in the
content.xml
- close the document (the undo function is not needed anymore)
- reload the document
-> the reference to A should have disappeared but is still there
- Workaround: save the file again -> then the undo information of the last
session is cleaned up.
Comment 3 mathewnanderson 2007-08-30 18:47:51 UTC 
I dont know that i'd call it a cosmetic issue. We found the issue because our 
font validation software kicked errors out to us. We work around it by manually 
deleting from the xml files but as OOo gets more widely used I'd think that 
font validation would be commonly used. So while its not a killer for us (minor 
nuisance really) I think its a tad more than cosmetic.