SeaMonkey RTL theme install.properties
Huda Sarfraz
Can anyone provide the original English version or English translation (from
Hebrew) of the install.properties file for these SeaMonkey RTL themes:
http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib-localized/seamonkey-theme-rtl-classic-1.1.xpi<http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib->
http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib-localized/seamonkey-theme-rtl-modern-1.1.xpi<http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib->
Thanks,
Huda.
Michael Wolf
Hi Huda,
I don't understand much Hebrew but I think the Hebrew install.properties
of the xpi-files you mentioned above is corresponding to that one for a
language pack:
I think there are following correspondings in the strings:
theme langpack
install_opt_en install_confirm (global or profile installation,
you should probably replace "language pack" by "theme".
Tsahi mentioned the themes (Modern או Classic). But seems it isn't
asked if profile or global because there is one success
message only (success_en).
success_reboot tell_reboot
success_en install_successglobal or install_successprofile?
fail_en install_failed
cancel_202_en need_write_perm
cancel_en install_cancel
Regards
Michael
Huda Sarfraz
>
> I don't understand much Hebrew but I think the Hebrew install.properties
> of the xpi-files you mentioned above is corresponding to that one for a
> language pack:
>
Thanks! I managed to get it done with the mapping you provided and a Hebrew
to English translator<http://www.stars21.com/translator/hebrew_to_english.html>trial.
It did ask for a global/local install, so I put in a generic
successful install message for the success_en string.
Thanks and Regards,
Huda.
(If you're interested, this is the translation it produced for the
install_opt_en string: This process will install edited the subject is one
of two ways: Or global (By the directory of the installation of the browser)
Or local (By the directory of your present profile). The advantage of global
installation he that enough to install one time in order that edited the
subject will be available for all the profiles. Similarly to the sets
(classic and? modern). The deficiency he that not easy to remove her. If you
prefer a global installation, pressure on " approval"; Differently, choice
in the button " cancellation " will execute a local installation)
Michael Wolf
> Thanks! I managed to get it done with the mapping you provided and a Hebrew
> to English translator<http://www.stars21.com/translator/hebrew_to_english.html>trial.
> It did ask for a global/local install, so I put in a generic
> successful install message for the success_en string.
> (If you're interested, this is the translation it produced for the
> install_opt_en string: This process will install edited the subject is one
> of two ways: Or global (By the directory of the installation of the browser)
> Or local (By the directory of your present profile). The advantage of global
> installation he that enough to install one time in order that edited the
> subject will be available for all the profiles. Similarly to the sets
> (classic and? modern). The deficiency he that not easy to remove her. If you
> prefer a global installation, pressure on " approval"; Differently, choice
> in the button " cancellation " will execute a local installation)
Hi Huda,
fine. That confirms my supposition. But the translation is still clumsy.
I think you can adopt the string install_confirm of the
install.properties for the language pack and replace language pack by
themes Classic or Modern. The Hebrew או means "or".
Please note that the methods of the messages object in install.js must
correspond to the string names in install.properties, e.g.
intall.js: messages.success_en
install.properties: success_en
That means you shouldn't mix the string names of hte install.properties
files of theme and language pack.
Regards
Robert Kaiser
> Can anyone provide the original English version or English translation (from
> Hebrew) of the install.properties file for these SeaMonkey RTL themes:
You should mail Tsahi, the creator of those themes, he offered to give
the English versions to you in the first thread you opened about this.
Robert Kaiser
Huda Sarfraz
I wasn't able to reply to his personal email address and I thought that he'd
read this post, sorry about the confusion.
Regards,
Huda.
Tsahi Asher
keep a copy if it, but i was hoping you did.
--
Tsahi Asher
Hebrew L10n Team
http://www.mozilla.org.il
Michael Wolf
> ציטוט Robert Kaiser:
>> Huda Sarfraz wrote:
>>> Can anyone provide the original English version or English
>>> translation (from
>>> Hebrew) of the install.properties file for these SeaMonkey RTL themes:
>>
>> You should mail Tsahi, the creator of those themes, he offered to give
>> the English versions to you in the first thread you opened about this.
>>
>> Robert Kaiser
>>
> iirc, i received the original file from you. to my stupidity, i didn't
> keep a copy if it, but i was hoping you did.
>
I tried to translate the Hebrew version to English. There are still some
unclear passages. Tsahi, would you correct the text?
Here is my attempt to translate:
install_opt_en = This process installs the theme pack?? in one of two
ways: either globally (into the installation folder of the browser) or
locally (into your current profile folder). The advantage of the global
installation is that it's enough to install once so that the theme
pack?? will be available to all profile (similarly to the packs?? Modern
or Classic). The disadvantage is that it isn't easy to remove it.\n\nIf
you prefer the global installation, press on "OK"; otherwise, if you
choose the button "Cancel", the local installation will be executed.
success_reboot_en = The installation of the theme pack?? has been
finished successfully.\n\nYou must start your system before you can
choose this theme pack?? for using.
success_en = The installation of the theme pack?? is finished successfully.
fail_en = The installation of the theme pack?? has failed.
cancel_202_en = The installation of the theme pack?? has been
cancelled.\n\nIt seems that you haven't the permission to write to the
chrome folder of Mozilla. Please install as?? root/system
administrator.\n\nError code:
cancel_en = The installation of the theme pack?? has cancelled.
\n\nError code:
I don't know the exact meaning of the Hebrew word arekha/arekhet
(kh=khaf). I translated it by "pack".
Regards
Michael
Tsahi Asher
install_opt_en=This process will install the theme in one of two ways:
global (in the browser's installation folder) or local (in your current
profile folder). The advantage of a global installation is that it's
enough to install once for the theme to be available to all profiles
(similar to the Modern or Classic themes [/I may have added this one
myself/]). The disadvantage is that it is not easy to uninstall.\n\nIf
you prefer a global installation, press OK. Otherwise, selecting the
Cancel button will install the theme locally.
success_reboot_en=The theme was installation was completed
successfully.\n\nYou should reboot your system before you can select
this theme for use.
success_en=Installing the theme was completed successfully.
fail_en=Installing the theme failed\n\nError code:
cancel_202_en=Theme installation was canceled.\n\nIt appears you don't
have write permission to the chrome folder of Mozilla [/should be
updated to SeaMonkey/]. Please install as root/Administrator.\n\nError code:
cancel_en=Theme installation was canceled\n\nError code:
hth
--
Tsahi Asher
Robert Kaiser
> ציטוט Robert Kaiser:
>> Huda Sarfraz wrote:
>>> Can anyone provide the original English version or English
>>> translation (from
>>> Hebrew) of the install.properties file for these SeaMonkey RTL themes:
>>
>> You should mail Tsahi, the creator of those themes, he offered to give
>> the English versions to you in the first thread you opened about this.
>>
>> Robert Kaiser
>>
> iirc, i received the original file from you. to my stupidity, i didn't
> keep a copy if it, but i was hoping you did.
Oh, if it's the file from me, it's probably the same I'm using in my
German XPIs ;-)
I've attached it, so it should be available here for everyone.
Robert Kaiser
P.S.: Just realized that not even a text-only attachment makes it
through here.
http://resources.kairo.at/mozilla/l10n/xpi/install.properties should
work though.
Michael Wolf
> Oh, if it's the file from me, it's probably the same I'm using in my
> German XPIs ;-)
>
> I've attached it, so it should be available here for everyone.
>
> Robert Kaiser
>
> P.S.: Just realized that not even a text-only attachment makes it
> through here.
> http://resources.kairo.at/mozilla/l10n/xpi/install.properties should
> work though.
No, this one is for the language pack. The other one that was needed is
for the installion of rtl theme packs.
Regards
Michael
Huda Sarfraz
>
> Oh, if it's the file from me, it's probably the same I'm using in my
> German XPIs ;-)
>
> I've attached it, so it should be available here for everyone.
>
> Robert Kaiser
>
> P.S.: Just realized that not even a text-only attachment makes it
> through here.
> http://resources.kairo.at/mozilla/l10n/xpi/install.properties should
> work though.
>
Thanks!
Huda Sarfraz
>
> alright, here it is:
> install_opt_en=This process will install the theme in one of two ways:
> global (in the browser's installation folder) or local (in your current
> profile folder). The advantage of a global installation is that it's
> enough to install once for the theme to be available to all profiles
> (similar to the Modern or Classic themes [/I may have added this one
> myself/]). The disadvantage is that it is not easy to uninstall.\n\nIf
> you prefer a global installation, press OK. Otherwise, selecting the
> Cancel button will install the theme locally.
> success_reboot_en=The theme was installation was completed
> successfully.\n\nYou should reboot your system before you can select
> this theme for use.
> success_en=Installing the theme was completed successfully.
> fail_en=Installing the theme failed\n\nError code:
> cancel_202_en=Theme installation was canceled.\n\nIt appears you don't
> have write permission to the chrome folder of Mozilla [/should be
> updated to SeaMonkey/]. Please install as root/Administrator.\n\nError
> code:
> cancel_en=Theme installation was canceled\n\nError code:
>
Sorry for the late reply, thank you,
Regards,
Huda
Huda Sarfraz
theme XPIs? The only difference is that they're in Urdu, and the previews
show them installed with an Urdu language pack. These are the original
names:
seamonkey-theme-rtl-classic-1.1.xpi<http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib->
seamonkey-theme-rtl-modern-1.1.xpi
<http://ftp.pwr.wroc.pl/pub/mozilla/seamonkey/releases/1.1/contrib->
Thanks,
Huda.
On 8/6/07, Tsahi Asher <tsahi_7...@yahoo.com> wrote:
> >
Robert Kaiser
> I have one last question about this: what should I name the translated rtl
> theme XPIs? The only difference is that they're in Urdu, and the previews
> show them installed with an Urdu language pack. These are the original
> names:
I'd love to have a single, generic version of them there if possible.
IMHO it doesn't make much sense to publish multiple versions of the same
file just with different installations messages and preview images.
I hope we can remove the need for such themes at all for SeaMonkey 2, I
hope Tsahi and you can help us getting at least the default theme, maybe
also Modern, in shape for that before we release a final.
We probably might need to get the infrastructure for CVS-based L10n
running first though.
Robert Kaiser
Huda Sarfraz
>
> I'd love to have a single, generic version of them there if possible.
> IMHO it doesn't make much sense to publish multiple versions of the same
> file just with different installations messages and preview images.
> I hope we can remove the need for such themes at all for SeaMonkey 2, I
> hope Tsahi and you can help us getting at least the default theme, maybe
> also Modern, in shape for that before we release a final.
> We probably might need to get the infrastructure for CVS-based L10n
> running first though.
>
What about either
1) having the installation messages in English, and the previews for the
Hebrew language pack? at least temporarily,
Or
2) If it's possible to modify the original such that it prompts the user for
the install language (and then selecting the preview image based on the
language selection), I can do that after looking at some XPIs that do
something similar.
Regards,
Huda.
Robert Kaiser
> What about either
>
> 1) having the installation messages in English, and the previews for the
> Hebrew language pack? at least temporarily,
That surely would be a possible way to go.
> Or
>
> 2) If it's possible to modify the original such that it prompts the user for
> the install language (and then selecting the preview image based on the
> language selection), I can do that after looking at some XPIs that do
> something similar.
I don't know if and how this is possible.
Robert Kaiser
Tsahi Asher
lot's of document.write() calls, that will build a combo box with the
available languages. then, in the install.js, this page will be opened,
and the selected language will be extracted and used for the rest of the
installation. this will require multiple install.properties files, or
multiple languages in the same file. this may require more javascript
than i know.
as for the preview image, this is defined in the RDF file. i can't see
how you can change that during installation, but maybe i don't know
enough about the chrome mechanism.
Michael Wolf
> i think it might be possible to select a language by opening a page with
> lot's of document.write() calls, that will build a combo box with the
> available languages. then, in the install.js, this page will be opened,
> and the selected language will be extracted and used for the rest of the
> installation. this will require multiple install.properties files, or
> multiple languages in the same file. this may require more javascript
> than i know.
>
> as for the preview image, this is defined in the RDF file. i can't see
> how you can change that during installation, but maybe i don't know
> enough about the chrome mechanism.
I think you could do it by a switch-case inquiry which could open the
concerning properties file by the window.open function. Or/And an array
could be used anyhow. And IMHO there is a handful of rtl languages and
how many of them have translations for Seamonkey? At the moment I know
Hebrew and Urdu only. Possibly Arabic, Farsi/Dari, Kurdish, Pashto. If a
new rtl language will be added English could be used as fallback
language for the time being. But I think it's better to include all
existing rtl languages no matter if there is a translation for SM at the
moment or not.
Regards
Huda Sarfraz
>
> Tsahi Asher napisa:
> > i think it might be possible to select a language by opening a page with
> > lot's of document.write() calls, that will build a combo box with the
> > available languages. then, in the install.js, this page will be opened,
> > and the selected language will be extracted and used for the rest of the
> think you could do it by a switch-case inquiry which could open the
> concerning properties file by the window.open function. Or/And an array
> could be used anyhow. And IMHO there is a handful of rtl languages and
> how many of them have translations for Seamonkey? At the moment I know
> Hebrew and Urdu only. Possibly Arabic, Farsi/Dari, Kurdish, Pashto. If a
> new rtl language will be added English could be used as fallback
> language for the time being. But I think it's better to include all
> existing rtl languages no matter if there is a translation for SM at the
> moment or not.
>
I've been trying to figure out how to do this, but so far the only way I can
find for users to input something (a language choice in this case) is using
buttons. I've been using this:
http://developer.mozilla.org/en/docs/XPInstall_API_Reference
as a guide. I haven't tried the combo box on the webpage idea that Tsahi
mentioned. Can anyone suggest any other XPIs (or other reference material)
that do something similar so that I can see how they do it.
Thanks,
Huda.