Recommended Addon

[Captain Caveman]

Creator: Martijn Kooij
Ext. Version: 1.3.2

Extension is compatible to:
Firefox: 1.0 - 3.0a1
Mozilla Suite: 1.7 - 1.8
Included locales: be-BY bg-BG ca-AD de-DE en-US es-ES fi-FI fr-FR it-IT ja-JP ko-KR mk-MK nb-NO nl-NL pl-PL pt-BR pt-PT ru-RU tr-TR zh-TW
Description: Open the host of a link.

 View on WTS -- Download the extension

This post has been edited by Captain Caveman: Jul 25 2007, 18:14

[Goofy]

I go and make the french locale if nobody objects

[Luana]

Pedro?
Do you want to co-localize this extension with me?
Or, do you prefere to localize it alone?

[Pedro]

Let's go M.I.A.O!!

@Captain Caveman
I have seen that the options window isn't localizated

[Goofy]

dear Pedro, I just localized the two missing strings of the about window, just have a look at the edit message above

The french locale is here

Attached File(s)

 openhost_locale_fr_FR.zip ( 1.13K ) Number of downloads: 28

 

[Luana]

We will wait for with patience!

ADDED
Ooops, the localization is really short!
So, I think Pedro may do it alone

[Captain Caveman]

Hi guys! Newbie here
You know I wanted to keep this extension as small as possible... So, I found another way to add the description you see in the Tools/extensions menu which saves quite a lot of space, cause it does not need a properties file.

How does this work now? Should I upload the new file?

ps1. Before today I did not even know you could also translate the description...

[Ptit Lutin]

Hi guys! Newbie here
You know I wanted to keep this extension as small as possible... So, I found another way to add the description you see in the Tools/extensions menu which saves quite a lot of space, cause it does not need a properties file.

How does this work now? Should I upload the new file?

ps. Before today I did not even know you could also translate the description...
[right][snapback]293[/snapback][/right]

Hi

A better solution than option 2 here ?
http://babelzilla.org/forum/index.php?showtopic=13

Could you explain that please

[Captain Caveman]

(I did not say better, just smaller, and maybe even easier for the translators...)
Option 2 requires 1 extra prefs.js file, and n extra ext.properties files.

My option uses the translation from the normal dtd file, and is added (only) on first run of the extension, dynamicly from code.
So you need no extra files, no extra places to translate something, and only 2 lines of code. The only disadvantage is, that it wont change if you change your locale... (Even that can me aranged, but it would require +/- 4 exrta lines of code...)

[Ptit Lutin]

(I did not say better, just smaller, and maybe even easier for the translators...)
Option 2  requires 1 extra prefs.js file, and n extra ext.properties files.

Option 2 doesn't require an extra .properties files

My option uses the translation from the normal dtd file, and is added (only) on first run of the extension, dynamicly from code.
So you need no extra files, no extra places to translate something, and only 2 lines of code. The only disadvantage is, that it wont change if you change your locale... (Even that can me aranged, but it would require +/- 4 exrta lines of code...)
[right][snapback]295[/snapback][/right]

not very good
Could you give us the code please ?

[Goofy]

Very interesting, and far beyond my capacities in terms of code understanding
But...
When I tried your last proposition, the initial description (in the extension manager window) remained in english, only the tooltip was set to the french text...
And if you speak of these lines (?)

CODE

document.getElementById("contentAreaContextMenu").addEventListener("popupshowing",Popup,true)
var oPref = Components.classes["@mozilla.org/preferences-service;1"].getService(Components.interfaces.nsIPrefService).getBranch("extensions.");
if (!oPref.prefHasUserValue("{32D83016-0657-4cd3-B7D2-0B4D12CEC60E}.description")) oPref.setCharPref("{32D83016-0657-4cd3-B7D2-0B4D12CEC60E}.description", document.getElementById("oh-context").getAttribute('tooltiptext'));

they are very likely to concern the tooltip text and not the initial description.

(Maybe I did not understand the whole thing, in that case please forgive me and forget about my nonsense )

[Captain Caveman]

1. it does require a properties file doesn't it? If so, then for MY extension, that would be an extra properties file, cause at the moment I don't use one.
2a. I don't think that a basic user will often (or at all) change his/her locale.
2b. It can be done so, but that would require some 4 lines of code extra
2c. The code is just making use of available translations from dtd on an item:
(Purely based on making it as small as possible... No beauty awards...)

CODE

JS:
var oPref =
Components.classes["@mozilla.org/preferences-service;1"].getService(Components.interfaces.nsIPrefService).getBranch("extensions.");
if (!oPref.prefHasUserValue("{32D83016-0657-4cd3-B7D2-0B4D12CEC60E}.description")) oPref.setCharPref("{32D83016-0657-4cd3-B7D2-0B4D12CEC60E}.description", document.getElementById("oh-context").getAttribute('tooltiptext'));

XUL:
<menu label="&openhost.context.main;" id="oh-context" tooltiptext="&openhost.description;">

[xavivars]

IMHO, the size of a properties file with a description won't be bigger than 100bytes, and once compressed, it size will be more or less a half. So, 50 bytes per locale doesn't increase the size of the extension too much....

[Goofy]

Sorry captain caveman,I tested again with a clean new profile in fr without changing locale pref, and it still does not work :
- everything else is in french, and the tooltip of course
- the initial description remains in english

... But I understand perfectly the challenge (half for fun ?) of the shortest possible code. I think there is much to remove from the content/contents.rdf files that include useless stuff (?) since the about.xul file gives the informations.

maybe this could save some bytes :
instead of having one "openhost" folder per locale, just have one which includes all the locales, as in many extensions I know (not sure it is byte saving, just suggesting)

[Captain Caveman]

Ok, dinner helps a lot...

I am quite sure it will work with this version.
The description will now change (after Ff restart/open new window) when you change your locale, and it saved me 83 characters doing that
I also took up on the idea of removing the locale's openhost subfolder, which will save 9 characters per locale...

Goofy, it might be that I screwed up you fr-FR translation by opening it in a dutch (non-unicode) text editor (never was really good in understanding character sets...). Could you check it?

I will update the main download file in a minute...

Enjoy translating these 6 lines!

[Pedro]

Ok!! Now I can post the definitive italian locale!!

(Removed old zip file)

[Goofy]

(apart from saving bytes, what I do like as a kind of funny challenge - what with having a kind of bookmarklet ? )

Don't be afraid translators, here are the ONLY strings to translate :

CODE

<!ENTITY openhost.context.main "Open Link Host">
<!ENTITY openhost.description "Open the host of a link.">
<!ENTITY openhost.createdby  "Created by:">
<!ENTITY openhost.context.cuwi "In Current Window">
<!ENTITY openhost.context.newi "In New Window">
<!ENTITY openhost.context.neta "In New Tab">

Even if the core code is subject to various weird adjustments, I think this set of strings will remain, so you can even add your direct translation down here !

[victory]

ja_JP locale

[xavivars]

Here you hava Catalan locale (ca-AD)

Attached File(s)

 openhost.locale.ca_AD.zip ( 775bytes ) Number of downloads: 28

 

[Ptit Lutin]

description localization still doesn't work.