Hi, for the launch of Firefox OS we're going to need some messaging headlines localized in your language. The slogans to be localized are: * "Look Ahead" * "Empower Yourself" * "Blaze Your Own Path" In addition to localizing the phrases, we would like advices from you about any negative connotations, language nuances, or cultural sensitivities any of these phrases have in their respective languages. These localized messages will be used to create graphic assets for you locale. If you have any doubt, don't hesitate and ask in the bug :-)
First of all sorry for the confusion but there's a mistake in one of the slogans to localize (please ignore "Empower Yourself"). These are the slogans that we'll be using, with the target audience. * "Look Ahead" (consumer audience) * "Be the Future" (developer audience) * "Blaze Your Own Path" (industry audience) These messages will be used to create marketing and advertising material. A couple of examples: http://www.flickr.com/photos/mozillaeu/sets/72157634593759364/ http://www.mozilla.org/en-US/styleguide/identity/firefoxos/community/ You can provide your localizations (or discuss them) as comments in this bug. Some background about these messages directly from the Creative Teams. There’s a sense of optimism that comes with a changing world as new opportunities and ways to communicate arise. When people feel it, they want to be part of it, not only to better their lives, but also to participate in a better world. That’s what Firefox OS promises and provides. It’s not just a smartphone. It’s a symbol of the journey they’re on and a companion on the road towards the future they now see. The idea of Look Ahead is meant to convey a sense of progress, innovation, growth. For many people, this will be their first smart phone and we want it to feel like an exciting milestone...a moment that represents personal progress and opportunity...a device that will impact their lives in a positive way and point toward continued growth in the future. Blaze Your Own Path tells operators and manufacturers that they can have more control and say than they do with other operating systems, like Android or iOS. As we say on our partner site, "to manage, customize and improve relationships with their customers." Be the Future is about being on the cutting of a new way forward in apps and operating systems, about defining how this new landscape will look and paving the way for the next generation.
Though I'm not the assignee, I guess we can start the discussion with these: * "Look Ahead" Κοιτάξτε μπροστά * "Be the Future" Φτιάξτε το δικό σας μέλλον * "Blaze Your Own Path" (industry audience) Φωτίστε το δικό σας μονοπάτι
Hi George, don't worry about the assignee (it's the automatic one for the Bugzilla component) and let's kick the discussion off :-) Another question: is it OK for your locale if the message is transposed to uppercase?
(In reply to Francesco Lodolo [:flod] from comment #3) > Another question: is it OK for your locale if the message is transposed to > uppercase? The only browser that can handle decently text-transform:uppercase (if that's what you mean) for my locale is Firefox. I believe that we want maximum visibility for those slogans so I think it is NOT OK.
Hi George, I am almost sure that the relevant text (slogans) will be embedded in a graphic so no need for a text transform. Francesco should know more about it though! Reagarding the strings here are my versions (1st string is the same): * "Look Ahead" Κοιτάξτε μπροστά * "Be the Future" Αλλάξτε το μέλλον * "Blaze Your Own Path" (industry audience) Χαράξτε τη δική σας πορεία
(In reply to George Fiotakis from comment #4) > The only browser that can handle decently text-transform:uppercase (if > that's what you mean) for my locale is Firefox. No, I meant if it could be awkward to see all-caps messages. These will be graphic assets, so no problem here, but we'll have to keep it in mind for the web parts.
I'm transferring the discussion to our mailing list so that more people can contribute. How much time do we have for this?
(In reply to George Fiotakis from comment #7) > How much time do we have for this? I hope to get an answer in the next days ;-)
For reference, this translation is currently used in tabzilla.lang ;Look ahead Δείτε το μέλλον
(In reply to George Fiotakis from comment #7) > I'm transferring the discussion to our mailing list so that more people can > contribute. > How much time do we have for this? I'd love our visual team to be able to start working on graphics next week, would that be possible for you guys to finish these translations by then?
Pascal, we will definitely have these finished by next week and even earlier! Thanks Francesco, I sent exactly the same thing yesterday to George and I'm waiting for his reply if we could use the same or we should change the one used for slogans. Any suggestions would be appreciated though!
After a long enough discussion in our list, I think it's time to close this. For reference, we decided that since those strings are going to be used in graphics (I guess something like https://secure.flickr.com/photos/mozillaeu/9259323707/in/set-72157634593759364) it's better to use something more catchy for marketing reasons. If however we need consistency with tabzilla, it would be better to keep the catchy phrase instead of the one we have now, yet we'll turn it to plural. * "Look Ahead" "Κοίτα μπροστά" All caps version: "ΚΟΙΤΑ ΜΠΡΟΣΤΑ" * "Be the Future" "Φτιάξε το μέλλον" All caps version: "ΦΤΙΑΞΕ ΤΟ ΜΕΛΛΟΝ" * "Blaze Your Own Path" "Χαράξτε τη δική σας πορεία" All caps version: "ΧΑΡΑΞΤΕ ΤΗ ΔΙΚΗ ΣΑΣ ΠΟΡΕΙΑ"
Thanks all! George, you beat me to it by a few minutes, but I was just about to share http://www.flickr.com/photos/mozillaeu/sets/72157634593759364/ as an example of how the all-caps treatment works. That's definitely how we'd use these phrases in marketing (not for billboards, necessarily, but something in that style). Since these are marketing headlines, it's important that they convey the original meaning, but also that they do so in a way that feels catchy and engaging. Pardon my ignorance here, but what's the process for vetting these for final use? Really appreciate the great work here.
If by "vetting for final use" you mean the process we used as a team, we simply discussed about it, propose a few ideas and amendments and came up with these. If you mean how can you be sure that those are the final strings, I guess I have to mark the bug fixed :)
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Hi all. Thanks so much for the work here. To help us understand the lines a little better, could someone provide a brief explanation of each one that talks about any cultural implications or wordplay that may be involved? We'd love to know how these will sound to a native speaker, what the tone is, whether they're formal or colloquial, etc. Any insights you could provide would be greatly appreciated.
Hi Matej, excuse me for the late reply, I'm having huge problems with my ISP lately. There's not any wordplay or cultural implications for any of those slogans. The first two are more colloquial since they are addressed to users/programmers and we used singular instead of plural (it's not clear in english, but in our language we have to choose one). "Κοίτα μπροστά" is a word-by-word translation from "look ahead" -one of the few times it works. "Φτιάξε το μέλλον" can be translated as "Make (or build) the future" - the english phrase can not be translated in Greek, you simply can not "be" the future in our language, it would sound pretty bad even if you consider it a wordplay. "Χαράξτε τη δική σας πορεία" can be translated as "set your own course". It's what navigators usually do for ship courses and as a metaphor it's widely used in our language. We have used plural for this one since it's not addressed to individuals and has to be more formal. Though the english phrase can be translated word-by-word in our language (if we translate "blaze" as "enlight"), it would sound like a reference to a latin-american leftist guerrilla group :) .
Thanks George. That's very helpful. I really appreciate the insights.
You need to log in before you can comment on or make changes to this bug.