Andrew Arensburger wrote:
On Wed, Oct 09, 2002 at 09:59:48PM +1000, Roger Buck wrote:
I now vote for:
<serverroot>/<theme>/<lang>/ ./style/ ./*.css
./catalogue/ ./*.html ./*.tmpl
./members/ ./*.html ./*.tmpl
./images/
... and so on at discretion of theme author....
I think that Dorian suggested that some time ago.
Does that make sense?
Mostly, except for the location of *.css files. (I confess that I'm almost entirely ignorant about CSS, so I'll ask you to put up with naive questions, and to enlighten me when I'm wrong.)
You're right, but you're wrong...
As I understand it, stylesheets specify colors, fonts, and all of those little presentation details. In particular, AIUI, stylesheets do not specify content. So why would the *.css files go in <theme>/<lang>? How are the French link colors different from the Italian or German colors?
You're right, here...
Okay, so the Japanese and Cherokee versions of the web page will obviously use different fonts. But most everything else will be identical across languages, right? Perhaps there should be theme-wide CSS and a separate per-language CSS?
you're wrong here : we can't embeed 2 style sheets in the same html page (not sure of this!) you're wrong too because you can link "pictures" (mostly backgrounds or buttons) in css, and you may need them in differents sizes depending on the language.
I'm mainly concerned with duplication ("Pragmatic Programmer" tip #11: Don't Repeat Yourself). If default/en/style/foo.css and default/jp/style/foo.css are separate, and need to be kept in sync, they _will_ drift apart. The same thing applies to language-specific templates.
You're right there. Thus, 2 points + and 1 point -. Not sure of the best decision. Maybe a question for our next irc meeting ? -- Paul