-
1. Re: composite images import black or garbled
mattrsullivan Aug 23, 2012 7:58 AM (in response to starrd)I've not seen your problem in my work, but also don't use FM text lines and boxes with my screenshots.
Have you tried pasting the screenshot into Illustrator and adding text callouts there? I believe you'll have better luck with one composite image than with a series of objects in your FM anchored frame.
-Matt
-
2. Re: composite images import black or garbled
starrd Aug 23, 2012 8:21 AM (in response to mattrsullivan)Thanks Matt:
I know that compositing the images outside of FM will solve it. It just seems
that the functionality to use the text boxes is present in FM and should work,
and in fact I think has worked in the past. I'm missing something...
-
3. Re: composite images import black or garbled
starrd Aug 23, 2012 12:49 PM (in response to starrd)UPDATE:
I found an old project in which these features worked and did the following experiment which now proves that I need Adobe engineering or Forum expert gods need to help me sort thru the options to get this working.
- Created new project file
- Imported settings file
- Changed Image conversion properties to below (unchecked all boxes at top and changed scale to 100, default to png - this matched previous project which only had the do not regenerate checkbox in RH9)
- Imported (linked) same book file as above
- Generated project
- Artwork appears with normal (albeit blurryish) screenshots, graphic leaders, and text boxes as desired
- Modify a caption in the text box of the art being tested
- Force update (just the chapter)
- Artwork is not refreshed.
- Modify conversion settings to set flag to allow distiller to regenerate the artwork
- Force update (just the chapter)
- The artwork breaks as indicated in my original posting.
Here are RH 9 image settiings that I tried to emulate:
Here are settings for above sequence in RH10 prior to enabling the regenerate checkbox:
The problem then appears to be that the conversion works with whatever algorithm RH uses to initially generate the artwork but the only means to subsequently regenerate it uses a different algorithm. Is it possible that one path uses <algorithm A> and the other path uses Distiller? Can't these both be the same path?
Augh. Bug?
-
4. Re: composite images import black or garbled
starrd Aug 24, 2012 12:30 PM (in response to starrd)UPDATE 2:
I reviewed a few more posts and had some interesting results, but still am hoping Mayank Agrawal will weigh in on this because the results are inconsistent.
Based on his article here: http://blogs.adobe.com/techcomm/2011/06/troubleshooting-framemaker-content-conversion-in-r obohelp-%E2%80%93-part-2images.html
I changed the PDF options in my FrameMaker source for the book to be High Quality and enabled the distiller options in the Project Settings for Images. No change in results.
I changed my settings to convert all images to jpg (most of my source are png), that seemed to work. The images were converting properly altho text boxes disappeared.
During this testing, I found that modifications I was making in the FM source were not getting picked up in RH despite doing a Force Update/Force Update All. I have seen this happen quite a lot, so exited both apps and restarted. Magically...everything now seems to work properly.
I then revisited an old project to test the theory...Project Settings for Image conversion had it set to PNG. Did a force update all to get a clean copy of content before changing the JPG setting...and the images all came thru fine as in the other project.
Now I have no idea whether JPG is necessary, whether the PDF setting in FM is used by the non-Distiller algorithm and that somehow made a difference, or whether all these conversion failures were due to a memory management problem that cleared up when I exited and restarted the two apps.
It's quite frustrating to not have a reproduceable, clean workflow for basic functionality. I *think* things are working and believe I can spend a day or two again if things break to tickle them back into working but I can't swear that I know what fixed it. It would be nice to have Dev jump in and explain.







