Forum Replies Created
-
AuthorPosts
-
Uwe Laubender
MemberDarn. It did not.
Remove [code] and [/code] from the beginning and the end of the script and give it a try.Uwe
Uwe Laubender
MemberWithout removing any layer or creating any layer, the following ExtendScript (JavaScript) should do what you want:
[code]
app.doScript
(removeAllPageItems,
ScriptLanguage.JAVASCRIPT,
[],
UndoModes.ENTIRE_SCRIPT,
"Remove All PageItems | SCRIPT");
function removeAllPageItems(){
//ExtendScript (JavaScript):
var myDoc = app.documents[0];//Unlock all layers in case some or all layers are locked:
myDoc.layers.everyItem().locked = false;//Unlock all page items in case some or all page items are locked:
myDoc.pageItems.everyItem().locked = false;//Remove all page items in one go:
myDoc.pageItems.everyItem().remove();};
[/code]Hope, that the code formatting in the forum’s editor is working as expected ;-)
Uwe
Uwe Laubender
MemberNot to forget “Source Sans Pro” of course.
All other provided fonts, as far as I can see, are not user-ready and must be “compiled” to user-friendly font files.
And “that” could be a big hurdle for some folks. You need the right tools and the courage to use them with some command line editing skills. User-friendliness is a different thing, I think.Uwe
Uwe Laubender
MemberHi together,
logging in here into the forum might be a big hurdle for some people.Now on topic:
Mathew Rechs of Adobe spoke about open source fonts provided by Adobe:
“Finally: The selection of high-quality open source typefaces has expanded dramatically in recent years. Adobe’s own open source type can be gotten here – no subscription, no Adobe ID required: https://github.com/adobe-fonts”
That’s more than ok, that’s fantastic.
I’m using the “Source Code Pro” and “Source Serif Pro” families a lot in my documentation for large scripting projects.Uwe
Uwe Laubender
Member@CreeDo – a shorter version without the two dashes would be:
app.activeDocument.links.everyItem().unlink();Uwe
Uwe Laubender
MemberAnother solution:
If you want PDF/X-1a as output format, you can go the Print-To-PostScript-Distill-To-PDF route.
Then the shifting of elements will *not* happen!Uwe
Uwe Laubender
MemberUwe Laubender
Member.fsName+"r"
Hi, Jongware!
.fsName+”r” should be .fsName+”r”. Somehow your blackslash was dropped by the forum software?
Uwe
Edit: mine, too…
So to everyone: just add a backslash before the “r”! Now i try to escape my backslash…
Uwe Laubender
MemberMatthew Laun of Adobe just posted another hack for terminating export to background. A more radical method. It will affect ALL export processes, not only PDF export. He says: “Note that this affects all background exporting, which includes PDF, IDML, and, I believe, InCopy Assignments.” And it will work for InDesign CS5.5 as well.
See here:
https://forums.adobe.com/messag…..90#3689090
P.S. btw, my script will work for InDesign CS5 & CS5.5
Uwe
Uwe Laubender
MemberMatthew Laun of Adobe just posted another hack for terminating export to background. A more radical method. It will affect ALL export processes, not only PDF export. He says: “Note that this affects all background exporting, which includes PDF, IDML, and, I believe, InCopy Assignments.” And it will work for InDesign CS5.5 as well.
See here:
https://forums.adobe.com/messag…..90#3689090
P.S. btw, my script will work for InDesign CS5 & CS5.5
Uwe
Uwe Laubender
MemberElTee said:
Just copy and paste the code into a text document and save it as ExportPDF_Foreground.jsx and then put the .jsx-file in the scripts folder in InDesign.
To access the script you need to pull up the Scripts panel and then just click the script to run it.
Hi vickyvaughn!
The script in NOT an Apple Script. it is the Adobe flavour of JavaScript called ExtendScript. The file ending is “.jsx”.
Just do like ElTee already said. The script is plain text, so copy it to TextEdit. Make sure that you press cmd+shift+t to get plain text. Save it with the name “ExportPDF_in_Foreground_CS5.jsx” even if TextEdit will recommend a .txt suffix. To use the script copy the file to the folder “Scripts Panel” which resides in “applications/Adobe InDesign CS5/Scripts”. Now it should show in the InDesign Scripts panel.
Uwe
Uwe Laubender
MemberElTee said:
Just copy and paste the code into a text document and save it as ExportPDF_Foreground.jsx and then put the .jsx-file in the scripts folder in InDesign.
To access the script you need to pull up the Scripts panel and then just click the script to run it.
Hi vickyvaughn!
The script in NOT an Apple Script. it is the Adobe flavour of JavaScript called ExtendScript. The file ending is “.jsx”.
Just do like ElTee already said. The script is plain text, so copy it to TextEdit. Make sure that you press cmd+shift+t to get plain text. Save it with the name “ExportPDF_in_Foreground_CS5.jsx” even if TextEdit will recommend a .txt suffix. To use the script copy the file to the folder “Scripts Panel” which resides in “applications/Adobe InDesign CS5/Scripts”. Now it should show in the InDesign Scripts panel.
Uwe
Uwe Laubender
MemberTom Dearie said:
Okay, a suggestion from Bob Levine has solved our PDF export problems with CS4 legacy files on CS5:
Rather than exporting to PDF, we added the document to a book, closed the document, and exported the Book to PDF through the Book Options Panel.
You can try my Export PDF script for exporting in “foreground” with single files not already stacked in a book. It circumvents the bug by using the “old” method of outputting in foreground. That method is still available by scripting.
You find the script here on Indesignsecrets in the forums:
https://creativepro.com/for…..h-cs5#2709Uwe
Uwe Laubender
MemberThere is a way of doing this; it's a 2-step process:
1. just place a grayscale tiff in InDesign, color it (use the direct selection tool, the white arrow, to select the image itself not the container!) with fill color white (CMYK 0,0,0,0 or [Paper]). If you placed the tiff on white background you will not see the image any more…
2. Select the container holding the image with the selection tool (black arrow tool) and apply fill color [Black]
And it's done: you inverted your image!
Uwe
Uwe Laubender
Member@Anne-Marie: thank you!
@Stix: Placing page “3” is also possible. See the following code:
//The PDF to place will be placed cropped to it's TrimBox value;
//true until a different setting in UI is set or true until another script forces a different behaviour:
app.pdfPlacePreferences.pdfCrop = PDFCrop.CROP_TRIM;//The background of the placed PDF will be set to “transparent”, set to “false” if you want the opposite.
//true until a different setting in UI is set or true until another script forces a different behaviour:
app.pdfPlacePreferences.transparentBackground = true;//The following is working only once in one placing operation and might be true for all PDFs loaded in the “place gun”:
app.pdfPlacePreferences.pageNumber = 3;
//After emptying the “place gun” and without starting this script again, in the next place operation pageNumber will default to “1”Attention:
if there is no page 3 in your PDF, the page that will be placed is the first page of your PDF. (To my surprise) the script will give no warning or error message.
Further: if you load several PDFs in your “place gun” and one of them does not contain a page 3, it depends on the loading order if any of the PDFs will be placed with page 3. Say, PDF 1 of 5 contains only 2 pages, then PDF 1 will trigger the default for itself and all consecutive loaded PDFs. Result: all PDFs are placed with their page 1.Uwe
-
AuthorPosts