<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/02/2015 10:07 AM, Dan Wilcox
wrote:<br>
</div>
<blockquote
cite="mid:2A6C60EC-77D2-4FCB-8666-B73E776316A9@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
What probably makes sense in the long run is for objects to have
two names: internal name (aka current english name) and a display
name (translated). I think that’s how <a moz-do-not-send="true"
href="https://scratch.mit.edu" class="">Scratch</a> does it, as
all of their building blocks are translated in other languages
too. We sat down with one of my German nephews and showed him
scratch. The UI was in German *and* the objects were all in German
too, which worked really nicely.<br class="">
</blockquote>
<br>
Yes, I'm curious how much of a pain point it is for users like him.
I can think of two general categories:<br>
1) people who don't speak English whose main language has an
alphabet that's a superset of the English alphabet<br>
2) people who don't speak English and read a separate alphabet than
the English one<br>
<br>
So if anyone else has user stories that fit one of those categories,
I'd like to hear about them.<br>
<br>
-Jonathan<br>
<br>
<blockquote
cite="mid:2A6C60EC-77D2-4FCB-8666-B73E776316A9@gmail.com"
type="cite">
<div class="">
--------<br class="">
Dan Wilcox<br class="">
@danomatika<br class="">
<a moz-do-not-send="true" href="http://danomatika.com" class="">danomatika.com</a><br
class="">
<div class=""><a moz-do-not-send="true"
href="http://robotcowboy.com" class="">robotcowboy.com</a></div>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>