[Sugar-devel] Handling of localization in Sugarizer/MusicBlocks
lionel.laske at gmail.com
Wed May 19 15:37:36 EDT 2021
Okay. Tell me once you're done.
Le mer. 19 mai 2021 à 00:47, Walter Bender <walter.bender at gmail.com> a
> I have been disappointed by webL10n from Day One. I have a bunch of
> supporting scripts but it is not very expressive and as you note,
> having a huge ini file is not optimal, I was planning to explore
> options this summer as part of Music Blocks 4.0. But had not started
> researching yet.
> On Sun, May 16, 2021 at 4:08 PM Lionel Laské <lionel.laske at gmail.com>
> > Hi all,
> > From the beginning, Sugarizer relies on the webL10n library  to
> > This library uses a .INI file where localizations are stored and loaded
> during page initialization.
> > Sounds like MusicBlocks use the same library too.
> > I'm thinking to change localization library in a future version of
> Sugarizer because:
> > webL10n has been deprecated since 2015
> > a pivot file format (PO Gettext) is used to be able to localize strings
> in the Sugarizer translate platform . It made the update process complex
> (INI to PO then PO to INI).
> > all language localizations are located in a huge file (260kb) that is
> not good for performance reasons.
> > I've done a short study here  to test another localization library
> i18next .
> and easy to use.
> > So I'm thinking to switch to i18next.
> > Is there any plan to change the localization library in MusicBlocks?
> > Do you experience another localization library?
> > Regards.
> > Lionel
> >  https://github.com/fabi1cazenave/webL10n
> >  https://translate.sugarizer.org
> >  https://github.com/llaske/l10nstudy
> >  https://github.com/i18next/i18next
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> Walter Bender
> Sugar Labs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel