← Back to team overview

ubiquity-slideshow team mailing list archive

Re: UbiquitySlideshow specification Wiki page shock and horror

 

Thanks for the message :)

"Continuing on that, how do you propose we handle sourcing translated
html files, when they exist?  It should fall back to the html files
for the C locale in the event of only some of the pages being
translated."

The current (mostly unimplemented and horrible) approach is merging slides (C locale) and slides.$LANG into one temporary directory, then playing from there. Of course, in a live cd that happens to waste memory for no good reason, but it should work.

I had tinkered with the build script creating a skeleton of symlinks for all the files for localized slides directories, pointing back to the base one.

In essence: Big hole there for something clever :)

The newest version of lp:ubiquity-slideshow has a thinner top border (thanks, H S!), and Slideshow.html was renamed to the less case-sensitivity-troubled index.html. The new border is hopefully a bit easier on the eye and allows considerably more room for illustrations, if it is necessary.

Localizable text around illustrations is meant to exist via alt text attributes. Presently they are useless, but some Javascript should make them more useful!

Interesting tning with the illustrations: they are not ever scaled. Text is at full size (7px). Thus the multiple illustrations are necessary to fit unscaled, solid looking information in (by breaking the important chunks apart, ideally in some kind of order). I don't think we could manage that for a single bigger one, but I can see the appeal of keeping things simple that way. Perhaps I'm missing something, of course!

Having said that, one or two wider ones could be used on occasion even within the current layout and the stylesheet would get them spaced evenly.


Thanks,

Dylan



Follow ups