> There's a lot of images in there, total output is 11MB: is this a > blocker?
Only if the images are necessary. Usually in Sage documentation we keep the function calls in, but let the images be generated by the user when they go through the documentation, if I recall correctly. So it would just be text that would be added. > Another issue is we need each cell to depend on the output of the > previous one. And many of the cells would have to be skipped, for > different reasons. That is easy to do. Most Sage documentation has things depending on previous input - see also for example William's NT book in the doc - and skipping cells is as easy as # not tested, I would imagine. > Getting a referee to do a formal review is more of an issue. Yes, that is true; but it could be one of your colleagues, or perhaps a group of them if you feel like it, that does the language part of the review. > > One thing OS projects are unfortunately not as > > good at is finding resources for translation, in any given direction. > > I have traslated some sections, and reviewed some sections of the > traslation: the spanish translation of the tutorial is progressing I don't even know that I would bother with the tutorial, as it is mostly for people who already know a fair amount of programming and CAS. -- You received this message because you are subscribed to the Google Groups "sage-edu" group. To post to this group, send email to sage-edu@googlegroups.com. To unsubscribe from this group, send email to sage-edu+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-edu?hl=en.
