Creator: alta88
Ext. Version: 1.0

Extension is compatible to:
Firefox: 3.0b4pre - 3.0.*
Included locales: ar be-BY cs-CZ da-DK de-DE el-GR en-GB en-US es-AR es-ES fi-FI fr-FR he-IL hr-HR hu-HU it-IT ja ko-KR lt-LT nb-NO nl-NL pl-PL pt-BR pt-PT ru-RU sk-SK sv-SE tr-TR uk-UA zh-CN zh-TW
Description: Customize and place multiple toolbars almost anywhere. Customize statusbar too.

 View on WTS -- Download the extension

Hi everyone,

I've uploaded TotalToolbar, found on mozdev.org. There are already 31 locales, and a few new strings have been added.

New strings:

totaltoolbar.dtd - 1 new string (23 existing translated strings)
totaltoolbar-new.dtd - 4 new strings
totaltoolbar.properties - 3 new strings

Thanks for your help.

You are here of course. Considering the great number of already existing translations, maybe it would be more correct to invite here all your previous translators, so that they can continue doing the good job here on our WTS?

Please add localize extension description.

aha. i have taken over this extension from aios and am a first timer - how would i do that?

thanks.

So... already existing translations come from AIOS translators, can you confirm?

hmm I don't know who is the original translator for el-GR but he has obviously done a very good job. If you can't contact him, PM me and i'll provide the new strings here (i don't want to register for the extension so early since the original translator might show up).

aios had quite a few translation credits from babelzilla, so i assume all current translations came from here, yes.

ah yes of course, za chwilę będzie nowe..

Please go here.
Because this extension have many translations the best way will be method before Gecko 1.9. Working also with Gecko 1.9.

Are you Pole?

ok just to have a memo, here are translators for AIOS that of course are welcome to complete TotalTolbar extension.
(fortunately, AIOS has been translated on BZ)

yes i had read that before, and the method i'm using is the pre 1.9 method, correct?

but goofy suggested i contact previous translators - is there an automated way to do that? or even find out who they are easily.. or is the only way to email each of ~30 individually?

if i upload a new .xpi, will the checkin by goofy for fr be lost? or should i take those changes and then upload?

Some informations about prepare files to upload to BabelZilla:
1. New strings have to be only in the en-US locale
2. All untranslated strings in the each locale should be removed
3. Before uploading new version you should download all locales from BabelZilla - minimum locales which was changed by translators after your last upload, do point 1-2
4. Check install.manifest for locale declarations - have to be all downloaded from BabelZilla, if not - you lost translators.

That's all. Go ahead.

thanks teo. ok, the latest upload has everything corrected. sorry goofy, i think i lost fr :(

just let me know how best to contact the previous translators..

to recap, the new strings are:

totaltoolbar.dtd - 1 new string
totaltoolbar-new.dtd - 4 new strings
totaltoolbar.properties - 3 new strings

Send PM to all AIOS translators using CC. AIOS is translated on BabelZilla.

mmmh it will take a couple of days to have everyone registering, but I can do that for you, don't worry.

[EDIT] Invitation messages now sent to all known translators

ROFLMAΟ !!! I am the original translator after all

@ alta88 :
It looks like your extension is not yet on AMO (not even in the sandbox), but since i guess you're going to submit it there,
it would be nice if you'd post here the strings that you will submit to AMO in order to get them translated as well (or you
could also add a dummy AMO.properties fiile in the xpi you submit to babelzilla for them).
Plus, when you submit it to AMO, drop a note here so we can help with the reviews.

thank you!

hehe..

actually, i don't intend to put it on AMO at the moment. maybe when they have their act more together.

but, would you recommend translating the mozdev.org pages? it's really only the index page and the FAQ page. how would the mechanics work? has anyone done this on mozdev.org?

Spanish (es-ES) locale completed and released in the WTS

Spanish (Spain) / es-ES

by Proyecto Nave

Greetings from Spain

P.S: Thanks Goofy for your PM

I don't know if mozdev.org pages can be localized, but even if they can, what's the use
since the extension will not be publised for a while more so the possible users will be limited
to a handful of hard-core enthousiasts ?
I'd consider that a waste of time for all of us (including yourself) for the time being.
Anyway, el-GR released.

Oh, I remember YOU are the original translator...


You made my day!

I'm registered as german translator and already released the localization. I realized there is one error in the german translation of AiOS. But yours should be fine now.

Thanks to Goofy for the invitation message!

back dear Ingo!

Hello Goofy, nice to see/read you again.

Well, i didn't read Goofy's message about the connection with aios at first but i'm glad to see people laugh
plus, i forgot to thank Goofy for the invitation
welcome back Ingo

gracias - heh, i will be in andalucia for 2 1/2weeks in april..

Finnish [fi-FI] ready

goofy, et al:

there are still many missing translations, what would be the best thing to do? it's very hard to see who (id to PM) belongs to what former AiOS translation to ask again.. the 2 lists in a previous post don't associate the name with an id/mail. the contact system could be a bit improved here.

also, technically, if certain strings have no translation, should the string be in en-US or blank? will Fx default that string to en-US if blank?

thanks!

sure it should be. the nicknames to PM are in the PMs I laready sent and for which I CC'ed you, so you can ask again perhaps. You can also fish missing translators out of this page
http://www.babelzilla.org/index.php?option...1&type=lang


Every locale MUST be filled with strings (in the target language or in English by default). If you leave blank lines for some entities, it will break the extension on intall

yes, but one can't know what nicknames correspond to what translator in the PM list - your notes have long names. anyway, i'll see what i can do.

On this page
http://www.babelzilla.org/index.php?option...1&type=lang
Editing one lang after another you can grab every valid nickname to send PM to

yes i know, but that is very painful for 30 locales.. ;)

also, the mechanism for getting strings is also painful. i'd rather not download 30 times 3 files worth of strings. this is very inefficient. these things would be nice:

1. on a locale translation page (ie view the specific version and locale and file page), the results should be already formatted in the structure for the .dtd or .properties file, as they are in the download file. so, the page should show, respectively:
<!ENTITY label.string "translated string"> or
property.name=translated string

2. all of the formatted strings should just be listed (together by type of file) in a multiline textbox (editable or not) such that a select/copy/paste from the web page into the extension author's local file is a few clicks operation per file.

might these changes be possible at some point?

I am not sure I understand the starting point of your suggestions, hence the suggestions themselves are not clear for me (remember I am goofy after all)

I don't understand why you

when you can download all available locales in one click
Click to view attachment

and why you need to copy/paste formatted strings inside your files one after another when all you have to do is drop the whole locale folders inside the main "locale" folder of your extension. Here an example of simple downlading of ALL locale files for one locale.
Click to view attachment

Please explain what you mean exactly.

aha. i should have tried the download all first, to see how it works; it's nice and automated. je m'excuse..

but say i want to just get one or two strings for one locale. only fast way is to download the file - i was thinking if the formatted strings were on the page it would just be cut/paste. i'm the type who opens and inspects each file to see if it's ok etc etc.

anyway thanks for your patience and help.

I see. Sure it is good practice to check every file . As you mention, you have to download the whole file even if you want to copy/paste a couple of strings, or formatted strings. For translator's work, we think it is easier to edit one string after another with the original string just above and not write in one multiline textbox. So I don't think we will modify this feature.

no nothing would change for the translator, that part is well done. you would just display an additional textbox, at the bottom, with all the formatted strings for a file together summed up automatically, via script, from the results in the translated boxes, so one drag select & copy is possible.

ah you mean an additional thing. Ok we shall discuss this on admin side.






Would this kind of link be enough for your needs ?
Click to view attachment

yes, exactly. actually, a link like that might be best, i was thinking originally just have it on the same page, but it might be too cluttered.

Hmm.. i received an update notification twice but i can't see any new/ altered strings.. so .. el-GR released again.

Spanish (es-ES) locale update in the WTS

Spanish (Spain) / es-ES

Greetings from Spain

P.S: Please, check tagbar.search_keyword entity in tagbar.dtd file, I think you have a typo: Keywrod.

hi. thanks great extension .

Uploaded ja-JP (Japanese) locale in WTS.

when you release next version,
please update "chrome.manifest" line 20 -> "locale totaltoolbar ja-JP chrome/locale/ja-JP/"
and remove \chrome\locale\JP directory.

#version 1.2 not work with firefox 3 RC1 (ja-JP) because locale JP incompleted.


regards.

thank you for the translation and for the manifest fix. i will release this soon, once i make an enhancement.

domo arigato!