Thanks @Pike,
I don’t meant they should translate the css words, but stuff within the content.
With dtd’s its a no brainer, its just an entity, I use it extensively to localize content. My translators on babelzilla dont even know they are translating for CSS, (which I think is appropritae, translators shouldnt worry about worry about the technicalities of usage).
Here is where I use dtd loclization in my production code:
You’l see in this section of style:
.stalled a.act-toggle:not(.active-me):hover:after
But it will have only content in its block body. Thats because the rest of the style is in the .css file with the same .stalled a.act-toggle:not(.active-me):hover:after, so I just “overload/plugin” (I guess you can say) the same selector the same selector but just with content.
I have found no other way to localize the CSS. Never needed to, this way was so easy.
I agree your mentioned workaround is very difficult, and maintaining it is a scary though, this dtd method here is a breeze. Whatever we move to, we should have an equally easy, if not easier method for localizing the content values in css.