L10n:WorldReady/Top10: Difference between revisions

Jump to navigation Jump to search

L10n:WorldReady/Top10 (view source)

Revision as of 09:50, 2 September 2011

1,094 bytes added ,  2 September 2011
no edit summary
No edit summary
No edit summary
Line 5: Line 5:
</p><p>These are the kinds of specific example that have been problematic in product naming and consistent messaging in the past.
</p><p>These are the kinds of specific example that have been problematic in product naming and consistent messaging in the past.
</p>
</p>
<pre class="_fck_mw_lspace"> personas -&gt; directly translates into some languages as "people", drawing confusion when the feature is about visual changes to the chrome.
<pre class="_fck_mw_lspace"> personas -&gt; directly translates into some languages as "people",
drawing confusion when the feature is about visual changes to the chrome.
</pre>
</pre>
<pre class="_fck_mw_lspace"> workspace -&gt; scratchpad  --&gt; tools | scratchpad
<pre class="_fck_mw_lspace"> workspace -&gt; scratchpad  --&gt; tools | scratchpad
</pre>
</pre>
<pre class="_fck_mw_lspace"> sumo site design -- selection of site theme/style
<pre class="_fck_mw_lspace">sumo site design -- selection of site theme/style US - friendly and approachable v. international  
US - friendly and approachable v. international preference for more formal and concise
preference for more formal and concise. Nurse and cat have pornographic connotations in some Asian
Nurse and cat have pornographic connotations in some Asian markets (Try google search for "Asian Nurse" or Nurse Cat Japan)
markets (Try google search for "Asian Nurse" or Nurse Cat Japan)
In this case SUMO design has been made flexible to remove the image.  JA is using this. See: http://support.mozilla.com/ja/home
 
Maybe this design is more suitable for locales where a more formal approach is desirable. Supporting possible multiple designs  
In this case SUMO design has been made flexible to remove the image.  JA is using this. See:  
  for sumo might have been, or still might be possible, but expensive.   In this way we might have constructed a "friendly design"  
http://support.mozilla.com/ja/home. Maybe this design is more suitable for locales where a more
and a "formal/concise  design" and each locale could opt in to the design best suited to the locale.
formal approach is desirable. Supporting possible multiple designs  for sumo might have been, or
still might be possible, but expensive.In this way we might have constructed a "friendly design"
and a "formal/concise  design" and each locale could opt in to the design best suited to the locale.
</pre>
</pre>
<h2> 2. Note Where Adapted Content is Desirable </h2>
<h2> 2. Note Where Adapted Content is Desirable </h2>
<p>Where we want names and concepts to be adapted to a locale, state those things up front.  Write content and concepts of campaigns in Basic English first, or just share more of these early planing designs flexible global outreach (message needs follow generally, but then tuned for specific locales)
<p>Where we want names and concepts to be adapted to a locale, state those things up front.  Write content and concepts of campaigns in Basic English first, or just share more of these early planing designs flexible global outreach (message needs follow generally, but then tuned for specific locales)
</p>
</p>
<pre class="_fck_mw_lspace">       Requires additional work by development/creative lead to explain intent of the campaign and were local flexibility is desired.
<pre class="_fck_mw_lspace">Requires additional work by development/creative lead to explain intent of the campaign and  
        Then localize it to en-US and or to be hip or trendy.   
where local flexibility is desired. Then localize it to en-US and or to be hip or trendy.   
        Maybe some some kind of "markup language" can be used to express both the intent and the implementation
Maybe some some kind of "markup language" can be used to express both the intent and the  
        (experiment proposed by pfinch and stas; see [1] and [2])
implementation (experiment proposed by pfinch and stas; see [1] and [2])
</pre>
</pre>
<h2> 3. Avoid slang, trendy catch phrases </h2>
<h2> 3. Avoid slang, trendy catch phrases </h2>
Line 32: Line 35:
<pre class="_fck_mw_lspace"> "webify me" vs. what!???
<pre class="_fck_mw_lspace"> "webify me" vs. what!???
</pre>
</pre>
<pre class="_fck_mw_lspace"> Awesome ---  http://matejnovak.com/2011/05/10/owning-awesome/
<pre class="_fck_mw_lspace">Awesome ---  http://matejnovak.com/2011/05/10/owning-awesome/
Awe actually meant “terror” or “dread” until the late 1700s, from which point on it retained only the slightly softer meaning of  
Awe actually meant “terror” or “dread” until the late 1700s, from which point on it retained only  
“reverential fear or wonder” (all definitions from the Shorter Oxford English Dictionary).  Awesome came along in the late 16th century  
the slightly softer meaning of “reverential fear or wonder” (all definitions from the Shorter  
  meaning “filled with awe” and then “inspiring awe” about a century later, both of which are still in use today. The positive
Oxford English Dictionary).  Awesome came along in the late 16th century  meaning “filled with  
colloquialism meaning “outstanding, remarkable” didn’t come along until the mid 20th century (interestingly enough, that came after the  
awe” and then “inspiring awe” about a century later, both of which are still in use today. The  
  adverb form, awesomely, began to mean “outstanding, very” in the late 19th century). All that brings us to today and the late 1900s slang  
positive colloquialism meaning “outstanding, remarkable” didn’t come along until the mid 20th  
meaning of “excellent” or “marvelous.”
century (interestingly enough, that came after the  adverb form, awesomely, began to mean  
  or  "scary cool..."
“outstanding, very” in the late 19th century). All that brings us to today and the late 1900s
slang meaning of “excellent”, “marvelous” or "scary cool..."
</pre>
</pre>
<pre class="_fck_mw_lspace"> Awesome --- the fall-out (http://vitosmo.tumblr.com/post/5609441897/be-awesome-says-what)
<pre class="_fck_mw_lspace">Awesome --- the fall-out (http://vitosmo.tumblr.com/post/5609441897/be-awesome-says-what)
On the SuMo homepage (https://support.mozilla.com/en-US/home) there’s an invitation to “Be Awesome”...  
On the SuMo homepage (https://support.mozilla.com/en-US/home) there’s an invitation to “Be Awesome”...  
Limiting the back-translation of the term to languages (*).. yields the following picture:
Limiting the back-translation of the term to languages (*).. yields the following picture:
Line 56: Line 60:
</p>
</p>
<h2> 4. Define Terms </h2>
<h2> 4. Define Terms </h2>
<p>Define use of nouns, verbs and adjectives when there are used in the design or copy
<p>Define use of nouns, verbs and adjectives when there are used in the design or copy. State clearly, what the trade marks, proper names, untranslatables are. Avoidf situations like [http://groups.google.com/group/mozilla.dev.l10n.web/browse_thread/thread/252750c5710f3dab this one - (scroll down the first few messages)]:
</p>
</p>
<pre class="_fck_mw_lspace">
While we were discussing about how to translate "Mozilla Marketplace" in Spanish, we found out
that the word "Bazar" it a really good one to avoid the bad connotations  of market (markets)
or store (very commercial oriented). Maybe Bazaar is a good one for English too. Also Bazaar
is pronounced really similar in a lot of languages. How are you translating "Marketplace"
in other locales? </pre>
<p>
This kind of a discussion should be done '''before''' and not''' after''' the fact...
</p>
<h2> 5. Allow Enough Space for Text </h2>
<h2> 5. Allow Enough Space for Text </h2>
<p>Please consider the length of copy and character limitation when creating designs.  For instance, it might take a Latin language 30 characters to express a 15 character English string.  Historically, we've run into this issue with Affiliate buttons where space is severely constrained.
<p>Please consider the length of copy and character limitation when creating designs.  For instance, it might take a Latin language 30 characters to express a 15 character English string.  Historically, we've run into this issue with Affiliate buttons where space is severely constrained.
Line 68: Line 82:
</p>
</p>
<h2> 8. Stay in touch </h2>
<h2> 8. Stay in touch </h2>
<p>Building on the above, host regular calls to provide help and make everyone a part of the process. Maybe even hold the occasional workshop in specific locales.
<p>Building on the above, host regular calls to provide help and make everyone a part of the process. Maybe even hold the occasional workshop in specific locales.
</p>
<p>Note that the median localizers-per-language count is probably one, maximum two (sg): there will always be more Mozilla products, sites and projects in need of localization than persons ready to do the job. So treat your localizers right: what they will appreciate more than a t-shirt you are thinking of sending out, is the warm glow of your attention and appreciation.
</p>
</p>
<h2> 9. Be available </h2>
<h2> 9. Be available </h2>
Smo
Confirmed users
209

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/346035"

Navigation menu