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]

Thanks Davide, I will try tonight.

Done: it works fine with your workaround. Thanks!

[dafi]

Done: it works fine with your workaround. Thanks!

Honestly I know this is only a workaround not a solution.
It is the quickest way to continue to use Externalize without waiting for a new build.
Maybe a solution should allow to choose the technique for discarding values per tag.
For example

CODE

  Tag/Attribute         Discard value RegExpr
     accesskey               None
     label                  RE1, RE2

Imagine a UI to obtain a similar result.
Adding an UI to handle files is a priority and I'll add it ASAP (but not before December )

Stay tuned

[Goofy]

Maybe a solution should allow to choose the technique for discarding values per tag.
For example

CODE

  Tag/Attribute         Discard value RegExpr
     accesskey               None
     label                  RE1, RE2

Imagine a UI to obtain a similar result.
Adding an UI to handle files is a priority and I'll add it ASAP (but not before December )

Stay tuned

I am impressed and not sure to understand how the per-tag regexp* will work , but I am ready for Goofytesting even if I must wait for Santa Claus

*For one thing I don't know about regexp syntax (I have read tutorials but I have no mathematician brain- well I suspect I have no brain at all to tell the truth) but what makes things more complicated is that every file may need a specific choice, and also in the same file sometimes a string must be externalized or not.

For example, it often happens to have in the same file
value="Davide is Great" (-->must be translated in every possible language)
and
value="Codestuff" (--> must be left as it is to make the extension run smoothly)

So the workaround here should be to allow user to select step by step what must be externalized and what mustn't be