1 Correct answer
~ Trevor ~ wrote:
But I found the REAL bug "
for (c=0;c<langs.length;c++){"should become"
for (c=0;c<langs.length-1;c++){"Quite a silly mistake
The script works really quite nicely now
Oh dear, oh dear, oh dear! 
Now I feel really silly, the "real" bug was not a bug and
"for (c=0;c<langs.length;c++){" was correct.
The -1 took off English: United States (don't know what's the difference between that and English: USA, as a Brit I never looked into it.)
the -1 did make a difference, my computer was feel
...
17
Replies
The mindsteam version is a lot more proffesional (I have it) but this also makes your copy nice and pretty. 
myDoc=app.documents[0];
langs=myDoc.languages;
con=[];
app.changeGrepPreferences = app.findGrepPreferences = null;
for (c=0;c<langs.length;c++){
app.findGrepPreferences.appliedLanguage=langs
; finds=new Array;
finds=myDoc.findGrep();
if (finds.length>0){
r=Math.floor((Math.random()*255));
g=Math.floor((Math.random()*255));
b=Math.floor((Math.random()*255));
con
= (app.activeDocument.conditions.item(langs .name).isValid) ? app.activeDocument.conditions.item(langs
.name) : app.activeDocument.conditions.add
({name: langs
.name, indicatorColor: [r,g,b], indicatorMethod: ConditionIndicatorMethod.USE_HIGHLIGHT}); app.changeGrepPreferences.appliedConditions = [con
]; finds=myDoc.changeGrep();
}
}
app.changeGrepPreferences = app.findGrepPreferences = null;
One can see that the : after the UK and French are Hebrew, That would be very hard to spot without this type of script 
After testing on a longer document I see the script is a bit on the slow side Oh well. 
I thought it might be nice to assign a constant color scheme to the language instead of a random one so if anybodies interested change the lines after if (finds.length>0){ to this
if (finds.length>0){
cc=0
for (d=0;d<langs
.name.length;d++) { cc+=langs
.name.charCodeAt(d)*235; }
r=cc % 255;
g=(5*(13*cc-7*r)) % 255;
b=(8*(9*cc-5*r-3*g) )% 255;
Message was edited by: ~ Trevor ~
Hi Peter,
I'm surprised by your answer, can't see why that should make a difference.
On testing, it does seem to make a bit of a difference but it's hard to tell.
But I found the REAL bug "for (c=0;c<langs.length;c++){" should become
"for (c=0;c<langs.length-1;c++){"
Quite a silly mistake
The script works really quite nicely now
(If one doesn't like the color of your favorite languages then experiment with the r g b formula)
Regards
Trevor
myDoc=app.documents[0];
langs=myDoc.languages.everyItem().getElements();
con=[];
for (c=0;c<langs.length-1;c++){
app.changeGrepPreferences = app.findGrepPreferences = null;
app.findGrepPreferences.appliedLanguage=langs
finds=new Array;
finds=myDoc.findGrep();
if (finds.length>0){
cc=0
for (d=0;d<langs
cc+=langs
}
r=cc % 255;
g=(5*(13*cc-7*r)) % 255;
b=(8*(9*cc-5*r-3*g) )% 255;
con
? app.activeDocument.conditions.item(langs
: app.activeDocument.conditions.add
({name: langs
app.changeGrepPreferences.appliedConditions = [con
finds=myDoc.changeGrep();
}
}
app.changeGrepPreferences = app.findGrepPreferences = null;
~ Trevor ~ wrote:
But I found the REAL bug "
for (c=0;c<langs.length;c++){"should become"
for (c=0;c<langs.length-1;c++){"Quite a silly mistake
The script works really quite nicely now
Oh dear, oh dear, oh dear! 
Now I feel really silly, the "real" bug was not a bug and
"for (c=0;c<langs.length;c++){" was correct.
The -1 took off English: United States (don't know what's the difference between that and English: USA, as a Brit I never looked into it.)
the -1 did make a difference, my computer was feeling moody and getting caught up with the splwow64.exe thread.
Anyway It seems to have cheered up and now come to terms with the American independence.
AdChoices