Recommended Addon

[Goofy]

This new topic is dedicated to the work on Davide Ficano's Externalize extension. This very good tool was originally requested by me (see on this topic ) and I tested it successfully since May '06 on more than 45 extensions which were lacking a locale structure, a good number of them were submitted on BZ by their devs afterwards (see this topic of the moderators corner)
I also began a babelwiki page which is uncomplete and needing screenshots among others.



Good news are coming. Dafi has now some time to spare on this extension. Just to remember, I put here some kind of wishlist by order of priority (imho) :


[color=#FF0000]* trim the length of the created entities to a customized number of characters. In the current version there is manual work to limit the length to something reasonable. So the entitizing process itself is very quick and spares much time, but you have to check every file afterwards for empty strings and too long entity names.
* add the extension name (or first chars of it) at the beginning of entity names (as it is common use for most of manually created entities)
* detect empty strings from the xul files and avoid creating empty useless entities
* make the .txt files editable and customizable throughout the extension interface
* fix a kind of mess that may happen when creating the doctype line in case there already is one (a "public" one, referring to FF chrome itself)
* add an extra dialog popping when a file is processed, telling "Strings from this file are now successfully entitized, do you want to process another file ? (Y/N)" . When there are numerous files to "externalize", user has to restart the main dialog for each file, it would be quicker to leave the main dialog (file selector) open as long as there are files to process

[Goofy]

dear Davide
Thanks for the new features! I used Externalize to localize Platypus, an extension with many xul and many js files, and it was working fine.
* Accurate report for the js string count
* Good detection of duplicate strings (listed like e.g "Platypus Help on lines 223, 257, 670")
* no problem to change the variable names

I suggest it is satisfactory and should be uploaded on dafzilla

--------about comments

If we have this kind of codelines :

CODE

        //alert(itemFrames.length);
        //alert(itemiFrames.length);
        var frame, iframe;
        if (itemFrames.length > 0)
        {
            for (var i = 0; i< itemFrames.length; i++)
            {
                frame = itemFrames[i].contentDocument;
                this.CheckFrames(frame, id); // recursion for frames
            }
        }
        if (itemiFrames.length > 0)
        {
            for (var i = 0; i < itemiFrames.length; i++)
            {
                iframe = itemiFrames[i].contentDocument;
                this.CheckFrames(iframe, id); // recursion for iframes
            }
        }
    }
    this.onToolsMenu=function()    //open setting dialog!
    {
        var win=window.openDialog("chrome://batchdownload/content/config.xul",
                      "Batchdownload", "chrome,centerscreen",null);
        win.focus();

I suppose it will not be difficult to declare :
if // is detected then skip this line and go to the next one
but then a line with an address including double slash will be skipped too with possible string on the same line being ignored... Unless some declaration tells :
- ignore double slash inside " " quotation marks.

...but I am sure you have already thought of all that before me and much more accurately.

[dafi]

* Accurate report for the js string count
* Good detection of duplicate strings (listed like e.g "Platypus Help on lines 223, 257, 670")
* no problem to change the variable names

I suggest it is satisfactory and should be uploaded on dafzilla

Very good news
Ok I upload on dafizilla ASAP.

If we have this kind of codelines :

[CUT]

I suppose it will not be difficult to declare :
if // is detected then skip this line and go to the next one
but then a line with an address including double slash will be skipped too with possible string on the same line being ignored... Unless some declaration tells :
- ignore double slash inside " " quotation marks.

...but I am sure you have already thought of all that before me and much more accurately.

Detect comments ins't difficult but there are two types of comment:
1. inline comment starting with //
2. multiple line comment starting with /* and ending with */

Detecting inline comment is easy, detecting multiple line is a bit more complicated due to my extraction strings algorithm.
I need to change algorithm and this is a bit invaside.
As you know I'm working to fix this problem that fortunately is affordable