<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>El 09/07/16 a las 10:10, Caryl Bigenho escribió:<br>
</p>
<blockquote cite="mid:BLU407-EAS96955E1443AFC62E11B7ECCC3D0@phx.gbl"
type="cite">
<div>We may be able to get an easy entry point by executing the
translation of Sugar to Cherokee and/or Navajo. [3] <br>
<br>
<div class="gmail_extra">[3] <span dir="ltr" id=":3al"><a
moz-do-not-send="true"
href="http://www.bbc.com/future/story/20140606-why-we-must-save-dying-languages"><a class="moz-txt-link-freetext" href="http://www.bbc.com/future/story/20140606-why-we-must-save-dying-languages">http://www.bbc.com/future/story/20140606-why-we-must-save-dying-languages</a></a></span><br>
</div>
</div>
</blockquote>
<br>
While Laura proposed to prioritize these in the context of promoting
Sugar on the broader US community, I offer that the experience of
localizing Sugar for these groups is a goal in itself, as a learning
experience for further work. As the article explains, there is <i>wisdom</i>
<i>embedded </i>in the words of the languages <i></i>of peoples
who have lived in these territories for thousands of years. This is
part of humanity's legacy and should not be lost.<br>
<br>
I do believe the mere possibility fluency in technology and properly
appropriable informatics has the power to empower native cultures to
better cope with modernity and even assume leadership in it.<br>
<br>
Perhaps we can learn from them how to exist under a dominant culture
(proprietary software).<br>
The dominant culture has everyone engulfed in a <i>dreamspell</i>
that makes it hard to see what is important.<br>
<br>
That said, for sure, Sugarizer should be part of what gets
translated when we discuss translating Sugar.<br>
<br>
Does anyone in these lists have contact with native north-american
people? Have we heard from the Mexican language efforts? I would
ping some contacts for US based natives if there could be support
for achieving this.<br>
<br>
Regards,<br>
Sebastian<br>
<br>
PS: do read, if you can, the linked article it is quite enlightening<br>
</body>
</html>