Issue 18771 - MSInteroperability-18: watermarks
Summary: MSInteroperability-18: watermarks
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: All All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: ms_interoperability, oooqa
Depends on: 18247 18732
  Show dependency tree
Reported: 2003-08-28 13:40 UTC by caolanm
Modified: 2017-05-20 11:25 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description caolanm 2003-08-28 13:40:55 UTC
MSInteroperability-18: watermarks.

Here thinks get a little interesting. Word can technically do this by means of
the background colour technique, see issue 18247. But what it actually does is
place objects anchored into the header. So to "import" watermarks we need simply
issue 18732 where something anchored to page in a header gets repeated on every
page using that header, as well as unified placement options for drawing object
and writer frames.

For export it depends if we want to repeat the winword hack of stuff anchored in
headers, or use their very own system similiar to background colours. The
difference is that the background feature is a canvas of the total page, and not
just the printable area as in word. Also open is what gets printed on paper. So
will have to kill a few trees to see if there is a difference between the two
modes. I wouldn't look forward to having to repeat word's UI trick of anchoring
watermarks to content in headers to export watermarking :-(
Comment 1 caolanm 2003-08-28 13:41:41 UTC
Accepted, while I brood about it.
Comment 2 Rainer Bielefeld 2003-12-28 10:12:53 UTC
Please check relation to issue 22405!

Comment 3 grsingleton 2003-12-28 13:01:13 UTC
Not releated. This deals solely using the header field to insert graphics. I for
one would hate to see M$'s hack implemented in OOo.
Comment 4 caolanm 2004-03-03 12:49:03 UTC
cmc->ama: I'll let you decide what we should do here. We already have background
watermark from writer to word implmented. And we have watermark from word to
writer implmented because thats just a graphic anchored in a header, which OD
has done. 

The thing is that our watermark export in word will expand to fill the entire
page, while in writer it fills only the pagetext area.

Possibility 1) thats good enough, no further action required
Possibility 2) allow writers watermarks to fill the entire page, make this the
default. Now export to word looks like our default, and re-import is the same as
it appears in word.
Possibility 3) Do the complicated hack on export to place the watermark as a
graphic anchored in the nearest header. No need to allow our watermarks to fill
the page in this case, as the only application which uses word's system to set a
watermark for the full page area is writer at the moment (no UI to do exactly
this in word). Re-import will simply import the graphic anchored in a header as
Comment 5 andreas.martens 2004-06-17 09:47:51 UTC
I think we need no 2.) for perfect roundtrips. But this is a feature task for
OOo Later.
Comment 6 ace_dent 2008-06-28 01:25:20 UTC
For info, related bugs affecting MS interoperability re. Watermark function:
Issue 18771 - MSInteroperability-18: watermarks
Issue 24088 - WW8: "Watermark" Graphics Problem, not in background after import
Issue 33004 - Background watermark image wrong position when imported from MS Word
Issue 43051 - WordML import: pagebackground watermarks not imported
Issue 74249 - Watermarks can't be exported properly (.doc file)
Issue 91058 - import word 8 doc layout and watermark problem
Comment 7 andreas.martens 2009-03-30 08:03:35 UTC
ama->os: Yet another open filter issue...
Comment 8 Marcus 2017-05-20 11:24:32 UTC
Reset assigne to the default "".
Comment 9 Marcus 2017-05-20 11:25:45 UTC
Reset assigne to the default "".