setting region/content display name for SeaMonkey XPI
Huda Sarfraz
I am trying to change the display name for my SeaMonkey content pack. I
changed displayName in /global-region/content.rdf as described here:
http://wiki.mozilla.org/L10n:MozillaTranslator
I did it manually and not through Mozilla Translator. But when I install the
new XPI, the name remains the same as it was before (i.e., the same as the
language pack name).
I've done it twice and even uninstalled SeaMonkey and removed my profile,
but my region display name does not change. Am I following the correct
procedure?
Thanks,
Huda.
Michael Wolf
Hu Huda,
did you repack the PK.jar after changing?
Huda Sarfraz
I did, and it installs correctly as well, except for the region
display name. I even unpacked it to check if I had made a mistake, but
the change I'd made was there in the rdf file. I will try again.
Thanks,
Michael Wolf
>> did you repack the PK.jar after changing?
>
> I did, and it installs correctly as well, except for the region
> display name. I even unpacked it to check if I had made a mistake, but
> the change I'd made was there in the rdf file. I will try again.
Hi Huda,
is in your contents.rdf file the correct version number? On the web page
you mentioned (http://wiki.mozilla.org/L10n:MozillaTranslator) in the
section "Exporting a Language Pack" is a "Warning:" that there is a bug
in the jar export mechanism that causes missing version number. If not,
the contents,rdf won't work.
Regards
Michael
Tsahi Asher
that bug.
--
Tsahi Asher
Hebrew L10n Team
http://www.mozilla.org.il
Ricardo Palomares Martinez
> ציטוט Michael Wolf:
>> Hi Huda,
>>
>> is in your contents.rdf file the correct version number? On the web
>> page you mentioned (http://wiki.mozilla.org/L10n:MozillaTranslator) in
>> the section "Exporting a Language Pack" is a "Warning:" that there is
>> a bug in the jar export mechanism that causes missing version number.
>> If not, the contents,rdf won't work.
>>
>> Regards
>> Michael
> i'm not sure this is up to date. i think the last version of MT fixed
> that bug.
>
Sorry, I missed this thread. Michael, I think that warning refers to
this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=258274
This is fixed, I think from MT 5.1.
And yes, the wiki content is definitely outdated. Now that I try to
keep the user guide shipped with MT updated, the wiki content could
probably be removed and just leave the link to the PDF version, but I
never have time for cleaning that... :-)
Ricardo.
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Michael Wolf
> Sorry, I missed this thread. Michael, I think that warning refers to
> this bug:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=258274
>
> This is fixed, I think from MT 5.1.
>
> And yes, the wiki content is definitely outdated. Now that I try to
> keep the user guide shipped with MT updated, the wiki content could
> probably be removed and just leave the link to the PDF version, but I
> never have time for cleaning that... :-)
Yes, it's the bug. If it has been fixed there should be another reason
for the error. But, Huda didn't reply to my email, so we don't know if
this bug is connected with his error.
Regards
Michael
Huda Sarfraz
>
> Yes, it's the bug. If it has been fixed there should be another reason
> for the error. But, Huda didn't reply to my email, so we don't know if
> this bug is connected with his error.
>
I checked the version number and it was ok, I even did it manually without
using Mozilla Translator but it wasn't working. I will try again, because I
sometimes get a problem with my XPI where my changes can't be seen when I
install it and I have to uninstall SeaMonkey, re-install it and then install
the updated XPI. It could be something like that. I'm still trying,
Michael Wolf
> I checked the version number and it was ok, I even did it manually without
> using Mozilla Translator but it wasn't working. I will try again, because I
> sometimes get a problem with my XPI where my changes can't be seen when I
> install it and I have to uninstall SeaMonkey, re-install it and then install
> the updated XPI. It could be something like that. I'm still trying,
Could you send me your PK.jar to my e-mail address?
Huda Sarfraz
>
I sent my PK.jar to Michael and he found out what was wrong, I was only
modifying the contents.RDF file in global-region, but there were others as
well where the displayname was something else. Thanks for the help,
Regards,
Huda.
Ricardo Palomares Martinez
> I sent my PK.jar to Michael and he found out what was wrong, I was only
> modifying the contents.RDF file in global-region, but there were others as
> well where the displayname was something else. Thanks for the help,
Michael, Huda, could this be a bug in MozillaTranslator? Please, let
me know if I should take a look at it.
TIA
Michael Wolf
> Huda Sarfraz escribió:
>> I sent my PK.jar to Michael and he found out what was wrong, I was only
>> modifying the contents.RDF file in global-region, but there were others as
>> well where the displayname was something else. Thanks for the help,
>
>
> Michael, Huda, could this be a bug in MozillaTranslator? Please, let
> me know if I should take a look at it.
Hi Ricardo,
no, in his message before last Huda wrote that he didn't use MT. The
error was that Huda used all chrome: entries of global-region
contents.rdf in all region contents.rdf, so he used the
chrome:displayName entry not only in global-region contents.rdf but also
in the other contents.rdf of the content-pack (communicator-region,
editor-region, messenger-region and navigator-region). But unlike
global-region there he used Urdu(PK) as chrome:displayName. Only in
global-region contents.rdf was the correct chrome:displayName, but it
seems that SM used the first chrome:displayName that it found and that
was one with Urdu(PK). Urdu(PK) is, however, this one for the locale.
REgards
Michael