Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | WW8: Support custom contours | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | umberto <umberto> | ||||
Component: | code | Assignee: | michael.ruess | ||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P4 | CC: | issues, pmartel60, sven.jacobi | ||||
Version: | OOo 1.1 RC2 | Keywords: | ms_interoperability, oooqa | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
URL: | http://www.seidlix.net/share/oo_bug01.jpg | ||||||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
umberto
2003-07-27 17:18:03 UTC
Oops: those pictures weren't transparent (they once were, they're not anymore). Umberto, What is the relationship between the jpeg at the referenced URL and the issue? Is it a picture of the Writer screen showing the distortion (as it seems) or is it the original imported picture? If it is not the original picture, can you attach a word document with the original picture in it that reproduces the issue? If the issue will reproduce itself if I simply insert the original picture into an empty .doc and open the result in OOo Writer, you could just provide the original picture as an attachment or URL. Also, I'm not sure how your later "Oops" comment changes the issue. The jpg at the location is a screen shot of the OO-Window. If you insert the original Jpeg in a .doc and import it in OO, it's fine. I have placed the .doc, which made me file this issue under http://www.seidlix.net/share/oo_bug01.zip and the original jpeg itself under http://www.seidlix.net/share/oo_bug01_orig.jpg In MS Word, you can cause text to wrap "tight" around a user-specified polygon instead of "square" around the bounding rectangle of a picture. There are three significant aspects to this bounding polygon: 1. The polygon is arbitrarily user-specified and need not correspond to "edges" or to "background" or "transparent" areas of the picture. 2. The polygon does NOT mask or clip the image -- the parts of the image outside the polygon are visible except where they may be overwritten by text or text highlighting. 3. The polygon defaults to being the bounding rectangle (effectively making tight == square) until the user moves and/or adds "wrap points" to set a different polygon. MS Word does not prompt the user to edit the wrap points when entering "tight" wrap mode, so there is no immediate feedback differentiating "tight" from "square" wrapping. OOo Writer import fails to recognize all of these aspects: 1. It disregards the user's predefined polygon and instead substitutes a potentially very complex polygon (or Contour in OOo Writer lingo) apparently based on some attempt at "edge" detection. This has the effect of shifting the wrapped text. 2. It uses the resulting contour as both a wrap boundary AND an image mask so that any parts of the image outside the contour are not displayed. 3. It applies the edge detection algorithm (1) even when the polygon is still set to the default bounding rectangle -- a case which (if it could be detected) might be better served by using a non-Contoured Page wrap (OOo Writer lingo for square wrap), an especially attractive option since it is probably faster/easier to render, does not introduce masking (2), and, because of the lack of prompting in MS Word to distinguish the unique features of "square" and "tight" wrap, may be exactly what the user intended. The combined effect of these 3 failures can make both the image and the surrounding text layout appear drastically distorted vs. the MS Word original. The simplest workaround (and possibly the quickest code fix) is to disable the Contour Wrap on all imported images -- thus treating them all as "square wraps". This fixes failures 2 and 3. It leaves the user to reconstruct the Contour (using the edge detector and/or the other tools provided) IF willing to sacrifice the masked parts of the image for the sake of reconstituting the text wrapping effect. Should this be 3 issues? HI->UMBERTO: Yor workaround is to select the graphic, context with right click and disable contour. Or you can edit the contour which is reachable also in context menu. HI->AMA: I recommend that the writer should behave like draw. Am I seeing this right? (I've not tried the contour functions in Writer yet.) In Word, I was able to select a contour and then modify it so it fit "loosely" around the part of a graphic that I wanted left clear. The text then flowed around the image, not in a square fashion, but in one that mimicked the shape of the graphic. It is a feature often seen in articles, brochures, handouts and magazines and looks quite impressive. I'd love to see it in OOo but I would consider it an enhancement rather than a defect. Created attachment 8272 [details]
Simpler .doc which loses critical contour points on import
Hi Caolán, are we able to import the contour points? And is it your problem or belongs it into the drawing engine? Hmm, we never supported wrap points. Looks tricky but possible to do. cmc->sj: Does powerpoint use such wrap points, or is it only word, looks like word is the only one that does this (making it my problem :-)) ? retitling enhancement Hi Caolán, I am back from vacation now and I am sorry, I must answer your question in the negative, PowerPoint and Excel is not supporting such a word wrapping, but I can give you some hints, therefore I will send you a mail. *** Issue 20816 has been marked as a duplicate of this issue. *** *** Issue 20605 has been marked as a duplicate of this issue. *** Have implemented custom contour import/export for 2.0 in workspace kilkennyfilterteam14. reopen to reassign cmc->mru: Done in kilkennyfilterteam14 Checked with CWS kilkennyfilterteam14. Verified. Will be integrated in OO 2.0. *** Issue 25286 has been marked as a duplicate of this issue. *** Closed. Works in src680m22. *** Issue 25447 has been marked as a duplicate of this issue. *** *** Issue 25519 has been marked as a duplicate of this issue. *** *** Issue 27662 has been marked as a duplicate of this issue. *** *** Issue 43420 has been marked as a duplicate of this issue. *** |