Doubts about trademarks and searchplugins for es-ES Fx 2.0 and Tb 2.0
Ricardo Palomares Martinez
Not that I was willing to do it, but it seems that, at least for the
next two weeks, I'm going to be in charge of Fx 2.0 l10n (this was the
only remaining Mozilla product I wasn't in charge of).
As I didn't expect to care about searchplugins new format and the
Firefox L10n requirements, I'm a bit lost, and that's not a good thing
when our language is designated as a Tier 1. :-(
In a first review, almost all entities and stringbundles with URLs in
es-ES are the same than en-US ones, except a minimum number that are
currently redirected to spanish (usually resumed) versions on
mozilla-europe.org. I've read about prepending ab-CD to original
mozilla.org but, should we wait until either:
- the original en-US URLs are updated/replaced to also prepend
"en-US"?
- the strings are removed to be generated by code as Firefox L10N
requirements says?
Or neither of that is going to happen and we should just insert our
language code in every .mozilla.org/com URL? BTW, who's going to
localize the web content itself?
Regarding bookmarks, we haven't touched it since Fx 1.5. Does that
mean that we don't need to touch it, or should we file a bug to
request approval after reviewing quicksearches format and requesting
permission to keep or change current RSS sample?
Talking about RSS sample, we already found a problem that maybe other
teams have already suffered: choosing a RSS candidate over the rest of
all raised some complaints from the others; besides, every option we
have got is "labeled" as representing a political trend (even though,
actually, the provided content of all of them is blank and neutral to
me). Is there any chance to get two or more RSS samples included in
bookmarks.html (assuming we can prove the owners consent to be linked,
of course)? I browsed spanish BBC news site, but it seems to be more
oriented to Hispano-America.
Finally, all en-US searchplugins have been migrated from Sherlock
format to OpenSearch, but our dictionary (http://www.rae.es/, the
normative organism to spanish) has no Opensearch support to the best
of my knowledge. Besides switching to another or "forcing" them to
support Opensearch, can we ship that searchplugin in Sherlock format
and use the Fx2 -> Fx3 transition period to convince RAE to add
Opensearch support?
A lot of these things should probably be filed in a bug, but as I
don't know if you, Axel, would want separate bugs, just one, or none,
I've decided to start here and let you direct me. Sorry to annoy you.
TIA
--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?
Marek Stepien
> Finally, all en-US searchplugins have been migrated from Sherlock
> format to OpenSearch, but our dictionary (http://www.rae.es/, the
> normative organism to spanish) has no Opensearch support to the best
> of my knowledge.
The site does not need to support anything more than HTTP. The
OpenSearch/MozSearch format used by Mozilla is just another way to
mark up the same information that the Sherlock plugins contained (i.e.
the URL for the search query, the search engine name, encoding etc.).
Read more here:
http://developer.mozilla.org/en/docs/Creating_MozSearch_plugins
--
Marek Stępień <mar...@aviary.pl>
AviaryPL - polski zespół lokalizacyjny Mozilli
http://www.firefox.pl/ | http://www.mozilla.org.pl/
Axel Hecht
These are all questions for Phil. Apart from the search plugin
implementation, which Marek already answered.
Axel
Phil Schwan
On Jul 30, 2006, at 13:37, Ricardo Palomares Martinez wrote:
> In a first review, almost all entities and stringbundles with URLs in
> es-ES are the same than en-US ones, except a minimum number that are
> currently redirected to spanish (usually resumed) versions on
> mozilla-europe.org. I've read about prepending ab-CD to original
> mozilla.org but, should we wait until either:
>
> - the original en-US URLs are updated/replaced to also prepend
> "en-US"?
I'm waiting for the final list of en-US URLs, which I expect to have
very soon, and then I will update them all to the new format and post
the list.
Before the localization files use the new URLs (or at least before
you check them in), I want to make sure that we have redirects in
place on the web server, so that they point to the existing content.
I'll post an email when that's ready.
> - the strings are removed to be generated by code as Firefox L10N
> requirements says?
As much as I would like this, I don't think the code is going to get
updated in time.
> BTW, who's going to localize the web content itself?
We're working with the mozilla-europe team to get similar
infrastructure deployed on mozilla.com, and content that is already
localized can be transferred from its current home. Pages that
aren't localized can redirect to the same language in a different
locale, or to en-US, or to a localized "Sorry! We don't have this in
your language." page.
It's up to the localization teams to decide whether or not to
localize the web content. I hope so, but I can't compel anyone. :)
> Regarding bookmarks, we haven't touched it since Fx 1.5. Does that
> mean that we don't need to touch it, or should we file a bug to
> request approval after reviewing quicksearches format and requesting
> permission to keep or change current RSS sample?
If the bookmarks or searches are localized versions of the en-US
bookmarks or searches, then don't file a bug -- you can just update
the URLs where necessary. If it's not a localized version of an en-
US bookmark, please do file an approval bug.
For the RSS sample, we're going to provide mozilla.com URLs that
redirect to the localized RSS feeds, as we already do for en-US.
> Talking about RSS sample, we already found a problem that maybe other
> teams have already suffered: choosing a RSS candidate over the rest of
> all raised some complaints from the others; besides, every option we
> have got is "labeled" as representing a political trend (even though,
> actually, the provided content of all of them is blank and neutral to
> me). Is there any chance to get two or more RSS samples included in
> bookmarks.html (assuming we can prove the owners consent to be linked,
> of course)? I browsed spanish BBC news site, but it seems to be more
> oriented to Hispano-America.
The real goal of the RSS feed is to show users an example of a
feature they might not otherwise know about. BBC was chosen as a
default simply because it's published in so many languages, so it's
easy to localize if the team doesn't choose something different.
But I've been asked to keep the out-of-the-box menus as minimal as
possible. For the same reason, you're going to see a sharp reduction
in the number of en-US bookmarks.
So by all means choose a more relevant site, and Mic will help you
get permission to link, but we would really like to have just one feed.
Thanks very much for your help!
-Phil
Ricardo Palomares Martinez
>
First of all, thank you very much for your reply.
>> BTW, who's going to localize the web content itself?
> (...)
> It's up to the localization teams to decide whether or not to localize
> the web content. I hope so, but I can't compel anyone. :)
>
Ok, that wasn't intended as an accusatory question, :-) it's just that
I'd like to know how much work is left to do yet.
> But I've been asked to keep the out-of-the-box menus as minimal as
> possible. For the same reason, you're going to see a sharp reduction in
> the number of en-US bookmarks.
>
> So by all means choose a more relevant site, and Mic will help you get
> permission to link, but we would really like to have just one feed.
Understood. Thanks again for your answers.
Ricardo.
huida...@gmail.com
Having regular Clients and good reputation
Product quality is 100% Nice
Feel free to contact us by email or telephone us
So that you can get the pleased offer and product
Email: huida...@yahoo.com
Email: huida...@gmail.com
TEL:008613713294118
IMO:+8613713294118
VIBER:+8613713294118
Whatsapp:+8613713294118
Skype:andyliu...@hotmail.com
QQ:2859908869
http://dghd-2.com
http://dghd-3.com
http://dghd-4.com
http://dghd-5.com
http://dghd-6.com
http://dghd-7.com
http://dghd-8.com
http://dghd-9.com
http://dghd10.com
http://dghd11.com
http://dghd12.com
http://dghd13.com
http://dghd14.com
http://dghd15.com
http://dghd16.com
http://dghd17.com
http://dghd18.com
http://dghd19.com
http://dghd20.com
http://dghd21.com
http://dghd22.com
http://dghd23.com
http://dghd24.com
http://dghd25.com
http://dghd26.com
http://dghd27.com
http://wxq-2.com
http://wxq-3.com
http://wxq-5.com
http://dongguanhuidabangonghaocai.com
http://wxq-5.com/a/qi_qushi/20171108/139.html
http://www.wxq-2.com/a/hui_shenghuo/20160421/48.html
http://dghd-7.com/news/81.html
http://wxq-5.com/index.html
http://dghd-7.com/news/180.html
http://dghd-7.com/cp/shimuchugui/340.html
http://dghd-5.com/a/news/jszc/20170219/288.html
http://www.dghd19.com/a/yule/291.html
http://www.dghd19.com/a/keji/
http://dghd-7.com/cp/shimuweiyu/
http://dghd-7.com/news/232.html
http://wxq-3.com/a/hui_shenghuo/20171104/135.html
http://dghd20.com/a/keji/
http://www.wxq-2.com/a/qi_qushi/20171204/295.html
http://dghd16.com/news/81.html
http://www.dghd-4.com/m/view.php?aid=365
http://wxq-5.com/index.html