Issue 4796 - No checks of invalid reference fields are possible in the UI
Summary: No checks of invalid reference fields are possible in the UI
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-13 15:29 UTC by schaber
Modified: 2013-02-07 22:42 UTC (History)
2 users (show)

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

Attachments
list of bad references by macro, not avail in OO writer natively (33.66 KB, image/jpeg)
2006-03-01 20:58 UTC, filipg 		no flags Details
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 schaber 2002-05-13 15:29:00 UTC 
When removing the target of references, it is not possible for the user to find 
out which references are affected. This is troublesome in larger documents. 
Users may end up having dead references in their documents. It could help a 
lot, if there was a tool showing invalid references (maybe as additional 
section in the navigator window or as separate tool)
Comment 1 schaber 2002-06-13 18:16:39 UTC 
Beside listing up unresolved references in the navigator, you may 
also think of iterating over these references using the 
search/replace dialog. Framemaker does it like this--you can search 
for unresolved references, as well as for normal text strings, 
regular expressions, attributes, or templates. It would also help to 
search for the representation of (evaluated) fields, e.g. for the 
date which is produced by a date field, in addition to the field 
name. This could be very useful for bibliography entries.
Things like that distinguish a professional word processing software 
from a semi-professional one.
Comment 2 stefan.baltzer 2002-06-24 13:16:29 UTC 
Reassigned to Éric.
Comment 3 eric.savary 2002-11-07 09:02:21 UTC 
ES->CJ: I agree that a kind "reference checker" would be usefull.
Comment 4 christian.jansen 2003-03-24 07:50:30 UTC 
Reassiged to Bettina.
Comment 5 iannz 2004-05-08 09:24:12 UTC 
I have written a macro for managing references. It is available from:
http://homepages.paradise.net.nz/hillview/OOo/

A thread in the forums discusing it is:
http://www.oooforum.org/forum/viewtopic.php?p=32188#32188
Comment 6 filipg 2006-03-01 20:54:06 UTC 
I also really want this functionalty. I don't say "need" becaused extendedPDF
macro will do it for you (I attached an image of what it outputs).

I'd like to see in native OO - a dumb list would beat waiting for the macro to
finish ->PDF dump of 300 pp.

Cheers,
Fil
Comment 7 filipg 2006-03-01 20:58:16 UTC 
Created attachment 34536 [details]
list of bad references by macro, not avail in OO writer natively
Comment 8 gregorytechsoft 2008-10-02 08:27:02 UTC 
Could this RFE be modified with the request to color-code elements in the Style 
and Navigator panes? id-est, in my instance, if automatic parsing and 
pagination can be handled, indicating which hyperlink references were "live" 
might also be done.
Comment 9 bettina.haberer 2010-05-21 15:09:57 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".