<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> As a Sugar activity, I don't think Sugar itself will be impacted. The name comes from a technical problem. I started with L10n.activity but the activity registration rejected it. I changed the name to remove the numbers and it was accepted. As I understand it lion is an accepted icon for L10n. I think instructions can be added as help in the activity or as 'tutorial' information on the server. At the moment the activity does itself support localization or help. I'll try to get it working then we can start on 'to-dos'. Tony <div class="moz-cite-prefix">On 04/23/2016 03:37 AM, Sebastian Silva wrote: </div> <blockquote cite="mid:571A7D87.8090007@fuentelibre.org" type="cite"> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> El 20/04/16 a las 22:28, Tony Anderson escribió: <blockquote cite="mid:571848D8.90505@usa.net" type="cite"> </blockquote> Really the discussion is lost in personal archives if not copying at least one mailing list. So I'm bringing sugar-devel back. <blockquote cite="mid:571848D8.90505@usa.net" type="cite">In version 1, I would not expect to incorporate Virtaal. Activities are open-ended so this and anything else can be added. Since the intent is for this activity to be used by learners, we need to hide the technicalities as much as possible and expose the simplest interface to accomplish the task. </blockquote> I agree with both. I stumbled on <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/User:CScott#Desiderata_for_9.1.0">http://wiki.laptop.org/go/User:CScott#Desiderata_for_9.1.0</a> which is a statement of design goals for Sugar before the new versioning scheme was applied, by a person inside the OLPC team. There are many interesting bits but one touching this subject says: <meta http-equiv="content-type" content="text/html; charset=utf-8"> <span style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12.7px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 19.05px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);">"Translation improvements <ul style="line-height: 19.05px; list-style-type: disc; margin: 0.3em 0px 0px 1.5em; padding: 0px; list-style-image: url("bullet.gif"); color: rgb(0, 0, 0); font-family: Arial, sans-serif; font-size: 12.7px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"> <li style="margin-bottom: 0.1em;">"multiple languages, multiple places": translation system should look in local, then activity, then system translation tables, then repeat for each in a set of fallback languages (eg, quechua, spanish, english)</li> <li style="margin-bottom: 0.1em;">separable translation packs</li> <li style="margin-bottom: 0.1em;">"click-to-translate": wiki-like editing of translatable labels in the UI"</li> </ul> So another idea is to propose it as a Sugar feature. I fear it would involve design consensus which is hard from experience. I like Tony's simplistic design (except the clever name). Developing it, it would be smart to use Virtaal's library. It should save some work and ensure compliance with standards. <blockquote cite="mid:571848D8.90505@usa.net" type="cite">The basic server capability is already available. Essentially, the school server keeps an 'repository' of the activities in ASLO. A selected activity can be downloaded and installed on demand. With the exception of a priviliged 8 activities, an activity can also be erased to free space on the local store. </blockquote> The workflow should include a simple way or instructions to submit updated .po files upstream, the basis for inclusion in new releases. <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>