Help - Search - Members - Calendar
Full Version: Classic Compact Options - Ver. 4.0.10b1
BabelZilla Board > Extensions > Firefox
Pages: 1, 2
KLB
Maintainer: KLB
Creator: Ken Barbalace EnvironmentalChemistry.com

Ext. Version: 4.0.10b1
Release date: 2012-02-22
Description: This adds the "Classic Compact Options" menu item to the "tools" menu, which allows one to change the appearance of the theme Classic Compact. Options include: using keyhole arrows; turning off gradient backgrounds; turning off rounded borders; and turning on chiseled toolbar dividers. Requires the theme Classic Compact v4.0.10 or higher.
Extension is compatible to: ( 4.0 - 13.0a1)

Included locales: de en-US es fr ja-JP nl pl pt-BR ru sq-AL sr sv-SE tr uk-UA zh-CN zh-TW

View on WTS -- Download the extension
markh
Welcome! welcomeani.gif

Just a bit of information for you: in case you have some queries about the WTS, you can find short and simple Questions&Answers about it here!

In case you're looking for a specific translator, please see the list of available translators on BabelZilla.
When you select the desired one, you can send him/her a P.M. or an e-mail (if and when public).

You may also insert a new Topic in the Help Section, in order to ask for specific translations, to write a general request about missing translations, etc.

The translators for Russian and Polish are currently unknown. You are welcome to invite them here and continue their work!
KLB
Thank you for the welcome. I was informed of this site this morning over on the MozillaZine.org forums where I host a support thread for my theme and extension.

The Russian translation was done by my wife and I had to pull tooth and nails to get her to do it for my theme and extension, so I doubt I can get her to help with any others. :-(

I'll send an invite to my Polish translator who came to me as a user of my theme.

I know that the majority of add-ons are English centric but that many Firefox users don't speak English. I'm sure non-English speaking users would really appreciate having as many add-on options as possible in their native language. This is why I'm trying to get my add-ons translated.
markh
QUOTE (KLB @ May 13 2008, 14:33) *
The Russian translation was done by my wife and I had to pull tooth and nails to get her to do it for my theme and extension, so I doubt I can get her to help with any others. :-(

I suggest you register as Russian translator then before someone 'hijacks' the translation wink.gif

QUOTE (KLB @ May 13 2008, 14:33) *
I know that the majority of add-ons are English centric but that many Firefox users don't speak English. I'm sure non-English speaking users would really appreciate having as many add-on options as possible in their native language. This is why I'm trying to get my add-ons translated.

That's exactly the reason for our existence!
KLB
QUOTE (markh @ May 13 2008, 14:29) *
I suggest you register as Russian translator then before someone 'hijacks' the translation wink.gif

I've done as you suggested. There may be some room for refinement of the Russian translation as some phrases are too long for the available space.


QUOTE (markh @ May 13 2008, 14:29) *
That's exactly the reason for our existence!

This site was a great idea.

I should note that the about.dtd is not actually used, it was just left in the extension for possible future use.
KLB
I have converted the AMO descriptions file I had referenced earlier into a DTD and uploaded it to this project.
teo
Hi Ken,
I like play with XUL and I made some, IMHO, improvements in your extension:
- new options window layout
- corrected about window layout
- link from about window is opened in the new tab instead new window
- changed in the about window OK button to Close
- corrected install.rdf file for display about window
- removed old method localize extension metadata (this is good solution for extensions which working with Gecko 1.8 and 1.9, but for extensions working with 1.9 only, better way is new method). For getting translation of description you can include .dtd or properties (better is .dtd) file when you upload extension to BabelZilla.

My version is in the attached file. I'm waiting for your opinion.

Polish locale released.
KLB
Teo,

I meant to mentioned this, but the about files are not being used. They are only in the extension for future reference in case I decide to add a custom about window.

While I may make refinements to the localization, at this point in time I do not want to be making changes to the layout of the options panel or make changes to the extension itself. I only want to open up the extension to users who do not read English.

I am a little concerned about the fact that so many changes were made to the original Polish translation and that some of the changes conflict with Polish terminology used in other areas of Firefox. For instance Firefox uses "Opcje" for "Options" and you changed the original translation of "Classic Compact Options" from "Opcje Classic Compact" to "Ustawienia motywu Classic Compact". My wife is a professional translator (Russian/English) and I do realize that there can be different ways to translate a phrase, but I need some way to know who is the most correct with Polish translation and I want to make sure that terminology remains consistent with what is used in Firefox.
teo
QUOTE (KLB @ May 17 2008, 00:04) *
I meant to mentioned this, but the about files are not being used. They are only in the extension for future reference in case I decide to add a custom about window.

I saw about.xul and about.dtd files but not working, I made these working smile.gif

QUOTE (KLB @ May 17 2008, 00:04) *
While I may make refinements to the localization, at this point in time I do not want to be making changes to the layout of the options panel or make changes to the extension itself. I only want to open up the extension to users who do not read English.

You are developer and you decide about your extension. As I wrote - I like some play with XUL smile.gif

QUOTE (KLB @ May 17 2008, 00:04) *
I am a little concerned about the fact that so many changes were made to the original Polish translation and that some of the changes conflict with Polish terminology used in other areas of Firefox. For instance Firefox uses "Opcje" for "Options" and you changed the original translation of "Classic Compact Options" from "Opcje Classic Compact" to "Ustawienia motywu Classic Compact". My wife is a professional translator (Russian/English) and I do realize that there can be different ways to translate a phrase, but I need some way to know who is the most correct with Polish translation and I want to make sure that terminology remains consistent with what is used in Firefox.

Ken, I'm Polish Localization Team of Firefox - Aviary.pl member, and believe me, I know what I translate and which terminology we use for Polish version. I used the same scheme as your wife "Настройки Классической Компактной темы", but we don't translate extensions and themes name. If in Russian translation extension name will be not translated, will be looks like "Настройки Classic Compact темы". This is the same as in mine translation "Ustawienia motywu Classic Compact". Настройки = Ustawienia, темы = motywu. smile.gif IMHO you should use 'Settings' instead 'Options'. In this extension we change settings. Settings=Настройки=Ustawienia smile.gif BTW I know Russian language smile.gif In Russian language 'option' is "опцион, опция".
KLB
Teo,

You have settled some of my translating concerns. I was just concerned about differences I was seeing and needed to figure out who was right. In regards to "options" verses "settings" I would prefer to use "options" as this is what is used for the Firefox options panel. I'm really concerned that phrases in my extension uses terminology that is consistent with terminology used throughout Firefox menus, options panel, etc. If there has to be a choice between technical correctness verses consistency with terminology used in Firefox, I would prefer to favor consistency with Firefox terminology.

Why don't you translate the name of an extension? In this case, not translating the phrase "classic compact" basically makes the name of the extension and theme meaningless to non-English speakers. I'd really prefer to see the name of my theme and extension translated along with everything else as the names are descriptive. The idea that the name should convey is that the theme is a classic (e.g. klasyczne) theme that is very compact (e.g. Zwarte)

teo
QUOTE (KLB @ May 17 2008, 02:39) *
Why don't you translate the name of an extension? In this case, not translating the phrase "classic compact" basically makes the name of the extension and theme meaningless to non-English speakers. I'd really prefer to see the name of my theme and extension translated along with everything else as the names are descriptive. The idea that the name should convey is that the theme is a classic (e.g. klasyczne) theme that is very compact (e.g. Zwarte)

Why? This is simple. Try ask Google "Klasyczne zwarte" and after "Clasic Compact" smile.gif Aviary.pl agree - don't translate extensions and themes name. Now are many addons (about 7000) but translated to Polish only about 600. Users looking for addons, searching by English name. E.g my friend tell me about extension for 'słowa kluczowe' (keywords). I'm looking for 'słowa kluczowe' and what? Nothing - this extension isn't translated to Polish, but if I will be looking 'keywords', I will find them.
All informations about 'klasyczne, zwarte' are in the summary and long description on addon page.
OK, IMHO my translation is OK, but if you think that is wrong, I can cancel mine registration as translator.

KLB
It is not that I think your translation is wrong, it is that I don't know if it is right or wrong and I'm just trying to make sure I make the right decision. I do not fully understand what the review process is for translations here.

In regards to the name of add-ons what if the translated name comes first with the English name put in parentheses. For instance I could use "Klasyczne zwarte (Classic Compact)"? This would help people search for add-ons by their English name, but still read it in their native language.
teo
@Ken,
Aviary.pl is team which make translation of Firefox, Thunderbird, Flock, SeaMonkey, Sunbird, Lighting, Bugzilla, SUSE and occasionally extensions. We have our system review. I'm this team member. On BabelZilla some national teams make review on national forums.

First of all 'Classic Compact' should be translated to Polish "Klasyczne kompaktowe". Previous I intentionally used your translation. If I use your translation model, 'Classic Compact Options' should be translated "Opcje motywu Klasycznego kompaktowego (Classic Compact)". Take many place and awful in Polish. That's all from my hands.

One remarks about English version. You used in the options window lower case characters for options name, but for AMO upper case. This is intentionally?
KLB
QUOTE (teo @ May 17 2008, 03:34) *
@Ken,
Aviary.pl is team which make translation of Firefox, Thunderbird, Flock, SeaMonkey, Sunbird, Lighting, Bugzilla, SUSE and occasionally extensions. We have our system review. I'm this team member. On BabelZilla some national teams make review on national forums.


Thank you for this background, it does help settle many of my concerns.

QUOTE (teo @ May 17 2008, 03:34) *
First of all 'Classic Compact' should be translated to Polish "Klasyczne kompaktowe". Previous I intentionally used your translation. If I use your translation model, 'Classic Compact Options' should be translated "Opcje motywu Klasycznego kompaktowego (Classic Compact)". Take many place and awful in Polish. That's all from my hands.

I don't fully understand what you are saying here, but I think you meant to say that the Polish translation of the title would be too long and is a little confusing. The name "Classic Compact Options" is a confusing in English as well until one understands that "classic compact" refers to the name of the theme and thus is a proper noun, not a pair of adjectives, then it starts to make more sense.

Without context the name "Classic Compact" makes no sense in English. When put into context in the AMO themes section, however, the name "Classic Compact" becomes a very good description of what the theme is about. In relation to Firefox 3, the word "classic" indicates that the theme has classic/traditional toolbar button styling and the word "compact" indicates a theme that uses very little space.

The problem with translating the title "Classic Compact Options" is that it won't make any sense without a broader context. My wife had problems with this as well. She was okay translating "Classic Compact" as "Классической Компактной" but she couldn't grasp the idea that "Классической Компактной" was a proper noun in the context of the extension and that "Настройки" simply indicated that this was the options panel for "Классической Компактной". She insisted on adding the noun "темы" so that in English the name for the extension would be "Options for the theme Classic Compact". In English, "Options for the theme Classic Compact" does make more sense than "Classic Compact Options" but it is also too long just like "Opcje motywu Klasycznego kompaktowego" is too long.

If we don't try to make grammatical sense of the name and instead use it as a string of descriptive words and assume the user will understand the context of those words (as I am doing in English) then we can shorten the name to "Opcje Klasycznego Kompaktowego". On the "Tools" menu this description would make sense to users and it would make sense to users when used in the context of the theme "Klasycznego Kompaktowego". It would at least make more sense to someone who could not read English than "Opcje Classic Compact", which would have no meaning what so ever. Think of it this way, since I don't speak Polish if I came across an extension titled a theme titled "Klasycznego Kompaktowego" or an extension "Klasycznego Kompaktowego options" it would mean nothing to me. I wouldn't be able to pronounce their names. If, however, "Klasycznego Kompaktowego" was translated into English, it would be grammatically awkward, but I could understand the idea being conveyed if put in context.

From a marketing standpoint when looking at a page full of extensions or themes with English names, a theme or extension with a name that is localized to the language of the user reviewing the page will catch the attention of the user. Even if the name is a little awkward it might just stop the user long enough to take a closer look.

QUOTE (teo @ May 17 2008, 03:34) *
One remarks about English version. You used in the options window lower case characters for options name, but for AMO upper case. This is intentionally?

Yes this is intentional to make the description on the AMO page more readable as I had no formatting ability on AMO. It would have been better to use a real bullet list instead of asterisks and to bold the option names, but I could only use plain text so I made a fake bullet list and made each option name if full caps.
teo
@Ken,
My translation is as is. If you want use mine version - OK, if not, also OK. Please decide, If yes, I still will be this extension translator, if not - I unregister as translator. Sorry, but I prefere play with XUL instead discus about "Opcje Classic Compact' vs "Ustawienia motywu Classic Compact". In Polish we speaking "Dyskusja na temat wyższości świąt Bożego Narodzenia nad świętami Wielkiej Nocy"
KLB
Just a quick update for everyone.

First I have asked for aleksander.adamowski to take over as lead of the Polish translation as he was actually the original Polish translator before I brought my project here. I do appreciate Teo's efforts, but I think things will go smoother if I can work with someone I know better.

Also with the release of Firefox 3.0, I'm getting lots of downloads for Classic Compact and Classic Compact Options, along with requests for new features. Given how long it takes to get extension updates approved, I'd really like to try and roll out new feature additions at the same time I roll out new localizations. Any localization assistance would be appreciated. I have observed that there has been some reference to my theme on Chinese and Arabic blogs/websites so if there are any Chinese or Arabic translators who would be willing to help localize this project to their languages it would be appreciated. I would also appreciate any assistance in dealing with any left to right issues that may be cropping up with my theme for Arabic speakers.
KLB
I'm getting ready to release Classic Compact Options for Firefox 3.5 and will be rolling up any completed translations into it when I do.
KLB
Updated versions of Classic Compact Options and Classic Compact have been uploaded to addons.mozilla.org with the available translations. As new translations are completed I will upload new updates that contain the new localizations.

Thank you to everyone for your help.
KLB
Maintainer: KLB
Creator: Ken Barbalace EnvironmentalChemistry.com

Ext. Version: 1.2.1
Description: REQUIREMENTS (WARNING)
This extension requires the theme "Classic Compact" v3.0.7 or higher be installed FIRST, which can be downloaded at: https://addons.mozilla.org/en-US/firefox/addon/3699

AVAILABLE OPTIONS
* Toolbar Buttons: Classic Compact 3.0 buttons (default) or Classic Compact 2.0 (FF2).

* Toolbar Arrow Style: Classic arrows (default, FF2, MC) or the new keyhole arrows (FF3)

* Background Style: Gradient backgrounds (default, MC) or flat background (FF)

* Toolbar Dividers: No dividers (default, MC) or chiseled dividers (FF)

* Border Corner Styling: Rounded corners (default), square corners, round tabs only (FF), or square scrollbars only.

* Scrollbars: Classic Compact styling (default) or OS native (FF)

* OS System Colors: Light/gray backgrounds (default) or dark/black backgrounds. This option is users of really dark operating system colors. It changes the critical black/dark glyphs to white and light hues.

* Webpage Window Border: enabled (default), disabled (MC). This turns off/on a 2 pixel think "sunken" border around the webpage pane. With this option enabled the webpage pane looks the same as other Windows apps and other window panes in Firefox. With it disabled an extra 4 pixels of vertical space is saved.

* Merge Menubar into One Button: No (default), Yes (MC). This option will merge the menubar into a single menu button such that one could then use the "customize toolbar option in Firefox to drag navigation bar buttons to the space made available on the menubar to save more vertical space.

* Tab Clip Width: integer value. This sets the maximum width tabs are allowed to be.

* Tab minimum width: integer value. This sets the minimum width a tab is allowed to be. The smaller this number is, the more tabs that will be shown before Firefox starts scrolling tabs.

* Tab Close Buttons: On all tabs (default), on active tab only, hide entirely, End of tab bar

* Open searches in new tab: No (default), yes.

OPTION NOTES (IMPORTANT):
FF, FF2 & FF3 options are the closest appearance to the default Windows Firefox theme. MC are the most compact options.

The OS System Color option does not change the background/foreground colors used by Firefox, which are still controlled by the Operating System. That option only changes the glyphs so that they are compatible with dark colors (e.g. black to white). To have dark background colors, you need to change the colors used by your operating system (e.g. desktop properties in Windows).


SOME SUGGESTED SETTING COMBINATIONS
* Most Compact: settings marked with "MC"

* Closest Firefox 2.0 Look: Settings marked with either "FF" or "FF2"

* Closest Firefox 3.0 Look: Settings marked with either "FF" or "FF3"

* My current favorite: all default except "border corner styling" which is set to "square scrollbars only"

REQUIREMENTS
Classic Compact Options requires the theme Classic Compact v3.0.7 or higher be installed. Classic Compact can be downloaded at: https://addons.mozilla.org/en-US/firefox/addon/3699
Extension is compatible to: ( 3.0 - 3.5.*)

Included locales: de-DE en-US fr-FR ja-JP nl-NL pl-PL pt-BR ru-RU tr-TR uk-UA

View on WTS -- Download the extension
KLB
It looks like the original translation owners were lost in the update. Hopefully this gets fixed shortly. There is an extra file called AMO_descriptions.dtd which contains the strings used for the companion theme "Classic Compact" and for the addons.mozilla.org strings for this extension and theme pair.
Goofy
smile.gif French update is in progress, while testing I found the Options dialog should be resizeable to content, because we are generally more verbose in French (and some other languages as well) than in English

see screenshot
KLB
QUOTE (Goofy @ Jul 31 2009, 08:02) *
smile.gif French update is in progress, while testing I found the Options dialog should be resizeable to content, because we are generally more verbose in French (and some other languages as well) than in English

see screenshot


I've discovered the verbose issue when trying to update AMO with what had been provided. surprise.gif

Since the short descriptions on AMO are limited to 250 characters now. Some editorial decisions will have to be made. For instance the phrase about supporting black backgrounds can be dropped from the list of features.

I'll try to work on making a resizeable option panel. Otherwise, if there is a size issue with the option panel, I can increase the size of the option panel if necessary.

By the way Twitter must really be a pain for verbose languages. hmm.gif
Goofy
smile.gif should be something like
<dialog id="myDialog" title="My Dialog"
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
onload="window.sizeToContent();"


(I am not sure, just watching mdc tutos)
KLB
There seems to be a bug with using window.sizeToContent(); as it crops off everything outside of the tabs (e.g. the note below the tabs).
KLB
I was finally able to solve the option panel size issue and I believe that the issues with hidden text in some locales has been resolved.

Translators need not worry about text wrapping or hidden text on the options panel. I have locale switcher installed so I'll be able to test and tweek if a given locale has issues.

I'll upload an update to Babelzilla when it becomes material, but right now doing so would just cause hassles due to the bugs on Babelzilla in relation to updating add-ons.
Goofy
smile.gif As there was some confusion between the two versions, I deleted the previous one (1.2), all locales are zipped here below if they can help.
Goofy
smile.gif would you please show us a screenshot of what a "chiseled" border could be, I have some problems to find the French equivalent, none of the usual translation sources I consulted seems to fit. Thanks
KLB
Here is a screenshot with flat backgrounds and chiseled dividers between toolbars


Below are some other option combinations as explained in the displayed option panel:



At https://addons.mozilla.org/en-US/firefox/addon/6969 there is an image gallery of different ways Classic Compact Options can change the look of the theme Classic Compact.
Goofy
smile.gif wow thanks a lot, so chiseled is somewhat a thin white line added border mmh ?
KLB
QUOTE (Goofy @ Aug 1 2009, 08:36) *
smile.gif wow thanks a lot, so chiseled is somewhat a thin white line added border mmh ?


Chiseled borders have a single pixel dark line (top/left) next to a single pixel white line (bottom/right) this gives the appearance of a grove being "chiseled" out of the background. Prior to Windows XP (e.g. Win2000), Windows made heavy use of chiseled borders. An unstyled horizontal rule (HR) HTML tag also uses the chiseled effect.
Goofy
smile.gif French version set as released and correct but the amo long description is not tested, I added <pre> and </pre> but am not sure at all everything will fit the amo real fields.

I suggest the long description items, in the case of this extension, should be in a simple .txt (utf-8) file for better usability. My 2 eurocents.
KLB
I've just pushed updated versions of Classic Compact and Classic Compact Options to AMO with the updated localizations. Hopefully they will get approved in a reasonable amount of time. I will push out updates as is appropriate when more translations are released.
KLB
I wanted to post a quick road map for Classic Compact Options and its companion theme Classic Compact.

Classic Compact Options v1.2.2, which contains all currently completed translations was posted to AMO bac on Aug 4, 2009 and is still pending review by AMO editors. My understanding is that extensions are taking just over a month to get approved.

Classic Compact v 3.2.2, which also contains all currently completed translations and was also posted on Aug 4. It has been approved and is currently active. All completed translations for AMO strings have also been updated on the AMO pages for Classic Compact and Classic Compact Options.

It is my hope to push out an update to Classic Compact by the end of Sept. I would push out any newly completed translations at that time.

Thank you for the efforts everyone has put into translating Classic Compact Options, Classic Compact & related AMO strings.
teo
I'm sending you corrected and up to date Polish versions of AMO strings for both addons. If you have any question why these strings have to change – ask me. These strings are completely corrected and now are in proper Polish grammar and punctuation.
KLB
QUOTE (teo @ Sep 7 2009, 16:43) *
I'm sending you corrected and up to date Polish versions of AMO strings for both addons. If you have any question why these strings have to change – ask me. These strings are completely corrected and now are in proper Polish grammar and punctuation.

Thanks!

Were these updated in the WTS strings? If not the corrections would get lost the next time I updated my locales by pulling all the strings from WTS.
teo
QUOTE (KLB @ Sep 7 2009, 22:25) *
Thanks!

Were these updated in the WTS strings? If not the corrections would get lost the next time I updated my locales by pulling all the strings from WTS.

I'm not your addons translator (you don't like my translation), but I'm maintainer and main translator of AMO Polish version. We – Aviary.pl official Polish translation Mozilla's products team, want see on this site good Polish language with proper grammar, punctuation and typography. So you can add my version to pl-PL locale and upload files next time with this proper translation.
KLB
I don't even remember what our disagreement was about with the translating. Did it have something to do with whether to use a Polish translation of the theme/extension name? I'd still prefer to see add-on names translated into the local language, but nobody does it so I've about given up on that happening.

I do understand the desire to have grammatically correct translations (I want the same thing).

I updated Polish localization of Classic Compact on AMO with your corrections, but I can't update Classic Compact Options on AMO because AMO now only allows 250 characters for add-on summary and the PL add-on summary is 344 characters in length. Basically I need a Polish summary that adequetly describes what Cassic Compact Options does in a much shorter fashion. The existing translation is:

QUOTE
Ten dodatek pozwala na dostosowanie ustawień motywu „Classic Compact”. Opcje zawierają: przyciski Firefoksa 2, przyciski nawigacyjne w kształcie dziurki od klucza, wyłączanie gradientowego tła; modyfikację obramowań, natywne paski przewijania systemu operacyjnego, obsługę ciemnych kolorów tła, integrację paska menu w jeden przycisk menu itp.
teo
QUOTE (KLB @ Sep 8 2009, 16:54) *
I updated Polish localization of Classic Compact on AMO with your corrections, but I can't update Classic Compact Options on AMO because AMO now only allows 250 characters for add-on summary and the PL add-on summary is 344 characters in length. Basically I need a Polish summary that adequetly describes what Cassic Compact Options does in a much shorter fashion. The existing translation is:

I'm extensions developer, but forgot about this limitation. sad.gif Below is reduced to 245 characters summary.

QUOTE
Dodatkowe ustawienia dla motywu Classic Compact: przyciski Firefoksa 2 i w kształcie dziurki od klucza, gradientowe tło, modyfikacja obramowań, natywne paski przewijania, obsługa ciemnych kolorów tła, integracja paska menu w jeden przycisk itp.
KLB
QUOTE (teo @ Sep 9 2009, 07:12) *
I'm extensions developer, but forgot about this limitation. sad.gif Below is reduced to 245 characters summary.

Thanks,

I have updated AMO and my DTDs rockon.gif
KLB
The forth coming Firefox 3.6 is necessitating some updates to my theme and extension. My hope is to push an update out within the next two weeks to beat the Firefox 3.6 release and hopefully get a jump on the add-on evaluation backlog. Any translations that are completed by the time I need to push out an update will be rolled up into the next releases of my add-ons. There will be no text changes to my add-ons.
KLB
Now that Firefox 4.0 is official, I've spent the past two weeks updating both my theme Classic Compact and Classic Compact Options (the extension this support thread is for). As much as possible I avoided changes to Classic Compact Options that would result in the need to update translations for locales, but I did end up adding one option. Obviously it's been a really long time since I've needed to update things here so I've totally forgotten how to do anything on this site. Rather than totally screwing things up I'll post some questions here first.

Do I need to insert blank ENTITY labels into locale DTDs for the new phrases or should I leave them out? How can I get my extension to default back to English for the new entity labels that have not yet been translated? Where do I update the notes about my add-on? I'd like to upload an updated version of my extension here, but it also requires downloading an updated version of my theme, which has not yet been pushed to addons.mozilla.org as I'm still in the development phase.

The new phrases I need translated for my options panel are:
  • Display toolbar button borders
  • Yes (default, FF2, FF4)
  • No (FF3)
  • Only back/forward
The locales I currently need these phrases translated for are: fr-FR, ja-JP, nl-NL, pl-PL, pt-BR, ru-RU & tr-TR
.
markh
QUOTE (KLB @ Mar 31 2011, 14:31) *
Do I need to insert blank ENTITY labels into locale DTDs for the new phrases or should I leave them out?
Please don’t, the WTS will look inside the en-US folder and add the entities automatically.

QUOTE
How can I get my extension to default back to English for the new entity labels that have not yet been translated?
When you download, use ‘strings replaced’.

QUOTE
Where do I update the notes about my add-on?
What do you mean? Any remarks inside the dtd or properties files will be displayed in the WTS. If you are referring to AMO metadata, you can either post a request or add a dtd for this specific purpose. If you are referring to extension metadata in install.rdf (localized tags), those can be inserted and will be parsed by the WTS.

QUOTE
I'd like to upload an updated version of my extension here, but it also requires downloading an updated version of my theme, which has not yet been pushed to addons.mozilla.org as I'm still in the development phase.
No problem, just upload the theme here or post a link to it. We all know that there is a certain risk in testing.

wink.gif
KLB
Okay, I'm uploading Classic Compact Options 4.0.7. It requires that my theme Classic Compact v4.0.7 also be installed. A test version of it can be downloaded from my website at: http://environmentalchemistry.com/classicc...ct-v4.0.0b1.jar
KLB
Okay, I've uploaded an updated version of Classic Compact Options. However, WTS created a whole new entry for it along with a new forum thread at: http://www.babelzilla.org/forum/index.php?showtopic=6641

My hope had been to simply update the XPI file and relevant DTDs. I'm now confused.
Fenian
Problem fixed, new extension & topic removed.

The guid of your extension was too long for the (old) WTS.
That's the reason why the uploaded version was a new extension for the WTS.
KLB
QUOTE (Fenian @ Mar 31 2011, 12:47) *
Problem fixed, new extension & topic removed.

The guid of your extension was too long for the (old) WTS.
That's the reason why the uploaded version was a new extension for the WTS.


Thanks for fixing that. smile.gif

Too bad the translator assignments have been lost. :(
Fenian
QUOTE (KLB @ Mar 31 2011, 19:55) *
Too bad the translator assignments have been lost. :(


I don't think they are lost.
We changed some language codes e.g. we use de, fr, nl, pl instead of de-DE, fr-FR, nl-NL and pl-PL.
I guess you can find the translators when you click on the new code.

The WTS has sent notification mails to 13 translators
KLB
QUOTE (Fenian @ Mar 31 2011, 13:02) *
I don't think they are lost.
We changed some language codes e.g. we use de, fr, nl, pl instead of de-DE, fr-FR, nl-NL and pl-PL.
I guess you can find the translators when you click on the new code.

The WTS has sent notification mails to 13 translators



Excellent!
rockon.gif
Alf
Dutch (nl) locale updated. Please change "nl-NL" in chrome.manifest, install.rdf and the locale sub folder to "nl" as Fenian mentioned in his post.
KLB
QUOTE (Alf @ Mar 31 2011, 15:22) *
Dutch (nl) locale updated. Please change "nl-NL" in chrome.manifest, install.rdf and the locale sub folder to "nl" as Fenian mentioned in his post.

Awesome! Thank you. I have changed the folder name as instructed.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.