1 Correct answer
I tend to over-complicate things so you may want a simpler solution, but if I were to rewrite the function you've shown me I would do it like this:
var options = {
// Bypass all find/replace prompts, just remove the newlines:
removeNewlines: false,
//
find: {
value: "[\\r\\n\\cC]", // Text to appear as default
title: "Find:", // Title of window
desc: "Enter RegExp/GREP/Text", // Description of window
flags: "gm",
},
replace: {
value: "",
title: "Replace:",
Explore related tutorials & articles
13
Replies
Isn't newline/linefeed character specific to OS? For instance on Windows, a normal press of Enter produces 003 shown on left with "Lorem ipsum dolor" and Control+Enter produces 015 shown on right with "hello world".
You can always identify a character via String.charCodeAt() to get the ASCII value to see exactly what character is being used for newlines (whether /r, /n, /r/n, or even ^z) then use caret syntax like above \c_ to target it.
1. /n
I know this is not very important, but I want to fix them because sometimes I want to delete it.
2. ^、$
These two are very important to me. I think there is any way to achieve them, like the following.
I can't really speak to the accuracy of the CEP panel you're using, but if you wanted to delete newlines this could be done like so:
var find = /[\r\n\cC]/gm,
replace = " ";
var texts = app.activeDocument.textFrames;
for (var i = 0; i < texts.length; i++)
texts[i].contents = texts[i].contents.replace(find, replace);
With regards to ^, you can split the string, process each line, then join and replace it:
var find = /^./gm,
replace = "2"
var doc = app.activeDocument,
texts = doc.textFrames;
for (var i = 0; i < texts.length; i++) {
var content = texts[i].contents;
var lines = content.split(/[\r\n\cC]/gm),
newStr = []
for (var e = 0; e < lines.length; e++)
newStr.push(lines[e].replace(find, replace));
texts[i].contents = newStr.join("\r\n");
}
Before running we have two TextFrameItems, the one at the top has word-wrapping and no newline but the TextFrame at the bottom ("foo, test, hello") has two newlines:
With the result being:
I tend to over-complicate things so you may want a simpler solution, but if I were to rewrite the function you've shown me I would do it like this:
var options = {
// Bypass all find/replace prompts, just remove the newlines:
removeNewlines: false,
//
find: {
value: "[\\r\\n\\cC]", // Text to appear as default
title: "Find:", // Title of window
desc: "Enter RegExp/GREP/Text", // Description of window
flags: "gm",
},
replace: {
value: "",
title: "Replace:",
desc: "Enter Text",
},
confirm: {
value: false,
title: "Enable line-splitting?",
desc: "Choose no to enable global flags and newline targeting",
},
lineSplitting: {
onSplit: /[\r\n\cC]/gm, // RegExp to use for manual newline split
onJoin: "\r\n", // Value to join newlines back with
},
showChanges: true, // Whether to display alert on completion noting change count
};
Array.prototype.filter = function(callback) {
var filtered = [];
for (var i = 0; i < this.length; i++)
if (callback(this[i], i, this)) filtered.push(this[i]);
return filtered;
};
function get(type, parent) {
if (arguments.length == 1 || !parent) parent = app.activeDocument;
var result = [];
if (!parent[type]) return result;
for (var i = 0; i < parent[type].length; i++) result.push(parent[type][i]);
return result;
}
function findReplace() {
try {
var doc = app.activeDocument,
scope = doc.selection.length
? get("selection").filter(function(i) {
return i.typename == "TextFrame";
})
: doc.textFrames,
count = 0;
if (options.removeNewlines) {
for (var i = 0; i < scope.length; i++) {
var content = scope[i].contents;
var lines = content.split(/[\r\n\cC]/gm),
newStr = [];
for (var e = 0; e < lines.length; e++)
newStr.push(lines[e].replace(find, replace));
scope[i].contents = newStr.join(" ").replace(/\s{2,}/gm, "");
}
return null;
}
var find = prompt(
options.find.desc,
options.find.value,
options.find.title
);
if (find !== null) {
var findRX = new RegExp(find, options.find.flags),
shouldSplit = confirm(
options.confirm.desc,
!options.confirm.value,
options.confirm.title
);
var replace = prompt(
options.replace.desc,
options.replace.value,
options.replace.title
);
if (replace !== null) {
for (var i = 0; i < scope.length; i++) {
var content = scope[i].contents;
if (shouldSplit) {
var lines = content.split(options.lineSplitting.onSplit),
newStr = [];
for (var e = 0; e < lines.length; e++) {
if (findRX.test(lines[e])) count++;
newStr.push(lines[e].replace(findRX, replace));
}
scope[i].contents = newStr.join(options.lineSplitting.onJoin);
} else {
if (findRX.test(scope[i].contents)) count++;
scope[i].contents = scope[i].contents.replace(findRX, replace);
}
}
if (options.showChanges) {
var alertStr = !count
? "No changes made"
: count > 1
? count + " changes made"
: "1 change made";
alert(alertStr);
}
}
}
} catch (err) {
alert("Error: " + err);
}
}
findReplace();
With options.removeNewLines set, there is no UI. It just takes this:
And turns it into this:
Otherwise all the option values at the top of the script determine the behavior and UI:
The above defaults to No, which targets the "paragraph" and all lines for a single RegExp replace. When choosing Yes, it will split each line into a sentence and run an individual replace on each sentence, then reconstruct and assign the value back to the original TextFrame. All this behavior is configurable through the options object at the top of the script.
AdChoices