Dear Jatin, Welcome to the Sugar Labs community, When reworking ASLO (a very valuable project), please do keep internationalization (i18n) and localization (L10n) in mind. You may or may not know that we do host PO files for L10n of NewASLO on our Pootle translation server:
https://translate.sugarlabs.org/projects/NewAslo/ We currently have very complete coverage in the following languages: Swedish, Spanish, Russian, Guaraní (Paraguay), English (United Kingdom), English, Dutch, Danish, Catalan, Albanian, Igbo. Obviously the fewer un-necessary UI string changes, the better we will be in terms of localizing the new product of your work, The Translation Team will obviously take care of any strings that must be changed to produce a better ASLO, but changes for the sake of changes can hopefully be avoided if the existing strings serve the intended purpose. Having the Spanish translation complete in a production instance is probably more important than any other language given the number of Spanish-speaking users we typically want to reach, but as FOSS, if you're going to accommodate more than one language, you might as well make it easy for all of them. When you get ready to go-live with the new ASLO service, we'd obviously love to have the chance (a week or two of string freeze) to catch up with your work and make sure what gets deployed reaches our key audiences in their native language(s). Laura Vargas would be a fine guide to i18n/L10n practices in Sugar Labs, but if you have any questions, feel free to reach out to me and I'll try to help, I'll probably be the one to contact about grabbing a new POT template from your repository and uploading it to Pootle for the localizers to work on, as well as generating the pull request when they have completed their work on the specific language's PO file. Looking forward to seeing your work blossom. cjl On Thu, May 18, 2017 at 3:37 AM, Jatin Dhankhar <dhankhar.ja...@gmail.com> wrote: > Hi, > Thank you Laura for attaching the proposal. > I will be glad if you can point me in the right direction regarding my GSOC > project, suggest flaws and how it can be improved. If anyone has any > questions or speculations, feel free to ping me. I am also writing weekly > summary of GSOC here https://jatindhankhar.in/posts/. > If something is missing or incorrect, let me know. > > Thanks, > Jatin Dhakhar > > On Thu, May 18, 2017 at 9:10 AM, Laura Vargas <la...@co.sugarlabs.org> > wrote: >> >> >> Hi Jatin welcome to Sugar Labs Community! >> >> Hi Aleksey, >> >> I hope to find time to be able to follow Jatin's project proposed time >> line. I hope you can find some time too. See pdf attached for project's >> details. >> >> Regards and blessings to all the team, >> >> >> Laura Victoria >> >> >> >> >> ---------- Forwarded message ---------- >> From: Tony Anderson <tony_ander...@usa.net> >> Date: 2017-05-17 18:57 GMT-05:00 >> Subject: Re: [Sugar-devel] New ASLO Project Definition >> To: Laura Vargas <la...@somosazucar.org> >> >> >> Hi, Laura >> >> Done. >> >> Tony >> >> >> On 05/18/2017 12:56 AM, Laura Vargas wrote: >> >> Samuel and new ASLO team, >> >> Can you please attach the pdf with the project description? >> >> In my opinion, as ASLO is such a powerful resource used today by active >> deployments, a successful successor will provide at least the same services. >> >> Regards >> >> Laura V. >> I&D SomosAZUCAR.Org >> >> “Solo la tecnología libre nos hará libres.” >> ~ Laura Victoria >> >> Happy Learning! >> #LearningByDoing >> #Projects4good >> #IDesignATSugarLabs >> #WeCanDoBetter >> >> >> _______________________________________________ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> > > > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > IAEP@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
