User talk:Atelaes/TargetedTranslations.js

Suggestion
Perhaps change for(     var a = 0;      NavFrame = document.getElementsByTagName('div')[a];      a++      ) { if (NavFrame.className == 'NavFrame') { to var notchecktrans = 1; for(     var a = 0;      NavFrame = document.getElementsByTagName('div')[a];      a++      ) { notchecktrans = 1; if (NavFrame.classname == 'checktrans') {notchecktrans=0);     if (NavFrame.className == 'NavFrame') { and                     else if (NavTargetTrans.innerHTML) {                        NavHead.appendChild(NavTargetTrans);                        }                     else {                        NavHead.appendChild(newNode('span', NavNoTarget)); to                     else if (NavTargetTrans.innerHTML) {                        NavHead.appendChild(NavTargetTrans);                        }                     else if (notchecktrans) {                        NavHead.appendChild(newNode('span', NavNoTarget)); &#x200b;—msh210℠ 16:32, 9 June 2010 (UTC)


 * Sorry I didn't see this until now, I swear I have this page on my watchlist. Anywho, it's irrelevant now, as the no translation message has been removed.  However, with the possibility of multiple languages I've considered adding it back, as an optional thing.  If I do, I'll definitely consider this code.  Oh, and I added a header.  Thanks.  -Atelaes λάλει ἐμοί 23:56, 23 June 2010 (UTC)

Possible change
(I'm pretty sure Atelaes isn't going to get this for a while, but I'm leaving this note anyway.) Perhaps a different customization process might be beneficial? --Yair rand (talk) 05:13, 6 August 2010 (UTC)