58 replies to this topic

[Goofy]

MMh, I tested and found the Firefox tab is ok on my system (small screenshot attached)
Has it anything to do with Matrix' choice of theme ? (I use the basic default theme)
Feel free to skip this suggestion if irrelevant . I just don't know

another suggestion : if the name of the "product" does not appear, it can be that MatrixIsAllOver tested with Deer Park or some kind of nightly build ? (again, just supposin')

Attached Files

•  editorzillaFFoption.png   2.08KB   21 downloads

[Luana]

Matrix, What's your name? I want to put it into the credits page
[right][snapback]2063[/snapback][/right]

Please, check your P.M.

Has it anything to do with Matrix' choice of theme ? (I use the basic default theme)

I don't think, 'cause I also use the Firefox default theme when I test the extensions
I use a different Windows *theme file, but I think that this is and it must be irrelevant!

another suggestion : if the name of the "product" does not appear, it can be that MatrixIsAllOver tested with Deer Park or some kind of nightly build ? (again, just supposin')
[right][snapback]2067[/snapback][/right]

Probably this is the true reason, 'cause I always test the extensions with at least three Firefox build different
The image is just that one of EditorZilla installed on Firefox D.P. 1.5 beta1!

[Goofy]

1 relevant suggestion out of 2, not bad for a goofy guy !

[MorZilla]

OK, the bug has been fixed.
Now, it works with Mozilla Suite!
Locales don't have to be updated.
Can anybody move this topic to the Multiapplication section?

Ptit Lutin : Done

[victory]

Morzilla:
one question: in idioma.js, 'If the file does not have a document, ...'
s/document/title/; isn't it?

[MorZilla]

Yes, the correct word was "Title". I also wrote "Change this settings"
In this week I will submit the new version of the extension, with a new name: Ñandú. Victory, Wait until I submit the file, and keep working.

[Goofy]

You mean EditorZilla becomes Nandu ?

[MorZilla]

Yes, you're right. I wanted to submit the extension on MozDev, but I could not register names with the "Zilla" subfix.

[Goofy]

StupidZilla they are ! What the f*** do they want to protect a suffix for ?!

I am surprised they did not forbid/sue BabelZilla ... Perhaps we should rename in BabelSquirrel or Babelion or BabelZoo...

[MorZilla]

Don't worry, Goofy! Anyway, I think that Ñandú is a good name, an Argentine name for the first Argentine extension!
I will upload the file on thursday.

The suffix "Zilla" can'tbe used only on MozDev projects, BabelZilla will always be BabelZilla!

[MorZilla]

Ñandú 0.5.5 is ready for translations:
(Attachment removed, check the posts below)

[Goofy]

hello Morzilla
glad to see you again with your born-again extension !
- the admin team is currently testing the new wts (online translation) with all the extensions we have got here, and we took the chance on the fly to see how it works when we submit Nandu. unfortunately, due to some limitations of the wts in terms of parsing .js files, it does not work properly with Nandu, and not more with EditorZilla.

- But of course, there is no objection to add locales to Nandu (excuse me for the accents, I don't know where to press on my keyboard) just here as usual !
Maybe you can manage in a future version to transfer your .js strings in some properties files ? I know it is quite a boring work but we think it would be better.

Of course there is no hurry...we are too delighted to have a young coder with such a beautiful extension !

[Andrea]

- But of course, there is no objection to add locales to Nandu (excuse me for the accents, I don't know where to press on my keyboard)

ALT+165 = Ñ
ALT+163 = ú

[MorZilla]

I am thinking to transform the .js files into DTD files, so the translators who uses text editor don't have troubles with UTF-8. (the translator can simply write "á", and not "\u00E1").

your born-again extension !

Make your own extension, and we can talk about it!

Don't worry, write "Ñandú" only if you have the "Ñ" key on your keyboard.

[Goofy]

Make your own extension

Are you joking ? Do you want me to destroy the whole BabelZilla board by submitting silly mistakes of my own ? (a full stock is currently available)

I am thinking to transform the .js files into DTD files

Good. If the strings are related to .js files in the content folder, it is easier to have a properties file (?), or your are obliged to change more things in the content and have .xul files instead of .js (I think)
... something tells me I becomes unclear here

according to me (thus far from certain) you have two options :
* localize strings from the .js files of the content with a stringbundle in one overlay file, then strings in a properties file of each locale
OR
* transfer strings to some .xul file in the content, then have them localized the usual way with entities.

(Please feel free to tell me if I am irrelevant, I like learning)

[MorZilla]

I made a big mistake
I read it wrong, "boring" where you wrote "born"...

I can tranform the entities into JavaScript properties (in the Content).
For example:
Into the DTD file:

CODE

<!ENTITY hello "Hello, folks!">

Into the JS/XUL file:

CODE

<script>
var localeHello = "&hello;";
</script>

In this way, localeHello will have the value "Hello, folks!".
I just neeed to update a JS file, nothing else.

I tested it with another extension.

[Goofy]

I raed it wnrog "bgrnio" werhe you wotre "norb"

(your message scrambled with Confuscator extension, just to add to the general confusion )

[Goofy]

I just received a harsh comment from Goofy (the so-called forum coordinator) telling me I am dangerously

[Luana]

Hi MorZilla,
I noticed a "free accesskey" in the editorTexto.xul file, line 86

CODE

<menuitem label="&volverm;" disabled="true" id="volver2" accesskey="V"/>

Just for me, for a complete test, I created the volvermAK entity...
Perhaps could it be better if you update the attached xpi file?

[MorZilla]

I have work for tomorrow...
I will submit the file again