Ahora en español, que me es más fácil :) Revisando la lista de órdenes
admitidas, vi que se habían traducido las órdenes Ask y Answers,
cuando responden directamente a sitios web que tienen ese nombre (no
tan sólo el servicio que dan). Mi primera reacción fue pensar que no
debían ser traducidos, pero no sé cuánta gente los usará si no lo
hacemos. ¿Les parece ver si logramos encontrar servicios parecidos en
Hi, i will try to write in english and spanish as well. Now, thanks to
Roberto, Jono, Mitcho and some other people, I'm using ubiquity in
spanish. I'm very happy with that. My only suggestion at this level is
with some commands (most social commands) that have the name or
depends in a website. Ask and Answers command (at least) depends
specificaly on websites with that name and they are translated in
spanish, losing that connection. But it's a problem if we don't
translated it, because nobody will use it in english. What do you
think it's the best approach? My first reaction is don't translated
it, but maybe it's better to find similar services in spanish.
Roberto, I agree that it is best if the translations of builtin
commands should simply be translations, and this includes the non-
translations of service names like "ask" or "answers".
> I translated the meaning of some commands to remember it easily
> Other thing we can do is add localized commands for our contries,
> and, in the settings page, sort them by country
I agree that we should instead bundle locale-specific feeds which can
be turned on, like some Spanish commands including the 11870 service
you mentioned. We haven't done this yet with any locale, but it would
not be hard to do. Perhaps we should consider consolidating all the US-
centric commands (like yelp) into a "US" feed as well so it can be
easily turned off.
I'd love to get other's thoughts on this as well. ^^
Blair McBride wrote:
> Locale/country specific commands definitely make sense. However, there
> is the use case of travelling to another country, and wishing to use
> commands/services specific to that region. So it would be great if it
> were also available as opt-in. Could also try something crazy like
> loading feeds based on geolocation data.
You may want to check with our web dev guys because I know geolocation
from IP addresses, for example, comes in very low on the list when
detecting what Firefox download should be offered to an end-user. I
think the rationale was that the data is a bit unreliable when trying to
pin down a user's preferences based on location.
< snip >
In general, I would like to see us move away from using URLs as
command names per se and towards making them plugin/provider arguments
for commands -- e.g. "search using ask.com" instead of "ask". Then we
localize the "search using" part and leave "ask.com" alone, or add
localized synonyms, or add more plugin/provider arguments for services
that are popular in a specific region.