Emle looks interesting. Library bundles have a library.info file with metadata and a section for each language; you can have a separate index page for each language, which is chosen according to the interface language you have set in Sugar.
Your js pages are effective, but they break "view source" a bit; you might consider adding a link that shows the effective source of the page being viewed. SJ On Mon, Jun 2, 2008 at 6:07 PM, C.W. Holeman II <[EMAIL PROTECTED]> wrote: > How is language handled in OLPC? Currently with Emle the user selects > a language before being given an index of pages in the specified language. > > http://emle.sourceforge.net/emle020400/index.html > > See also: > > http://emle.sourceforge.net/index.shtml > http://wiki.laptop.org/go/User:Cwhii > > Emle has a lang directory which contains the language specific message > files. > The index.hmtl page examines the lang directory to determine which > languages > are supported then displays this list for the user to select from. How does > this correspond to the structure expected by OLPC for content bundles? > > -- > C.W.Holeman II | [EMAIL PROTECTED] | http://JulianLocals.com/cwhii > To only a fraction of the human race does God give the privilege of > earning one's bread doing what one would have gladly pursued free, for > passion. I am very thankful. The Mythical Man-Month Epilogue/F.P.Brooks > _______________________________________________ > Library mailing list > [email protected] > http://lists.laptop.org/listinfo/library >
_______________________________________________ Library mailing list [email protected] http://lists.laptop.org/listinfo/library
