CustomizeGoogle - Ver. 0.75, Updated: 20/10/08 16:57 Options

[CustomizeGoogle]

Creator: CustomizeGoogle
Ext. Version: 0.75

Extension is compatible to:
( 1.0 - 3.1.*) ( 0.4 - 1.2.*) ( 1.0 - 2.0.*)
Included locales: ar-SA,be-BY,bg-BG,ca-AD,cs-CZ,da-DK,de-DE,el-GR,en-GB,en-US,es-AR,es-CL,es-ES,eu-ES,fa-IR,fi-FI,fr-FR,fy-NL,he-IL,hr-HR,hu-HU,hy-AM,id-ID,it-IT,ja-JP,ko-KR,lt-LT,nb-NO,nl-BE,nl-NL,pl-PL,pt-BR,pt-PT,ro-RO,ru-RU,sk-SK,sq-AL,sr-YU,sv-SE,th-TH,tr-TR,uk-UA,zh-CN,zh-TW
Description: Enhance Google search results and remove ads and spam

 View on WTS -- Download the extension

This post has been edited by CustomizeGoogle: Oct 20 2008, 15:57

[Goofy]

We are glad to see you here with this interesting extension. I wonder if there still exists languages not available for it yet
Maybe some locales needing to be updated ?

[CustomizeGoogle]

Thanks!

At least I can think of two more languages: danish and norwegian

 
We are glad to see you here with this interesting extension. I wonder if  there still exists languages not available for it yet 
Maybe some locales needing to be updated ?
[right][snapback]1648[/snapback][/right]

[xavivars]

I sent you the update for Catalan locale.

Did you get it?

[CustomizeGoogle]

I'm looking for translators for

# Afrikaans, af-ZA
# Asturian, ast-ES
# Greek, el-GR
# Irish, ga-IE
# Korean, ko-KR
# Lithuanian, lt-LT
# Macedonian, mk-MK
# Punjabi, pa-PK
# Romanian, ro-RO
# Slovenian, sl-SI
# Welsh, cy-GB

Are you a translator that translates to another language than the above? Please check out the right column at http://www.customizegoogle.com to see if it's already translated. If not, contact me!

This post has been edited by CustomizeGoogle: May 12 2006, 09:24

[Goofy]

Some of them may be picked and PM'd/mailed here on the translator's list :
http://www.babelzilla.org/forum/index.php?showtopic=233

[Akilles]

Some of them may be picked and PM'd/mailed here on the translator's list :
http://www.babelzilla.org/forum/index.php?showtopic=233
[right][snapback]6027[/snapback][/right]

That list says that all fr-FR translators are also fi-FI translators...

[Goofy]

probably wrong copy-paste manoeuvre when updating translor's list;
Sorry for that. Could you help us rebuild the fi-FI list ? Thanks.
[edit] MMmh it seems your are the only one up to now, am I right ?

[Akilles]

[edit] MMmh it seems your are the only one up to now, am I right ?
[right][snapback]6030[/snapback][/right]

Yeah, I'm the only one for now.

[funTomas]

 
We are glad to see you here with this interesting extension. I wonder if  there still exists languages not available for it yet 
Maybe some locales needing to be updated ?
[right][snapback]1648[/snapback][/right]

Goofy, could you please help CustomizeGoogle and check out what's missing in this extension's records? I still can't see the list of locales at the WTS detail of extension and register as an official translator and eventually check my locale's translation. Thanks a lot!

[Goofy]

You are right, I cannot see any clue of the submitted xpi (!)
Please CustomizeGoogle, would you mind submitting again on the wts
it seems your previous submission is not registered for whatever reason.
-- Sorry for annoying

Submission page is here :
http://www.babelzilla.org/index.php?option...lude&Itemid=100

[CustomizeGoogle]

<_< You are right, I cannot see any clue of the submitted xpi (!)
Please CustomizeGoogle, would you mind submitting again on the wts
it seems your previous submission is not registered for whatever reason.
-- Sorry for annoying

Result:

CODE

Uploading customizegoogle-0.39.xpi OK
Extracting customizegoogle-0.39.xpi OK
Parsing install.rdf OK
Updatecheck  Previous version found
Backup of previous version OK
Scanning for existing locales OK
Extracting .jar FAILED
Adding to WTS OK
Adding locale files to WTS OK
Updating support topic OK
Sending notification mails OK

[CustomizeGoogle]

CustomizeGoogle 0.39 (all locales) can be found here:

http://www.customizegoogle.com/customizegoogle-0.39.xpi

[Goofy]

hello
Sorry for long pondering on the submission issue, now we have bad & good news.

Fenian noticed that the special structure of your extension could not be taken into account by the WTS as it runs currently.

For explanation how the WTS handles extensions:
Extracting the xpi
Read install.rdf
Extracting the .jar (inside the chrome folder)

For customizgoogle this means: Creating a .jar and adding customizegoogle to the locale path, so that we have 'customizegoogle/locales/en-US'

The absence of .jar file inside the chrome folder seems to be the problem, and the (unzipped) folder named "customizegoogle" creates a different path as expected.

(- if I happen to be wrong, please send a PM to Fenian for more details)

So we are very sorry but we cannot change the current process of the WTS for your extension only, as you undertand, because it would not work with all the other extensions
The easiest way is for you to change the structure as indicated above, but of course it is up to you to decide.

------

[incidently I am very curious about the special urls.rdf files of each locale. Would you mind explaining what is their function ? mmmh remember I am no codehacker, please stay basic]

[CustomizeGoogle]

For customizgoogle this means: Creating a .jar and adding customizegoogle to the locale path, so that we have 'customizegoogle/locales/en-US'

The absence of .jar file inside the chrome folder seems to be the problem, and the (unzipped) folder named "customizegoogle" creates a different path as expected.

I've followed your instructions and have created a new CustomizeGoogle.xpi file which I have uploaded to Babelzilla. It's not publicly available yet. In the process I've also looked at the BetterSearch extension, which seems to work fine with the WTS system.

In the new .xpi file there is a .jar file instead of a folder. Also, the folder containing the locales is still called 'locale' and not 'locales' as you suggested. BetterSearch is also using 'locale' so I guess that shouldn't be a problem.

Your system still doesn't find the locales. I don't get any errors at all when uploading it to the WTS. If there is anything else I can do, please tell me. But to me it seems as if there is something wrong in the WTS...

[incidently I am very curious about the special urls.rdf files of each locale. Would you mind explaining what is their function ? mmmh remember I am no codehacker, please stay basic]

You can read the details of RDF Advanced: here.

Basic: I'm using it to store the urls to different alternative search engines. If you're from germany you get alternative urls to yahoo.de. If you're from france you get yahoo.fr etc.

You can also check out the CustomizeGoogle flash introduction.

Maby the WTS can't handle rdf files? In that case, you can ignore them.

edit: It should be WTS, not WTF

[CustomizeGoogle]

Ok, now I've made another tiny update to see if it made any difference to WTS. But now I'm unable to upload. It seems as if babelzilla timeouts. I've attached the .xpi file to this message. Could someone please update it to the WTS?

Attached File(s)

 customizegoogle_0.40.xpi ( 131.26K ) Number of downloads: 62

 

[Goofy]

Some mystery going on (for me)

It is possible something goes wrong with the wts and this extension, I just don't know

I notice another unusual thing in the structure again :

xpi-->(unzip)-->chrome-->customizegoogle.jar--(unzip)--->customizegoogle-->content/locale/skin---

I think the red folder is an unecessary step in the package. I don't pretend it explains anything, I just let you know.

generally speaking, in extensions, you have :


xpi-->(unzip)-->chrome-->customizegoogle.jar--(unzip)-->content/locale/skin---
then :
content -->customizegoogle-->various files
locale --->customizegoogle--->various locale folders

(I suspect you know that perfectly better than me)

[CustomizeGoogle]

Some mystery going on (for me)

It is possible something goes wrong with the wts and this extension, I just don't know

I notice another unusual thing in the structure again :

xpi-->(unzip)-->chrome-->customizegoogle.jar--(unzip)--->customizegoogle-->content/locale/skin---

I think the red folder is an unecessary step in the package. I don't pretend it explains anything, I just let you know.

generally speaking, in extensions, you have :
xpi-->(unzip)-->chrome-->customizegoogle.jar--(unzip)-->content/locale/skin---
then :
content -->customizegoogle-->various files
locale --->customizegoogle--->various locale folders

(I suspect you know that perfectly better than me)
[right][snapback]6589[/snapback][/right]

Ok. I'm not an expert on this. But I've seen a lot of extensions, and some do this, and some do that. The reason I added the 'customizegoogle' folder was because you said:

....so that we have 'customizegoogle/locales/en-US'....

I'll have another look at it.

[Goofy]

Please wait a moment before getting infuriated by my previous post.
I have just been testing the submission of your xpi on our sandbox test site... after FF crashes I can tell you that apparently all the locales are ok on the wts (sandbox side only, remember) but I received a massive enormous list of alert messages that I send immediately to Fenian for analysis
I just can guess from the code that it quite possible the numerous addresses of the urls.rdf file may cause uncomfortable submission.

Stay tuned

[CustomizeGoogle]

Ok. But FYI I've created a new .xpi file with all the folders in the right place (yes - I'm pretty sure that's everything is like WTS expects it).

So, If you want to test to upload the new .xpi file, I've attached it to this message.

Attached File(s)

 customizegoogle_0.40.xpi ( 131.33K ) Number of downloads: 58