Hyperlink export bug

Hyperlinks and button hyperlinks either export to pdf incorrectly or not at all. I've read that this is a bug. I'm not a programmer, so may of the fixes are beyond my ken. Does someone have a fix? Can you explain it to me as though I were an idiot?

https://www.dropbox.com/s/7p1a8bg0sf9ebdh/I.A%20Job%20of%20Thinking.indd
I sincerely hope it’s operation error. The first two “Facebook” pages have links on them. The “NASDAQ” link adds %20 when clicked. Some of the links for “friends” do not appear in the pdf.
I’m afraid I will be offline for a few days due to health issues. However, I would appreciate any help I can get.
Thank you for your help and patience.
Sharon

Similar Messages

  • Indesign CS6 epub export bug

    I am using Indesign CS6 to export a book to epub. Having problems with automatic numbers and bullets as well as spacing issues; however, I've made some adjustments and am getting a pretty decent epub. Here's the issue: When I convert my epub to Mobi using Calibre, I get double bullets and double numbers in my lists. I used this same process to create a Mobi file a few months ago in Indesign 5.5 with no problem. So I took one of my CS6 files, exported it to IDML, opened it in CS5.5 and exported to ePub. I then took that epub and converted it to Mobi using Calibre. No double bullets or numbers. So the issue is coming from Indesign CS6.
    Anyone else had this issue. Any other ideas on how to get a clean Mobi file from CS6?

    Thanks a million.
    Re: Indesign CS6 epub export bug
    created by Steve Werner in InDesign - View the full discussion
    lotuscott,
    You should get the 8.0.1 update for InDesign CS6. It fixes several EPUB bugs including the "space before" problem and the "epub-ruby" (which is I believed intended for Japanese language.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4773256#4773256
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4773256#4773256
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4773256#4773256. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in InDesign by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Keyword exporting bug also impacts catalogs imported from PSE 6

    Hi,
    I haven't seen any mention of it, but the keyword exporting bug reported for catalogs imported from LR 1.x also impacts catalogs imported from Photoshop Elements 6. i.e. all Keywords imported from my PSE 6 catalog have "Include in export", "Export Containing Keywords", and "Export Synonyms" properties set to false.
    I've reported the bug, but as it seems the same as described in KB 405074 (and more importantly, its fix works for formerly PSE catalogs as well!), I'm sure it will be fixed in the next update.
    http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405074&sliceId=2
    Thanks,
    Matt

    Hi Brian,
    When I installed the trial for LR2 I was asked whether I wanted to upgrade my existing PSE6 catalog.
    Screenshot of this can be found here: http://dawsons.id.au/temp/pse6-to-lr2-catalog.png
    That's it. I haven't imported any keywords via any other method.
    Thanks,
    Matt
    PS I'm impressed with the level of Lightroom team involvement in these forums. I've been a PSE user for at least 5 years and have never received feedback from that team re posts/support calls/feature request/bug reports. I've been a LR user for about two weeks and I've already had Tom and yourself reply to my posts. You've got to be happy with that!

  • Mono export bug

    strange export bug I experienced this weekend, I think its a metadata issue.
    Before the export I had to relink all the material because we had moved all the material from one SAN to another. Exported the show using Premiere, not AME, to Prores. The timeline have two mono audio tracks, each panned left and right. I then used AME to convert the new Prores file to export a MXF version and a h264 version.
    All the files came out with only audio in the left channel! But when I check on a different machine the Prores came out with sound in both channels, but the MXF and h264 did not. I then removed all the "Media Cache" and "Media Cache Files", located in the Library/Application Support/Adobe/Common/ folder.
    I then reimported the files, and now the Prores came up with audio in both channels but the MXF and h264 was still "corrupted".
    Have someone experienced the same? Why would the Prores file, with audio in both channels, produce a single mono track MXF/h264 file? Do people regularly delete the "Media Cache" and "Media Cache Files"? PEBCAK?
    Both machines where the new mac pro, 10.9.5, with similar specs, 3,5Ghz 32GB ram dual AMD FirePro D500, with Adobe Premiere 8.2
    Any thoughts is appreciated

    The Prores was exported with these settings:
    Audio Codec: AAC
    Sample Rate: 48KHz
    Channels: Stereo
    Audio Track Layout: 2 Mono Tracks
    Channel Layout: Mono
    The MXF was exported with these settings:
    Audio Codec: Uncompressed
    Sample Rate: 48KHz
    Channels: 2 Channel
    No multichannel

  • Document to document hyperlinks exported to epub do not work

    I've been flooding the forums lately with a lot of ebook questions recently . . . hopefully this will be the last one. I've created multiple documents combined into a book, so that when I export my ebook, I'll get the necessary breaks within the book.  However, the cross references/hyperlinks that I've created using text anchors throughout the book only work if the source and destination are in the same document.  If I have a source in one document referring to a destination in another document, when I export the epub file, the link only jumps at the source rather than linking to the destination. I've creating the links by selecting the open document from the document drop down and then selecting the destination from the text anchor drop down.  It seems to work within ID, but not exported as epub.  What am I doing wrong?  I really need to fix this problem so my TOCs will work, at least.

    You are not doing anything wrong. It a bug in CS5.
    What happens is, the reference to the source file drops out of the code line, like this:
    <a id="anchor-50-anchor" /><span class="superscript"><a href="#anchor-57-anchor">1</a>
    and to should look like this
    <a id="anchor-50-anchor" /><span class="superscript"><a href="Notes.xhtml#anchor-57-anchor">1</a>
    So you will need to insert to relevant .xhtml file back into the code. I use Dreamweaver for the code stuff (only because it's free with CS package and because if give a preview window)
    I doesn't take long to fix...

  • CR6.4 RC1 - XMP export bug, anybody else has it?

    I think I found a bug, and although I also found a workaround, here it is.
    My environment: Windows 7, Photoshop CS5, Camera Raw 6.4 RC1, all of them 64-bits.
    Steps to reproduce the bug:
    1. Open several raw files at once in Camera Raw (in my case, Olympus E-PL2 ORF files, but it probably doesn`t matter). For this bug, take images that are likely to have different white balance settings. Also make sure that those are original files, never modified by Camera Raw (or anything else) and that they have no XMP sidecars yet.
    2. Wait until thumbnails are generated (may not be relevant...). Don't click on any of them, just let them be created.
    3. Click on "Select All". Again, don't change the displayed image, just select them all.
    4. In Basic/White Balance, select Auto. All thumbnails are properly updated
    5. Export settings to XMP (from the menu on the right-most toolbar, i.e. still "Basic" if you haven`t changed it)
    6. Keep Camera Raw open, and have a look at the XMP files.
    The BUG : they all contain the same white balance settings (crs:WhiteBalance, crs:Temperature and crs:Tint) which happen to be the computed settings for the first image (the only one displayed so far). All other settings seems to be fine though (i.e. they are from their respective image).
    However, if you go back in Camera Raw and then click on some other images, not all of them. You can see that their WB settings are different and properly computed (as far as "Auto" can properly compute them). Export to XMP again. WB settings are then right, but only for the images that you clicked on. Those that were never displayed full size still have the wrong WB settings (from the first image).
    Obviously, the workaround is to click on each of them. Still that's a bit awkward, especially in my "quite-automated" workflow, where I'm not yet to the point to look at each image individually. Can't tell if this bug exist too on any other version of CR, and my E-PL2 raw files can only be opened in CR 6.4 anyway (unless I change some tags to fool CR).
    Can anybody can reproduce that bug on similar or different environment? And could Adobe fix it, if it is a bug?

    btw, don't know why I wrote RC1... I just meant Release Candidate!

  • Color Shift Happening When Exporting - Bug in Acrobat Export?

    Hi, we are using InDesign CS3 and trying to output a file to send to a printer. We are desiring to have all colors converted to the printer's CMYK color space upon exporting (they sent us their ICC profile).
    But we are getting a bizarre bug that I cannot figure out. It seems like it's actually a software bug, not an issue with settings. I'll try to describe the issue here:
    Upon using 'Convert to Destination (Preserver Numbers or Not)' in the PDF export dialog in InDesign (using PDF/X-4 setting), using the 'Document CMYK' profile, there is a shift in color for 1 particular element. We have a grayscale image of a bunch of dots (black dots on solid white background) that is placed in a frame in InDesign. This image is 'colorized' in InDesign by setting an image color and a frame color (the image color appears as the 'foreground' and the frame color is the 'background'). We've been doing this all the way back to the Quark days (many years). But if the 'background/frame' color is a combination of C+M+Y (with no black), the Magenta and Yellow values are shifted to the Yellow and Black channels (for example - 52c, 5m, 10y, 0k becomes 52c, 0m, 5y, 10k).
    I have never run into this before, and we've run this job with the same element many times now over the last couple years. But I have always used 'No Color Conversion' in my PDFs in the past. So it has something to do with the 'conversion'.
    So far I've tried:
    - Creating new document with just the single element, also created from scratch. So it's not an error in the file.
    - Starting with different profiles (to make sure the profile wasn't corrupt).
    - Choosing 'Preserve Numbers' or not when outputting PDF.
    - All sorts of color combinations. It also appears that if there is black in the color, this value gets shifted to the magenta channel, then the magenta & yellow bump down.
    - Checked the grayscale image to make sure it was flat, and using pure black & white colors. It is.
    I've also tried printing to Distiller (we have Acrobat 8 Pro), but the settings are a lot different here so I'm not sure if I set it up properly. I made a duplicate of the default PDFX3 2002 profile, then edited the color settings to 'Convert Everything to CMYK' and set our printer's profile as the CMYK Color Space. But images are converted to 'DeviceCMYK' and not the profile I put.
    - ANYBODY have any ideas or even know where I would start???
    THANKS. This job needs to go out, but I'm also trying to get a solid workflow down for the future.

    Looks like the issue in the CM thread.
    I'm trying to replicate the issue but haven't done it yet. Still grasping at straws
    1. Did the ID doc ever undergo Convert to Profile?
    2. In Swatch Panel do "Add unnamed colors". Make sure the grayscale is colored with swatches, not colors created in the Color Picker
    3. Do the color values in the swatches have crazy decimal values? Is the color mode of the swatches CMYK?
    4. What format are the grayscale links - TIFF or PSD?
    5. Make certain they are links, not embedded (I'm sure they are links though)
    6. The colorization - are there tints applied to the object colors, or are they 100%?

  • MAJOR EDL Export BUG in 8.2!

    I just upgraded to version 8.2 and now there is a major bug when exporting EDLs with audio clips!   EDLs (cmx3600 format) should only export Timecode In/Out for Source & Record.   The latest 8.2 version is now incorrectly outputting SAMPLE FORMAT for EDLS for any audio clips!  This is a major bug and potentially show-stopping.
    What 8.2 is exporting:
    What it used to (and should continue to) export before 8.2:

    with my PP 8.2.0 (65) Build, I get the same error with edl WAV audio clips until I 'link' video clip with audio clip below on the timeline
    I believe after linking the video clip to the audio clip (below on the timeline), then exporting the edl, the timecode format displays properly
    However, my edl export ability still needs work, because I would think my video timecode needs to match my audio timecode (for linked clips) so I am still working on importing the edl into Speedgrade and 'hearing' the audio
    I was getting the same error audio text file as AjentJJ30, until I 'linked' video with audio,
    so far my edl text file appears as below
    TITLE: edl with wav link
    FCM: DROP FRAME
    001  AX       V     C        00:00:00:00 00:00:24:23 00:00:00:00 00:00:24:23
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0951_C0005_[000000-002420].mxf
    002  AX       AA    C        01:03:06:05 01:03:30:28 00:00:00:00 00:00:24:23
    * FROM CLIP NAME: full shoot
    003  AX       V     C        00:00:24:23 00:00:41:22 00:00:24:23 00:00:41:22
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0955_C0001_[000000-004258].mxf
    004  AX       AA    C        01:06:32:22 01:06:49:21 00:00:24:23 00:00:41:22
    * FROM CLIP NAME: full shoot
    005  AX       V     C        00:00:41:22 00:01:00:10 00:00:41:22 00:01:00:12
    * FROM CLIP NAME: bmpcc_1_2015-02-05_0958_C0003_[000000-004444].mxf
    006  AX       AA    C        01:09:17:29 01:09:36:17 00:00:41:22 00:01:00:12
    * FROM CLIP NAME: full shoot
    EDIT: as you can see my WAV file does not show the proper clip name, as well as not displaying the .wav file extension.
    I chase after the edl displaying proper WAV data, but could not achieve any solid results. My dng video clips from the bmpcc have wav files, normally they do not import into Speedgrade with the dng sequence, so using the video clips to test the edl process isn't very helpful.
    I can not get results to support having the WAV edl data working when importing into SpeedGrade.
    Sorry to think otherwise.

  • Web gallery export bug: Crop ratio change doesn't update correctly

    I've just submitted this as a bug to the Aperture feedback site, but then realized that maybe I should have asked around to find out if it was just me or if it's an actual bug.
    Try this: Export a web gallery to your site. Now change the cropped aspect ratio of one or more images in the gallery. Now export the gallery again and when Aperture asks if you want to Update or Replace the existing gallery, select Update. (This option is supposed to save time by only sending the changed files to the site.) The image that was cropped differently will still show up in the Index and Detail view with the old ratio, but the new dimensions will be stretched to fit the old ratio.
    I've done this repeatedly and it's completely reproducible. The only way to get the gallery to display correctly is to select Replace when exporting the gallery. Obviously, if your gallery is larger than a handful of images this will take a while and it defeats the purpose of the Update option.
    Does anyone find this same issue or am I the only one?

    Yeah, that makes sense.
    I'm thinking now that if I create a new version in the web gallery and crop it just for the web export the app will probably re-send that image out to the web site because it treats the new version as a different image. Since the new version really doesn't take up any meaningful hard drive space this wouldn't be a deal-breaker, but I would have to remember to NOT delete that version or change the crop ratio before uploading the gallery again.

  • JSFL - PNG export bug in CS5.5, works in CS4 - 8000px limit

    We have a series of JSL scripts that export our ad banners in both SWG and GIF format. The GIFs are compiled by exporting each of the 3 frames of the SWF as PNG images then a .jsx script runs in Photoshop and compiles them into a GIF.
    This all worked fine in Flash CS4. Running the script on FLAs in FLash CS5.5 produces this error at the PNG export stage:
    The bitmap is too large. The largest bitmap that can be created is 8000x8000 pixels.
    The line of code that triggers this error is:
    fl.getDocumentDOM().exportPNG((pngPath+resName+".png"), true, false);
    The path variables are fine and produce a valid path (see below). As you know the first boolean states whether to 'use current PNG export settings' (true) or to show the settings dialog on export (false). The second Boolean states whether to export only the current frame (true) or all frames in the SWF (false).
    If I change the 'use current PNG export settings' to false and show the export dialog and OK the default values the export runs fine (which is how I know there is no issue with the export path).
    Showing the dialog box on each export is not acceptable because we have over 10,000 of these banners to export over the next couple of months.
    I'd like to know:
    [1] Is this an actual bug?
    [2] Can anyone suggest a workaround?

    To reproduce this behaviour create an FLA in CS4, make 3 keyframes, draw a filled rectangle (or whatever) on each frame then save it somewhere (ie C:\test.fla)
    Then create a Flash JavaScript file, paste the following code into it and save it in the same location as the FLA. (ie C:\script.jsfl)
    exportPath = fl.scriptURI.substr(0,fl.scriptURI.lastIndexOf("/"))+"/";
    fl.getDocumentDOM().exportPNG(exportPath+"Frame.png", TRUE, FALSE);
    The first line of code here just gets the location of the jsfl file and removes the filename to give an export path.
    The second line export each frame to the same location as the FLA and JSFL files.
    This should run fine in CS4 and you will see the following in your save location:
    test.fla
    script.jsl
    Frame0001.png
    Frame0002.png
    Frame0003.png
    If you change the first boolean in the export command to FALSE and run the script again you should see the PNG export settings dialog box and when you OK it you will get the same export result.
    Now open the FLA and JSFL files in CS5.5 and run the JSFL. With the boolean set to TRUE you should get an error (the 8000px error), however if you set it to FALSE so that you get the settings dialog when you OK it the export will run fine.
    Change it back to TRUE and you will get an error again.

  • CSV export bug in one report

    Hey guys and Apex-friends!
    I have a problem with the export of one of my reports.
    The Column BF is always empty when exported to Excel. In fact, the header is created but the results are not shown.
    If I drop the Page item P480_BIOTOPBAUMFLAECHE the data is exported as it should be but false of course. I just did that for testing purposes of course.
    On my page the results are displayed correctly. I guess that the computation is not carried out. Is there a way to fix that bug?
    Here is my report query!
    select
    :P480_BIOTOPBAUMFLAECHE as flaeche,
    count(b.lng_baumart) * 10000 / :P480_BIOTOPBAUMFLAECHE AS bf,
    LNG_BAUMART,
    p.STR_LRT_MAIN
    from
    VT_TBL_BIOTOPBAUM b,
    VT_PUNKTDATEN_JOIN p
    where
    (p.CNT_GEBIET = :P480_CNT_GEBIET)
    and (b.LNG_INV_PT_ID = p.INV_PT_ID_SUB)
    and (p.str_lrt_main = :P480_STR_LRT)
    and (b.int_bezug = -1)
    and (p.int_status_sub = 3)
    group by
    p.STR_LRT_MAIN,
    lng_baumartIf you have an idea or hint, please let me know!
    Thanks a lot!
    Sebastian

    Hi,
    I do not know does this help, but try
    select
    :P480_BIOTOPBAUMFLAECHE as flaeche,
    count(b.lng_baumart) * 10000 / TO_NUMBER(:P480_BIOTOPBAUMFLAECHE) AS bf,
    LNG_BAUMART,
    p.STR_LRT_MAIN
    from
    VT_TBL_BIOTOPBAUM b,
    VT_PUNKTDATEN_JOIN p
    where
    (p.CNT_GEBIET = :P480_CNT_GEBIET)
    and (b.LNG_INV_PT_ID = p.INV_PT_ID_SUB)
    and (p.str_lrt_main = :P480_STR_LRT)
    and (b.int_bezug = -1)
    and (p.int_status_sub = 3)
    group by
    p.STR_LRT_MAIN,
    lng_baumart

  • Arguable, Excel Export Bug

    When using a substitution string to define a region’s no data found message, if one attempts to use a substitution string as no data found message, it will work fine during normal display. However, when taking the CSV output of an empty report (enter the questionable nature of this being a bug) the substitution string is not evaluated.
    Is this working as intended or can this be fixed by the APEX team?
    I know it is a nit-picky type thing as what usefulness would an empty report provide and why would anyone attempt to export it, but as the corporate wheel turns I am asked investigate every little thing.

    It took me a second to figure out what exactly the we did in our application, but here is a test page for you to work with:
    http://apex.oracle.com/pls/otn/f?p=33318:1:
    It would seem that in our application (which is pretty huge and spans multiple applications) we have an idea of a master list page. On this list page there is only one report and there is an export to CSV icon on a tool bar that we output above the page's content. This icon is only active on master list pages since they by definition and requirement only have 1 large report on the page. The icon has a link that is forged based on inspecting how the #CSV_LINK# replacement works in region templates.
    The test page posted above uses such knowledge to make a #CSV_LINK# in the report template. And I am sure at this point you are saying to yourself "this is obviously in this guys hands and not our problem."
    I am not guessing the reason it could not be reproduced is that the CSV_LINK is not output when the report query returns no data found.
    Example of the HTML in the region template being used:
    &lt;a href=&quot;f?p=&amp;APP_ID.:&amp;APP_PAGE_ID.:&amp;SESSION.:FLOW_EXCEL_OUTPUT_#REGION_ID#_en-us&quot;&gt;Custom Export Link&lt;/a&gt;

  • Export bug?

    I have an object in my library that is exported for
    actionscript. Export in first frame is UNchecked.
    I placed an instance of the object on the root timeline on
    Frame 3.
    Despite this, the object is not included in the movie, and is
    not accessable from actionscript.
    I'm positive it is on the timeline (always).
    If I check export in first frame, then it works fine.
    Is it a bug?

    Nevermind. I moved the frame with the "dummy" instances of
    the exported objects (frame 3) in front of the frame that uses the
    exported objects (frame 2). So now frame 2 has the dummies and
    frame 3 actually invokes them in actionscript.
    The behavior is very strange, and still might be a bug. By
    including instances, the objects should be included in the swf. So
    they should be accessible from any frame once the movie is fully
    loaded, yet they are accessible only if they appear on a frame
    before the frame you are accessing them in actionscript. It doesn't
    make sense.

  • FCPX XDCAM Export Bug?

    Final Cut Pro X offers the option to export media in XDCAM HD422 50 Mbps, which is the only format my broadcaster can process (with Sony Xpri). However the exported file has no video. Audio is just fine.
    Even if i re-import the exported file in FCPX there is just black video. It seems to me like a bug. Does anyone have an idea how to export XDCAM format without another (pricey) software?

    Original files were 1920*1080 at 25i. The first screenshot is what FCPX shows. The second is Quicktime-Info after exporting. I have to play out 4 mono audio tracks for sony's xpri. I also used 1280*720 at 50p material. Same problem. No video...

  • IPhoto Exporting bug ?

    Ok lets see if I can explain this I haven't seen this problem before and I have over 10,000 photos in iPhoto, I imported from my cameras memory card 25 images some portrait, and some landscape none of them edited yet so no changes to the original files yet.
    Now I decide to upload to my SmugMug account using the SmugMug export plugin, while they were uploading I noticed that the file sizes of the portrait photos were about half the files size of what they should have been. So I decided to do a little trouble shooting to see if it was the plugin or iPhoto where this bug is.
    Tests were done on non edited files, and the JPEG Quality was set to MAX (Grayed out while the following first 2 choices were used)
    1. So here is what I did, started with iPhoto -->file export -->original, to a folder on the desktop and everything was correct file sizes.
    2. iPhoto -->file export -->current and the landscape file sizes were ok but the portrait photos were about half the file size.
    3. iPhoto -->file export -->JPEG and JPEG Quality=MAX the landscape files are fine but portrait photos were about half the file size.
    So here is the issue, if you edit or make changes to your files and want to export the current photos all your portrait photos will export at about half the normal file size. As for the SmugMug plugin it appears to be using the "current file, or JPEG setting".
    Why is iPhoto messing with the file sizes on export when using "current file setting" for portrait when lanscapes are fine?
    Message was edited by: Islander
    Message was edited by: Islander

    My two cents on this issue.
    Having recently upgraded to a dSLR, I too ran into the "Orientation" tag issue with rotated photos. As you pointed out, my dSLR acts the same in that the auto rotation ON/OFF menu item in the camera only applies to playback of the photo. The orientation tag is still applied to every photo regardless.
    So in my case, I use a (now long in the tooth) application called Cameraid to initially review new photos, rotate them as needed, throw out the bad ones, and then batch rename the bunch according to my renaming rules. The problem is, this program rotated the files great, but does not update the Orientation tag. What then happens is if I then loaded the photo into an application (e.g. Preview, Photo Shop Elements) or to a web site (e.g. Flickr) that recognizes and acts on the Orientation tag, it would slip those photos again so that they would now display 90-degrees from "normal" because I had already rotated them.
    I also just recently got my ne iMac, so I am slowly updating my work flow tools. I would like to find something equivalent to Cameraid that can batch rename with the same complete flexibility and also allow me to rotate photos AND update the "Orientation" flag to match. In the meantime, I am using a little command line application that can "fix" the orientation flag for me. I made a little script file that looks at all the new photos in my work folder and "fixes" the Orientation tag so that they are all "Normal" (not rotated) then in Cameraid I rotate the photos like I normally do and everything matches.
    So since I started to play around with iPhoto again with my new Mac (I haven't seriously played around with it since iPhoto v2) I didn't notice the problem you describe because my workflow fixes all my rotation and orientation issues before they hit iPhoto. Not an ideal workflow, but it is getting the job done.
    Just thought I would share my own observations. I will have to look at my photos when I get home and try your troubleshooting steps with my "fixed" portrait photos and see if I can the same issue as you or if making the Orientation tag for portrait photos be "normal" (zero) if that allows iPhoto to not resize the files on exported photos. When I get a chance to try it, I will report back.
    Regards,
    Patrick

Maybe you are looking for