Recommended Addon

[Pedro]

Hi stakats.
I am here again

I downloaded and translated the rc3 version of Zotero and I have seen that all my requests are solved... great work!

It remains only:

- the description... I recommend you this simply tutorial to translate it

http://www.babelzilla.org/index.php?option...6&Itemid=83


- and these two untranslated entities...





... I think that's all

Bye bye

Luca

[Turcan]

Where did you have rc3 for translation? At babelzilla is only rc2.
Mihai

[Pedro]

I downloaded the rc3 version from Zotero's home page and I manually edited the italian files

I made this just for curiosity, I think we should wait the new stakats upload for officially version

Bye bye

Pedro

[teo]

Hi stakats,
I'm editor of Polish translation. In meantime I rewrote options dialog window for better look. I resolved all ugly problems indicated on attached screenshots.
In the attached file is rebuilt 'preferences.xul' file tested on RC3
Please give me your judgment.

Attached File(s)

 zot1.png ( 26.33K ) Number of downloads: 18
 zot2.png ( 21.71K ) Number of downloads: 12
 zot3.png ( 18.57K ) Number of downloads: 13
 zot4.png ( 18.58K ) Number of downloads: 12
 zot5.png ( 18.34K ) Number of downloads: 12
 preferences.zip ( 3.56K ) Number of downloads: 1

 

[teo]

... I think that's all
Luca

Not all!
Still not localized:
1. 'There was an error starting Zotero' from 'overlay.xul' and 'overlay.js' files
2. 'Error initializing Zotero database' from 'schema.js' file
3. All alerts from 'bundle.js' file
4. Extension description.

I found problem with keyboard and shortcuts. In the many countries national characters are typing with right [Alt] key. In the Zotero are used shortcuts [Alt+character] In the Polish keyboard we use L, O, and N (which are used in Zotero as shortcuts) for Polish diacritic characters. This causes bug. I can't write Polish national characters in Zotero. Please change [Alt] key to another one.

[stakats]

We're ready to upload a new RC to BabelZilla with the last few unlocalized strings ready to translate. But first I need some help. Each time that we upload a new version of the extension, BabelZilla either loses all of the previous translations, or else it shows the translations as 100% done even when they're only partially complete. Could somebody please provide detailed instructions on exactly what to do on our end? Should we prepare an extension including all of the already translated strings on BabelZilla? Or submit one with just en-US? What is the best workflow to ensure that BabelZilla carries over all of the previous work? You all have done such great work, and I want to make things as easy as possible for you in the future. Thank you. -Sean

[Goofy]

Hi Sean

First thing to do is download all locales from the wts (there is a handy link for that)
I attach them here
 Zotero__locales.tar.gz ( 298.57K ) Number of downloads: 0

so that translator's work can be easily re-uploaded in case some weird thing happens with the coming update.
Second you should save translator's list as provided in your "Manage my extensions" page. Sometimes there are (again) strange things happening and translator's registration are lost.

Now you have to follow a 17-step guide
1. drop all provided locales (except en-US) in the new version of your extension
So only the en-US is updated with the most recent strings
5. check carefully that every locale is mentioned in the chrome.manifest. It is the more important point because the WTS uses their path to register them.
17. You can submit your new build.

[teo]

This is not all!!
Before dropping all locales in the new extension version you have to remove from all locales not translated lines (they are in English) and changed by you lines. If you change in the en-US locale entity (name or content) you have to remove this entity from each locale. Not add new entity! These new should be only in the en-US locale. Its very important include all locales, even they have some strings translated. Remember as Goofy mentioned - don't forget in the chrome.manifest insert all registered locales.
Now after uploading will be displayed proper percentage and translators will be see in WTS yellow textboxes which signifying non translated strings.

[markh]

Alternatively, you can follow the tutorial on this

[teo]

@markh,
This is very good tutorial for begining. Now all untranslated string are filled by their English counterparts and developer MUST remove them from locales.

[markh]

@markh,
This is very good tutorial for begining. Now all untranslated string are filled by their English counterparts and developer MUST remove them from locales.

Yes, it's one of the less known but potentially annoying bugs in the WTS. In any case, visiting the Help-Q&A section is always advisable in case of questions regarding functionality of the WTS.

[teo]

@stakats
Could you explain me for what is menuitem red rounded on attached picture?

Next bug in the RC3
Option 'Display Zotero above/below browser content' not working.

Attached File(s)

 zot6.png ( 4.93K ) Number of downloads: 10

 

[Pedro]

@stakats
Could you explain me for what is menuitem red rounded on attached picture?

I think it's for choose what resolver use... at the moment there aren't resolvers then I think it's impossible to set them. Just an idea

Next bug in the RC3
Option 'Display Zotero above/below browser content' not working.

In my Firefox (Mozilla/5.0 (X11; U; Linux i686; it; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6) this feature works properly

[teo]

In my Firefox (Mozilla/5.0 (X11; U; Linux i686; it; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6) this feature works properly

You are right. In new blank profile working properly but after restart Firefox.

[Pedro]

You are right. In new blank profile working properly but after restart Firefox.

For me also if I open a new window... restart Firefox seems not necessary

[Rintze]

Will the plugins for Word and Openoffice also be submitted to Babelzilla for translation for the Zotero 1.0 release?

[stakats]

FYI: We will upload a new version of Zotero to BabelZilla within the next day, so please do not work on any Zotero string translation until then.

[doannhutung]

FYI: We will upload a new version of Zotero to BabelZilla within the next day, so please do not work on any Zotero string translation until then.

It's Oct 22 now, and I haven't seen any new RC yet. I wasn't aware of this thread, so I went ahead and translated RC2 (to Vietnamese -- vn locales). It's now 60% completed. What will I have to do to import the work I've done into RC5 when it's uploaded to BabelZilla? (I've already downloaded the locales as a tar.gz file.)

[markh]

It's Oct 22 now, and I haven't seen any new RC yet. I wasn't aware of this thread, so I went ahead and translated RC2 (to Vietnamese -- vn locales). It's now 60% completed. What will I have to do to import the work I've done into RC5 when it's uploaded to BabelZilla? (I've already downloaded the locales as a tar.gz file.)

Just keep your files locally. When the new RC is uploaded it will probably be included in the new xpi and you will get an update notification (provided the dev includes it). If it isn't, just re-register as translator and upload your files through the upload link. New strings will be highlighted in yellow.

[stakats]

Just keep your files locally. When the new RC is uploaded it will probably be included in the new xpi and you will get an update notification (provided the dev includes it). If it isn't, just re-register as translator and upload your files through the upload link. New strings will be highlighted in yellow.

Zotero 1.0.0rc5 now available on BabelZilla. Vietnamese strings updated in the interim attached here for doannhutung.

Attached File(s)

 Zotero_vi_VN_locales.tar.gz ( 11.54K ) Number of downloads: 5