Yes, that's what I meant. I'll give it a try later this week. On Feb 17, 2010, at 4:04 PM, P T Withington wrote:
> On 2010-02-16, at 19:52, Raju Bitter wrote: > >> I haven't tested if it works to compile a LZO referencing a CSS for >> different languages. Someone would have to try that, do you think that will >> work, Tucker? > > Not sure exactly what you are asking here. > > In the model you gave, your build process is modifying the source for each > target language and (re-)compiling. Since an LZO is essentially opaque, you > can't follow that same model. Ideally, we'd like to have fully dynamic CSS > that you could reload at runtime. This would let you change language on the > fly. I don't see that happening right away, but what you _should_ be able to > do today is create a library containing the stylesheet for each language you > plan to support, compile that library as a dynamic <import>, and arrange for > your server to deliver the correct language-style-import when your app is > loaded. (I've not tested this. If someone want to try, please do. We do > have a goal of greatly improving the CSS support in OL 5, so I'd like to > pursue this as a step toward runtime-loadable CSS styles.)
