11.07.2015 Views

Analyzing the “Photographic Evidence” of the Nanking Massacre

Analyzing the “Photographic Evidence” of the Nanking Massacre

Analyzing the “Photographic Evidence” of the Nanking Massacre

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Fitch Photos -(21)Photo 93 Photo 91 Photo 89 Photo 91 Photo 92 Photo90Photo89= Fitch Photo Photo92= Fitch Photo Photo90= Fitch Photo Photo93= Fitch Photo Photo91= Fitch Photo Photo94= Fitch Photo (21)One obvious contradiction that instantly strikes <strong>the</strong> reader <strong>of</strong> this quoted passage.If <strong>the</strong> Fitch family had really closely preserved <strong>the</strong>se photographs in <strong>the</strong>ir possession forhalf a century, some <strong>of</strong> <strong>the</strong> photos could not have been printed in RBS or WMRB, whichwere published in 1938. There are several o<strong>the</strong>r inconsistencies and questionable points inthis explanation:1. Although Tooker himself supposedly took <strong>the</strong>se photographs, he contradicted himself bysaying that a Japanese soldier had photographed some <strong>of</strong> <strong>the</strong>m. Had a Japanese militaryman truly have been <strong>the</strong> photographer, one wonders who told Tooker about him, and howhe obtained <strong>the</strong>m from <strong>the</strong> military man, at what location and on what date.2. What was <strong>the</strong> name <strong>of</strong> <strong>the</strong> Korean film developer? What was <strong>the</strong> identity <strong>of</strong> <strong>the</strong>American to whom that Korean sent <strong>the</strong> photo prints—Tooker himself or someone else?How did that Korean become acquainted with that American?3. Although Tooker himself reportedly took some photographs, none were credited to him.Did Tooker not take any images <strong>of</strong> <strong>the</strong> Japanese?147

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!