Hi colleagues,
OK, my two pennies on this topic.
Reframing pages is always a dangerous sport, especially in a facing-page document. Indeed, since those facing pages are not supposed to undergo any 'move' along the X-axis, each time a reframe occurs that involves changing X coordinates, many unexpected things may happen behind the scene. The page geometry is modified, its translation attributes are readjusted in its transformation matrix, the relationship with the master spread may be somehow altered, and as discussed in other threads bugs or issues with the masterPageTransform property may occur, weird shifts that seem unrepairable, not to mention the options related to layout rules, and so on.
So it's hard to design a script that works in all environments, all versions, all configurations. There is always an obscure preference that someone has activated, or disabled, which interacts with the whole system and ruins all our effort.
There is at least one law that we have learned from experience: DO NEVER TRUST the page.bounds property. If you attempt to reframe pages, assuming that no better solution has been found, try to work with properly resolved coordinates—myPage.resolve(…)—and stick to the tools that coordinate spaces and transformation provide. Here is an attempt to fix your problem on this basis.
Try this:
// YOUR SETTINGS
// =====================================
// Values required IN POINTS (negative numbers allowed, for increasing the area.)
// ---
const CROP_SIDE = 12.225/*pt*/,
CROP_TOP = 12.225/*pt*/,
CROP_BOTTOM = 100/*pt*/;
// Export options, etc.
// ---
const DOC_NAME_MAX_SIZE = 12,
OUT_PATH = "/Volumes/Testing/binuscan Test/BookViewerTest/";
const JPG_EXPORT_PREFS = {
jpegQuality: +JPEGOptionsQuality.high,
exportResolution: 170,
jpegExportRange: +ExportRangeOrAllPages.exportRange,
};
(function exportPageAreas()
// =====================================
// Should support the tricky 'facing-page' case, including when
// pages have different sizes, and whatever the rulerOrigin mode.
{
// Boring constants.
// ---
const CS_INNER = +CoordinateSpaces.INNER_COORDINATES,
CS_SPREAD = +CoordinateSpaces.SPREAD_COORDINATES,
TL = +AnchorPoint.TOP_LEFT_ANCHOR,
BR = +AnchorPoint.BOTTOM_RIGHT_ANCHOR;
const LEFT_HAND = +PageSideOptions.LEFT_HAND;
// Context validation.
// ---
var doc = app.properties.activeDocument;
if( !doc ){ alert( "No document!" ); return; }
// Export prefs.
// ---
const EXP_JPG = +ExportFormat.JPG,
JEP = app.jpegExportPreferences,
filePrefix = OUT_PATH + doc.properties.name.substr(-DOC_NAME_MAX_SIZE);
JEP.properties = JPG_EXPORT_PREFS;
// Last variables.
// ---
var pages = doc.pages.everyItem().getElements(),
pg, pgName,
dxLeft, dxRight,
xyTL, xyBR;
// Loop.
// ---
while( pg=pages.pop() )
{
// Page corners coords in the parent space.
// (Note: Do Never Trust page.bounds!)
// ---
xyTL = pg.resolve(TL, CS_SPREAD)[0];
xyBR = pg.resolve(BR, CS_SPREAD)[0];
// Opposite corners => reframe.
// ---
dxLeft = LEFT_HAND == +pg.side ? CROP_SIDE : 0;
dxRight = dxLeft ? 0 : CROP_SIDE;
pg.reframe( CS_SPREAD,
[
[ xyTL[0]+dxLeft, xyTL[1]+CROP_TOP ],
[ xyBR[0]-dxRight, xyBR[1]-CROP_BOTTOM ]
]);
// Export.
// ---
JEP.pageString = pgName = pg.name;
doc.exportFile(EXP_JPG, new File(filePrefix+('00'+pgName).substr(-3)+'.jpg'));
// Restore page. Here we can't safely re-use [xyTL,xyBR] as it is,
// because the spread space origin *may* have moved during reframe.
// Therefore we need to formally reverse the calculation.
// ---
xyTL = pg.resolve(TL, CS_SPREAD)[0];
xyBR = pg.resolve(BR, CS_SPREAD)[0];
pg.reframe( CS_SPREAD,
[
[ xyTL[0]-dxLeft, xyTL[1]-CROP_TOP ],
[ xyBR[0]+dxRight, xyBR[1]+CROP_BOTTOM ]
]);
}
alert( 'Page areas have been successfully exported.' );
})();
May work or may fail… Who knows?
@+
Marc
1 bonne réponse
37
Réponses
AdChoices