Should we create language layers?

[zvi]

I know that DW is not going to supply language layers for users or its clones and children. But I've written one layout and adapted another one which had some user facing text. For both of those, following the current style guidelines, I just put the English text in the layout layer. But, I've been thinking about it a little more, and I am increasingly convinced that's the wrong move for two reasons.

(1) If those bits of text are properties in an i18n layer, then they can be changed in the wizard. Yay, customization for DW users!

(2) If a primarily non-English clone site picks up the style, they will be able to make the adjustment quickly, instead of digging deep into the CSS or HTML, looking for where the text string appears.

I can't figure out a compelling reason not to move these text strings out of the layout layer and into an i18n layer. Can someone point out the drawbacks to me?

Comments

[janinedog]

Well, you could still define them as properties in the layout layer (and probably should), so they could be changed in the wizard. As for the rest of it, I have no opinion really. :)

[mark]

I can't think of any reasons not to do it. Even though we aren't translating the site, we still spend the time to internationalize it so that it can be localized by people who want to take the code.

Specifically for dw-free styles, I'd say that moving the text to an i18n layer is a good use of time that, even if it doesn't help DW specifically, will help people who use the code.