2 Correct answers
@Bedazzled532, you've made a terrific start! Next you will need to get the story you want to check, so in my example below I've just got the story that the you have selected. I compare it paragraph-by-paragraph with the masterContentFile, and apply a characterStyle "Bad" if it doesn't match.
function main() {
var masterContentFile = File("d:/readid.txt");
var badCharacterStyleName = 'Bad';
if (!masterContentFile.exists) {
alert('Could not find master content file "' + mas
Hi @Bedazzled532, here is a version that checks word by word:
function main() {
var masterContentFile = File("d:/readid.txt");
var badCharacterStyleName = 'Bad';
if (!masterContentFile.exists) {
alert('Could not find master content file "' + masterContentFile + '".');
return;
}
var doc = app.activeDocument,
badCharacterStyle = doc.characterStyles.itemByName(badCharacterStyleName);
if (!badCharacterStyle.isValid) {
alert('Could not fin
30
Replies
Ohhhhhh
Now, that makes sense!
Like I said previously, my solution won't work for you. What I used is called a "GREP Style." It's something you set up inside a paragraph style. It basically is constantly running a GREP Find query against everything marked with that paragraph style, and anytime it finds a hit, it marks it with a character style. StackExchange tells me that there are around seven to eight thousand lines in the Quran, depending on how you count 'em. (Does the surah name count? How about bismillah? But it doesn't matter, because...) This means that your paragraph style would need about eight thousand GREP queries running constantly on your entire document, which would probably be impossible. Even if it didn't crash InDesign, I expect it would slow it down to the point of unusability. It's a cool technique, just not for your use case. I'll add a quick animation at the end of my post showing you how it owrks.
What you'd want instead, I think, would be a script that you'd run once, after layout, which would compare the lines in your doc against your master document. That way you can have each of your non-matching lines flagged for your review, without spending a vast amount of resources on constantly searching your entire document. I like m1b's idea a lot, but it's hard to adapt to your case, because I very much doubt that you're in there re-keying the Quran when you have the complete raw text of the document in another file. You're trying to automate post-layout QA review, right?
Anyhow, I'm looking at your sample screenshot, and I'm seeing a few things that confuse me. The character drops (the pink rectangles) are there because you're using Adobe Arabic here, and it doesn't have an end of ayah glyph, yes? Also, the first line doesn't have an end of ayah because it's actually the bismillah, right? I'm asking because we'd need some kind of segmentation to chop up your target document, and end of ayah is something I've used myself to that end, in the past.
Lastly, here's the GREP Style technique that I think would crash your computer. It works fine for a few searches, probably not so well for thousands.
Okay, so there's lots of possibilities, here. The first that occurs to me is completely free of scripting effort, and feels like a late 20th century workaround. Back then, software generally didn't have a way to mark text as e.g. Dari or Pashto or Burmese or whatever. So, if I did make a custom dictionary for a language, I'd have to pretend that it was named something else. So our Hmong dictionary was actually coded as "English - Scottish." Hmong translator thought that was funny.
Anyhow. We make you a custom dictionary file. Each "word" in the dictionary is a whole line of your Quran file. So we load it in as a custom dictionary, and make sure that it's not using the actual Hunspell dictionary. Then, if a single word is misspelled, you get the red wavy underline indicating a misspelling. Here's how it could work:
1) Take your Master Quran File, and make it into a raw text file.
a) Remove all of the line numbers from your master. This is actually the only place we'll be using GREP.
I don't know if you are using the decorative brackets or the actual end-of-ayah glyph because they've all dropped, but you can just copy them out of your text and paste them into the "Find what" field. I have two separate clauses to find either one-digit or two-digit verse numbers:
﴿\d﴾|﴿\d\d﴾
You might need to play with this query to get it to capture all of your verse numbers...
b) Use the text tool to select the entire Quran, whack Control-A
c) File -> Export, choose "Text Only" as the file format. Give it a unique name (like QuranCustomDict.txt)
2) Add this custom dictionary to InDesign
a) Edit -> Preferences -> Dictionary -> Arabic
b) Add the dictionary
c) Make sure that Spelling is set to User Dictionary Only
3) Turn on Dynamic Spelling (Edit -> Preferences -> Spelling -> check the Dynamic Spelling box)
4) Go to your layout file that you want to check and ensure that all text is set to Arabic language, if it's not already:
a) Open a Find/Change dialog, go to the GREP tab
b) your "Find what" query is
.+
which means "find everything"
c) leave "Change to" blank
d) in the Change Formatting area, go to Advanced Character Formats and specify Arabic
e) whack that Change All button
Now, if that is all set up correctly, then any divergence from the lines as they appear in your custom dictionary get marked as spelling errors. I have a fatha on the clipboard and am simply pasting it into random words, here:
AdChoices
