Missing text after EXPORT from PMD to PDF

Hi,
I have a document, designed through Adobe pagemaker 70, which I would like converted to PDF. Within Adobe PageMaker 70 I performed a File-->Export-->Adobe PDF, kept all the default options and managed to generate a PDF version of the *.PMD document. However, some of the text in the PDF document is missing. I searched on the internet and discovered one can do Document-->Examine Document within Adobe Acrobat 9 Pro to display any hidden text. Doing this I was able to see the missing text.
There is an image in the source Pagemaker document, but the image is not square but cropped along it's outside edge and the text flows around the edge (hope that makes sense). What's puzzling is that in Adobe Acrobat 9 Pro the generate PDF has the image displayed in a box and some (not all) the text behind this box is shown as hidden, where as in the source document all text flowing around the image is visible.
Can anyone please help with this problem and tell me how I can get the hidden text in my PDF document to display so it's visible in an Acrobat Reader or when printed?... I am still a bit of a newbie with both Pagemaker and Acrobat so your help would be much appreciated.
Thanks in advance.
Sharon
PS: I have not uploaded the file but do not mind doing so if some one is able to help and requests either the source PMD file or the generated PDF file

Hi,
The "question mark" displayed may be refereed to the missing font.
Are you trying to convert a public web page? if yes then please share a link so that i can also test it.
Regards,
Anoop

Similar Messages

Missing filters after exporting from lightroom

I am currently moving my photo editing from a 32-bit WinXP machine to a 64-bit Win7 machine. For the time being, both computers have CS4 Design Premium and Lightroom 2.5 installed. All apps on both machines are currently up-to-date.
The issue, and this ONLY occurs on the 64-bit Win7 machine, is that all of my third party filters disappear when I bring a file from Lightroom into Photoshop. They aren't greyed-out. They are not listed. Period.
I've tossed out the PS preferences and made sure that both the 64-bit ver. of PS and the regular ver. of PS both point to the correct extra plugins folder.
It has nothing to do with images coming out of Lightroom in @ 16bit because they are exported that way on the XP machine as well. Filters that can't be run on 16-bit images just appear as greyed-out.
I can open an image directly in Photoshop and all of the filters are there. If I export the same image (and it doesn't matter whether I choose "edit in Photoshop" or "Open as a smart object"); if it's coming from Lightroom the filters are gone.
Does anybody have any ideas why this would occur and, more importantly, how to fix it because this is really crippling productivity.
Thank you.
M. Green

I'm not sure what you mean - did you mean save an image to 32-bit?
I don't have a way (that I know of) to control which PS exe. Lightroom sends to image to when I choose to edit in PS. I'm assuming it's going to the 64-bit app. But in any case, I don't think it should matter. I opened both PS exe's and made sure that both pointed to the same plugins folder.
I posted here because it seemed like a PS issue and I don't know what the policy is around here about cross-posting the same issue to different forums.

PDFs dull in Acrobat after exporting from Indesign - again

Hi folks,
I am aware of a previous post which discussed this issue which was apparently resolved, but it appears to have reared its ugly head again. The problem - since updrading to Mavericks and the Creative Cloud, pdfs in Acrobat are very dull after export from Indesign and it is not a transparency blend or Indesign issue. I understand Adobe blamed Apple for not updating their colour management software and the reply from Adobe was:
"We have found the root cause of this issue and are in process of providing a fix. Once this is done, we will test it to make sure that it works as expected and will release an update patch for all our users."
I am running the latest version or everything but it appears to still be a problem. I have also uninstalled Acobat XI and tried earlier versions without success. I have a print job to send off tomorrow and I am very nervous about how this will print.

Sorry about that, I apparently forgot to attach the file; have done so now.
The method I'm using for creating outlines is simply to use the "Create Outlines" command under the Type menu within InDesign. Then I create my PDF files by using the Export command under the File menu and choosing the PDF/X1a option. 99% of the time I get perfect results, it's only when I try to make outline type that I encounter this problem. You'll clearly see the artifacts in question in the example attached.
I don't know whether or not the press would have printed these artifacts, as you suggest, since no printer has been willing to execute a file that shows any anomaly in the proof process. I can't say that I blame them.
Hopefully you will see what I'm talking about and can recommend a solution, though I like your idea of simply giving them a properly executed file and then telling them to get a life. It hasn't worked so far, as I unfortunately deal with a lot of Neanderthals around here, but I suppose it's worth putting forth again the next time this issue arises. It will.
By the way, no print house of my choosing is this far behind the curve, if at all. These cavemen are always printers who have long-standing relationships with my clients, and for whatever reason (generally lowest cost I'm sure), the clients think they hung the moon. We, of course, no otherwise, but it does it profit a designer to tell his client he or she is crazy for using a printer who is a decade behind the technology curve.
We cowboy up and seek solutions, eh?

Embedding font problems (when exporting from InDesign to PDF)

A message alert is shown, when opening a pdf - after exporting from InDesign: Cannont exctract the embedded Font Frutiger.
We have uninstalled the frutiger font and installed an open type. But the font is not embedded anyhow..?
Can anyone help?
Thanks very much.
Jane

I don't know if you need help scripting this, but...........
If you can not re-create the PDF from InDesign using the OTF,
In Acrobat, highlight the text with the acrobat touch-up text tool, right click and go to properties. You should be able to assign the OTF font running on you system, and select the embed option.
If not, this is why PitStop is an indespensable (sp?) tool.
Best of luck

Page numbers incorrect after conversion from Excel to pdf

Page numbers incorrect after conversion from Excel to pdf
""This above link (thread:834599) is from a case back in 2011 that claims to solve this problem, but it does not solve this problem. I think that customer only cared about having continuous page numbering, not discrete page numbering per sheet.
========================
I still have this issue in Acrobat XI and MS Office Professional Plus 2010. I keep upgrading to no avail. This regression has resulted in a huge time drain for me. If you fixed it, please explain how I can get my hands on the resolution.
Previous versions of Excel and Adobe Acrobat enabled flexibility around the "Page #" of "Number of Pages" (Page &[Page] of &[Pages]) token, depending on context and usage. The "# of pages" token could represent EITHER the number of pages in the workbook OR the number of pages in the tab/sheet, depending on how you generated the PDF:
You could select "Selected Sheets" and then select all or some of the individual sheets in the workbook, and the PDF would honor the discrete numbering of each of the sheets, so the first page of each sheet was p1 and the "# of pages" was the number of pages in the sheet; not the number of pages in the workbook; or
You could select "Entire Workbook" and the PDF would honor continuous page numbers across all sheets, as a single document.
Now, it only honors the total number of pages in the workbook, regardless of the method you use to publish to PDF: saving as PDF, printing to PDF, using "createPDF" from Acrobat plugin to Excel's menu ribbon; selecting all sheets, some sheets, or Entire Workbook; automatic First page number or "1" under Page Setup > Page> First page number. (This last option, btw, does restart every sheet at p1, but it hardly makes sense if the total number of pages is still the total number in the workbook instead of the number in the sheet.)
I spent a lot of time trying each which way that the blog posts recommended and have tried this on multiple versions of Excel and Acrobat now.
NONE of these time-consuming experiments gave me what I wanted.They all insist that "Page #" of "Number of Pages" (Page &[Page] of &[Pages]) is the total number of pages in the workbook or the total number of pages in the selected sheets combined.
The numbering are correct in Excel Page Layout.
The same issue happens when using LibreOffice calc. (Although, I never tested with Libre Office before, so I don't know that it ever worked).
The workaround now is to create PDF for each spreadsheet one at a time, and then compile them using the Acrobat combine/binder feature. All alternatives are extremely time consuming and tedious. It used to be automatic. This is a major regression that has gone untreated for over a year now, maybe two years.
My task takes infinitely more time to complete than it did with previous versions of Acrobat. That means that days are added to my project, when the functionality used to enable a quick pdf generation that was ready for review, now I have to do this very manual time-consuming set of steps to generate a draft. As the project has grown and more tabs are added, my pdf-generation task takes that much longer. We require lots of drafts. It used to be easy and fast. Now it is hard and time-consuming.
In my opinion, the problem is not Excel; it is Acrobat because it was introduced with an upgrade in Acrobat, not an upgrade in Excel. The problem was introduced in Acrobat 9 or 10. Please provide a patch or add-on or something.

If you are setting up the page numbers in Excel, the resulting PDF would display the the page numbers created in Excel. On Excel 2010 support page, (http://office.microsoft.com/en-us/excel-help/insert-and-remove-page-numbers-on-worksheets- HA010342619.aspx#BM2) is stated the following "tip" which indicates by default Excel 2010 starts numbering each tab with 1. Exel's workaround tip is below -
Set a different number for the starting page
Tip To number all of the worksheet pages in a workbook sequentially, first add page numbers to all worksheets in a workbook, and then use the following procedure to begin the page number for each worksheet with the appropriate number. For example, if your workbook contains two worksheets that with both be printed as two pages, you would use this procedure to begin the page numbering for the second worksheet with the number 3.
On the Page Layout tab, in the Page Setup group, click the Dialog Box Launcher next to Page Setup.
On the Page tab, in the First page number box, type the number that you want to use for the first page.
Tip To use the default numbering system, type Auto in the First page number box.
Also helpful in the same section is the note on viewing page numbers. To see if the page numbering dilemma originates in Excel make sure you are using the Page Layout View see below:
Hide All
If you want numbers shown on pages when you print a worksheet you can insert page numbers in the headers or footers of the worksheet pages. Page numbers that you insert are not displayed on the worksheet in Normal view — they are shown only in Page Layout view and on the printed pages.
Overall it may be easier not to create the page numbers in Excel but instead create then in Acrobat using the Headers and Footers option in Acrobat. I hope this helps - it sounds like a frustrating issue you are experiencing.

Cannot Open Excel File after exporting from Disco Plus

Hi there,
I got a question from one user having issue with opening Excel file after exporting from Disco Plus.
The report has been using for a while and he is using Excel 2003 version and Discoverer 10g(10.1.2.2), he never got this kind of error before, just recently got error.
After exporting from Disco Plus he saved file on his desktop and when he tries to open the excel it says "Cannot be Accessed, can be corrupted...." but this is not from network drive since he saved file on local desktop or C drive.
Also not for all reports, only this particular report and only specific parameter, for example for parameter 2008 Feb opened successfully, but for2009 Feb he gets this error when trying to open excel.
i tried in excel 2007 also , i dont think this is Excel version error, am not sure.
Also after go live last week (we upgraded database from 9i to 10g) but i am not sure this causes ,since for one parameter working, for other parameter not working.
Actually we should get one window for Macro when we try to open excel, but he is not getting it seems.
Any ideas/thoughts on this would be greatly appreciated.
Thanks for your help
--skat

Rod,
Thanks for your quick response on this.
Yes, we can export to other formats as well, but actually exporting is working, after saving the file on our local desktop/drive and when we try to open we get this kind messages or we cannot open the file, we should get message window for Macro to enable/disable but for this report we are not getting this either,
Also this happens only for specific parameters,like i mentioned above it works I mean excel file opens for one set of parameters but for some other set of parameters cannot open.
For example :- when we enter FEB 2008 it works, if we enter FEB 2009 it won't open the file.
This is weird
I am still working on this issue, may be better to recreate the report again might be helpful,
Any ideas/comments/thoughts would be great
Thanks
Skat

Missing text after pdf export.

I am having problems exporting to PDF from Publisher 2007.
I am using Adobe professional 8, Publisher 2007 on Windows Vista 64.
The files are created and printed to PDF. When I take a look at the PDF there are blocks of text missing. If I re-export the file again, 9 times out of 10 the text will be missing. Periodically everything will work fine with the same document. In the most recent document I am using Helvetica 55 Roman 12pt. All the body text is identical (at least from what I can tell). This exact same document exports to PDF perfectly on a Windows XP SP2 machine using Adobe Professional 8 and Office 2007.
As far as I can tell, this only occurs in when exporting from Publisher, which leads me to believe that it is an MS problem but I have been unable to find any information about something Publisher specific.
Thanks in advance for any help. This is frustrating.
Jason

I spoke too soon.
I exported (using the adobe add-in) 8 documents. The first 1, 2, 3, 5, and 7 were fine. Numbers 4, 6, and 8 had problems.
All these documents were created from the same template. I did the first and all subsequent documents were created by duplicating pages and swapping text. The page numbers vary from 5 to 16. There is no apparent connection with page count as several of the larger ones exported perfectly.
I don't know if this information is relevant at all. I am hoping that it gives someone an indication of what might be causing this.
Thanks again,
Jason

Placed PDF missing text after re-exporting to PDF

I'm using OSX 10.6 with InDesign CS3 504.
When I place PDFs into an InDesign file, and then PDF that InDesign file, some of the PDFs are missing text. All text boxes have been made from the same original text box, just modified for content, and shape very slightly.
The text that is missing is most often white, where it's being used over the top of black frames. There is one instance of black text over a white frame missing.
I've tried exporting to .inx, and then re-pdfing. I've also tried copying text boxes that are 'working' and changing the content, but still the same text boxes are missing their text.
Any help much appreciated. Thanks.
Message was edited by: agreen01

i already tried exporting to .inx about 3 hours ago. unfortunately i'm very pressed for time with a meeting in about 1 hour, so i've recreated the problem text boxes. luckily there were only about 10 of them and it only took 10 mins.
before that i tried to isolate the problem element, but couldn't find one. every time i removed something, i still got the problem. the only time i didn't get the problem was when i had just the text boxes on their own, with none of the other essential page elements.
thanks for your help, though.

PDF has missing text when created from FM 9

My Software:
Windows XP Professional Version 2002 SP 3
FrameMaker 9.0p255
Adobe Acrobat 9 Pro Version 9.4.1
When generating a PDF document from FrameMaker, the PDF document has random missing text, including whole paragraphs, sentences and some text in tables. We have several FrameMaker books and they are all having the same issues. These books were fine when we last published updates within the last month and we have not made any changes to fonts.
When generating a PDF from FrameMaker, we always print the book to a postscript file first following these steps:
- Go to File > Print Book.
- Select the Adobe PDF printer.
- Select the Print to File option and specify a .ps filename.
- Select the Generate Acrobat Data option.
- Use Acrobat Distiller to convert the PS file to PDF.
Note that I also tried File > Save As PDF and got the same results.

Did you reboot after the hotfix? fwiw, other users on the forum have had difficulty with the hotfix not being installed correctly the first time around.
once you download the hotfix from MS you have to run the .exe, and then when it’s finished you have to reboot. Then check the Add or Remove programs in Control panel, and click the “show updates” button, then scroll way down to see the hotfixes, to be sure that #952909 is shown.
What fonts are you using in your documents? Specific type (PS, TT, OTF) and any other info you have (foundry, etc).
Do the "gaps" seem to occur when there are font changes in the document, e.g. when words in a sentence are bold or when a paragraph in a different weight (e.g. bold italic) follows, say, a "regular" text weight paragraph? As another test, can you highlight a segment of good+bad+good text in the PDF, do Control+c to copy it to the clipboard, then Control+v to paste it into a different file (Word, text editor, even another new FM document). Do the words of the "missing" text segments show up?
edit: the hotfix download process is a bit confusing; if I remember correctly it has to be requested, then MS sends a link to the download webpage, then the downloaded .exe has to be run.

No Hyperlink in PDF after export from Crystal Reports 2008 SP2

When I export a report from Crystal Reports 2008 Developer (as well as from the runtime) SP2 to PDF the Hyperlink to a file on hard disk is missing.

Hi,
Go through this LInk
Re: No hyperlinks after exporting to pdf
Regards,
Salah

Shaded areas on PDF after exporting from Indesign

Hello, I'm working on booklets for work using Indesign. So far most of the information in the booklet have been placed by PDF files. My supervisor sent me another PDF he would like added to the booklet. My problem is when I placed the PDF onto the page it looks fine but once I export the booklet from Indesign to PDF you see shaded areas on the page. This has never happened before and I can't seem to fix it. Does anyone have any ideas?

So the sidebar frame is a native ID text frame? I see two shaded areas inthe screen shot that interect that sidebar, and neither of them seems really related to it in any way.
Are you willing to share the file with me for examination?
Have you tired the standard Troubleshooting 101 steps: Replace Your Preferences and Remove minor corruption by exporting?

Background missing when exporting from indesign to pdf

Sometimes when I export a file from indesign to pdf, my background doesn't show up. The background is just a block of solid colour, or gradient. The background block of colour is usually the full size of the page. I've tried to play around to see what is causing this to happen and sometimes if I reduce the size of the block to say, 1/3 of the page then the block of colour shows up, but then when I make it the full size of the page as I actually need it to be, the colour block doesn't show up when I export it to pdf (i've tried all the different pdf presets and it doesn't make a difference)??? Does anyone know why and how to fix it?
thanks!

I believe export is an ID option, not an Acrobat option. In that case, you probably should ask in the ID forum.

Preserving Black when Exporting from InDesign to PDF

Hi All:
I hope someone who knows Acrobat can help me with this. I have an InDesign file that I must export to PDF. That in itself isn't the problem. This is:
The text in InDesign is solid black (000000), but once it exports to PDF, it collects a myriad of colors and will not print preperly to the newsprint. I'm doing this for a newspaper. I use InDesign, they use Quark. The client uses InDesign as well. I can NOT figure out how to convince Acrobat to leave the color alone.
I've tried to figure it out with the Ink Manager, etc., but for the life of me, no matter what I do, It comes out as all the colors of the rainbow. It LOOKS black in the PDF, but when you select it, it is NOT black. It's a mess. Two full pages of this stuff and I'll have to redo the whole darned thing in Quark unless I can figure this out.
I have tried using "Preserve Black" once it's in PDF format, but it doesn't seem to do anything. Obviously I'm missing something in the Export from InDesign function, but I can't figure out what.
Can someone help me?
Thanks so much, in advance.

Okay. Above is the swtch from the original Color Preset. Below is the swtch after I made the changes mentioned above. I'm sure I'm not the only one who sees no difference. ??

Format changing when exporting from InDesign to PDF

I am using Acrobat 8 version 8.1.2, and InDesign version 5.0.2.
I am noticing a very specific problem when exporting some files to PDF from InDesign.
We often have a format where we have a numbered list of right-aligned number, followed by some text, a leader line, and then another number at the end of the line. This is set up with a left indent and a first line left indent (rather than using the numbered list options), and then the necessary tabs later in the lines.
I am finding since we switched to IDCS3, that when I export to PDF, lines containing this format change in the PDF. The text that appears after the number in the front of the line is pushed over on top of the leader line, leaving a huge white space. On rarer occasions, it will move things in lines that have no indents, but contain tabs that aren't being used.
I have been able to get the files to export correctly by removing the left indent and first-line left indent and using tabs instead (or by removing unused tabs). But we have hundreds of files set up in this manner so going in and changing how they are all set up is problematic to say the least.
Is this a known issue? Does anyone know why this might happen and how I can prevent it?

I haven't tried printing to PDF. I will try that and see what happens. Unfortunetly, where I work we are required to export to PDF rather than print to PDF, so if it works it will only be a clue for me rather than a solution.
Thanks for the reply. I'll try a cross post to the InDesign forms.

Unlogged Missing Photos After Import From Aperture

Hi!
I have just made the switch from Aperture to Lightroom, and have use the 1.1 version of the Aperture import plugin.
In my Aperture Library I have, according to the Library -> Photos: 11105 Photos, however after importing to Lightroom, I have only 10967 photos. I have checked the import log, and there were 4 items which failed to import - 3 were .mpo files (panoramas from an xPeria) and 1 was a .gif file. This leaves a deficit of 133 photos that I can't account for.
Is there any way to compare the aperture library to the lightroom library to see what is missing?

*WARNING* Once agin, this is a VERY long post! And this contains not only SQL, but heaps of command line fun!
TLDR Summary: Aperture is storing duplicates on disk (and referencing them in the DB) but hiding them in the GUI. Exactly how it does this, I'm not sure yet. And how to clean it up, I'm not sure either. But if you would like to know how I proved it, read on!
An update on handling metadata exported from Aperture. Once you have a file, if you try to view it in the terminal, perhaps like this:
$ less ApertureMetadataExtendedExport.txt
"ApertureMetadataExtendedExport.txt" may be a binary file. See it anyway?
you will get that error. Turns out I was wrong, it's not (only?) due to the size of the file / line length; it's actually the file type Aperture creates:
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: Little-endian UTF-16 Unicode text, with very long lines
The key bit being "Little-endian UTF-16", that is what is causing the shell to think it's binary. The little endian is not surprising, after all it's an X86_64 platform. The UTF-16 though is not able to be handled by the shell. So it has to be converted. There are command line utils, but Text Wrangler does the job nicely.
After conversion (to Unicode UTF-8):
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: ASCII text, with very long lines
and
$ less ApertureMetadataExtendedExport.txt
Version Name    Title   Urgency Categories      Suppl. Categories       Keywords        Instructions    Date Created    Contact Creator Contact Job Title       City    State/Province Country Job Identifier Headline        Provider        Source Copyright Notice        Caption Caption Writer Rating IPTC Subject Code       Usage Terms     Intellectual Genre      IPTC Scene      Location        ISO Country Code        Contact Address Contact City    Contact State/Providence        Contact Postal Code     Contact Country Contact Phone   Contact Email   Contact Website Label   Latitude        Longitude       Altitude        AltitudeRef
So, there you have it! That's what you have access to when exporting the metadata. Helpful? Well, at first glance I didn't think so - as the "Version Name" field is just "IMG_2104", no extension, no path etc. So if we have multiple images called "IMG_2104" we can't tell them apart (unless you have a few other fields to look at - and even then just comparing to the File System entries wouldn't be possible). But! In my last post, I mentioned that the Aperture SQLite DB (Library.apdb, the RKMasters table in particular) contained 11130 entries, and if you looked at the Schema, you would have noticed that there was a column called "originalVersionName" which should match! So, in theory, I can now create a small script to compare metadata with database and find my missing 25 files!
First of all, I need to add that, when exporting metadata in Aperture, you need to select all the photos! ... and it will take some time! In my case TextWrangler managed to handle the 11108 line file without any problems. And even better, after converting, I was able to view the file with less. This is a BIG step on my last attempt.
At this point it is worth pointing out that the file is tab-delimited (csv would be easier, of course) but we should be able to work with it anyway.
To extract the version name (first column) we can use awk:
$ cat ApertureMetadataExtendedExport.txt | awk -F'\t' '{print $1}' > ApertureMetadataVersionNames.txt
and we can compare the line counts of both input and output to ensure we got everything:
$ wc -l ApertureMetadataExtendedExport.txt
   11106 ApertureMetadataExtendedExport.txt
$ wc -l ApertureMetadataVersionNames.txt
   11106 ApertureMetadataVersionNames.txt
So far, so good! You might have noticed that the line count is 11106, not 11105, the input file has the header as I printed earlier. So we need to remove the first line. I just use vi for that.
Lastly, the file needs to be sorted, so we can ensure we are looking in the same order when comparing the metadata version names with the DB version names.
$ cat ApertureMetadataVersionNames.txt | sort > ApertureMetadataVersionNamesSorted.txt
To get the Version Names from the DB, fire up sqlite3:
$ sqlite3 Library.apdb
sqlite> .output ApertureDBMasterVersionNames.txt
sqlite> select originalVersionName from RKMaster;
sqlite> .exit
Checking the line count in the DB Output:
$ wc -l ApertureDBMasterVersionNames.txt
   11130 ApertureDBMasterVersionNames.txt
Brilliant! 11130 lines as expected. Then sort as we did before:
$ cat ApertureDBMasterVersionNames.txt | sort > ApertureDBMasterVersionNamesSorted.txt
So, now, in theory, running a diff on both files, should reveal the 25 missing files.... I must admit, I'm rather excited at this point!
$ diff ApertureDBMasterVersionNamesSorted.txt ApertureMetadataVersionNamesSorted.txt
IT WORKED! The output is a list of changes you need to make to the second input file to make it look the same as the first. Essentially, this will (in my case) show the Version Names that are missing in Aperture that are present on the File System.
So, a line like this:
1280,1281d1279
< IMG_0144
< IMG_0144
basically just means, that there are IMG_0144 appears twice more in the DB than in the Metadata. Note: this is specific for the way I ordered the input files to diff; although you will get the same basic output if you reversed the input files to diff, the interpretation is obviously reversed) as shown here: (note in the first output, we have 'd' for deleted, and in the second output it's 'a' for added)
1279a1280,1281
> IMG_0144
> IMG_0144
In anycase, looking through my output and counting, I indeed have 25 images to investigate. The problem here is we just have a version name, fortunately in my output, most are unique with just a couple of duplicates. This leads me to believe that my "missing" files are actually Aperture handling duplicates (though why it's hiding them I'm not sure). I could, in my DB dump look at the path etc as well and that might help, but as it's just 25 cases, I will instead get a FS dump, and grep for the version name. This will give me all the files on the FS that match. I can then look at each and see what's happening.
Dumping a list of master files from the FS: (execute from within the Masters directory of your Aperture library)
$ find . -type f > ApertureFSMasters.txt
This will be a list including path (relative to Master) which is exactly what we want. Then grep for each version name. For example:
$ grep IMG_0144 ApertureFSMasters.txt
./2014/04/11/20140411-222634/IMG_0144.JPG
./2014/04/23/20140423-070845/IMG_0144 (1).jpg
./2014/04/23/20140423-070845/IMG_0144.jpg
./2014/06/28/20140628-215220/IMG_0144.JPG
Here is a solid bit of information! On the FS i have 4 files called IMG_0144, yet if I look in the GUI (or metadata dump) I only have 2.
$ grep IMG_0144 ApertureMetadataVersionNamesSorted.txt
IMG_0144
IMG_0144
So, there is two files already!
The path preceding the image in the FS dump, is the date of import. So I can see that two were imported at the same time, and two separately. The two that show up in the GUI have import sessions of 2014-06-28 @ 09:52:20 PM and 2014-04-11 @ 10:26:34 PM. That means that the first and last are the two files that show in the GUI, the middle two do not.... Why are they not in the GUI (yet are in the DB) and why do they have the exact same import date/time? I have no answer to that yet!
I used open <filename> from the terminal prompt to view each file, and 3 out of my 4 are identical, and the fourth different.
So, lastly, with a little command line fu, we can make a useful script to tell us what we want to know:
#! /bin/bash
grep $1 ApertureFSMasters.txt | sed 's|\.|Masters|' | awk '{print "<full path to Aperture Library folder>"$0}' | \
while read line; do
openssl sha1 "$line"
done
replace the <full path to Aperture Library folder> with the full path to you Aperture Library Folder, perhaps /volumes/some_disk_name/some_username/Pictures/.... etc. Then chmod 755 the script, and execute ./<scriptname> <version name> so something like
$ ./calculateSHA.sh IMG_0144
What we're doing here is taking in the version name we want to find (for example IMG_0144), and we are looking for it in the FS dump list. Remember that file contains image files relative to the Aperture Library Master path, which look something like "./YYYY/MM/DD/YYYYMMDD-HHMMSS/<FILENAME>" - we use sed to replace the "./" part with "Masters". Then we pipe it to awk, and insert the full path to aperture before the file name, the end result is a line which contains the absolute path to an image. There are several other ways to solve this, such as generating the FS dump from the root dir. You could also combine the awk into the sed (or the sed into the awk).. but this works. Each line is then passed, one at a time, to the openssl program to calculate the sha-1 checksum for that image. If a SHA-1 matches, then those files are identical (yes, there is a small chance of a collision in SHA-1, but it's unlikely!).
So, at the end of all this, you can see exactly whats going on. And in my case, Aperture is storing duplicates on disk, and not showing them in the GUI. To be honest, I don't actually know how to clean this up now! So if anyone has any ideas. Please let me know I can't just delete the files on disk, as they are referenced in the DB. I guess it doesn't make too much difference, but my personality requires me to clean this up (at the very least to provide closure on this thread).
The final point to make here is that, since Lightroom also has 11126 images (11130 less 4 non-compatible files). Then it has taken all the duplicates in the import.
Well, that was a fun journey, and I learned a lot about Aperture in the process. And yes, I know this is a Lightroom forum and maybe this info would be better on the Aperture forum, I will probably update it there too. But there is some tie back to the Lightroom importer to let people know whats happening internally. (I guess I should update my earlier post, where I assumed the Lightroom Aperture import plugin was using the FS only, it *could* be using the DB as well (and probably is, so it can get more metadata))
UPDATE: I jumped the gun a bit here, and based my conclusion on limited data. I have finished calculating the SHA-1 for all my missing versions. As well as comparing the counts in the GUI, to the counts in the FS. For the most part, where the GUI count is lower than the FS count, there is a clear duplicate (two files with the same SHA-1). However I have a few cases, where the FS count is higher, and all the images on disk have different SHA-1's! Picking one at random from my list; I have 3 images in the GUI called IMG_0843. On disk I have 4 files all with different SHA-1's. Viewing the actual images, 2 look the same, and the other 2 are different. So that matches 3 "unique" images.
Using Preview to inspect the exif data for the images which look the same:
image 1:
Pixel X Dimension: 1 536
Pixel Y Dimension: 2 048
image 2:
Pixel X Dimension: 3 264
Pixel Y Dimension: 2 448
(image 2 also has an extra Regions dictionary in the exit)
So! These two images are not identical (we knew that from the SHA-1), but they are similar (content is the same - resolution is the same) yet Aperture is treating these as duplicates it seems.. that's not good! does this mean that if I resize an image for the web, and keep both, that Aperture won't show me both? (at least it keeps both on disk though, I guess...)
The resolution of image 1, is suspiciously like the resolutions that were uploaded to (the original version of) iCloud Photos on the iPhone (one of the reasons I never used it). And indeed, the photo I chose at random here, is one that I have in an iCloud stored album (I have created a screensaver synced to iCloud, to use on my various Mac's and AppleTVs). Examining the data for the cloud version of the image, shows the resolution to be 1536x2048. The screensaver contains 22 images - I theorised earlier that these might be the missing images, perhaps I was right after all? Yet another avenue to explore.
Ok. I dumped the screensaver metadata, converted it to UTF-8, grabbed the version names, and sorted them (just like before). Then compared them to the output of the diff command. Yep! the 22 screensaver images match to 22 / 25 missing images. The other 3, appear to be exact duplicates (same SHA-1) of images already in the library. That almost solves it! So then, can I conclude that Lightroom has imported my iCloud Screensaver as normal photos of lower res? In which case, it would likely do it for any shared photo source in Aperture, and perhaps it would be wise to turn that feature off before importing to Lightroom?

Missing text after EXPORT from PMD to PDF

Similar Messages

Maybe you are looking for